From: Andi Kleen <andi@firstfloor.org>
To: mingo@elte.hu, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: mainline boot failures III: scheduler NULL pointer reference
Date: Sat, 26 Apr 2008 16:26:34 +0200 [thread overview]
Message-ID: <20080426142634.GA28930@basil.nowhere.org> (raw)
FYI
I see lots of boot failures on various setups with current mainline
(git8, b1721d0da266b4af8cb4419473b4ca36206ab200). Unfortunately
they are all different.
All with a defconfig kernel. Haven't investigated closely yet:
This one is a recursive oops with most of the data scrolling away
and unfortunately also no serial console handy, but it's
a NULL pointer reference in set_next_entity somewhere in the scheduler.
-Andi
reply other threads:[~2008-04-26 14:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20080426142634.GA28930@basil.nowhere.org \
--to=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=torvalds@osdl.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