From: John Stultz <john.stultz@linaro.org>
To: Stefan Bader <stefan.bader@canonical.com>
Cc: NeilBrown <neilb@suse.de>,
Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
Sander Eikelenboom <linux@eikelenboom.it>,
rjw@sisk.pl, Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: Regression: ONE CPU fails bootup at Re: [3.2.0-RC7] BUG: unable to handle kernel NULL pointer dereference at 0000000000000598 1.478005] IP: [<ffffffff8107a6c4>] queue_work_on+0x4/0x30
Date: Wed, 04 Jan 2012 10:35:32 -0800 [thread overview]
Message-ID: <1325702132.3037.100.camel@work-vm> (raw)
In-Reply-To: <4F04452C.7020209@canonical.com>
On Wed, 2012-01-04 at 13:25 +0100, Stefan Bader wrote:
> Which may point to execution of the irq worker (including a schedule_work)
> before the rtc-cmos parts are finished... Would explain why moving the
> initialize call further down does at least narrow the window for it to happen...
> The only thing I do not understand then is why that seems only to happen on Xen
> guests...
Its just likely with Xen SMP guests that the race window is larger. I
suspect similar behavior could be tripped on other slower SMP boxes as
well.
thanks
-john
next prev parent reply other threads:[~2012-01-04 18:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-03 16:13 [3.2.0-RC7] BUG: unable to handle kernel NULL pointer dereference at 0000000000000598 [ 1.478005] IP: [<ffffffff8107a6c4>] queue_work_on+0x4/0x30 Sander Eikelenboom
2012-01-03 19:07 ` Regression: ONE CPU fails bootup at " Konrad Rzeszutek Wilk
2012-01-03 19:17 ` Sander Eikelenboom
2012-01-03 19:26 ` Stefan Bader
2012-01-03 20:11 ` Sander Eikelenboom
2012-01-03 20:10 ` Sander Eikelenboom
2012-01-03 22:33 ` Konrad Rzeszutek Wilk
2012-01-03 23:09 ` John Stultz
2012-01-04 0:31 ` NeilBrown
2012-01-04 0:53 ` John Stultz
2012-01-04 1:20 ` NeilBrown
2012-01-04 14:46 ` Konrad Rzeszutek Wilk
2012-01-04 15:12 ` Regression: ONE CPU fails bootup at Re: [3.2.0-RC7] BUG: unable to handle kernel NULL pointer dereference at 0000000000000598 " Stefan Bader
2012-01-05 22:03 ` NeilBrown
2012-01-04 8:17 ` Stefan Bader
2012-01-04 12:25 ` Stefan Bader
2012-01-04 13:17 ` Sander Eikelenboom
2012-01-04 18:33 ` John Stultz
2012-01-04 14:13 ` Stefan Bader
2012-01-06 20:41 ` John Stultz
2012-01-08 20:48 ` Sander Eikelenboom
2012-01-09 13:26 ` Stefan Bader
2012-01-04 18:35 ` John Stultz [this message]
2012-01-04 18:36 ` John Stultz
2012-01-04 18:50 ` Stefan Bader
2012-01-04 19:47 ` Konrad Rzeszutek Wilk
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=1325702132.3037.100.camel@work-vm \
--to=john.stultz@linaro.org \
--cc=konrad.wilk@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@eikelenboom.it \
--cc=neilb@suse.de \
--cc=rjw@sisk.pl \
--cc=stefan.bader@canonical.com \
--cc=tglx@linutronix.de \
/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