Status of ATA tagging in Stable

[ian j hart]

On Saturday 29 March 2003 6:42 pm, Kevin Oberman wrote:
> I have a P3 system running STABLE built on March 7. I installed a new
> IBM DTLA disk drive and was distressed at its slowness, so I tried
> turning on tagging to see if that would help. It seemed to, until...

What do you mean by *new*? These drives were renamed some long time ago.
IIRC quality was a bit poor for early drives.

>
> 3 AM when my periodic tasks started running. The system lost all disk
> access and logged lots of errors (a few of which I added to the end of
> this message).
>
> I rebooted the system this morning and the problem re-appeared when fsck
> ran. I then turned off tagged queuing and the system came up normally.
>
> Is there some problem with the DTLA drive or is this a driver problem?

Yes, the drive could be DOA. However it's equally likely to be the controller 
or the cable. Lots of M/Bs have suspect UDMA implementations.

My IC35L080's are fine (GigaByte 7VTXE+)

Take a look at this for starters (wrapped).

http://ssddom01.hgst.com/tech/techlib.nsf/techdocs/\
	85256AB8006A31E587256A7800700048/$file/dtla_com2.pdf

>
> R. Kevin Oberman, Network Engineer
> Energy Sciences Network (ESnet)
> Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab)
> E-mail: oberman at es.net			Phone: +1 510 486-8634
>
> 03:01:18 ptavv /kernel: ad0: no request for tag=0
> 03:01:18 ptavv /kernel: ad0: invalidating queued requests
> 03:01:18 ptavv /kernel: ad0: no request for tag=0
> 03:01:18 ptavv /kernel: ad0: invalidating queued requests
> 03:01:28 ptavv /kernel: ad0: READ command timeout tag=0 serv=1 - resetting
> 03:01:28 ptavv /kernel: ad0: invalidating queued requests
> 03:01:28 ptavv /kernel: ata0: resetting devices .. ad0: invalidating queued
> requests 03:01:28 ptavv /kernel: ad0: DMA limited to UDMA33, non-ATA66
> cable or device 03:01:28 ptavv /kernel: done
> 03:01:28 ptavv /kernel: ad0: no request for tag=0
> 03:01:28 ptavv /kernel: ad0: invalidating queued requests
> 03:01:28 ptavv /kernel: ad0: no request for tag=1
> 03:01:28 ptavv /kernel: ad0: invalidating queued requests
> 03:01:39 ptavv /kernel: ad0: READ command timeout tag=0 serv=1 - resetting
> 03:01:39 ptavv /kernel: ad0: invalidating queued requests
> 03:01:39 ptavv /kernel: ad0: timeout waiting for READY
> 03:01:39 ptavv /kernel: ad0: invalidating queued requests
> 03:01:39 ptavv /kernel: - resetting
> 03:01:39 ptavv /kernel: ata0: resetting devices .. ad0: invalidating queued
> requests 03:01:39 ptavv /kernel: ad0: DMA limited to UDMA33, non-ATA66
> cable or device 03:01:39 ptavv /kernel: done
> 03:01:39 ptavv /kernel: ata0: resetting devices .. ad0: invalidating queued
> requests 03:01:39 ptavv /kernel: ad0: DMA limited to UDMA33, non-ATA66
> cable or device 03:01:39 ptavv /kernel: done
> 03:01:39 ptavv /kernel: ad0: WRITE command timeout tag=3 serv=0 - resetting
> 03:01:39 ptavv /kernel: ad0: invalidating queued requests
> 03:01:39 ptavv /kernel: ata0: resetting devices .. ad0: invalidating queued
> requests 03:01:39 ptavv /kernel: ad0: DMA limited to UDMA33, non-ATA66
> cable or device 03:01:39 ptavv /kernel: done
> 03:01:39 ptavv /kernel: ad0: WRITE command timeout tag=2 serv=0 - resetting
> 03:01:39 ptavv /kernel: ad0: invalidating queued requests
> 03:01:39 ptavv /kernel: ata0: resetting devices .. ad0: invalidating queued
> requests 03:01:39 ptavv /kernel: ad0: DMA limited to UDMA33, non-ATA66
> cable or device 03:01:39 ptavv /kernel: done
> 03:01:39 ptavv /kernel: ad0: READ command timeout tag=1 serv=0 - resetting
> 03:01:39 ptavv /kernel: ad0: invalidating queued requests
> 03:01:39 ptavv /kernel: ata0: resetting devices .. ad0: invalidating queued
> requests 03:01:39 ptavv /kernel: ad0: DMA limited to UDMA33, non-ATA66
> cable or device 03:01:39 ptavv /kernel: done
> 03:01:39 ptavv /kernel: ad0: no request for tag=1
> 03:01:39 ptavv /kernel: ad0: invalidating queued requests
> 03:01:49 ptavv /kernel: ad0: READ command timeout tag=0 serv=0 - resetting
> 03:01:49 ptavv /kernel: ad0: invalidating queued requests
> 03:01:49 ptavv /kernel: ata0: resetting devices .. ad0: invalidating queued
> requests 03:01:49 ptavv /kernel: ad0: DMA limited to UDMA33, non-ATA66
> cable or device 03:01:49 ptavv /kernel: done
> 03:01:49 ptavv /kernel: ad0: READ command timeout tag=0 serv=1 - resetting
> 03:01:49 ptavv /kernel: ad0: invalidating queued requests
> 03:01:49 ptavv /kernel: ata0: resetting devices .. ad0: invalidating queued
> requests 03:01:49 ptavv /kernel: ad0: DMA limited to UDMA33, non-ATA66
> cable or device 03:01:49 ptavv /kernel: done
> 03:01:49 ptavv /kernel: ad0: WRITE command timeout tag=3 serv=0 - resetting
> 03:01:49 ptavv /kernel: ad0: invalidating queued requests
> 03:01:49 ptavv /kernel: ata0: resetting devices .. ad0: invalidating queued
> requests 03:01:49 ptavv /kernel: ad0: DMA limited to UDMA33, non-ATA66
> cable or device 03:01:49 ptavv /kernel: done
> 03:01:49 ptavv /kernel: ad0: WRITE command timeout tag=2 serv=0 - resetting
> 03:01:49 ptavv /kernel: ad0: invalidating queued requests
> 03:01:49 ptavv /kernel: ata0: resetting devices .. ad0: invalidating queued
> requests 03:01:49 ptavv /kernel: ad0: DMA limited to UDMA33, non-ATA66
> cable or device 03:01:49 ptavv /kernel: done
> 03:01:49 ptavv /kernel: ad0: READ command timeout tag=1 serv=0 - resetting
> 03:01:49 ptavv /kernel: ad0: invalidating queued requests
> 03:01:49 ptavv /kernel: ata0: resetting devices .. ad0: invalidating queued
> requests 03:01:49 ptavv /kernel: ad0: DMA limited to UDMA33, non-ATA66
> cable or device 03:01:49 ptavv /kernel: done
> _______________________________________________
> freebsd-stable at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscribe at freebsd.org"

-- 
ian j hart

Quoth the raven, bite me!
	Salem Saberhagen (Episode LXXXI: The Phantom Menace)