linux-kernel - RE: 2.6.38.3 and 2.6.39-rc4 hangs after "Booting the kernel" on quad Pentium Pro system

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, 22 Apr 2011 18:28:20 -0700
From:	Yuhong Bao <yuhongbao_386@...mail.com>
To:	<chris@...muel.org>, <alan@...rguk.ukuu.org.uk>
CC:	<hpa@...or.com>, <tglx@...utronix.de>, <mingo@...hat.com>,
	<x86@...nel.org>, <linux-kernel@...r.kernel.org>
Subject: RE: 2.6.38.3 and 2.6.39-rc4 hangs after "Booting the kernel" on
 quad Pentium Pro system


> Sigh, that's just reminded me that a couple of years ago I
> had a private discussion with H. Peter Anvin about 2.6.25
> panic'ing on boot with:
>
> initrd extends beyond end of memory (0x0ffef173 > ox01000000)
>
> He gave me a modified syslinux to dump out memory information
> and it reported:
>
> INT 15h = f000:f859 DOS RAM: 638K (0x9f800) INT 12h: 638K (0x9f800)
> INT 15 88: 0x3c00 (15360K) INT 15 E801: 0x0000 (0K) 0x0000 (0K)
>
> He responded with:
>
> # Right... you have a system dependent on E801, and somehow E801
> # returns crap.
> #
> # I'm going to cook up a modified meminfo.c32 for you and see if
> # we can't track this down.

This is a stupid BIOS, but do you know if it used E820 in  the old kernel?
I wonder if this has something to do with the changes made to support ACPI 3.0 changes to E820?
This would be easy to diagnose with DOS DEBUG with no himem.sys loaded.

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