linux-kernel - Re: kernel won't boot on a Cyrix MediaGXm (Geode )

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:	Mon, 21 Jul 2008 22:16:34 -0700
From:	Samuel Sieb <samuel@...b.net>
To:	Juergen Beisert <jbe@...gutronix.de>
CC:	linux-kernel@...r.kernel.org
Subject: Re: kernel won't boot on a Cyrix MediaGXm (Geode )

Juergen Beisert wrote:
> Samuel,
> 
> On Montag, 21. Juli 2008, 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
> Yes. My patch makes some chipset tweaks working as expected. Or at least it 
> makes them work. It seems nobody ever tested them before. Remove the 
> following line (or change it to meet your CPU clock frequency):
> 
This system is kind of an embedded one and it's been working fine, so I 
haven't bothered upgrading the OS for a long time.  Once I get this 
working I will be keeping it more up to date.

> linux-2.6.25/arch/x86/kernel/cyrix.c, line 151. Disable this line or change 
> the value 0x04 according to the speed of your CPU. This tweak helps others 
> with random hangs of their system.
> 
I tried various values and various combinations of commenting out lines 
and the only one that worked for me was to comment out the PCR1 line 
just above it.  With that line commented out (or both of them), it 
boots.  I do get a message about the TSC clocksource being unstable, 
which is a new feature as well.  I can only say that in 2.6.14 it was 
fine.  I could do similar tests if you want to know when that started 
happening.
--
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/