linux-kernel - Re: Panic early in boot

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] [day] [month] [year] [list]

Date:	Sat, 6 Jun 2009 23:03:12 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Jeff Mitchell <jeffrey.mitchell@...il.com>
Cc:	Jiri Slaby <jirislaby@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Panic early in boot

On Sat, 6 Jun 2009 12:35:33 -0400
Jeff Mitchell <jeffrey.mitchell@...il.com> wrote:

> > Don't worry to append a link to the screenshot next time ;).
> 
> Done...  http://tinypic.com/r/2vuwz1j/5
> 
> > Looks like dmi_string_nosave gets a mess. It tries to dereference
> > 0xffffffffeff44003d. Could you investigate to which save_indent in
> > dmi_decode does the dmi_decode+0x72 correspond to?

The dmi code isn't robust against corrupt BIOS DMI tables. I have a patch
pending for this if you want to try it out. I've no idea if that is the
trigger in your case but it may be.

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