From owner-freebsd-scsi Mon Feb 12 18:32:24 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id SAA23456 for freebsd-scsi-outgoing; Mon, 12 Feb 1996 18:32:24 -0800 (PST) Received: from Aspen.Woc.Atinc.COM (aspen.woc.atinc.com [198.138.38.205]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA23439 for ; Mon, 12 Feb 1996 18:32:10 -0800 (PST) Received: (from root@localhost) by Aspen.Woc.Atinc.COM (8.6.12/8.6.9) id VAA02053; Mon, 12 Feb 1996 21:32:08 -0500 Date: Mon, 12 Feb 1996 21:32:07 -0500 (EST) From: Charlie ROOT X-Sender: root@Aspen.Woc.Atinc.COM Reply-To: jmb@freebsd.org To: freebsd-scsi@freebsd.org Subject: ncr.c | anaconda | cdrom changer bug Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk my second scsi bus dies if dump reaches the end of a tape and i abort the dump. the ncr scsi driver now report errors for each scsi operation. i an using an archive anaconda QIC-1305 tape drive and dump. (boot dmesg output at end, with kernel config file) i have SCSIDEBUG and superscsi in the kernel, so i can provide more data as requested. scsi chain: sc200 card----nakamichi---archive---fujitsu 1GB harddrive ncr 53c810 7 cdrom anaconda changer qic tape target: 7 0 4 6 luns: 0-6 none none dump process: DUMP: 49.01% done, finished in 0:10 DUMP: End of tape detected DUMP: Closing /dev/rst0.2 DUMP: Change Volumes: Mount volume #2 DUMP: Is the new volume mounted and ready to go?: ("yes" or "no") DUMP: Is the new volume mounted and ready to go?: ("yes" or "no") DUMP: Do y ou want to abort?: ("yes" or "no") DUMP: The ENTIRE dump is aborted. so i did an "mt -f /dev/rst0 rewoffl" the tape was ejected. resulting dmesg output: ncr1:4: ERROR (80:140) (8-2a-0) (0/13) @ (544:900b0000). script cmd = 910a0000 reg: da 10 80 13 47 00 04 1f 01 08 84 2a 80 00 0a 00. ncr1: handshake timeout ncr1: restart (scsi reset). st0(ncr1:4:0): COMMAND FAILED (6 ff) @f068b200. st0(ncr1:4:0): UNIT ATTENTION st0(ncr1:4:0): NOT READY st0(ncr1:4:0): NOT READY ncr1:4: ERROR (80:140) (8-2a-0) (0/13) @ (544:900b0000). script cmd = 910a0000 reg: da 10 80 13 47 00 04 1f 01 08 04 2a 80 00 0a 00. ncr1: handshake timeout ncr1: restart (scsi reset). st0(ncr1:4:0): COMMAND FAILED (6 ff) @f068b200. then i tried to mount a cdrom: (mount -t cd9660 /dev/cd6c /mnt) the mount failed: "cd9660: /dev/cd6c: Input/output error" cd6(ncr1:0:6): asynchronous. cd6(ncr1:0:6): UNIT ATTENTION asc:29,0 cd6(ncr1:0:6): Power on, reset, or bus device reset occurred ncr1:0: ERROR (80:140) (8-2a-0) (e0/13) @ (544:900b0000). script cmd = 910a0000 reg: da 10 80 13 47 e0 00 1f 01 08 04 2a 80 00 0a 00. ncr1: handshake timeout ncr1: restart (scsi reset). cd6(ncr1:0:6): COMMAND FAILED (6 ff) @f068b600. cd6(ncr1:0:6): asynchronous. inserted a tape into the drive, which accepted the tape. then did another "mt -f /dev/rst0 rewoffl" producing this output: ncr1:4: ERROR (80:140) (8-2a-0) (0/13) @ (544:900b0000). script cmd = 910a0000 reg: da 10 80 13 47 00 04 1f 01 08 04 2a 80 00 0a 00. ncr1: handshake timeout ncr1: restart (scsi reset). st0(ncr1:4:0): COMMAND FAILED (6 ff) @f068b200. the tape was ejected. the cdrom changer sounds as if it changed cdroms! the archive anaconda tape drive chatters/buzzes as if it is resetting ?? the only other item on this scsi chain is a fujitsu 1GB drive. trying to mount causes: Aspen:[69] mount /dev/sd2e /mnt /dev/sd2e on /mnt: Operation not permitted Aspen:[70] id uid=0(root) gid=0(wheel) groups=0(wheel), 2(kmem), 3(sys), 4(tty), 5(operator), 20(staff), 31(guest) and in dmesg: st0(ncr1:4:0): COMMAND FAILED (6 ff) @f068b200. sd2(ncr1:6:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. sd2(ncr1:6:0): UNIT ATTENTION asc:29,0 sd2(ncr1:6:0): Power on, reset, or bus device reset occurred , retries:2 sd2s1: type 0xa5, start 62, end = 2131187, size 2131126 : OK WARNING: R/W mount of /usr denied. Filesystem is not clean - run fsck. this scsi bus is unusable till reboot. ;( Jonathan M. Bresler FreeBSD Postmaster jmb@FreeBSD.ORG play go. ride bike. hack FreeBSD.--ah the good life i am moving to a new job. PLEASE USE: jmb@FreeBSD.ORG boot time dmesg output: syncing disks... done Rebooting... FreeBSD 2.1-STABLE #0: Sun Feb 11 18:07:54 EST 1996 jmb@Aspen.Woc.Atinc.COM:/home/sup/src/sys/compile/ASPEN CPU: i486DX (486-class CPU) real memory = 16777216 (16384K bytes) avail memory = 15069184 (14716K bytes) Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A sio2 not found at 0x3e8 sio3 not found at 0x2e8 lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 not found at 0xffffffff fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 not found at 0x1f0 ep0 not found at 0x300 npx0 on motherboard npx0: INT 16 interface Probing for devices on the PCI bus: chip0 rev 4 on pci0:0 ncr0 rev 2 int a irq 9 on pci0:1 (ncr0:0:0): "DEC DSP3053LS X442" type 0 fixed SCSI 2 sd0(ncr0:0:0): Direct-Access sd0(ncr0:0:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 511MB (1046532 512 byte sectors) (ncr0:1:0): "FUJITSU M1606S-512 6220" type 0 fixed SCSI 2 sd1(ncr0:1:0): Direct-Access sd1(ncr0:1:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1041MB (2131992 512 byte sectors) chip1 rev 3 on pci0:2 vga0 rev 0 on pci0:4 ncr1 rev 1 int a irq 11 on pci0:5 (ncr1:0:0): "NRC MBR-7 110" type 5 removable SCSI 2 cd0(ncr1:0:0): CD-ROM cd0(ncr1:0:0): asynchronous. cd0(ncr1:0:0): NOT READY asc:4,1 cd0(ncr1:0:0): Logical unit is in process of becoming ready can't get the size (ncr1:0:1): "NRC MBR-7 110" type 5 removable SCSI 2 cd1(ncr1:0:1): CD-ROM cd1(ncr1:0:1): asynchronous. cd1(ncr1:0:1): NOT READY asc:4,1 cd1(ncr1:0:1): Logical unit is in process of becoming ready can't get the size (ncr1:0:2): "NRC MBR-7 110" type 5 removable SCSI 2 cd2(ncr1:0:2): CD-ROM cd2(ncr1:0:2): asynchronous. cd2(ncr1:0:2): NOT READY asc:4,1 cd2(ncr1:0:2): Logical unit is in process of becoming ready can't get the size (ncr1:0:3): "NRC MBR-7 110" type 5 removable SCSI 2 cd3(ncr1:0:3): CD-ROM cd3(ncr1:0:3): asynchronous. cd present.[326402 x 2048 byte records] (ncr1:0:4): "NRC MBR-7 110" type 5 removable SCSI 2 cd4(ncr1:0:4): CD-ROM cd4(ncr1:0:4): asynchronous. cd present.[269574 x 2048 byte records] (ncr1:0:5): "NRC MBR-7 110" type 5 removable SCSI 2 cd5(ncr1:0:5): CD-ROM cd5(ncr1:0:5): asynchronous. cd present.[300158 x 2048 byte records] (ncr1:0:6): "NRC MBR-7 110" type 5 removable SCSI 2 cd6(ncr1:0:6): CD-ROM cd6(ncr1:0:6): asynchronous. cd present.[160790 x 2048 byte records] (ncr1:4:0): "ARCHIVE ANCDA 2750 28077 -003" type 1 removable SCSI 1 st0(ncr1:4:0): Sequential-Access density code 0x0, drive empty (ncr1:6:0): "FUJITSU M1606S-512 6234" type 0 fixed SCSI 2 sd2(ncr1:6:0): Direct-Access sd2(ncr1:6:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. 1041MB (2131992 512 byte sectors) kernel config file: # # ASPEN # # machine "i386" cpu "I486_CPU" ident ASPEN maxusers 10 options INET #InterNETworking options FFS #Berkeley Fast Filesystem options PROCFS #Process filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options UCONSOLE #X Console support options "FAT_CURSOR" #block cursor in syscons or pccons # options "SCSI_DELAY=15" #Be pessimistic about Joe SCSI device options "NCONS=4" #4 virtual consoles options USERCONFIG #Allow user configuration with -c options "COMPAT_43" #Compatible with BSD 4.3 # options BOUNCE_BUFFERS #include support for DMA bounce buffers options PROBE_VERBOSE #get all pci bus data options COMPAT_LINUX options SYSVSHM options SYSVSEM options SYSVMSG options "IBCS2" # options MAXMEM= options SCSIDEBUG config kernel root on sd1 swap on sd1 and sd0 dumps on sd1 controller isa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 # tape ft0 at fdc0 drive 2 controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller ncr0 #Only need one of these, the memory allocation grows controller scbus0 device sd0 device sd1 device sd2 device sd3 device st0 device st1 device cd0 #Only need one of these, the code dynamically grows device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr device npx0 at isa? port "IO_NPX" irq 13 vector npxintr device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr device sio2 at isa? port "IO_COM3" tty irq 5 vector siointr device sio3 at isa? port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr device lpt1 at isa? port? tty device ep0 at isa? port 0x300 net irq 10 vector epintr pseudo-device loop pseudo-device ether pseudo-device log pseudo-device sl 2 # # ijppp uses tun instead of ppp device # pseudo-device tun 2 pseudo-device pty 16 pseudo-device speaker pseudo-device gzip # Exec gzipped a.out's pseudo-device bpfilter 4 pseudo-device superscsi From owner-freebsd-scsi Tue Feb 13 12:46:42 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id MAA06394 for freebsd-scsi-outgoing; Tue, 13 Feb 1996 12:46:42 -0800 (PST) Received: from jjarray.umd.edu (jjarray.umd.edu [129.2.40.99]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id MAA06388 Tue, 13 Feb 1996 12:46:40 -0800 (PST) Received: (from fcawth@localhost) by jjarray.umd.edu (8.7.3/8.6.12) id PAA00282; Tue, 13 Feb 1996 15:46:39 -0500 (EST) From: Fred Cawthorne Message-Id: <199602132046.PAA00282@jjarray.umd.edu> Subject: Exabyte 8200 To: freebsd-hardware@freebsd.org Date: Tue, 13 Feb 1996 15:46:38 -0500 (EST) Cc: freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4 PL24 ME8a] Content-Type: text Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk I have just upgraded the firmware in my Exabyte 8200 drive to a newer version, and now it at least works with FreeBSD-current... The problem is that it is streaming very slowly. It isn't stopping and going, but it only writes about 60-80 K/second. I have heard that people use this drive, and I wanted to know if there are any special modes to select or anything. Do people ever get resonable speeds with this drive?? I know this thing is old but it seems that it should be able to write a 2 gig tape in under 6 hours... Any information would be appreciated... Fred. From owner-freebsd-scsi Tue Feb 13 14:06:51 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id OAA11758 for freebsd-scsi-outgoing; Tue, 13 Feb 1996 14:06:51 -0800 (PST) Received: from luke.pmr.com (luke.pmr.com [206.224.65.132]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id OAA11753 Tue, 13 Feb 1996 14:06:48 -0800 (PST) Received: (from bob@localhost) by luke.pmr.com (8.6.12/8.6.9) id QAA18341; Tue, 13 Feb 1996 16:06:23 -0600 From: Bob Willcox Message-Id: <199602132206.QAA18341@luke.pmr.com> Subject: Re: Exabyte 8200 To: fcawth@jjarray.umd.edu (Fred Cawthorne) Date: Tue, 13 Feb 1996 16:06:22 -0600 (CST) Cc: freebsd-hardware@FreeBSD.org, freebsd-scsi@FreeBSD.org In-Reply-To: <199602132046.PAA00282@jjarray.umd.edu> from "Fred Cawthorne" at Feb 13, 96 03:46:38 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.org Precedence: bulk Fred Cawthorne wrote: > > > I have just upgraded the firmware in my Exabyte 8200 drive to a newer > version, and now it at least works with FreeBSD-current... The problem > is that it is streaming very slowly. It isn't stopping and going, but it > only writes about 60-80 K/second. I have heard that people use this > drive, and I wanted to know if there are any special modes to select or > anything. Do people ever get resonable speeds with this drive?? > I know this thing is old but it seems that it should be able to write a > 2 gig tape in under 6 hours... > > Any information would be appreciated... I have several of these that I use on 2.1-stable systems w/o any (major) problems. Performance is right at the theroetical limit of 240kb/sec. Mine are connected to NCR 810 controllers. I use them with dump, tar, cpio, and afio. Sometimes when I feel like it I will pipe the output through team to the drive (though I don't think it really changes the performance any). The problems that I do have with the drives is one of positioning to different files down the tape. When I dump to them I will place multiple file systems on a single tape as multiple tape files (as many as will fit in the 2gb). This works ok, but it is a real pain to get restore to properly locate the desired tape file. So far, I've yet to fail to get the file I need when really necesary, but is is never easy (and I really don't know why...it should be easy, the documentation makes it sound easy). > Fred. > -- Bob Willcox bob@luke.pmr.com (or obiwan%bob@uunet.uu.net) Austin, TX From owner-freebsd-scsi Tue Feb 13 15:22:00 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA17461 for freebsd-scsi-outgoing; Tue, 13 Feb 1996 15:22:00 -0800 (PST) Received: from irz301.inf.tu-dresden.de (irz301.inf.tu-dresden.de [141.76.1.11]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA17400 Tue, 13 Feb 1996 15:21:38 -0800 (PST) Received: from sax.sax.de by irz301.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id AAA07821; Wed, 14 Feb 1996 00:21:32 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id AAA19144; Wed, 14 Feb 1996 00:21:32 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id AAA06462; Wed, 14 Feb 1996 00:05:52 +0100 (MET) From: J Wunsch Message-Id: <199602132305.AAA06462@uriah.heep.sax.de> Subject: Re: Exabyte 8200 To: fcawth@jjarray.umd.edu (Fred Cawthorne) Date: Wed, 14 Feb 1996 00:05:52 +0100 (MET) Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199602132046.PAA00282@jjarray.umd.edu> from "Fred Cawthorne" at Feb 13, 96 03:46:38 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk As Fred Cawthorne wrote: > The problem > is that it is streaming very slowly. It isn't stopping and going, but it > only writes about 60-80 K/second. At which block size? -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Tue Feb 13 23:22:03 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id XAA20053 for freebsd-scsi-outgoing; Tue, 13 Feb 1996 23:22:03 -0800 (PST) Received: from irz101.inf.tu-dresden.de (irz101.inf.tu-dresden.de [141.76.1.9]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id XAA20047 for ; Tue, 13 Feb 1996 23:21:58 -0800 (PST) Received: from sax.sax.de by irz101.inf.tu-dresden.de (8.6.12/8.6.12-s1) with ESMTP id IAA26982; Wed, 14 Feb 1996 08:21:30 +0100 Received: by sax.sax.de (8.6.11/8.6.12-s1) with UUCP id IAA22463; Wed, 14 Feb 1996 08:21:30 +0100 Received: (from j@localhost) by uriah.heep.sax.de (8.7.3/8.6.9) id IAA04995; Wed, 14 Feb 1996 08:15:18 +0100 (MET) From: J Wunsch Message-Id: <199602140715.IAA04995@uriah.heep.sax.de> Subject: Re: Warning: SCSI reprobing is hazardous to your health? To: freebsd-scsi@freebsd.org Date: Wed, 14 Feb 1996 08:15:16 +0100 (MET) Cc: regnauld@tetard.frmug.fr.net (Philippe Regnauld) Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199602131927.UAA03176@tetard.frmug.fr.net> from "Philippe Regnauld" at Feb 13, 96 08:27:18 pm X-Phone: +49-351-2012 669 X-Mailer: ELM [version 2.4 PL23] MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk [Moved to freebsd-scsi.] > - Has anybody heard of this kind of behaviour ? The reprobe code used to work only on some SCSI controllers. The NCR however belongs to them. > - The occasional panic after reprobe -- is that normal (not that > I will try it out anymore). I've never seen this, i've only experienced hard system hangs inside DELAY(). You don't have any stacktrace or coredump of the panic? It's hard to say what happened without even a hint on where to search. The only known problem is configuring the kernel dump area to a swap partition that starts at offset 0 of the disk. There's an open PR by me for it: [1995/10/26] kern/794 swap partition at offset 0 still broken The core dump consistently trashes the disklabel in this case. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) From owner-freebsd-scsi Wed Feb 14 09:51:55 1996 Return-Path: owner-freebsd-scsi Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id JAA03005 for freebsd-scsi-outgoing; Wed, 14 Feb 1996 09:51:55 -0800 (PST) Received: from hpcsos.col.hp.com (root@hpcsos.col.hp.com [15.255.240.16]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id JAA02939 for ; Wed, 14 Feb 1996 09:50:33 -0800 (PST) Received: from srmail.sr.hp.com by hpcsos.col.hp.com with ESMTP (1.37.109.16/15.5+IOS 3.14) id AA126060220; Wed, 14 Feb 1996 10:50:20 -0700 Received: from hpnmhjw.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA149210068; Wed, 14 Feb 1996 09:47:48 -0800 Received: from mina.sr.hp.com by hpnmhjw.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA217380062; Wed, 14 Feb 1996 09:47:42 -0800 Message-Id: <199602141747.AA217380062@hpnmhjw.sr.hp.com> To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Cc: freebsd-scsi@freebsd.org Subject: Re: Warning: SCSI reprobing is hazardous to your health? In-Reply-To: Your message of "Wed, 14 Feb 1996 08:15:16 +0100." <199602140715.IAA04995@uriah.heep.sax.de> Date: Wed, 14 Feb 1996 09:47:42 -0800 From: Darryl Okahata Sender: owner-freebsd-scsi@freebsd.org Precedence: bulk > The only known problem is configuring the kernel dump area to a swap > partition that starts at offset 0 of the disk. There's an open PR by > me for it: > > [1995/10/26] kern/794 swap partition at offset 0 still broken > > The core dump consistently trashes the disklabel in this case. Thanks for mentioning this. I was going to redo my disk configuration and move the swap area to the beginning of the disk, but I guess not (I have to replace my root disk, as it's dying). -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day.