linux-kernel - Re: [BUG] (regression) AMD k6-III/450 won't boot w/2.6.22-rc1

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:	Wed, 16 May 2007 12:30:00 -0400
From:	Dave Jones <davej@...hat.com>
To:	Chuck Ebbert <cebbert@...hat.com>
Cc:	Bob Tracy <rct@...rkin.frus.com>,
	Jan Engelhardt <jengelh@...ux01.gwdg.de>,
	Randy Dunlap <randy.dunlap@...cle.com>,
	linux-kernel@...r.kernel.org, Andi Kleen <ak@...e.de>,
	Joachim Deguara <joachim.deguara@....com>
Subject: Re: [BUG] (regression) AMD k6-III/450 won't boot w/2.6.22-rc1

On Wed, May 16, 2007 at 11:53:22AM -0400, Chuck Ebbert wrote:
 > Bob Tracy wrote:
 > > Jan Engelhardt wrote:
 > >>> On Tue, 15 May 2007 22:13:14 -0500 (CDT) Bob Tracy wrote:
 > >>>
 > >>>> The 2.6.22-rc1 boot panics early in amd_mcheck_init() with my k6-III/450.
 > 
 > > Intel machine check architecture supported.
 > > general protection fault: 0000 [#1]
 > > PREEMPT
 > > Modules linked in:
 > > CPU:   0
 > > EIP: 0060:[<c01079f4>]  Not tainted VLI
 > > EFLAGS: 00010286   (2.6.22-rc1 #1)
 > > EIP is at amd_mcheck_init+0x2b/0xc3
 > > 
 > 
 > rdmsr with ecx == 0x179 (Machine Check Global Capabilities Register)
 > 
 > Probably K6 doesn't have that.

sounds right. Intel style MCE capability was introduced with the Athlon
on AMD systems iirc.

 > Caused by:
 > 
 > 	[PATCH] i386: check capability

Though this would imply that Bobs K6-3 is reporting that it does have
that bit in its cpuid flags.

Bob, can you send your /proc/cpuinfo and dmesg |grep CPU  ?

	Dave

-- 
http://www.codemonkey.org.uk
-
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/