linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: William Knop <wknop@andrew.cmu.edu>
Cc: linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
	linux-ide@vger.kernel.org
Subject: Re: libata badness
Date: Mon, 04 Oct 2004 14:01:29 -0400	[thread overview]
Message-ID: <41618FF9.7080801@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.60-041.0410041323160.9105@unix43.andrew.cmu.edu>

William Knop wrote:
> 
> 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.

If you are getting random oopses all over the place, I would suspect 
hardware before I suspect buggy code.

Jim's, and others' suggestions were good:  check power connectors (not 
just overall power consumption), test CPU, RAM, temperature, ...

	Jeff




  parent reply	other threads:[~2004-10-04 18:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-04 12:12 libata badness William Knop
2004-10-04 13:59 ` Jon Lewis
2004-10-04 15:50   ` William Knop
2004-10-04 16:06     ` Mark Lord
2004-10-04 16:24       ` William Knop
2004-10-04 16:30       ` Jeff Garzik
2004-10-04 16:09     ` Jon Lewis
2004-10-04 16:34       ` William Knop
2004-10-04 16:30 ` Jeff Garzik
2004-10-04 16:55   ` William Knop
2004-10-04 17:42   ` William Knop
2004-10-04 17:50     ` Jim Paris
2004-10-04 18:03       ` William Knop
2004-10-04 18:01     ` Jeff Garzik [this message]
2004-10-04 22:47 ` Neil Brown
2004-10-05  3:11   ` William Knop
2004-10-05  4:49     ` Brad Campbell
2004-10-05  5:27       ` Norman Schmidt

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=41618FF9.7080801@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-raid@vger.kernel.org \
    --cc=wknop@andrew.cmu.edu \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).