Date: Fri, 11 Dec 1998 13:09:58 -0800 (PST) From: Tom Wadlow <wadlow@pilot.net> To: Matthew Jacob <mjacob@feral.com> Cc: scsi@FreeBSD.ORG Subject: Re: A problem with SCSI Message-ID: <Pine.GSO.4.05.9812111306310.7222-100000@arrow.pilot.net> In-Reply-To: <Pine.LNX.4.04.9812111239280.1719-100000@feral-gw>
next in thread | previous in thread | raw e-mail | index | archive | help
One more bit of info about this that I just discovered. I had installed 3.0-RELEASE on the A machine below, and it was dying occasionally with the "Invalidating pack" problem. Same thing for the B machine. So just now, in an attempt to build a stable platform, I tried to install 2.2.8-RELEASE on the A machine, and discovered that the 2.2.8 boot floppy cannot see the BusLogic SCSI controller, whereas the the 3.0 boot floppy can. So that seems to imply that the SCSI driver code has been updated in ways relevant to this problem between the 2 and 3 releases. --Tom On Fri, 11 Dec 1998, Matthew Jacob wrote: > Date: Fri, 11 Dec 1998 12:39:59 -0800 (PST) > From: Matthew Jacob <mjacob@feral.com> > To: Tom Wadlow <wadlow@pilot.net> > 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 <mjacob@feral.com> > > > To: Tom Wadlow <wadlow@pilot.net> > > > 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 <gibbs@narnia.plutotech.com> > > > > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.4.05.9812111306310.7222-100000>