Bug#617756: closed by Ben Hutchings
On 03/11/2011 08:36:06 AM, Debian Bug Tracking System wrote:
> This is an automatic notification regarding your Bug report
> which was filed against the linux-2.6 package:
> #617756: linux-image-2.6.32-5-686: NMI received for unknown reason 3d
> on CPU 0.
> It has been closed by Ben Hutchings <email@example.com>.
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Ben Hutchings
> <firstname.lastname@example.org> by
> replying to this email.
> 617756: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=617756
> Debian Bug Tracking System
> Contact email@example.com with problems
======quoted message from Ben Hutchings <firstname.lastname@example.org>, subject
"Re: Bug#617756: linux-image-2.6.32-5-686: NMI received for unknown
reason 3d on CPU 0."======
> On Fri, 2011-03-11 at 00:22 -0600, Karl O. Pinc wrote:
> > Package: linux-2.6
> > Version: 2.6.32-30
> > Severity: normal
> > *** Please type your report below this line ***
> > Hi,
> > I don't know whether this is a hardware problem or a kernel problem
> > but figured I'd report it. I just upgraded to squeeze and am
> > these messages on the console and in dmesg:
> > [31934.320083] Uhhuh. NMI received for unknown reason 3d on CPU 0.
> > [31934.320109] Do you have a strange power saving mode enabled?
> > [31934.320125] Dazed and confused, but trying to continue
> > [36364.673879] Uhhuh. NMI received for unknown reason 2d on CPU 0.
> > [36364.673905] Do you have a strange power saving mode enabled?
> > [36364.673922] Dazed and confused, but trying to continue
> > I first noticed a problem, related or not, a month or so ago after
> > box crashed, twice over the course of a week, while still
> > running lenny (stock kernel). I've not had a crash before or
> > since but went looking and found (lenny kernel) messages in
> > /var/log/kern.log like:
> This is very likely a hardware fault. The power supply or RAM may be
> faulty, or the CPU may be overclocked or overheating.
I ran memtest86+ on it for 48 hours and got 3 failures. This is a
much lower frequency of errors than that in the dmesg output
but is a clear indication of some problem. I'll see about
replacing the ram and see if the problem goes away.
Thanks for the help.
(The CPU is not overclocked and should not be overheating because
nothing has changed. I'll crack the case and see if there's
anything obviously, like a fan has stoppped.)
Free Software: "You don't pay back, you pay forward."
-- Robert A. Heinlein
To UNSUBSCRIBE, email to debian-kernel-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact email@example.com
|All times are GMT. The time now is 12:58 PM.|
VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.