From: Jens Axboe <jens.axboe@oracle.com>
To: Glenn Maynard <glenn@zewt.org>
Cc: Jeff Garzik <jeff@garzik.org>,
linux-kernel@vger.kernel.org,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Crash during SATA reads
Date: Thu, 12 Nov 2009 11:12:58 +0100 [thread overview]
Message-ID: <20091112101257.GG8742@kernel.dk> (raw)
In-Reply-To: <bd36f99e0911120211h2bda5062qe90d7be56203523@mail.gmail.com>
On Thu, Nov 12 2009, Glenn Maynard wrote:
> On Thu, Nov 12, 2009 at 4:55 AM, Jens Axboe <jens.axboe@oracle.com> wrote:
> > To rule out any potential hardware problems, have you run any extensive
> > memory checks on this machine?
>
> God damn it. I ran memtest+ just a week or so ago and it was fine
> through several passes; now it's failing badly. I'm inclined to send
> Kingston a bill for a day and a half of wasted time.
Auch, perhaps it's just seated badly? Power problems? Or yes, you just
got crap RAM :/
> I didn't think back to memory since I'm used to memory problems in
> userspace, where they cause wildly variable crashes. Of course, the
> kernel's far more likely to stick data in the same spot, so it makes
> sense that it doesn't cause as much volatility, leading to a bunch of
> related-looking crashes.
Well, at least it's a relief that it isn't a kernel issue :-)
--
Jens Axboe
prev parent reply other threads:[~2009-11-12 10:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 9:18 Crash during SATA reads Glenn Maynard
2009-11-11 9:26 ` Jeff Garzik
2009-11-11 12:12 ` Glenn Maynard
2009-11-11 21:09 ` Glenn Maynard
2009-11-11 21:39 ` Jeff Garzik
2009-11-11 22:19 ` Glenn Maynard
2009-11-12 2:28 ` Dmitry Monakhov
2009-11-12 5:26 ` Glenn Maynard
2009-11-12 9:16 ` Jens Axboe
2009-11-12 9:48 ` Glenn Maynard
2009-11-12 9:55 ` Jens Axboe
2009-11-12 10:11 ` Glenn Maynard
2009-11-12 10:12 ` Jens Axboe [this message]
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=20091112101257.GG8742@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=glenn@zewt.org \
--cc=jeff@garzik.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.