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

Message-Id: <200609242349.k8ONndgr004562@auster.physics.adelaide.edu.au>
Date:	Mon, 25 Sep 2006 09:19:39 +0930 (CST)
From:	Jonathan Woithe <jwoithe@...sics.adelaide.edu.au>
To:	davej@...hat.com (Dave Jones)
Cc:	jwoithe@...sics.adelaide.edu.au (Jonathan Woithe),
	hugh@...itas.com (Hugh Dickins), akpm@...l.org (Andrew Morton),
	aia21@....ac.uk (Anton Altaparmakov),
	linux-kernel@...r.kernel.org
Subject: Re: Fw: 2.6.17 oops, possibly ntfs/mmap related

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

Power and cooling should be fine, and I've checked fans etc for correct
functioning - all is ok.  The other thing worth noting is that the problems
with this machine only started once the USB/NTFS HDD started being used.
Before this the machine has been rock solid for 2+ years, and the usage
patterns haven't changed.  Anyway, I'll keep an eye on it and post any
subsequent information as it becomes available.

Regards
  jonathan

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