ad0: READ command timeout....

[Thomas Nystrom]

Stephen McKay wrote:
> 
> On Monday, 19th May 2003, Tenebrae wrote:
> 
> >On Sun, 18 May 2003, Dan Langille wrote:
> >
> >> This morning I found a frozen box.  On the console was this:
> >>
> >> ad0: READ command timeout tag=0 serv=0 - resetting
> >> ata0: resetting devices .. ata0-slave: ATA identify retries exceeded
> >> done
> >>
> >> After reboot, those messages were found in /var/log/messages.
> >>
> >> I'm running FreeBSD 4.8-RC from Apr 4 10:45:49 EST 2003.
> >
> >I've had similar problems.  This has come up a few times on the mailing
> >list in the past, especially regarding certain lines of IBM drives.
> >Suggestions include replacing your IDE cable, making sure it's not longer
> >than 18 inches...and replacing the drive as it's probably on its last leg.
> >Back it up while you can.
> 
> I am plagued with all sorts of ata command timeout problems.  Some of the
> hardware is brand new, some of it not.  I think the problem is in the ata
> code.  If not, how can I get some detailed reporting so I can trace the
> true culprit?  How can I get at the so called SMART info?  And what's in
> the -current ata driver that hasn't made it back into -stable?
> 

"Me too!"

I have the same kind of problems but I know when it happens: When my
backup should start at 01.00. I'm running a script each night that dumps
some partitions to files on a separate HD. That disc is normally not
used or accessed during the whole day excecpt when the backup is run.
Sometimes it can go several weeks between the problems, sometimes it can
occur twice a week.

The discs are:
  ad0: 28629MB <ST330621A> [58168/16/63] at ata0-master UDMA33
  ad1: 39093MB <FUJITSU MPG3409AT E> [79428/16/63] at ata0-slave UDMA33
  ad2: DMA limited to UDMA33, non-ATA66 cable or device
  ad2: 39093MB <FUJITSU MPG3409AT E> [79428/16/63] at ata1-master UDMA33
  acd0: CDROM <> at ata1-slave PIO4

The disc that hangs is ad1. It is a rather old machine and is not
capable of anything else than UDMA33.

The message I see on the console is:
  ad1: READ command timeout tag=0 serv=0 - resetting
  ata0: resetting devices....

and the machines hangs there with the disk indicator LED turned on but
without any disc activity.

I have run FreeBSD on this machine for several versions and I have the
feeling that the problems didn't occur with 4.5R but started with 4.6R
or 4.7R. Currently I run 4.8R.

Complete dmesg/pciconf/whatssoever on request.

/thn

-- 
---------------------------------------------------------------
Svensk Aktuell Elektronik AB                     Thomas Nyström
Box 10                                    Phone: +46 8 35 92 85
S-191 21  Sollentuna                        Fax: +46 8 35 92 86
Sweden                                      Email: thn at saeab.se
---------------------------------------------------------------