From owner-freebsd-stable@FreeBSD.ORG Sat Mar 29 11:41:28 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6744237B401 for ; Sat, 29 Mar 2003 11:41:28 -0800 (PST) Received: from pc2-cove3-6-cust88.brhm.cable.ntl.com (pc2-cove3-6-cust88.brhm.cable.ntl.com [81.107.10.88]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FC5643F85 for ; Sat, 29 Mar 2003 11:41:27 -0800 (PST) (envelope-from ianjhart@ntlworld.com) Received: from alpha.private.lan (alpha.private.lan [192.168.0.2]) id h2TJetDb012941; Sat, 29 Mar 2003 19:40:55 GMT (envelope-from ianjhart@ntlworld.com) From: ian j hart To: "Kevin Oberman" , stable@freebsd.org Date: Sat, 29 Mar 2003 19:40:55 +0000 User-Agent: KMail/1.5 References: <20030329184236.71A3C69@ptavv.es.net> In-Reply-To: <20030329184236.71A3C69@ptavv.es.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200303291940.55250.ianjhart@ntlworld.com> cc: sos%sos@spider.deepcore.dk Subject: Re: Status of ATA tagging in Stable X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 29 Mar 2003 19:41:36 -0000 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@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@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org" -- ian j hart Quoth the raven, bite me! Salem Saberhagen (Episode LXXXI: The Phantom Menace)