linux-kernel - RE: next-20081104 - kernel panic on ia64 box, at __mutex_lock_interruptible

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <57C9024A16AD2D4C97DC78E552063EA35C7EEAA3@orsmsx505.amr.corp.intel.com>
Date:	Tue, 9 Dec 2008 10:50:56 -0800
From:	"Luck, Tony" <tony.luck@...el.com>
To:	Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>
CC:	"sfr@...b.auug.org.au" <sfr@...b.auug.org.au>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	"linux-ia64@...r.kernel.org" <linux-ia64@...r.kernel.org>
Subject: RE: next-20081104 - kernel panic on ia64 box, at
	__mutex_lock_interruptible_slowpath

>       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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/