[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4A8E9B63.4090400@sgi.com>
Date: Fri, 21 Aug 2009 15:04:35 +0200
From: Jes Sorensen <jes@....com>
To: Ingo Molnar <mingo@...e.hu>
CC: Jens Axboe <jens.axboe@...cle.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>, Yinghai Lu <yinghai@...nel.org>,
linux-kernel <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...hat.com>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: Latest Linus tree oopses on Nehalem box
On 08/21/2009 01:46 PM, Ingo Molnar wrote:
> Might be useful to see your full crashlog, if you are allowed to
> post that, plus your kernel .config would be useful to know too.
> Plus would be useful to know whether this is a regression relative
> to .30 or a yet unfixed bug triggering on your class of hardware.
Hi again,
It looks like this is either timing related or a false alarm :(
I saved the .config reverted to an older commit, and then tried to go
back, and now the thing will suddenly boot.
I'll try to see if I can reproduce it, if I manage, I shall be happy to
post the .config and the full boot log. It's a Supermicro motherboard of
some sort:
Supermicro X8DTN+
AMIBIOS Core Ver:08.00.15
There is nothing special about it, but I know the BIOS is utter junk.
Sorry for the noise.
Cheers,
Jes
--
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/
Powered by blists - more mailing lists