linux-kernel - Re: Regression: boot failure on AMD Elan TS-5500

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <487D250A.70200@zytor.com>
Date:	Tue, 15 Jul 2008 15:30:34 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Sean Young <sean@...s.org>
CC:	Jeremy Fitzhardinge <jeremy@...p.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	linux-kernel@...r.kernel.org,
	the arch/x86 maintainers <x86@...nel.org>
Subject: Re: Regression: boot failure on AMD Elan TS-5500

Sean Young wrote:
> 
> When I bisected this issue between latest and 2.6.23 the issue seemed to be
> here (round about 2.6.24-rc1). Trying to repeat the same things on latest 
> just led to confusion.
> 
> So I've started from scratch with contemporary trees and found something 
> very different.
> 
> 2.6.25: works
> 2.6.25.5: works
> 2.6.25.6: broken
> 2.6.25.10: broken
> 2.6.26: works
> 
> Now the issue which was introduced in 2.6.25.6 is that a rdtsc will be done
> even though this CPU does not support it (before console_init(), leaving
> me with only one led for output!). This issue has been fixed in 2.6.26 but 
> not in 2.6.25-stable.
> 
> The protected mode jump was just a red herring (or at least whatever was 
> broken back then is fixed now); 2.6.26 is working fine and that's good 
> enough for me.
> 

Okay, that is good to know.  We did move the jmp in pmjump.S for 2.6.26; 
even if it ended up being redundant I have to say I'm happier following 
the documented script, especially given the apparent recent 
documentation change on Intel's part about this.

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