From owner-freebsd-scsi Tue Nov 14 22:22:34 1995 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id WAA20983 for freebsd-scsi-outgoing; Tue, 14 Nov 1995 22:22:34 -0800 Received: from flowbee.interaccess.com (jaykuri@flowbee.interaccess.com [198.80.0.32]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id WAA20974 for ; Tue, 14 Nov 1995 22:22:32 -0800 Received: (from jaykuri@localhost) by flowbee.interaccess.com (8.6.12/8.6.9) id AAA27593; Wed, 15 Nov 1995 00:12:49 -0600 Date: Wed, 15 Nov 1995 00:12:48 -0600 (CST) From: Jay Kuri To: Julian Elischer cc: freebsd-scsi@freebsd.org Subject: Re: Help! My SCSI-2 CD rom is timing out In-Reply-To: <199511140020.QAA25858@ref.tfs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk > if justin is happy with the versions of the aic driver you are using > then I suggest that you build a kernel with the SCSI_DEBUG option > (or is it SCSIDEBUG) (check LINT I thnk) > and thren under that kernel, set the debugging on htat device to > 15 then try access it as normal. > the resulting console output should be captured using dmesg and sent > back to us.. (on the scsi list..) I did as you said. I added the SCSIDEBUG in the kernel config, rebooted the system, and tried using the command 'scsi -f cd0a -d 15' to turn on debugging. Unfortunately all it did was time out again, this time on the scsi command. The dmesg follows: FreeBSD 2.1.0-951104-SNAP #0: Tue Nov 14 20:25:06 1995 jaykuri@jayshouse.iway.net:/usr/src/sys/compile/JAYSHOUSE.SCSI CPU: i486DX (486-class CPU) real memory = 16777216 (16384K bytes) avail memory = 15077376 (14724K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 10 maddr 0xcc000 msize 8192 on isa ed0: address 00:00:c0:6c:71:b5, type SMC8416C/SMC8416BT (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 520MB (1065456 sectors), 1057 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 814MB (1667232 sectors), 1654 cyls, 16 heads, 63 S/T, 512 B/S aic0 at 0x140-0x15f irq 11 on isa aic0 waiting for scsi devices to settle (aic0:1:0): "MEDIAVIS RENO CD-ROMX2A 2.04" type 5 removable SCSI 2 cd0(aic0:1:0): CD-ROM cd0(aic0:1:0): UNIT ATTENTION asc:28,0 cd0(aic0:1:0): Not ready to ready transition, medium may have changed cd present.[400000 x 2048 byte records] npx0 on motherboard npx0: INT 16 interface sb0 at 0x220 irq 5 drq 1 on isa sb0: sbxvi0 at 0x0 drq 5 on isa sbxvo0: sbmidi0 at 0x330 on isa opl0 at 0x388 on isa opl0: cd0(aic0:1:0): timed out cd0(aic0:1:0): timed out cd0(aic0:1:0): timed out cd0(aic0:1:0): timed out cd0(aic0:1:0): timed out cd0(aic0:1:0): timed out cd0(aic0:1:0): timed out cd0(aic0:1:0): timed out cd0(aic0:1:0): timed out # last line from scsi command cd0(aic0:1:0): timed out # first line from mount command cd0(aic0:1:0): MEDIUM ERROR asc:2,0 No seek complete cd0(aic0:1:0): ILLEGAL REQUEST asc:21,0 Logical block address out of range The only difference I saw between this and the last time was that this time when I first issued the 'scsi -f /dev/cd0a -d 15' after about 3 lines of 'cd0(aic0:1:0): timed out' I got the following message on the console, but it did not show in the dmesg: ioctl [SCIODEBUG]: Inappropriate ioctl for device I managed to kill some files last night and had to re-install the root-partition. I took the opportunity (if you could call it that) to upgrade to 2.1.0-951104-SNAP. So I am now running a stock 2.1 system. However, the problem persists. Here is the oddity: I managed to mount the cd once. It mounted and looked ok. I could access it. When I umounted it and tried to mount it again, it went back to the problem that I've described. Here is an additional oddity: a colleague of mine has a similar drive to mine (the same model, in fact) As a control I decided to try to mount his drive. When his drive was in the place of mine, it mounted right away. The difference I noticed was that when BSD probed the SCSI bus and reported the devices, it reported my drive as "MEDIAVIS RENO CD-ROMX2A 2.04" and reported my colleagues as "MEDIAVIS RENO CD-ROMX2A 1.03" I've also tried another of the same drives (the 2.04 type) and got the same problems. Thanks in advance for any help, Jay K.