From: Dave Hansen <dave@sr71.net>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
Richard Purdie <rpurdie@linux.intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: -tip: origin tree boot crash
Date: Fri, 18 Dec 2009 11:30:50 -0800 [thread overview]
Message-ID: <1261164650.27372.1742.camel@nimitz> (raw)
In-Reply-To: <20091218170622.GA1354@elte.hu>
On Fri, 2009-12-18 at 18:06 +0100, Ingo Molnar wrote:
> * Dave Hansen <dave@sr71.net> wrote:
> I just double-checked it again on a couple of my systems and it seems to
> > deny loading the module correctly.
> >
> > What kind of hardware is this? Could you send me 'dmidecode' output?
> >
> > I'm wondering if your hardware matched the "Intel" string somehow and the
> > dmi code didn't bother to check anything else. I'll also go try and run on
> > a few more pieces of hardware and see if I can get it to trigger.
>
> It's an Athlon64 whitebox PC - a pretty old one - and nothing special.
>
> Also note the crash signature - it crashes in the DMI code. Note, this is a
> built-in-driver (not a modular driver) bootup.
I figured as much since you said it was a real bootup problem. I've
been testing the same way.
I've tried a few other pieces of hardware that I have sitting around and
can't seem to recreate this. I've also double-checked the code to look
for any obvious bugs. No luck on either front. You didn't see any
other dmesg output from these, did you?
pr_info("skipping hardware autodetection\n");
pr_info("Please send 'dmidecode' output to dave@sr71.net\n");
-- Dave
next prev parent reply other threads:[~2009-12-18 19:30 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-18 16:45 -tip: origin tree boot crash Ingo Molnar
2009-12-18 17:01 ` Dave Hansen
2009-12-18 17:06 ` Ingo Molnar
2009-12-18 19:30 ` Dave Hansen [this message]
2009-12-18 20:10 ` Linus Torvalds
-- strict thread matches above, loose matches on Subject: below --
2009-12-24 22:00 Linux 2.6.33-rc2 - Merry Christmas Linus Torvalds
2009-12-25 10:27 ` -tip: origin tree boot crash Ingo Molnar
2009-12-25 19:49 ` Dmitry Torokhov
2009-12-26 20:19 ` Len Brown
2009-12-26 20:17 ` Len Brown
2009-12-27 4:20 ` Len Brown
2009-12-28 9:44 ` Ingo Molnar
2009-12-28 12:01 ` Ingo Molnar
2009-12-28 15:02 ` Paul Rolland
2009-12-28 16:15 ` Paul Rolland
2009-12-28 16:53 ` Paul Rolland
2009-12-28 20:17 ` Dmitry Torokhov
2009-12-30 6:14 ` Len Brown
2009-12-30 7:13 ` Paul Rolland
2009-12-17 9:02 Ingo Molnar
2009-12-17 9:27 ` Christoph Hellwig
2009-12-17 9:44 ` Ingo Molnar
2009-12-17 9:32 ` Al Viro
2009-12-17 9:35 ` Christoph Hellwig
2009-12-17 9:44 ` Ingo Molnar
2009-12-17 9:52 ` Ingo Molnar
2009-12-17 9:54 ` Al Viro
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=1261164650.27372.1742.camel@nimitz \
--to=dave@sr71.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rpurdie@linux.intel.com \
--cc=torvalds@linux-foundation.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