linux-kernel - Re: -tip: origin tree boot crash

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 18 Dec 2009 09:01:29 -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 17:45 +0100, Ingo Molnar wrote:
> Today's -tip crashes during bootup (x86 allyesconfig, 64-bit), due to this 
> commit from yesterday's upstream -git tree:
> 
>  commit a328e95b82c1b8483ae5ab2f809140664d7f6c92
>  Author: Dave Hansen <dave@...1.net>
>  Date:   Thu Oct 1 15:43:32 2009 -0700
> 
>     leds: LED driver for Intel NAS SS4200 series (v5)
> 
> The crash serial log is attached below. I suspect this driver was not booted 
> on hardware that does not have that LED interface?

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.

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