From owner-freebsd-stable Fri Mar 23 13:25:11 2001 Delivered-To: freebsd-stable@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 5DE9737B718 for ; Fri, 23 Mar 2001 13:25:08 -0800 (PST) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f2NLP6s17840; Fri, 23 Mar 2001 14:25:06 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200103232125.f2NLP6s17840@aslan.scsiguy.com> To: "Brett G. Lemoine" Cc: freebsd-stable@freebsd.org Subject: Re: ahc - Invalidating pack In-Reply-To: Your message of "Fri, 23 Mar 2001 12:48:06 PST." <200103232048.MAA19814@blah.incyte.com> Date: Fri, 23 Mar 2001 14:25:06 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >> This looks like a device issue. From what the controller can tell, >> the jaz drive never re-selects us after taking a command and disconnecting. > >I had the same errors on my root drive (SEAGATE ST318404LW) too, I >just didn't get to capture it. I was only able to come to that conclusion by looking at all of the debugging output. It is hard to say that your problem was the same without having the full diagnostic output. >> You might be able to figure that out with a PCI bus analyzer and >> a SCSI bus analyzer. > >Well those are two items I've never seen, much less owned or know how to >use. Any suggestions on where I should go from here? Any way to get >additional information that might better pin down where the fault lies? If you can spare the system for a bit, you could ship it here and I could try to figure out what is wrong with it. I have both a PCI bus analyzer and a SCSI bus analyzer. Since the parity errors seem to coincide with sound output, I'm pretty sure that this is just broken hardware. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message