From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752110AbZKLKLw (ORCPT ); Thu, 12 Nov 2009 05:11:52 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751551AbZKLKLw (ORCPT ); Thu, 12 Nov 2009 05:11:52 -0500 Received: from mail-pw0-f42.google.com ([209.85.160.42]:36232 "EHLO mail-pw0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751263AbZKLKLv (ORCPT ); Thu, 12 Nov 2009 05:11:51 -0500 MIME-Version: 1.0 In-Reply-To: <20091112095544.GF8742@kernel.dk> References: <4AFA835B.9000904@garzik.org> <4AFB2F2A.7080900@garzik.org> <20091112091602.GC8742@kernel.dk> <20091112095544.GF8742@kernel.dk> Date: Thu, 12 Nov 2009 05:11:56 -0500 Message-ID: Subject: Re: Crash during SATA reads From: Glenn Maynard To: Jens Axboe Cc: Jeff Garzik , linux-kernel@vger.kernel.org, linux-scsi Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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. 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. Thanks. -- Glenn Maynard