From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jens Axboe Subject: Re: Crash during SATA reads Date: Thu, 12 Nov 2009 11:12:58 +0100 Message-ID: <20091112101257.GG8742@kernel.dk> References: <4AFA835B.9000904@garzik.org> <4AFB2F2A.7080900@garzik.org> <20091112091602.GC8742@kernel.dk> <20091112095544.GF8742@kernel.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Glenn Maynard Cc: Jeff Garzik , linux-kernel@vger.kernel.org, linux-scsi List-Id: linux-scsi@vger.kernel.org On Thu, Nov 12 2009, Glenn Maynard wrote: > On Thu, Nov 12, 2009 at 4:55 AM, Jens Axboe 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