From owner-freebsd-scsi Fri Dec 11 22:37:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22756 for freebsd-scsi-outgoing; Fri, 11 Dec 1998 22:37:43 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail-oak-1.pilot.net (mail-oak-1.pilot.net [198.232.147.16]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA22749 for ; Fri, 11 Dec 1998 22:37:41 -0800 (PST) (envelope-from wadlow@pilot.net) Received: from corsair.pilot.net (corsair.pilot.net [204.48.17.12]) by mail-oak-1.pilot.net with ESMTP id WAA16939; Fri, 11 Dec 1998 22:37:31 -0800 (PST) Received: from arrow.pilot.net (arrow.pilot.net [204.48.17.29]) by corsair.pilot.net with ESMTP id WAA27603; Fri, 11 Dec 1998 22:37:31 -0800 (PST) Received: from localhost (wadlow@localhost) by arrow.pilot.net (arrow) with ESMTP id WAA09914; Fri, 11 Dec 1998 22:37:29 -0800 (PST) Date: Fri, 11 Dec 1998 22:37:29 -0800 (PST) From: Tom Wadlow To: Matthew Jacob cc: scsi@FreeBSD.ORG Subject: Re: A problem with SCSI In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org More info. I had two crashes, both with "Invalidating pack" and the following: (da0:bt0:0:0:0) CCB 0xf49e06c0 - timed out (da0:bt0:0:0:0) CCB 0xf49e0140 - timed out The machine froze after that so nothing else was printed or logged. --Tom On Fri, 11 Dec 1998, Matthew Jacob wrote: > Date: Fri, 11 Dec 1998 12:39:59 -0800 (PST) > From: Matthew Jacob > To: Tom Wadlow > Cc: scsi@FreeBSD.ORG > Subject: Re: A problem with SCSI > > > Invalidating pack can come about if a there's a I/O error on that drive. > That's what we're trying to gather info about. > > On Fri, 11 Dec 1998, Tom Wadlow wrote: > > > The ones that crashed said "Invalidating pack" and then died. The "tagged" messages were > > coming from the one that didn't crash, but was doing things that seemed odd to me (i.e. > > generating these tagged messages was new behavior. Sounds like it was just debugging info > > and not anything to worry about from your description). > > > > Also, the one that didn't crash is using an Adaptec SCSI controller (sorry, I just noticed > > that I forgot to include that in my earlier message). > > > > --tom > > > > On Fri, 11 Dec 1998, Matthew Jacob wrote: > > > > > Date: Fri, 11 Dec 1998 11:50:09 -0800 (PST) > > > From: Matthew Jacob > > > To: Tom Wadlow > > > Cc: scsi@FreeBSD.ORG > > > Subject: Re: A problem with SCSI > > > > > > > > > Any other messages when it crashed? The 'tagged openings' message is just > > > the process of throttling down the # of cmds outstanding per device.. > > > > > > > > > On Fri, 11 Dec 1998, Tom Wadlow wrote: > > > > > > > > > > > > Date: Fri, 11 Dec 1998 11:07:29 -0700 (MST) > > > > > From: Justin T. Gibbs > > > > > Subject: Re: A problem with SCSI > > > > > > > > > > > occasionally, the da driver says: "Invalidating pack", and drops > > > > > > the disk offline and everything hangs. This is unfortunate. > > > > > > > > > > Certainly is. What kind of hardware are you using (SCSI controller, > > > > > devices on the bus, CPU, etc.)? > > > > > > > > I've built out several systems from 3.0-RELEASE that all seeem to manifest this problem. > > > > Two die on a regular basis. The third gets strange messsages but seems to stay up. > > > > > > > > Machines dying with "Invalidating pack" > > > > A) Pentium 100MHz > > > > 64MB RAM > > > > BusLogic 496 SCSI controller > > > > 4GB Connor SCSI (only device on the SCSI chain) > > > > Ethernet > > > > Floppy > > > > > > > > B) Pentium 120MHz > > > > 96MB RAM > > > > BusLogic 496 SCSI controller > > > > 1GB Connor SCSI (only device on the SCSI chain) > > > > Ethernet > > > > Floppy > > > > > > > > Machine with strange messages: > > > > Pentium II 330 MHz > > > > 128MB RAM > > > > HP SCSI CDROM > > > > Seagate 4GB SCSI (boot device) > > > > Seagate 9GB SCSI > > > > Ethernet > > > > > > > > The strange messages this machine is getting look like this: > > > > > > > > (da0:ahc0:0:0:0): tagged openings now 64 > > > > (da0:ahc0:0:0:0): tagged openings now 63 > > > > (da1:ahc0:0:1:0): tagged openings now 64 > > > > (da1:ahc0:0:1:0): tagged openings now 63 > > > > (da1:ahc0:0:1:0): tagged openings now 62 > > > > (da1:ahc0:0:1:0): tagged openings now 61 > > > > (da1:ahc0:0:1:0): tagged openings now 60 > > > > (da1:ahc0:0:1:0): tagged openings now 59 > > > > (da1:ahc0:0:1:0): tagged openings now 58 > > > > (da1:ahc0:0:1:0): tagged openings now 57 > > > > (da1:ahc0:0:1:0): tagged openings now 56 > > > > (da1:ahc0:0:1:0): tagged openings now 55 > > > > (da1:ahc0:0:1:0): tagged openings now 54 > > > > (da1:ahc0:0:1:0): tagged openings now 53 > > > > (da1:ahc0:0:1:0): tagged openings now 52 > > > > (da1:ahc0:0:1:0): tagged openings now 51 > > > > (da1:ahc0:0:1:0): tagged openings now 50 > > > > (da1:ahc0:0:1:0): tagged openings now 49 > > > > > > > > but it hasn't crashed yet. Which is good, as this is my primary workstation. > > > > > > > > Machine B above has been updated to 3.0-CURRENT (as of last night), but still exhibits the > > > > problem. All are running the GENERIC kernel. > > > > > > > > --Tom > > > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-scsi" in the body of the message > > > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message