From owner-freebsd-scsi Sun Jul 15 4:44:45 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by hub.freebsd.org (Postfix) with ESMTP id 4A09737B401 for ; Sun, 15 Jul 2001 04:44:39 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from bde.zeta.org.au (bde.zeta.org.au [203.2.228.102]) by mailman.zeta.org.au (8.9.3/8.8.7) with ESMTP id VAA24872; Sun, 15 Jul 2001 21:44:28 +1000 Date: Sun, 15 Jul 2001 21:42:14 +1000 (EST) From: Bruce Evans X-Sender: bde@besplex.bde.org To: Peter Wemm Cc: mjacob@feral.com, Jim Bryant , scsi@FreeBSD.ORG Subject: Re: oddity with dump(8) or sa(4) in -current In-Reply-To: <20010714230005.14DC6380B@overcee.netplex.com.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, 14 Jul 2001, Peter Wemm wrote: > Matthew Jacob wrote: > > > > On Fri, 13 Jul 2001, Bruce Evans wrote: > > > > > On Thu, 12 Jul 2001, Matthew Jacob wrote: > > > > > > > On Thu, 12 Jul 2001, Jim Bryant wrote: > > > > > On a side note, what happened to the "raw" device nodes [/dev/*rsa*]? I > 'm guessing that the lack of "raw" nodes doesn't make a diff, > > > > > as /dev/*sa* are all character-mode devices. > > > > > > > > No, all devices are block devices now. Linux has no raw, FreeBSD has no > > > > cooked. Feh. > > > > > > No. No devices are block devices now (or yesterday; block devices > > > went away in 4.0). Linux has no character disk devices; FreeBSD has > > > no block disk devices. Feh. Tapes are a little different from disks. > > > > Really? I'll have to tell the ANSI SCSI committee! I understated a little. Tapes are more than a little different from disks. > He means *buffered* devices (aka block, using bdevsw, and the buffer cache) > went away. Raw devices (aka character, using cdevsw, but going direct to I really did mean block devices... > the device) are what we kept. Raw devices are accessible depending on the > backing device.. eg: must be block sized transfers/seeks/etc for things > like tapes/disks/etc, but can be any for things like frame buffers. > Buffered (block, cached) can be written on any size/alignment and can be > seeked for disks. We have not had the gross B_TAPE flag for some time that > was used to stop the buffer cache getting too creative with the tape > strategy routines (ie: doing random IO). > > Unix stat(2) calls raw devices "character" and buffered devices "block", > even though raw devices can be both block or byte addressable and > buffered devices enabled character/byte IO. :-) Hence the tangled up > terminology. There are only character-special and block-special devices for stat(2) and in POSIX. I intentionally didn't "raw" or "cooked" because those terms are fuzzy. "block" is not fuzzy; it is just sort of backwards as it applied to disks (the block devices were byte addressable but the non-block devices are only block addressable). Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Jul 15 15:47:27 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id F21CF37B403 for ; Sun, 15 Jul 2001 15:47:23 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6FMlHS07387; Sun, 15 Jul 2001 15:47:18 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Sun, 15 Jul 2001 15:47:01 -0700 (PDT) From: Matthew Jacob Reply-To: To: Jim Bryant Cc: Subject: Re: oddity with dump(8) or sa(4) in -current In-Reply-To: <3B4E2BE3.F92F44C6@yahoo.com> Message-ID: <20010715154021.O13069-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org The sa(4) driver is getting back toward usability it had a while back, but it's still got a long way to go. I'm not quite sure yet whether I've fixed your specific issue because I haven't done tape spanning yet. I have done some simple tests and it's now back to what it should have been. Fixed block tapes still have problems reading logical EOT, but that's been true for a while anyway. You can pick up the current scsi_sa if you want to try it from: http://people.freebsd.org/~mjacob/scsi_sa.c -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 16 7:56:37 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp1.sentex.ca (smtp1.sentex.ca [199.212.134.4]) by hub.freebsd.org (Postfix) with ESMTP id 4590F37B403 for ; Mon, 16 Jul 2001 07:56:29 -0700 (PDT) (envelope-from mike@sentex.net) Received: from simoeon.sentex.net (simeon.sentex.ca [209.112.4.47]) by smtp1.sentex.ca (8.11.2/8.11.1) with ESMTP id f6GEuIT32274 for ; Mon, 16 Jul 2001 10:56:18 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <5.1.0.14.0.20010716102020.031905d0@marble.sentex.ca> X-Sender: mdtpop@marble.sentex.ca X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Mon, 16 Jul 2001 10:50:11 -0400 To: scsi@freebsd.org From: Mike Tancsa Subject: SCSI timeout problems going from May23 to July13 kernel Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, A previously working system started to show problems with the tape drive since doing a make world. The may23 kernel worked great, but my Friday the 13th kernel is giving me problems on doing a backup. (yes, I was tempting fate! ;-)) The MFC seems to be from the 24th of June, so I doubt its an all pervasive bug. Is it just coincidence that my hardware is going bad ? May 23 17:26:23 backup2 /kernel: sa0 at ahc0 bus 0 target 0 lun 0 May 23 17:26:23 backup2 /kernel: sa0: Removable Sequential Access SCSI-2 device May 23 17:26:23 backup2 /kernel: sa0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) Jul 13 10:33:44 backup2 /kernel: ahc0: port 0xe000-0xe0ff mem 0xeb201000-0xeb201fff irq 11 at dev ice 13.0 on pci0 Jul 13 10:33:44 backup2 /kernel: sa0 at ahc0 bus 0 target 0 lun 0 Jul 13 10:33:44 backup2 /kernel: sa0: Removable Sequential Access SCSI-2 device Jul 13 10:33:44 backup2 /kernel: sa0: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): SCB 0x9 - timed out while idle, SEQADDR == 0x8 Jul 16 09:31:20 backup2 /kernel: STACK == 0x3, 0x181, 0x16b, 0x0 Jul 16 09:31:20 backup2 /kernel: SXFRCTL0 == 0x80 Jul 16 09:31:20 backup2 /kernel: ahc0: Dumping Card State at SEQADDR 0x8 Jul 16 09:31:20 backup2 /kernel: SCSISEQ = 0x12, SBLKCTL = 0xa, SSTAT0 0x0 Jul 16 09:31:20 backup2 /kernel: SCB count = 20 Jul 16 09:31:20 backup2 /kernel: Kernel NEXTQSCB = 14 Jul 16 09:31:20 backup2 /kernel: Card NEXTQSCB = 14 Jul 16 09:31:20 backup2 /kernel: QINFIFO entries: Jul 16 09:31:20 backup2 /kernel: Waiting Queue entries: Jul 16 09:31:20 backup2 /kernel: Disconnected Queue entries: 0:9 Jul 16 09:31:20 backup2 /kernel: QOUTFIFO entries: Jul 16 09:31:20 backup2 /kernel: Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Jul 16 09:31:20 backup2 /kernel: Pending list: 9 Jul 16 09:31:20 backup2 /kernel: Kernel Free SCB list: 15 16 17 18 19 0 1 2 3 4 5 6 7 8 13 12 11 10 Jul 16 09:31:20 backup2 /kernel: Untagged Q(0): 9 Jul 16 09:31:20 backup2 /kernel: sg[0] - Addr 0x73af000 : Length 4096 Jul 16 09:31:20 backup2 /kernel: sg[1] - Addr 0x74f0000 : Length 4096 Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): Queuing a BDR SCB Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): Bus Device Reset Message Sent Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): no longer in timeout, status = 34b Jul 16 09:31:20 backup2 /kernel: ahc0: Bus Device Reset on A:0. 1 SCBs aborted Jul 16 09:31:21 backup2 /kernel: (sa0:ahc0:0:0:0): unable to rewind after test read Jul 16 09:35:40 backup2 /kernel: (sa0:ahc0:0:0:0): SCB 0x9 - timed out while idle, SEQADDR == 0x8 Jul 16 09:35:40 backup2 /kernel: STACK == 0x3, 0x181, 0x16b, 0xf4 Jul 16 09:35:40 backup2 /kernel: SXFRCTL0 == 0x80 Jul 16 09:35:40 backup2 /kernel: ahc0: Dumping Card State at SEQADDR 0x8 Jul 16 09:35:40 backup2 /kernel: SCSISEQ = 0x12, SBLKCTL = 0xa, SSTAT0 0x0 Jul 16 09:35:40 backup2 /kernel: SCB count = 20 Jul 16 09:35:40 backup2 /kernel: Kernel NEXTQSCB = 14 Jul 16 09:35:40 backup2 /kernel: Card NEXTQSCB = 14 Jul 16 09:35:40 backup2 /kernel: QINFIFO entries: Jul 16 09:35:40 backup2 /kernel: Waiting Queue entries: Jul 16 09:35:40 backup2 /kernel: Disconnected Queue entries: 0:9 Jul 16 09:35:40 backup2 /kernel: QOUTFIFO entries: Jul 16 09:35:40 backup2 /kernel: Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Jul 16 09:35:40 backup2 /kernel: Pending list: 9 Jul 16 09:35:40 backup2 /kernel: Kernel Free SCB list: 15 16 17 18 19 0 1 2 3 4 5 6 7 8 13 12 11 10 Jul 16 09:35:40 backup2 /kernel: Untagged Q(0): 9 Jul 16 09:35:40 backup2 /kernel: sg[0] - Addr 0x73af000 : Length 4096 Jul 16 09:35:40 backup2 /kernel: sg[1] - Addr 0x74f0000 : Length 4096 Jul 16 09:35:40 backup2 /kernel: (sa0:ahc0:0:0:0): Queuing a BDR SCB Jul 16 09:35:40 backup2 /kernel: (sa0:ahc0:0:0:0): Bus Device Reset Message Sent Jul 16 09:35:40 backup2 /kernel: (sa0:ahc0:0:0:0): no longer in timeout, status = 34b Jul 16 09:35:40 backup2 /kernel: ahc0: Bus Device Reset on A:0. 1 SCBs aborted Jul 16 09:35:41 backup2 /kernel: (sa0:ahc0:0:0:0): unable to rewind after test read Jul 16 09:40:00 backup2 /kernel: (sa0:ahc0:0:0:0): SCB 0xe - timed out while idle, SEQADDR == 0x8 Jul 16 09:40:00 backup2 /kernel: STACK == 0x3, 0x181, 0x16b, 0xf4 Jul 16 09:40:00 backup2 /kernel: SXFRCTL0 == 0x80 Jul 16 09:40:00 backup2 /kernel: ahc0: Dumping Card State at SEQADDR 0x8 Jul 16 09:40:00 backup2 /kernel: SCSISEQ = 0x12, SBLKCTL = 0xa, SSTAT0 0x0 Jul 16 09:40:00 backup2 /kernel: SCB count = 20 Jul 16 09:40:00 backup2 /kernel: Kernel NEXTQSCB = 9 Jul 16 09:40:00 backup2 /kernel: Card NEXTQSCB = 9 Jul 16 09:40:00 backup2 /kernel: QINFIFO entries: Jul 16 09:40:00 backup2 /kernel: Waiting Queue entries: Jul 16 09:40:00 backup2 /kernel: Disconnected Queue entries: 0:14 Jul 16 09:40:00 backup2 /kernel: QOUTFIFO entries: Jul 16 09:40:00 backup2 /kernel: Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Jul 16 09:40:00 backup2 /kernel: Pending list: 14 Jul 16 09:40:00 backup2 /kernel: Kernel Free SCB list: 15 16 17 18 19 0 1 2 3 4 5 6 7 8 13 12 11 10 Jul 16 09:40:00 backup2 /kernel: Untagged Q(0): 14 Jul 16 09:40:00 backup2 /kernel: sg[0] - Addr 0x73af000 : Length 4096 Jul 16 09:40:00 backup2 /kernel: sg[1] - Addr 0x74f0000 : Length 4096 Jul 16 09:40:00 backup2 /kernel: (sa0:ahc0:0:0:0): Queuing a BDR SCB Jul 16 09:40:00 backup2 /kernel: (sa0:ahc0:0:0:0): Bus Device Reset Message Sent Jul 16 09:40:00 backup2 /kernel: (sa0:ahc0:0:0:0): no longer in timeout, status = 34b Jul 16 09:40:00 backup2 /kernel: ahc0: Bus Device Reset on A:0. 1 SCBs aborted Jul 16 09:40:01 backup2 /kernel: (sa0:ahc0:0:0:0): unable to rewind after test read Jul 16 10:16:08 backup2 /kernel: (sa0:ahc0:0:0:0): SCB 0xe - timed out while idle, SEQADDR == 0x8 Jul 16 10:16:08 backup2 /kernel: STACK == 0x3, 0x181, 0x16b, 0xf4 Jul 16 10:16:08 backup2 /kernel: SXFRCTL0 == 0x80 Jul 16 10:16:08 backup2 /kernel: ahc0: Dumping Card State at SEQADDR 0x8 Jul 16 10:16:08 backup2 /kernel: SCSISEQ = 0x12, SBLKCTL = 0xa, SSTAT0 0x0 Jul 16 10:16:08 backup2 /kernel: SCB count = 20 Jul 16 10:16:08 backup2 /kernel: Kernel NEXTQSCB = 9 Jul 16 10:16:08 backup2 /kernel: Card NEXTQSCB = 9 Jul 16 10:16:08 backup2 /kernel: QINFIFO entries: Jul 16 10:16:08 backup2 /kernel: Waiting Queue entries: Jul 16 10:16:08 backup2 /kernel: Disconnected Queue entries: 0:14 Jul 16 10:16:08 backup2 /kernel: QOUTFIFO entries: Jul 16 10:16:08 backup2 /kernel: Sequencer Free SCB List: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 Jul 16 10:16:08 backup2 /kernel: Pending list: 14 Jul 16 10:16:08 backup2 /kernel: Kernel Free SCB list: 15 16 17 18 19 0 1 2 3 4 5 6 7 8 13 12 11 10 Jul 16 10:16:08 backup2 /kernel: Untagged Q(0): 14 Jul 16 10:16:08 backup2 /kernel: sg[0] - Addr 0x73af000 : Length 4096 Jul 16 10:16:08 backup2 /kernel: sg[1] - Addr 0x74f0000 : Length 4096 Jul 16 10:16:08 backup2 /kernel: (sa0:ahc0:0:0:0): Queuing a BDR SCB Jul 16 10:16:08 backup2 /kernel: (sa0:ahc0:0:0:0): Bus Device Reset Message Sent Jul 16 10:16:08 backup2 /kernel: (sa0:ahc0:0:0:0): no longer in timeout, status = 34b Jul 16 10:16:08 backup2 /kernel: ahc0: Bus Device Reset on A:0. 1 SCBs aborted Jul 16 10:16:09 backup2 /kernel: (sa0:ahc0:0:0:0): unable to rewind after test read To try and bring things back to sanity, I did a camcontrol reset scsi0 ---Mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 16 9: 9:12 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id F257C37B401 for ; Mon, 16 Jul 2001 09:09:08 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f6GG95U69942; Mon, 16 Jul 2001 10:09:06 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200107161609.f6GG95U69942@aslan.scsiguy.com> To: Mike Tancsa Cc: scsi@FreeBSD.ORG Subject: Re: SCSI timeout problems going from May23 to July13 kernel In-Reply-To: Your message of "Mon, 16 Jul 2001 10:50:11 EDT." <5.1.0.14.0.20010716102020.031905d0@marble.sentex.ca> Date: Mon, 16 Jul 2001 10:09:05 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): SCB 0x9 - timed out >while idle, SEQADDR == 0x8 ... >Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): Queuing a BDR SCB >Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): Bus Device Reset Message >Sent >Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): no longer in timeout, >status = 34b >Jul 16 09:31:20 backup2 /kernel: ahc0: Bus Device Reset on A:0. 1 SCBs aborted >Jul 16 09:31:21 backup2 /kernel: (sa0:ahc0:0:0:0): unable to rewind after >test read I wonder if the timeouts are now too short for your tape drive? Matt may have more ideas. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 16 9:29:40 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id C1CEB37B411 for ; Mon, 16 Jul 2001 09:29:35 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6GGTRS15851; Mon, 16 Jul 2001 09:29:27 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Mon, 16 Jul 2001 09:29:09 -0700 (PDT) From: Matthew Jacob Reply-To: To: Mike Tancsa Cc: Subject: Re: SCSI timeout problems going from May23 to July13 kernel In-Reply-To: <200107161609.f6GG95U69942@aslan.scsiguy.com> Message-ID: <20010716092359.F96667-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Timeouts were lengthened, not shortened recently. This looks like it timed out on the test read in samount...... that's a four (4) minute timeout. The tape driver is very broken in a lot of ways. Use the scsi_sa.c that's on my web page on freebsd.org (http://people.freebsd.org/~mjacob/scsi_sa.c) with a CAMDEBUG kernel that has camcontrol -Ic N:0:0 (you'll have to supply the N for the ordinal bus number the tape is on) and ship me the output. -matt On Mon, 16 Jul 2001, Justin T. Gibbs wrote: > >Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): SCB 0x9 - timed out > >while idle, SEQADDR == 0x8 > > ... > > >Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): Queuing a BDR SCB > >Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): Bus Device Reset Message > >Sent > >Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): no longer in timeout, > >status = 34b > >Jul 16 09:31:20 backup2 /kernel: ahc0: Bus Device Reset on A:0. 1 SCBs aborted > >Jul 16 09:31:21 backup2 /kernel: (sa0:ahc0:0:0:0): unable to rewind after > >test read > > I wonder if the timeouts are now too short for your tape drive? Matt > may have more ideas. > > -- > Justin > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Jul 16 9:45:42 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id EE15337B403 for ; Mon, 16 Jul 2001 09:45:37 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f6GGjWS16158; Mon, 16 Jul 2001 09:45:33 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Mon, 16 Jul 2001 09:45:14 -0700 (PDT) From: Matthew Jacob Reply-To: To: Jim Bryant Cc: Subject: an example of tape breakage still... Message-ID: <20010716093605.O96667-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org EOM handling, even in my patched driver, is still broken: nellie.feral.com > tape_pattern_tester -v -b 32k -f /dev/nsa0 .......Rewind Tape ........Write Pass End of File 15 (524288000 total bytes written) End of File 31 (1048576000 total bytes written) End of File 47 (1572864000 total bytes written) End of File 63 (2097152000 total bytes written) End of File 79 (2621440000 total bytes written) End of File 95 (3145728000 total bytes written) End of File 111 (3670016000 total bytes written) End of File 127 (4194304000 total bytes written) End of File 143 (4718592000 total bytes written) End of File 159 (5242880000 total bytes written) End of File 175 (5767168000 total bytes written) End of File 191 (6291456000 total bytes written) End of File 207 (6815744000 total bytes written) End of File 223 (7340032000 total bytes written) End of File 239 (7864320000 total bytes written) End of File 255 (8388608000 total bytes written) End of File 271 (8912896000 total bytes written) End of File 287 (9437184000 total bytes written) End of File 303 (9961472000 total bytes written) write: Input/output error EOT at File 306 Record 500 Offset 0 (10043392000 total bytes written) Elapsed Seconds: 6175; Data Rate: 1.55109MB/s .......Rewind Tape .........Read Pass End of File 15 (524288000 total bytes read) End of File 31 (1048576000 total bytes read) End of File 47 (1572864000 total bytes read) End of File 63 (2097152000 total bytes read) End of File 79 (2621440000 total bytes read) End of File 95 (3145728000 total bytes read) End of File 111 (3670016000 total bytes read) End of File 127 (4194304000 total bytes read) End of File 143 (4718592000 total bytes read) End of File 159 (5242880000 total bytes read) End of File 175 (5767168000 total bytes read) End of File 191 (6291456000 total bytes read) End of File 207 (6815744000 total bytes read) End of File 223 (7340032000 total bytes read) End of File 239 (7864320000 total bytes read) End of File 255 (8388608000 total bytes read) End of File 271 (8912896000 total bytes read) End of File 287 (9437184000 total bytes read) End of File 303 (9961472000 total bytes read) EOT at File 307 Record 0 Offset 0 (10043424768 total bytes read) Elapsed Seconds: 5218: Data Rate: 1.83557MB/s -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Jul 19 20:14: 5 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.vkpc.com (cr1004613-a.rct1.bc.wave.home.com [24.113.38.121]) by hub.freebsd.org (Postfix) with SMTP id 050BE37B405 for ; Thu, 19 Jul 2001 20:14:02 -0700 (PDT) (envelope-from danny@vkpc.com) Received: (qmail 1671 invoked from network); 20 Jul 2001 03:13:56 -0000 Received: from unknown (HELO dyoo) (192.168.1.10) by cr1004613-a.rct1.bc.wave.home.com with SMTP; 20 Jul 2001 03:13:56 -0000 From: "Danny Yoo" To: Subject: Illegal cable configuration?? (SCSI, new install of FreeBSD) Date: Thu, 19 Jul 2001 20:14:55 -0700 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I'm trying to set up FreeBSD 4.3-RELEASE on an old IBM PC Server 330 (Pentium Pro 200). It's got an on-board Adaptec 7880 SCSI controller, and I've only got two SCSI devices inside: a Quantum HD and an IBM CD-ROM. My problem is that when the system boots up with mfsroot.flp (boot disk #2) AFTER the kernel configuration, I get a message akin to: ahc0: Illegal cable configuration!! Only two connectors on the adapter may be used at a time! And then a few lines later it hangs at: "Waiting 15 seconds for SCSI devices to settle" Now, the system is currently running Corel Linux just fine; I can access the HD and CD-ROM without a hitch. I'm _pretty_ sure that the SCSI connections are properly terminated (this is my first time using a SCSI system)... I say that solely based on the fact that Corel works just fine. I'd assume that an ill-configured SCSI system would create noticeable problems right away? I'm not sure what the system means by: "Only two connectors on the adapter may be used at a time!" The external connector isn't used and the external termination jumper is set (I've tried it in both positions); only the internal connector cable is used which connects first to the HD then to the CD-ROM. I've tried reversing the order, I've tried disconnecting the CD-ROM from the system to no avail. I've looked through the BIOS for "auto-termination/hardware-termination" options (suggested in an archive posting) but my system apparently does not have such a feature. I'm sorry if the specifications of my problem is too vague; I'll gladly try to offer more information if it is needed. I have spent about 1.5 hours searching google and the digest archives; one other person had the EXACT same problem as I did, but the only person to respond to him told him that he should post to this list (I guess he was posting somewhere else). (I've posted this to freebsd-questions/newbies and they suggested I try here. Please CC replies directly to me as I am not a list subscriber.) Much thanks in advance, Danny Yoo To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 21 8: 2:48 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from gate.qubesoft.com (gate.qubesoft.com [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id 2774237B405; Sat, 21 Jul 2001 08:02:43 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from bluebottle.qubesoft.com (bluebottle [192.168.1.2]) by gate.qubesoft.com (8.11.3/8.11.3) with ESMTP id f6LF2fh66406; Sat, 21 Jul 2001 16:02:42 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from builder03 (dhcp139.qubesoft.com [192.168.1.139]) by bluebottle.qubesoft.com (8.11.4/8.11.4) with SMTP id f6LF2fI26014; Sat, 21 Jul 2001 16:02:41 +0100 (BST) (envelope-from n_hibma@qubesoft.com) From: "Nick Hibma" To: , , Subject: RE: USB/umass in addition to "other" SCSI Date: Sat, 21 Jul 2001 16:02:41 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4522.1200 Importance: Normal In-Reply-To: <20010705192240.DEF1437B406@hub.freebsd.org> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org You will be sheer out of luck with those card readers. So far I don't think any of them are supported. They all do their own thing. Linux supports a few of them I think, but no one has ported the driver across. Nick -----Original Message----- From: owner-freebsd-scsi@FreeBSD.ORG [mailto:owner-freebsd-scsi@FreeBSD.ORG]On Behalf Of lists@mediumgreen.com Sent: 05 July 2001 16:22 To: freebsd-scsi@FreeBSD.ORG; dakota@FreeBSD.ORG Subject: Re: USB/umass in addition to "other" SCSI I think I heard Andrew Gordon say: >On Wed, 4 Jul 2001, Kenneth W Cochran wrote: > >> Hello -scsi: >> >> How do I "connect" a USB "disk" when I already have a SCSI >> HBA & other peripherals installed & operating? What great timing for this discussion.. I've been trying to get a compact flash reader working on my machine at home for a couple of days. >It should appear of its own accord when usbd sees it. However, this >doesn't appear to work properly at present. I've attached the device before startup and have noticed some usbd messages when I remove and reinstall it. Jul 4 22:06:22 blueberry /kernel: ugen0: at uhub0 port 2 (addr 3) disconnected Jul 4 22:06:22 blueberry /kernel: ugen0: detached Jul 4 22:06:26 blueberry /kernel: ugen0: SIIG DigiFilm-Combo Reader, rev 1.00/0.01, addr 3 blueberry# usbdevs addr 1: UHCI root hub, VIA addr 2: Microsoft IntelliMouse® Optical, Microsoft addr 3: DigiFilm-Combo Reader, SIIG >> And what will >> (should :) be its device-name (in /dev)? > >/dev/daX* where X is the next available number By the above output, I figured that da3 is what I'd use, but it does seem to work (FWIW, I've tired da[0-4]): blueberry# mount -t msdos /dev/da3s1 /mnt msdos: /dev/da3s1: Device not configured blueberry# camcontrol devlist at scbus0 target 2 lun 0 (pass0,cd0) at scbus0 target 4 lun 0 (pass1,sa0) at scbus0 target 4 lun 1 (pass2,ch0) >> & "camcontrol rescan 1" gives >> me an ioctl() error. > >I haven't found a method that works other than to have the device present >at boot time. Had it present at boot. Have everything that seems relevant in my kernel.... # SCSI peripherals device scbus # SCSI bus (required) device da # Direct Access (disks) device sast of options # Sequential Access (tape etc) device cdalso present i# CD device pass # Passthrough device (direct SCSI access) # USB support device uhci # UHCI PCI->USB interface device ohci # OHCI PCI->USB interface device usb # USB Bus (required) device ugen # Generic device uhid # "Human Interface Devices" device ukbd # Keyboard device ulpt # Printer device umass # Disks/Mass storage - Requires scbus and da device ums # Mouse Is there anything I've forgotten? -matthew To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 21 8: 8: 9 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from gate.qubesoft.com (gate.qubesoft.com [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id 0B69F37B405 for ; Sat, 21 Jul 2001 08:08:06 -0700 (PDT) (envelope-from n_hibma@FreeBSD.ORG) Received: from bluebottle.qubesoft.com (bluebottle [192.168.1.2]) by gate.qubesoft.com (8.11.3/8.11.3) with ESMTP id f6LF85h66438; Sat, 21 Jul 2001 16:08:05 +0100 (BST) (envelope-from n_hibma@FreeBSD.ORG) Received: from localhost (localhost [127.0.0.1]) by bluebottle.qubesoft.com (8.11.4/8.11.4) with ESMTP id f6LF84I26110; Sat, 21 Jul 2001 16:08:04 +0100 (BST) (envelope-from n_hibma@FreeBSD.ORG) Date: Sat, 21 Jul 2001 16:08:04 +0100 (BST) From: Nick Hibma X-X-Sender: To: Kenneth W Cochran Cc: Subject: Re: USB/umass in addition to "other" SCSI In-Reply-To: <200107041422.KAA21945@world.std.com> Message-ID: <20010721160322.L25714-100000@bluebottle> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > How do I "connect" a USB "disk" when I already have a SCSI > HBA & other peripherals installed & operating? And what will > (should :) be its device-name (in /dev)? > > USB devices in this case can be a ZIP-250 USB and/or a USB > digital camera (which mounts just fine in Linux 2.4.x & is > seen as a MS-DOS filesystem). > > Umass, scbus, da & pass are configured into the running kernel. > OS is RELENG_4 as of 1 July. > > "Camcontrol rescan 0" doesn't show it(?) But I'm thinking > this will be a different bus(?) & "camcontrol rescan 1" gives > me an ioctl() error. If you have other SCSI hardware in your system, the USB umass driver might not be bus 0, but bus 1. Do a camcontrol devlist -v to see what's where. If the device is recognized by the umass driver it 'should' appear as daX with X either 0 or the number of SCSI drives in the system + 1. > I'm guessing that I should probably "wire down" my devices > (or at least the USB one?) in my kernel config, but before I > do that I could use some input from Someone Who Know More > About This Than I(tm). :) That, & I'm not sure about the > kernel-config syntax for this... Don't wire things down unless the order the kernel decides things should be in is wrong. But as you seem to be able to boot fine, that is not the case. Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 21 8: 9:53 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from gate.qubesoft.com (gate.qubesoft.com [212.113.16.243]) by hub.freebsd.org (Postfix) with ESMTP id 8CC8937B405 for ; Sat, 21 Jul 2001 08:09:50 -0700 (PDT) (envelope-from n_hibma@qubesoft.com) Received: from bluebottle.qubesoft.com (bluebottle [192.168.1.2]) by gate.qubesoft.com (8.11.3/8.11.3) with ESMTP id f6LF9nh66451; Sat, 21 Jul 2001 16:09:49 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Received: from localhost (localhost [127.0.0.1]) by bluebottle.qubesoft.com (8.11.4/8.11.4) with ESMTP id f6LF9nI26143; Sat, 21 Jul 2001 16:09:49 +0100 (BST) (envelope-from n_hibma@qubesoft.com) Date: Sat, 21 Jul 2001 16:09:49 +0100 (BST) From: Nick Hibma X-X-Sender: To: Andrew Gordon Cc: Kenneth W Cochran , Subject: Re: USB/umass in addition to "other" SCSI In-Reply-To: <20010704181957.G65863-100000@server.arg.sj.co.uk> Message-ID: <20010721160811.Y25714-100000@bluebottle> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > > How do I "connect" a USB "disk" when I already have a SCSI > > HBA & other peripherals installed & operating? > > It should appear of its own accord when usbd sees it. However, this > doesn't appear to work properly at present. usbd doesn't handle umass (anymore). > > & "camcontrol rescan 1" gives > > me an ioctl() error. > > I haven't found a method that works other than to have the device present > at boot time. Hm, it should work at any time (as in, I use the umass driver as a module that I load (including CAM as a module) at runtime, then connect and disconnect the device many a time and that works. Could you describe to me in which cases it does not work? Nick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 21 12:17:16 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sgi04-e.std.com (sgi04-e.std.com [199.172.62.134]) by hub.freebsd.org (Postfix) with ESMTP id 81AF837B401; Sat, 21 Jul 2001 12:17:13 -0700 (PDT) (envelope-from kwc@world.std.com) Received: from world.std.com (world-f.std.com [199.172.62.5]) by sgi04-e.std.com (8.9.3/8.9.3) with ESMTP id PAA16953626; Sat, 21 Jul 2001 15:17:12 -0400 (EDT) Received: (from kwc@localhost) by world.std.com (8.9.3/8.9.3) id PAA08777; Sat, 21 Jul 2001 15:17:11 -0400 (EDT) Date: Sat, 21 Jul 2001 15:17:11 -0400 (EDT) From: Kenneth W Cochran Message-Id: <200107211917.PAA08777@world.std.com> To: Nick Hibma Subject: Re: USB/umass in addition to "other" SCSI Cc: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >From n_hibma@FreeBSD.ORG Sat Jul 21 11:08:08 2001 >Date: Sat, 21 Jul 2001 16:08:04 +0100 (BST) >To: Kenneth W Cochran >cc: >Subject: Re: USB/umass in addition to "other" SCSI > >> How do I "connect" a USB "disk" when I already have a SCSI >> HBA & other peripherals installed & operating? And what will >> (should :) be its device-name (in /dev)? >> >> USB devices in this case can be a ZIP-250 USB and/or a USB >> digital camera (which mounts just fine in Linux 2.4.x & is >> seen as a MS-DOS filesystem). >> >> Umass, scbus, da & pass are configured into the running kernel. >> OS is RELENG_4 as of 1 July. >> >> "Camcontrol rescan 0" doesn't show it(?) But I'm thinking >> this will be a different bus(?) & "camcontrol rescan 1" gives >> me an ioctl() error. > >If you have other SCSI hardware in your system, the USB >umass driver might not be bus 0, but bus 1. Do a > > camcontrol devlist -v > >to see what's where. Did that; hw (Iomega Zip-250) still didn't show up... (?) >If the device is recognized by the umass driver it 'should' >appear as daX with X either 0 or the number of SCSI drives >in the system + 1. It did indeed do that after I started usbd. I hadn't been running that before... >> I'm guessing that I should probably "wire down" my devices >> (or at least the USB one?) in my kernel config, but before I >> do that I could use some input from Someone Who Know More >> About This Than I(tm). :) That, & I'm not sure about the >> kernel-config syntax for this... > >Don't wire things down unless the order the kernel decides >things should be in is wrong. But as you seem to be able to >boot fine, that is not the case. Makes sense... >Nick -kc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 21 12:17:48 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sgi04-e.std.com (sgi04-e.std.com [199.172.62.134]) by hub.freebsd.org (Postfix) with ESMTP id 447FA37B406 for ; Sat, 21 Jul 2001 12:17:45 -0700 (PDT) (envelope-from kwc@world.std.com) Received: from world.std.com (world-f.std.com [199.172.62.5]) by sgi04-e.std.com (8.9.3/8.9.3) with ESMTP id PAA17052299; Sat, 21 Jul 2001 15:17:42 -0400 (EDT) Received: (from kwc@localhost) by world.std.com (8.9.3/8.9.3) id PAA09061; Sat, 21 Jul 2001 15:17:41 -0400 (EDT) Date: Sat, 21 Jul 2001 15:17:41 -0400 (EDT) From: Kenneth W Cochran Message-Id: <200107211917.PAA09061@world.std.com> To: Nick Hibma Subject: Re: USB/umass in addition to "other" SCSI Cc: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >From n_hibma@qubesoft.com Sat Jul 21 11:09:53 2001 >Date: Sat, 21 Jul 2001 16:09:49 +0100 (BST) >To: Andrew Gordon >cc: Kenneth W Cochran , >Subject: Re: USB/umass in addition to "other" SCSI > >> > How do I "connect" a USB "disk" when I already have a SCSI >> > HBA & other peripherals installed & operating? >> >> It should appear of its own accord when usbd sees it. However, this >> doesn't appear to work properly at present. > >usbd doesn't handle umass (anymore). Huh? It does for me(!) No usbd, no zip250 recognition; yes usbd, yes zip250... OS is 4.3-stable as of 15 July 2001. >> > & "camcontrol rescan 1" gives >> > me an ioctl() error. >> >> I haven't found a method that works other than to have the device present >> at boot time. > >Hm, it should work at any time (as in, I use the umass >driver as a module that I load (including CAM as a module) >at runtime, then connect and disconnect the device many a >time and that works. Could you describe to me in which >cases it does not work? > >Nick & with usbd running, connect zip250 & then "camcontrol rescan ..." works just fine... What's Still Not Working is an Olympus USB digital camera. It is supposed to appear as a SCSI device with a MS-DOS filesystem (& indeed does with Linux, with kernel 2.4.x). Try that with FreeBSD & not only does it not "mount" but it crashes (freezes) the OS, without even so much as a panic/dump/trace. :( -kc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Jul 21 16:52:40 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (Postfix) with ESMTP id B40B837B401 for ; Sat, 21 Jul 2001 16:52:30 -0700 (PDT) (envelope-from arg@arg1.demon.co.uk) Received: by arg1.demon.co.uk (Postfix, from userid 300) id E118E9B07; Sun, 22 Jul 2001 00:52:23 +0100 (BST) Received: from localhost (localhost [127.0.0.1]) by arg1.demon.co.uk (Postfix) with ESMTP id D35915D21; Sun, 22 Jul 2001 00:52:23 +0100 (BST) Date: Sun, 22 Jul 2001 00:52:23 +0100 (BST) From: Andrew Gordon X-X-Sender: To: Nick Hibma Cc: Kenneth W Cochran , Subject: Re: USB/umass in addition to "other" SCSI In-Reply-To: <20010721160811.Y25714-100000@bluebottle> Message-ID: <20010722000136.Q54613-100000@server.arg.sj.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Sat, 21 Jul 2001, Nick Hibma wrote: > > > How do I "connect" a USB "disk" when I already have a SCSI > > > HBA & other peripherals installed & operating? > > > > It should appear of its own accord when usbd sees it. However, this > > doesn't appear to work properly at present. > > usbd doesn't handle umass (anymore). Do you mean that it's now interrupt driven, or are you just drawing a distinction between "usbd the program" and "the kernel thread supervised by usbd"? > > I haven't found a method that works other than to have the device present > > at boot time. > > Hm, it should work at any time (as in, I use the umass driver as a > module that I load (including CAM as a module) at runtime, then connect > and disconnect the device many a time and that works. Could you describe > to me in which cases it does not work? This is a 4.3-stable system, world and kernel sources last updated about 2 days ago (though it's behaved the same for as long as I've been using this drive). All of the USB drivers are compiled-in to the kernel rather than being loaded as KLDs. With the drive connected at boot time (doesn't matter if there's any media in the drive), it appears thus: ohci0: mem 0xe2103000-0xe2103fff irq 9 at device 7.4 on pci0 usb0: OHCI version 1.0, legacy support usb0: SMM does not respond, resetting usb0: on ohci0 usb0: USB revision 1.0 uhub0: AMD OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered ukbd0: Belkin Components USB-PS2 Adapter , rev 1.10/1.20, addr 2, iclass 3/1 kbd1 at ukbd0 ums0: Belkin Components USB-PS2 Adapter , rev 1.10/1.20, addr 2, iclass 3/1 ums0: 5 buttons and Z dir. umass0: Fuji Photo Film SmartMedia R/W, rev 1.00/1.00, addr 3 umass0: Get Max Lun not supported (STALLED) ....snip non-USB devices... da1 at umass-sim0 bus 0 target 0 lun 0 da1: Removable Direct Access SCSI-2 device da1: 650KB/s transfers da1: 62MB (128000 512 byte sectors: 64H 32S/T 62C) This configuration goes on to work fine; you can insert/eject media, mount filesystems, read/write etc. with no problems. In this state, camcontrol reports: rocket(root)# camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus1 target 0 lun 0 (pass1,da1) rocket(root)# camcontrol rescan 1 Re-scan of bus 1 was successful rocket(root)# camcontrol devlist at scbus0 target 0 lun 0 (pass0,da0) at scbus1 target 0 lun 0 (pass1,da1) rocket(root)# If I boot without the drive connected, and then plug it in (again, doesn't matter if there's any media in the drive), the console shows: umass0: Fuji Photo Film SmartMedia R/W, rev 1.00/1.00, addr 3 umass0: Get Max Lun not supported (STALLED) In this state, "camcontrol devlist" shows: at scbus0 target 0 lun 0 (pass0,da0) at scbus1 target 0 lun 0 (probe0) If I then attempt a "camcontrol rescan 1", the camcontrol process blocks forever waiting on "cbwait". If I disconnect the drive (whether or not I tried to do anything with it after plugging in), a panic results. If the system was booted with the drive connected, and it is then disconnected/reconnected, the devlist again shows the "(probe0)" and it doesn't work, but instead of the panic some errors get logged: Jul 22 00:39:22 rocket /kernel: umass0: BBB reset failed, TIMEOUT Jul 22 00:39:27 rocket /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Jul 22 00:39:32 rocket /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT Jul 22 00:39:37 rocket /kernel: umass0: BBB reset failed, TIMEOUT Jul 22 00:39:42 rocket /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Jul 22 00:39:47 rocket /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT Jul 22 00:39:52 rocket /kernel: umass0: BBB reset failed, TIMEOUT Jul 22 00:39:57 rocket /kernel: umass0: BBB bulk-in clear stall failed, TIMEOUT Jul 22 00:40:02 rocket /kernel: umass0: BBB bulk-out clear stall failed, TIMEOUT Jul 22 00:40:02 rocket syslogd: exiting on signal 15 The dump from the panic shows the following (I've kept the dump if you want to see any more from it): IdlePTD 3792896 initial pcb at 305c00 panicstr: page fault panic messages: --- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x0 fault code = supervisor read, page not present instruction pointer = 0x8:0xc021cc0d stack pointer = 0x10:0xc02bb744 frame pointer = 0x10:0xc02bb764 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio trap number = 12 panic: page fault syncing disks... Fatal trap 12: page fault while in kernel mode fault virtual address = 0x30 fault code = supervisor read, page not present instruction pointer = 0x8:0xc01fb4e0 stack pointer = 0x10:0xc02bb56c frame pointer = 0x10:0xc02bb574 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio trap number = 12 panic: page fault Uptime: 1m8s dumping to dev #da/0x20001, offset 1785984 dump 127 126 125 124 123 122 121 120 119 118 117 116 115 114 113 112 111 110 109 108 107 106 105 104 103 102 101 100 99 98 97 96 95 94 93 92 91 90 89 88 87 86 85 84 83 82 81 80 79 78 77 76 75 74 73 72 71 70 69 68 67 66 65 64 63 62 61 60 59 58 57 56 55 54 53 52 51 50 49 48 47 46 45 44 43 42 41 40 39 38 37 36 35 34 33 32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1 0 --- #0 dumpsys () at ../../kern/kern_shutdown.c:472 472 if (dumping++) { (kgdb) where #0 dumpsys () at ../../kern/kern_shutdown.c:472 #1 0xc0155597 in boot (howto=260) at ../../kern/kern_shutdown.c:312 #2 0xc0155914 in poweroff_wait (junk=0xc02b466f, howto=0) at ../../kern/kern_shutdown.c:559 #3 0xc0275b29 in trap_fatal (frame=0xc02bb52c, eva=48) at ../../i386/i386/trap.c:951 #4 0xc0275801 in trap_pfault (frame=0xc02bb52c, usermode=0, eva=48) at ../../i386/i386/trap.c:844 #5 0xc02753eb in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = 0, tf_esi = -1060317440, tf_ebp = -1070877324, tf_isp = -1070877352, tf_ebx = -1070792452, tf_edx = 6865472, tf_ecx = -919424256, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1071663904, tf_cs = 8, tf_eflags = 66050, tf_esp = -1060317440, tf_ss = -1060317440}) at ../../i386/i386/trap.c:443 #6 0xc01fb4e0 in acquire_lock (lk=0xc02d00fc) at ../../ufs/ffs/ffs_softdep.c:271 #7 0xc01ff550 in softdep_update_inodeblock (ip=0xc0ccd700, bp=0xc34cc2a4, waitfor=0) at ../../ufs/ffs/ffs_softdep.c:3775 #8 0xc01fa7b9 in ffs_update (vp=0xc932b300, waitfor=0) at ../../ufs/ffs/ffs_inode.c:106 #9 0xc0202874 in ffs_sync (mp=0xc0c3e800, waitfor=2, cred=0xc0731900, p=0xc031d100) at ../../ufs/ffs/ffs_vfsops.c:988 #10 0xc01842b7 in sync (p=0xc031d100, uap=0x0) at ../../kern/vfs_syscalls.c:545 #11 0xc015534a in boot (howto=256) at ../../kern/kern_shutdown.c:233 #12 0xc0155914 in poweroff_wait (junk=0xc02b466f, howto=0) at ../../kern/kern_shutdown.c:559 #13 0xc0275b29 in trap_fatal (frame=0xc02bb704, eva=0) at ../../i386/i386/trap.c:951 #14 0xc0275801 in trap_pfault (frame=0xc02bb704, usermode=0, eva=0) ---Type to continue, or q to quit--- at ../../i386/i386/trap.c:844 #15 0xc02753eb in trap (frame={tf_fs = 16, tf_es = 16, tf_ds = 16, tf_edi = -1059803776, tf_esi = 0, tf_ebp = -1070876828, tf_isp = -1070876880, tf_ebx = -1059803776, tf_edx = -1060261576, tf_ecx = -1059803776, tf_eax = 0, tf_trapno = 12, tf_err = 0, tf_eip = -1071526899, tf_cs = 8, tf_eflags = 66118, tf_esp = -1059803776, tf_ss = -1059803776}) at ../../i386/i386/trap.c:443 #16 0xc021cc0d in usbd_transfer (xfer=0xc0d4ad80) at ../../dev/usb/usbdi.c:285 #17 0xc0225673 in umass_setup_ctrl_transfer (sc=0xc0d53000, udev=0xc0cd7da0, req=0xc0d53076, buffer=0x0, buflen=0, flags=0, xfer=0xc0d4ad80) at ../../dev/usb/umass.c:1049 #18 0xc02256e5 in umass_clear_endpoint_stall (sc=0xc0d53000, endpt=2, pipe=0xc0cc1c00, state=9, xfer=0xc0d4ad80) at ../../dev/usb/umass.c:1082 #19 0xc0225cf1 in umass_bbb_state (xfer=0xc0d4ae00, priv=0xc0d53000, err=USBD_IOERROR) at ../../dev/usb/umass.c:1513 #20 0xc021d387 in usb_transfer_complete (xfer=0xc0d4ae00) at ../../dev/usb/usbdi.c:839 #21 0xc021a4e5 in ohci_process_done (sc=0xc0729000, done=130123200) at ../../dev/usb/ohci.c:1248 #22 0xc021a262 in ohci_intr1 (sc=0xc0729000) at ../../dev/usb/ohci.c:1065 #23 0xc021a155 in ohci_intr (p=0xc0729000) at ../../dev/usb/ohci.c:994 (kgdb) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message