linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>
Cc: Willy Tarreau <willy@w.ods.org>,
	Marcelo Tosatti <marcelo@conectiva.com.br>,
	lkml <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.21-rc3 : IDE pb on Alpha
Date: Sun, 25 May 2003 13:55:11 -0700	[thread overview]
Message-ID: <20030525205511.GC23651@matchmail.com> (raw)
In-Reply-To: <Pine.SOL.4.30.0305252242430.10573-100000@mion.elka.pw.edu.pl>

On Sun, May 25, 2003 at 10:45:00PM +0200, Bartlomiej Zolnierkiewicz wrote:
> On Sun, 25 May 2003, Mike Fedyk wrote:
> 
> > On Sun, May 25, 2003 at 07:00:46PM +0200, Willy Tarreau wrote:
> > > hda: task_no_data_intr: status=0x51 { DriveReady SeekComplete Error }
> > > hda: task_no_data_intr: error=0x04 { DriveStatusError }
> >
> > Can you revert back to your previous kernel and run badblocks read-only on
> > it a few times.  Your drive may be going bad.
> 
> 
> 
> Everything is okay, older drives don't understand some commands.
> I will fix it, but now its low on my TODO list.
> 

Bart, is there any chace you could change the printks to show the name of
the command that caused the drive to produce the error (assuming non
ide-tcq, with tcq I'd immagine that it'd be a bit harder).

This way someone who hasn't read the IDE spec might be able to tell that
this isn't a warning of impending failure.

BTW, is this information encoded in the two lines above somewhere, and if so
how would I read it?

Thanks,

Mike

  reply	other threads:[~2003-05-25 20:45 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-22 22:19 Linux 2.4.21-rc3 Marcelo Tosatti
2003-05-22 23:46 ` J.A. Magallon
2003-05-26 17:04   ` Alan Cox
2003-05-23  0:51 ` Barry K. Nathan
2003-05-23  5:32   ` Marc-Christian Petersen
2003-05-23  7:04     ` [BUG] 2.[45] ioperm fix seems broken (was Re: Linux 2.4.21-rc3) Barry K. Nathan
2003-05-23  9:00       ` Barry K. Nathan
2003-05-23  8:27 ` Linux 2.4.21-rc3 Benjamin Herrenschmidt
2003-05-23 13:38 ` Linux 2.4.21-rc3 - ipmi unresolved Eyal Lebedinsky
2003-05-23 13:41   ` Marc-Christian Petersen
2003-05-26  2:09     ` Corey Minyard
2003-05-25  7:57   ` Keith Owens
2003-05-26  3:37     ` Corey Minyard
2003-05-26  3:54       ` Keith Owens
2003-05-27  0:30         ` Corey Minyard
2003-05-27  3:09           ` Keith Owens
2003-05-27  4:45             ` Registering for notifier chains in modules (was Linux 2.4.21-rc3 - ipmi unresolved) Corey Minyard
2003-05-27  5:30               ` Keith Owens
2003-05-27 14:48                 ` Corey Minyard
2003-05-27 16:02                   ` viro
2003-05-27 17:09                     ` Corey Minyard
2003-05-28  0:15                       ` Keith Owens
2003-05-26 17:08     ` Linux 2.4.21-rc3 - ipmi unresolved Alan Cox
2003-05-23 21:10 ` Linux 2.4.21-rc3 [net-pf-4, devfs audio, drm radeon] Gabor Z. Papp
2003-05-25 17:36 ` Linux 2.4.21-rc3 : IDE pb on Alpha Willy Tarreau
2003-05-25 17:00   ` Willy Tarreau
2003-05-25 20:37     ` Mike Fedyk
2003-05-25 20:45       ` Bartlomiej Zolnierkiewicz
2003-05-25 20:55         ` Mike Fedyk [this message]
2003-05-25 21:23           ` Bartlomiej Zolnierkiewicz
2003-05-26  7:28 ` Linux 2.4.21-rc3: doesn't build with CONFIG_BLK_DEV_HD_ONLY=y Jerome Chantelauze
2003-05-26 13:16 ` Linux 2.4.21-rc3 Santiago Garcia Mantinan
2003-05-27  1:14   ` Jeff Chua
2003-05-27  3:37 Linux 2.4.21-rc3 : IDE pb on Alpha Jason Papadopoulos
2003-05-27  4:53 ` Willy Tarreau
2003-05-27  9:40   ` Ivan Kokshaysky
2003-05-27 12:31     ` Willy Tarreau
2003-05-27 14:04       ` Ivan Kokshaysky
2003-05-27 14:37         ` Willy Tarreau
2003-05-28  0:38         ` Willy Tarreau
2003-05-28  1:41         ` Jason Papadopoulos
2003-05-28  3:12           ` Jeff Garzik
2003-05-29  0:35             ` Jason Papadopoulos
2003-05-29  1:10               ` Jeff Garzik
2003-05-28 14:45           ` Ivan Kokshaysky
2003-05-31 15:24         ` Ben Collins
2003-06-01 18:40           ` Ivan Kokshaysky

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=20030525205511.GC23651@matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=B.Zolnierkiewicz@elka.pw.edu.pl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=willy@w.ods.org \
    /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).