From owner-freebsd-scsi Wed Jun 30 14:28:16 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id D7A39156F4 for ; Wed, 30 Jun 1999 14:28:09 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id XAA13173; Wed, 30 Jun 1999 23:05:34 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id WAA04041; Wed, 30 Jun 1999 22:07:53 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199906302007.WAA04041@yedi.iaf.nl> Subject: Re: FreeBSD panics with Mylex DAC960SX In-Reply-To: <199906301909.OAA85863@aurora.sol.net> from Joe Greco at "Jun 30, 1999 2: 9:12 pm" To: jgreco@ns.sol.net (Joe Greco) Date: Wed, 30 Jun 1999 22:07:53 +0200 (CEST) Cc: ken@plutotech.com, scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org 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: 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: 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