linux-kernel - Re: [049/197] x86, amd: Get multi-node CPU info from NodeId MSR instead of PCI config space

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <alpine.LNX.2.00.1004270906370.7579@pobox.suse.cz>
Date:	Tue, 27 Apr 2010 09:07:24 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Andreas Herrmann <andreas.herrmann3@....com>
Cc:	Greg KH <gregkh@...e.de>, linux-kernel@...r.kernel.org,
	stable@...nel.org, stable-review@...nel.org,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Alan Cox <alan@...rguk.ukuu.org.uk>,
	"H. Peter Anvin" <hpa@...or.com>
Subject: Re: [049/197] x86, amd: Get multi-node CPU info from NodeId MSR
 instead of PCI config space

On Tue, 27 Apr 2010, Andreas Herrmann wrote:

> > > 2.6.32-stable review patch.  If anyone has any objections, please let us know.
> > 
> > This patch is causing kernel panic on boot on Magny Cours CPU here 
> > (cpu family 16, model 9, stepping 1).
> > 
> > Please see screenshot from the paniced kernel on 
> > 
> >    http://www.jikos.cz/jikos/junk/screenshot.jpg 
> > 
> > (sorry for bad quality of this screenshot, it was captured only from the 
> > IPMI/HTTP console so far, I will try to grab something better tomorrow)
> > 
> > Also this screenshot probably doesn't show the complete picture -- see the 
> > "end trace" marker on the very first line. I will try to have something 
> > better tomorrow, but maybe this rings bell for someone right away.
> 
> This looks like a BIOS issue to me. Obviously this is a pre-production
> test system where an old BIOS is installed. A BIOS update should fix
> this issue for you.

I can confirm that on different Magny Cours system (16/9/1) with a newer 
BIOS, the NodeID is provided correctly via MSR, and the issue doesn't 
trigger.

Thanks,

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
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/