mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Eric D. Mudama" <edmudama@bounceswoosh.org>
To: Ed Tomlinson <edt@aei.ca>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
	Jens Axboe <axboe@suse.de>
Subject: Re: 2.6.7-mm7 ide errors
Date: Sat, 10 Jul 2004 10:20:26 -0600	[thread overview]
Message-ID: <20040710162026.GA12371@bounceswoosh.org> (raw)
In-Reply-To: <200407100848.15665.edt@aei.ca>

On Sat, Jul 10 at  8:48, Ed Tomlinson wrote:
>Hi,
>
>The ide error introduced with the barrier patches are still happening here with mm7. 
>
>Jul 10 08:06:04 bert usb.agent[1705]:      usbhid: loaded successfully
>Jul 10 08:06:04 bert input.agent[1738]:      joydev: loaded successfully
>Jul 10 08:06:06 bert kernel: lp: driver loaded but no devices found
>Jul 10 08:06:16 bert kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
>Jul 10 08:06:16 bert kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
>Jul 10 08:06:16 bert kernel: ide: failed opcode was: 0xe7
>Jul 10 08:06:18 bert kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
>Jul 10 08:06:18 bert kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
>Jul 10 08:06:18 bert kernel: ide: failed opcode was: 0xe7
>
>Typically  I get one of the above every couple of minutes and have since the barrier changes
>when into mm.
>
>What can I do to help get to the bottom of this problem?

0xE7 is the 'FLUSH CACHE' command for use on drives <= 137GB.

What model of drive do you have, and how big is it?


-- 
Eric D. Mudama
edmudama@mail.bounceswoosh.org


  reply	other threads:[~2004-07-10 16:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-10 12:48 Ed Tomlinson
2004-07-10 16:20 ` Eric D. Mudama [this message]
2004-07-10 18:12   ` Ed Tomlinson

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=20040710162026.GA12371@bounceswoosh.org \
    --to=edmudama@bounceswoosh.org \
    --cc=akpm@osdl.org \
    --cc=axboe@suse.de \
    --cc=edt@aei.ca \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®