linux-kernel - Re: Fw: 2.6.17 oops, possibly ntfs/mmap related

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: <20060922154035.GB22531@redhat.com>
Date:	Fri, 22 Sep 2006 11:40:35 -0400
From:	Dave Jones <davej@...hat.com>
To:	Jonathan Woithe <jwoithe@...sics.adelaide.edu.au>
Cc:	Hugh Dickins <hugh@...itas.com>, Andrew Morton <akpm@...l.org>,
	Anton Altaparmakov <aia21@....ac.uk>,
	linux-kernel@...r.kernel.org
Subject: Re: Fw: 2.6.17 oops, possibly ntfs/mmap related

On Fri, Sep 22, 2006 at 04:47:00PM +0930, Jonathan Woithe wrote:
 
 > > Given a machine check happened, the state of the machine in general
 > > is questionable.  I'd recommend a run of memtest86+ 
 > 
 > That was already done.  No memory errors were reported over 10 passes.
 > 
 > Secondly, the machine check indication was only present on one of the two
 > oopses we saw.  Furthermore, there was no indication in any log files
 > that a machine check had occurred in the case of the second oops.
 > Then again, perhaps machine checks don't get logged which would make this
 > observation irrelevant.
 > 
 > Could we be looking at a dying CPU?

Maybe. Or some other hardware problem. Insufficient cooling/power for eg.

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