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]

Message-Id: <201104231016.23579.chris@csamuel.org>
Date:	Sat, 23 Apr 2011 10:16:18 +1000
From:	Chris Samuel <chris@...muel.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <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

Syt mae Alan! ;-)

On Sat, 23 Apr 2011 02:34:22 AM Alan Cox wrote:

> earlyprintk=vga

Ahh, that's a new one on me, and it reveals that the kernel
has gone from 2.6.18 detecting:

256MB LOWMEM available.

to 2.6.39-rc4 detecting:

16MB LOWMEM available.

That would explain an awful lot..

> (or better yet earlyprintk=ttyS0 and a serial port)

Hmm, I might still have a null modem cable hanging around..

> There are a couple of PPro funnies - there's an area of memory that
> must be excluded due to a chip errata and I seem to remember some
> PPro boxes also having slightly quirking E820 (BIOS memory
> reporting behaviour)

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.

Unfortunately nothing happened and when I prodded him it turned
out he'd been too busy, so I just kept on running old kernels
from that point on and completely forgot about why. :-(

Hope life is still good in Abertawe!

Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC

This email may come with a PGP signature as a file. Do not panic.
For more info see: http://en.wikipedia.org/wiki/OpenPGP

Download attachment "signature.asc " of type "application/pgp-signature" (483 bytes)