Date: Wed, 30 Jun 1999 22:07:53 +0200 (CEST) From: Wilko Bulte <wilko@yedi.iaf.nl> To: jgreco@ns.sol.net (Joe Greco) Cc: ken@plutotech.com, scsi@FreeBSD.ORG Subject: Re: FreeBSD panics with Mylex DAC960SX Message-ID: <199906302007.WAA04041@yedi.iaf.nl> In-Reply-To: <199906301909.OAA85863@aurora.sol.net> from Joe Greco at "Jun 30, 1999 2: 9:12 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
As Joe Greco wrote ... > > > You're probably right about the device returning a size of zero. It isn't > > > immediately clear to me why the open routine would cause a panic, *unless* > > > the Mylex unit returns good status for the read capacity command, but > > > returns a capacity of 0. > > > > Although this definitely a bogus response I don't see the point in panic-ing > > the machine. An offensive message on the console, by all means. A panic? > > > > This remark assumes you are not booting from the raid of course :) > > Couldn't boot from it 'til it was ready (which it isn't, which leads to this > entire problem). > > Okay, anyways, ddb output. I really have no clue what I'm doing with the > kernel debugger so if I did anything stupid and you need other data, let me > know what to do. > > I put the camcontrol statement and then a fsck -p into root's .profile so > that it'd be a bit easier to manage this little show. > > changing root device to dda0 at ahc0 bus 0 target 0 lun 0 > da0: <SEAGATE ST34371W 0484> Fixed Direct Access SCSI-2 device > da0: 40.0MB/s transfers (20.0MHz, offset 15, 16bit), Tagged Queueing Enabled > da0: 4148MB (8496884 512 byte sectors: 255H 63S/T 528C) > a0s1a > da1 at ahc0 bus 0 target 1 lun 0 > da1: <MYLEX DAC960SX138928B5 4332> Fixed Direct Access SCSI-2 device > da1: 40.0MB/s transfers (20.0MHz, offset 16, 16bit), Tagged Queueing Enabled > da1: A > Enter full pathname of shell or RETURN for /bin/sh: > erase ^H, kill ^U, intr ^C > /sbin/camcontrol cmd -n da -u 1 -v -c 25 0 0 0 0 0 0 0 0 0 -i 8 i4 i4 > camcontrol: error sending command > (pass1:ahc0:0:1:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (pass1:ahc0:0:1:0): NOT READY > end of camcontrol > /dev/rda0s1a: cFILESYSTEM CLEANk; SKIPPING CHECKpS > 2% fragmentationlean, 127256 f1ree (296 frags, c15870 blocks, 0. > ) > > > Fatal trap 18: integer divide fault while in kernel mode Integer divide fault... hmm. I have this old DEC RRD42 cdrom drive that works just fine with 2.2.7 but panics a 3.1 install floppy with 'integer divide fault'. 100% repeatable too. On an Adaptec 1740 EISA card by the way. I'll drag it home tomorrow evening to see if it gives a similar traceback. Could be something completely different of course. But still. Wilko -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org 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?199906302007.WAA04041>