[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1261164650.27372.1742.camel@nimitz>
Date: Fri, 18 Dec 2009 11:30:50 -0800
From: Dave Hansen <dave@...1.net>
To: Ingo Molnar <mingo@...e.hu>
Cc: linux-kernel@...r.kernel.org,
Richard Purdie <rpurdie@...ux.intel.com>,
Linus Torvalds <torvalds@...ux-foundation.org>
Subject: Re: -tip: origin tree boot crash
On Fri, 2009-12-18 at 18:06 +0100, Ingo Molnar wrote:
> * Dave Hansen <dave@...1.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@...1.net\n");
-- Dave
--
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