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  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:	Mon, 21 Jul 2008 22:10:30 -0700
From:	Samuel Sieb <>
To:	Ingo Molnar <>
CC:	"Rafael C. de Almeida" <>,
	Linux Kernel <>,
	Thomas Gleixner <>,
	"H. Peter Anvin" <>
Subject: Re: kernel won't boot on a Cyrix MediaGXm (Geode )

Ingo Molnar wrote:
> * Rafael C. de Almeida <> wrote:
>> Samuel Sieb wrote:
>>> I have a computer here with a CPU that the BIOS identifies as:
>>> Cyrix MediaGXm/Cx5530 Unicorn Revision 1.19.3B
>>> I can't boot any kernel later than 2.6.22 on it.  Anything later either
>>> hangs or gives random kernel panics while booting.  I tracked down the
>>> problem to a specific commit:
>>> commit f25f64ed5bd3c2932493681bdfdb483ea707da0a
> does the debug patch below (ontop of v2.6.26 or later kernels) make the 
> system bootable again? Commit f25f64ed5 changed the meaning of that 
> line. This patch switches back to the old behavior (which essentially 
> did nothing, due to macro side-effect bugs).
Commenting out this line didn't have any effect that I could see.  I was 
hoping one way or another it would affect the TSC unstable message I 
get, but it didn't even change that.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists