public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Jonathan Woithe <jwoithe@physics.adelaide.edu.au>
Cc: Hugh Dickins <hugh@veritas.com>, Andrew Morton <akpm@osdl.org>,
	Anton Altaparmakov <aia21@cam.ac.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: Fw: 2.6.17 oops, possibly ntfs/mmap related
Date: Fri, 22 Sep 2006 11:40:35 -0400	[thread overview]
Message-ID: <20060922154035.GB22531@redhat.com> (raw)
In-Reply-To: <200609220717.k8M7H0Ir021258@auster.physics.adelaide.edu.au>

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

  reply	other threads:[~2006-09-22 15:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20060912205602.57568b2a.akpm@osdl.org>
2006-09-21  9:54 ` Fw: 2.6.17 oops, possibly ntfs/mmap related Anton Altaparmakov
2006-09-21 14:41   ` Anton Altaparmakov
2006-09-21 17:52     ` Andrew Morton
2006-09-21 19:04       ` Hugh Dickins
2006-09-21 19:24         ` Dave Jones
2006-09-22  7:17           ` Jonathan Woithe
2006-09-22 15:40             ` Dave Jones [this message]
2006-09-24 23:49               ` Jonathan Woithe
2006-09-22  6:59       ` Anton Altaparmakov
2006-09-22  7:23         ` Jonathan Woithe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20060922154035.GB22531@redhat.com \
    --to=davej@redhat.com \
    --cc=aia21@cam.ac.uk \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=jwoithe@physics.adelaide.edu.au \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox