Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268439AbUJDSEt (ORCPT ); Mon, 4 Oct 2004 14:04:49 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268378AbUJDSEo (ORCPT ); Mon, 4 Oct 2004 14:04:44 -0400 Received: from smtp.andrew.cmu.edu ([128.2.10.83]:32644 "EHLO smtp.andrew.cmu.edu") by vger.kernel.org with ESMTP id S268400AbUJDSD5 (ORCPT ); Mon, 4 Oct 2004 14:03:57 -0400 Date: Mon, 4 Oct 2004 14:03:56 -0400 (EDT) From: William Knop To: Jim Paris cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org, linux-ide@vger.kernel.org Subject: Re: libata badness In-Reply-To: <20041004175003.GA10814@jim.sh> Message-ID: References: <41617AA0.9020809@pobox.com> <20041004175003.GA10814@jim.sh> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 811 Lines: 19 > Or else something else on your system is bad. Like your CPU or RAM. > Run memtest for a while. I ran memtest for a few hours. It all checks out. Also, CPU intensive stuff doesn't cause weirdness. The only things which cause corruption, so far as I can tell, are operations on my raid device, md0. Copying from the array takes a while for a crash, while rebuilding a drive on the array is very prompt (<1m) at causing a crash. The crashes likely as not cause widespread kernel corruption. It's only a matter of time before my root fs is blown away again. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/