public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Jes Sorensen <jes@sgi.com>
Cc: Jens Axboe <jens.axboe@oracle.com>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>, Yinghai Lu <yinghai@kernel.org>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@redhat.com>,
	Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Latest Linus tree oopses on Nehalem box
Date: Fri, 21 Aug 2009 15:26:58 +0200	[thread overview]
Message-ID: <20090821132658.GD10263@elte.hu> (raw)
In-Reply-To: <4A8E9B63.4090400@sgi.com>


* Jes Sorensen <jes@sgi.com> wrote:

> 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.

I'd say it's timing related and still unfixed - crashes that deep in 
the scheduler we'd sure know about, had we fixed such in any recent 
kernels. Do you still have the last 10 lines of the bootup leading 
up to the crash?

	Ingo

  reply	other threads:[~2009-08-21 13:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-21 10:53 Latest Linus tree oopses on Nehalem box Jes Sorensen
2009-08-21 11:46 ` Ingo Molnar
2009-08-21 11:58   ` Peter Zijlstra
2009-08-21 14:42     ` [tip:sched/core] sched: Avoid division by zero tip-bot for Peter Zijlstra
2009-08-25 19:11       ` Peter Zijlstra
2009-08-26  9:16         ` Yinghai Lu
2009-08-26  9:25           ` Peter Zijlstra
2009-08-27 11:08           ` [PATCH] sched: Avoid division by zero - really Peter Zijlstra
2009-08-27 12:19             ` Eric Dumazet
2009-08-27 12:32               ` Peter Zijlstra
2009-08-28  6:30             ` [tip:sched/core] sched: Fix " tip-bot for Peter Zijlstra
2009-08-21 13:04   ` Latest Linus tree oopses on Nehalem box Jes Sorensen
2009-08-21 13:26     ` Ingo Molnar [this message]
2009-08-21 13:35       ` Jes Sorensen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090821132658.GD10263@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=hpa@zytor.com \
    --cc=jens.axboe@oracle.com \
    --cc=jes@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=yinghai@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox