From owner-freebsd-bugs Sun Dec 12 20:30: 8 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id 733F314D95 for ; Sun, 12 Dec 1999 20:30:04 -0800 (PST) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id UAA75213; Sun, 12 Dec 1999 20:30:04 -0800 (PST) (envelope-from gnats@FreeBSD.org) Date: Sun, 12 Dec 1999 20:30:04 -0800 (PST) Message-Id: <199912130430.UAA75213@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: "Kenneth D. Merry" Subject: Re: kern/15447: Seagate ST32550 (Barracuda 2LP) may be a broken tagged queueing drive? Reply-To: "Kenneth D. Merry" Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/15447; it has been noted by GNATS. From: "Kenneth D. Merry" To: klh@netcom.com Cc: freebsd-gnats-submit@FreeBSD.ORG Subject: Re: kern/15447: Seagate ST32550 (Barracuda 2LP) may be a broken tagged queueing drive? Date: Sun, 12 Dec 1999 21:29:20 -0700 On Sun, Dec 12, 1999 at 06:40:28PM -0800, klh@netcom.com wrote: > A separate problem is causing my system to sometimes boot up with > tagged queueing enabled and sometimes not. I've recently been stressing > the disk significantly more than usual and have encountered user-level > I/O errors that I traced back to the enabling of tagged queueing. > > With tagged queueing off, everything always works. With it on, > a heavy load of seeks will cause reads and writes to start failing. > I was able to verify this by running a test case on two ST32550s, both > on line during the same kernel boot and both identical in all respects > except that one had tagged queueing enabled and the other didn't (the > randomness of this enabling is a separate problem). The drive without > tagging always works perfectly; the drive with tagging always fails > at random places during the test. I verified that it is not specific > to the individual drives by doing reboots until the formerly tag-enabled > drive booted up tag-disabled -- whereupon it then performed perfectly > again. I also verified that the filesystems were identical by doing > a complete track-by-track copy of one to the other prior to testing. > > The ST32550 is not in the latest quirks table in cam_xtp.c, although > several other Seagates are. The Barracuda 2LP was at one time fairly > popular so I'm a little surprised this hasn't shown up before, but > who knows. Maybe most FreeBSD users have IDE drives. No, there are many, many people using Seagate drives (including me) successfully in FreeBSD systems. I think this problem is most likely peculiar to your particular system and/or drives. > >Fix: > Obviously the ST32550 can be added to the quirks table in cam_xtp.c. > I just hope this does not reflect some underlying problem with > tagged queueing support of Seagates in general. Nope, it reflects a problem either with your drives or your cabling and termination setup. You need to supply some more information before we can make any sort of guess at what is going on. So, please send (and make sure you do a "group" reply to this mail, so it winds up in the PR database) full 'dmesg' output from your system, including any kernel messages that have shown up while doing your tests. Please don't send the output of /var/log/messages, unless it is necessary to show problems that happened in a previous boot. The output of dmesg(8) is easier to read. Also, please send a description of your cabling and termination setup. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message