linux-kernel - RE: 2.6.38-rc2: Uhhuh. NMI received for unknown reason 2d on CPU 0.

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]

Message-ID: <9F0C2539CB50A743894F8FCEEB1D56920714B3@mx1.guavus.com>
Date:	Mon, 21 Feb 2011 06:56:44 +0000
From:	Preeti Khurana <Preeti.Khurana@...vus.com>
To:	"Underwood, Ryan" <Ryan.Underwood@...ghtsafety.com>,
	"paulmck@...ux.vnet.ibm.com" <paulmck@...ux.vnet.ibm.com>,
	Cyrill Gorcunov <gorcunov@...il.com>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: 2.6.38-rc2: Uhhuh. NMI received for unknown reason 2d on CPU 0.

> >
> > Given 2.6.35, has anyone tried applying the following patch?
> >
> > 	https://patchwork.kernel.org/patch/23985/
> >
> > It turned out to resolve an otherwise mysterious RCU CPU stall warning
> > for someone running 2.6.36, IIRC.
> >
> 
	This fix is already in 2.6.35, so this doesn't seem to be an issue.

> Now I've tried 2.6.38-rc5 which already includes that patch, and the same
> problems remain.  It also includes the following patch that Preeti seems to
> have had some success with on 2.6.35, so my problem must really be
> elsewhere:
> https://lkml.org/lkml/2011/1/6/131
> 
> Since a previous BIOS version is known to work I may end up having to do
> some BIOS-bisecting today...

Ryan,
   Cant say that this patch (https://lkml.org/lkml/2011/1/6/131) worked for me since I am not able to reproduce the problem quite reliably and now not getting the problem even under the original kernel without this patch.  Just wondering what triggers this problem.

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