From: "Luck, Tony" <tony.luck@intel.com>
To: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
CC: "sfr@canb.auug.org.au" <sfr@canb.auug.org.au>,
       "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
       LKML <linux-kernel@vger.kernel.org>,
       "linux-ia64@vger.kernel.org" <linux-ia64@vger.kernel.org>
Date: Tue, 9 Dec 2008 10:50:56 -0800
Subject: RE: next-20081104 - kernel panic on ia64 box, at
	__mutex_lock_interruptible_slowpath
Thread-Topic: next-20081104 - kernel panic on ia64 box, at
	__mutex_lock_interruptible_slowpath
Thread-Index: AclZzQOPncGz+fh6TEGiZ1760e+B5AAYdB/A
Message-ID: <57C9024A16AD2D4C97DC78E552063EA35C7EEAA3@orsmsx505.amr.corp.intel.com>
References: <20081204200745.eff0ac87.sfr@canb.auug.org.au>
 <20081209070730.GA12102@linux.vnet.ibm.com>
In-Reply-To: <20081209070730.GA12102@linux.vnet.ibm.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7BIT
MIME-Version: 1.0
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 532
Lines: 12

>       next-20081204 kernel panic's, while booting up on ia64 box. This panic
> was not reproducible with the latest next-20081208 kernel.

I saw that too ... it was preceeded by an "impossible" WARN_ON message,
so I put it down to some experimental/untested code in linux-next.

-Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/