Re: ide errors in 7-rc1-mm1 and later

Jens Axboe
2004-06-04T11:32:39Z

On Fri, Jun 04 2004, Ed Tomlinson wrote:
> On June 4, 2004 05:42 am, Jens Axboe wrote:
> > On Thu, Jun 03 2004, Andrew Morton wrote:
> > > Ed Tomlinson <edt@aei.ca> wrote:
> > > >
> > > > Hi,
> > > >
> > > > I am still getting these ide errors with 7-rc2-mm2. I get the errors even
> > > > if I mount with barrier=0 (or just defaults). It would seem that something is
> > > > sending my drive commands it does not understand...
> > > >
> > > > May 27 18:18:05 bert kernel: hda: drive_cmd: status=0x51 { DriveReady SeekComplete Error }
> > > > May 27 18:18:05 bert kernel: hda: drive_cmd: error=0x04 { DriveStatusError }
> > > >
> > > > How can we find out what is wrong?
> > > >
> > > > This does not seem to be an error that corrupts the fs, it just slows things
> > > > down when it hits a group of these. Note that they keep poping up - they
> > > > do stop (I still get them hours after booting).
> > >
> > > Jens, do we still have the command bytes available when this error hits?
> >
> > It's not trivial, here's a hack that should dump the offending opcode
> > though.
>
> Hi Jens,
>
> I applied the patch below and booted into the new kernel (the boot
> message showed the new compile time). The error messages remained the
> same - no extra info. Is there another place that prints this (or
> (!rq) is true)?

!rq should not be true, strange... are you sure it just doesn't to go
/var/log/messages, it should be there in dmesg. Alternatively, add a
KERN_ERR to that printk.

--
Jens Axboe