Date: Sun, 4 Apr 1999 12:46:40 -0500 (CDT) From: Igor Roshchin <igor@physics.uiuc.edu> To: scottd@cloud9.net (Scott Drassinower) Cc: gladiatr@sunflower.com, patseal@hyperhost.net, freebsd-questions@FreeBSD.ORG, freebsd-stable@FreeBSD.ORG Subject: Re: no active SCB; BUS DEVICE RESET Message-ID: <199904041746.MAA17537@alecto.physics.uiuc.edu> In-Reply-To: <Pine.BSF.4.10.9904040019590.20524-100000@earl-grey.cloud9.net> from "Scott Drassinower" at "Apr 4, 1999 0:25:59 am"
next in thread | previous in thread | raw e-mail | index | archive | help
I have seen similar behaviour with (ahc0:0:0): "QUANTUM TRB850S 0405" type 0 fixed SCSI 2 in combination with Adaptec 2940UW, but that was yet with the 2.1-STABLE I am not sure how relevant it is to the current problem, but at that time I was told that it was due to imperfect driver for the ahc (which was fixed since that - somewhere in 2.2.x), and/or due ot a "bad" combination of 2940 with Quantum HDD, where the later was not responding correctly at times - when the i/o was at high level. Igor > > I see the same problem with a pair of Quantum Viking II U2W disks on an > Adaptec controller. The notices seem to be less frequent with 3.1-RELEASE > than 3.0, but are still there. > > It could be that Quantum has updated firmware for these beasts, but I > wonder if there is something in the ahc0 driver that might be a little > wacky. This is the 7890 chipset on an Asus P2B board of some sort. > > -- > Scott M. Drassinower scottd@cloud9.net > Cloud 9 Consulting, Inc. White Plains, NY > +1 914 696-4000 http://www.cloud9.net > > On Sat, 3 Apr 1999, SDS wrote: > > > On Sat, 3 Apr 1999, Patrick Seal wrote: > > > > > da0: <MICROP 3243-19 1128RA 28RA> Fixed Direct Access SCSI-2 device > > > da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing > > > Enabled > > > da0: 4095MB (8388315 512 byte sectors: 255H 63S/T 522C) > > > > > > > Patrick, > > > > Yup. Gotta love it. Feel ripped off yet? I had a Micropolis 2 GB drive > > that had the same problem. It's the firmware. And there's nothing that > > can be done as Micropolis is no longer (as you undoubtedly know). This > > problem is not OS or architecture specific. I tried the damned thing in a > > SPARC, with different SCSI controllers, a Windows 95 machine (!!!) and > > finally ended up dumping it in an old 286 w/ an old ISA controller > > running DOS (and it will still periodically crash). At least FreeBSD offers > > some diagnostic messages (the others would just lock up) > > > > It seems that this drive cannot handle dis/reconnects properly. I fought > > with my drive for 2 years. Save your strength... > > > > Regards, > > Stephen > > > > Don't worry about the future. Stephen Spencer > > Or worry, but understand that worrying Lawrence, KS > > is about as effective as trying to solve gladiatr@sunflower.com > > an algebra equation by chewing bubble gum. -lee perry > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-stable" in the body of the message > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-stable" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904041746.MAA17537>