From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S268399AbUJDRuO (ORCPT ); Mon, 4 Oct 2004 13:50:14 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S268379AbUJDRuO (ORCPT ); Mon, 4 Oct 2004 13:50:14 -0400 Received: from NEUROSIS.MIT.EDU ([18.95.3.133]:36483 "EHLO neurosis.jim.sh") by vger.kernel.org with ESMTP id S268365AbUJDRuJ (ORCPT ); Mon, 4 Oct 2004 13:50:09 -0400 Date: Mon, 4 Oct 2004 13:50:03 -0400 From: Jim Paris To: William Knop Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org, linux-ide@vger.kernel.org Subject: Re: libata badness Message-ID: <20041004175003.GA10814@jim.sh> References: <41617AA0.9020809@pobox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.6+20040722i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > I just got another oops while trying to cp from my md/raid5 array (2 of 3 > sata drives) to another sata drive on the same controller. This time, > though, it said there's a bug in timer.c, line 405, and that the > stack's garbage. I'm thinking it has nothing to do with timer.c, and > something in md or libata is chomping all over the kernel. Or else something else on your system is bad. Like your CPU or RAM. Run memtest for a while. -jim