Date: Mon, 24 Jan 2000 16:04:34 +0100 From: Jeroen Ruigrok/Asmodai <asmodai@wxs.nl> To: scsi@freebsd.org Subject: Need some real good advice to track this problem down Message-ID: <20000124160434.D691@daemon.ninth-circle.org>
next in thread | raw e-mail | index | archive | help
As Kenneth (and probably Matthew or Justin) might remember, I had some trouble with unexpected busfrees about a year ago. I have been having them every once in a while since I wasn't that clued on SCSI, I have now been doing some reading up on the subject and present some information on which I need some expert help. This is an `old' system, back from 1996. The mainboard is a Diamond Flow, Inc. (DFI) board G185IPV - rev C+, which has 96 MB in SIMMs, a Pentium 200MMX (which is not overclocked). Two NICs (ep0 and fxp0), a Tseng vidcard, an AWE-32 and that's it basically. The host controller is an AHC2940UW from 1996. The BIOS version was 1.23, and I flashed it (successfully) to 2.20 last night. This is not an OEM card, but a real original Adaptec card. I have had the problems with both versions of the BIOS. The SCSI layout is as fllows: | The length of this cable is 1.35 meters and has 6 connectors |--------|-------|-------|-------|------| (Narrow (50-pins) bus) | 39 cm 24 24 24 24 AHC| | 50 cm 20 |------------------|-------------------| (Wide (68-pins) bus) | The length of this one is 70 cm and has three connectors On the narrow bus we have: [from card to outer device] AHC----disk1----disk2-----cdrom----empty------term AHC = AHC2940UW disk1 = da0 at ahc0 bus 0 target 0 lun 0 da0: <QUANTUM FIREBALL_TM3200S 300X> Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 3067MB (6281856 512 byte sectors: 255H 63S/T 391C) Verified that no jumpers are set to termination. disk2 = da1 at ahc0 bus 0 target 1 lun 0 da1: <QUANTUM FIREBALL SE6.4S PJ0A> Fixed Direct Access SCSI-2 device da1: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da1: 6149MB (12594960 512 byte sectors: 255H 63S/T 784C) Verified that no jumpers are set to termination. The cdrom = cd0 at ahc0 bus 0 target 5 lun 0 cd0: <SONY CD-ROM CDU-415 1.1i> Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present Verified that no jumpers are set to termination. It does have a jumper on allow/prevent (which I still don't know what it is) and Parity (which I believe is necessary). Then one empty connector and then followed by an _active_ terminator. (Which I bought on Kenneth's advice I think after he mentioned that cdrom drives sometimes suck with their termination.) On the wide bus we have: [from card to outer device] AHC---------disk3-------disk4 AHC=the same as above disk3 = da2 at ahc0 bus 0 target 2 lun 0 da2: <SEAGATE ST39173W 6244> Fixed Direct Access SCSI-2 device da2: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da2: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) This drive has absolutely _no_ jumpers set. disk4 = da3 at ahc0 bus 0 target 4 lun 0 da3: <SEAGATE ST32171W 0484> Fixed Direct Access SCSI-2 device da3: 40.000MB/s transfers (20.000MHz, offset 8, 16bit), Tagged Queueing Enabled da3: 2047MB (4194057 512 byte sectors: 255H 63S/T 261C) This drive has Term Enable, Term From Drive and Term To Bus set. I was getting these messages randomly over time: Jan 14 11:37:44 daemon /kernel: Unexpected busfree. LASTPHASE == 0x40 Jan 14 11:37:44 daemon /kernel: SEQADDR == 0x110 Jan 14 11:38:12 daemon /kernel: Unexpected busfree. LASTPHASE == 0x40 Jan 14 11:38:13 daemon /kernel: SEQADDR == 0x110 Jan 22 13:42:55 daemon /kernel: Unexpected busfree in Data-out phase Jan 22 13:42:55 daemon /kernel: SEQADDR == 0x112 Jan 22 13:43:23 daemon /kernel: Unexpected busfree in Data-out phase Jan 22 13:43:23 daemon /kernel: SEQADDR == 0x112 Jan 22 13:45:04 daemon /kernel: Unexpected busfree in Data-out phase Jan 22 13:45:04 daemon /kernel: SEQADDR == 0x112 Jan 23 19:33:24 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:33:25 daemon /kernel: SEQADDR == 0x113 Jan 23 19:34:11 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:34:11 daemon /kernel: SEQADDR == 0x112 Jan 23 19:34:49 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:34:50 daemon /kernel: SEQADDR == 0x112 Jan 23 19:35:47 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:35:47 daemon /kernel: SEQADDR == 0x113 Jan 23 19:36:15 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:36:16 daemon /kernel: SEQADDR == 0x112 Jan 23 19:46:55 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:46:56 daemon /kernel: SEQADDR == 0x112 Jan 23 19:47:25 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:47:25 daemon /kernel: SEQADDR == 0x112 Jan 23 19:47:57 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:47:57 daemon /kernel: SEQADDR == 0x113 Jan 23 19:48:46 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:48:47 daemon /kernel: SEQADDR == 0x113 Jan 23 19:49:23 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:49:24 daemon /kernel: SEQADDR == 0x79 Jan 23 19:49:52 daemon /kernel: Unexpected busfree in Data-in phase Jan 23 19:49:52 daemon /kernel: SEQADDR == 0x113 I then wanted to test the new BIOS v2.20 and decided on rawio on da3 which is empty, so I did a rawio -a /dev/da3: Jan 24 15:07:37 daemon /kernel: Unexpected busfree in Data-in phase Jan 24 15:07:38 daemon /kernel: SEQADDR == 0x112 Jan 24 15:07:50 daemon /kernel: Unexpected busfree in Data-in phase Jan 24 15:07:50 daemon /kernel: SEQADDR == 0x112 Jan 24 15:08:01 daemon /kernel: Unexpected busfree in Data-in phase Jan 24 15:08:02 daemon /kernel: SEQADDR == 0x113 Jan 24 15:08:02 daemon /kernel: (da3:ahc0:0:4:0): Invalidating pack Jan 24 15:08:13 daemon /kernel: Unexpected busfree in Data-in phase Jan 24 15:08:13 daemon /kernel: SEQADDR == 0x112 Jan 24 15:08:24 daemon /kernel: Unexpected busfree in Data-in phase Jan 24 15:08:25 daemon /kernel: SEQADDR == 0x113 Jan 24 15:08:25 daemon /kernel: (da3:ahc0:0:4:0): Invalidating pack Jan 24 15:08:25 daemon /kernel: (da3:ahc0:0:4:0): Synchronize cache failed, status == 0x4a, scsi status == 0x0 I also tried changing the AHC2940UW with a spare AHC2940U2W, but I get the same problems. I hope this is enough information, please let me know if I need to test other things. I really want to know what on earth I am doing wrong here. -- Jeroen Ruigrok vd W/Asmodai asmodai@[wxs.nl|bart.nl|freebsd.org] Documentation nutter/B-rated Coder BSD: Technical excellence at its best The BSD Programmer's Documentation Project <http://home.wxs.nl/~asmodai>; I accept that some things will never change, I've let your tiny minds magnify my agony... 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?20000124160434.D691>