From owner-freebsd-scsi Sun May 18 11:31:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA06269 for freebsd-scsi-outgoing; Sun, 18 May 1997 11:31:24 -0700 (PDT) Received: from capella.grayphics.com (root@capella.grayphics.com [207.211.152.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA06264; Sun, 18 May 1997 11:31:22 -0700 (PDT) Received: from localhost (nick@localhost) by capella.grayphics.com (8.8.5/8.8.3) with SMTP id LAA05806; Sun, 18 May 1997 11:31:18 -0700 (PDT) Date: Sun, 18 May 1997 11:31:18 -0700 (PDT) From: Nick Esborn To: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org Subject: RELENG-22 fatal trap 18 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Yesterday I set up a serial console to catch a frequent spontaneous reboot that has been plaguing my machine since the upgrade to 2.2.1-R and RELENG-2.2 970510. Attached below is the output from the panic and the boot that followed. What are my options to resolve this? Does the new 2.2.2 address any kernel or SCSI bugs above and beyond RELENG-2.2? This only seems to happen after periods of very high activity, such as running the Bovine rc5 client for serveral hours at a time. I am running the P6 at 233 MHz, but I have extensive cooling measures in place, and it ran fine under the same load and 2.1.5 for several months at a time, so I don't think that is it. The only hardware addition made since the machine was a 2.1.5 machine that never crashed was the Micropolis 3243W. Has anyone had particular problems with this model and the 2940UW? Thanks in advance for any help. --- Fatal trap 18: integer divide fault while in kernel mode instruction pointer = 0x8:0xf01b5eea stack pointer = 0x10:0xefbffea0 frame pointer = 0x10:0xefbffeb4 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 = 1943 (pike) interrupt mask = net tty bio panic: integer divide fault syncing disks... 2 syncing disks... 228 28 28 28 28 28 28 28 28 28 28 28 28 28 28 28 28 28 28 28 giving up Automatic reboot in 15 seconds - press a key on the console to abort Rebooting... Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2-970510-RELENG #0: Sat May 17 16:36:32 PDT 1997 nick@capella.grayphics.com:/usr/src/sys/compile/CAPELLA CPU: Pentium Pro (233.09-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x617 Stepping=7 Features=0xfbff,MTRR,PGE,MCA,CMOV> real memory = 100663296 (98304K bytes) avail memory = 94867456 (92644K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 ahc0 rev 0 int a irq 15 on pci0:13 ahc0: aic7880 Wide Channel, SCSI Id=7, 1annel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "MICROP 3243WT P429" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 4095MB (8388315 512 byte sectors) (ahc0:2:0): "SEAGATE ST43400N 1022" type 0 fixed SCSI 2 sd1(ahc0:2:0): Direct-Access 2777MB (5688447 512 byte sectors) de0 rev 17 int a irq 14 on pci0:14 de0: DE500-XA 21140 [10-100Mb/s] pass 1.1 de0: address 00:00:f8:01:1d:27 de0: enabling 10baseT port vga0 rev 0 int a irq 11 on pci0:15 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flagsswapon: adding /dev/sd0s1b as swap device swapon: adding /dev/sd1s1b as swap device Automatic reboot in progress... /dev/rsd0a: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED) /dev/rsd0a: 1716 files, 83208 used, 171111 free (87 frags, 21378 blocks, 0.0% fr agmentation) /dev/rsd0s1f: UNREF FILE I=276850 OWNER=sky MODE=100664 /dev/rsd0s1f: SIZE=5 MTIME=May 15 15:06 1997 (CLEARED)^M06 1997 (CLEARED)^M /dev/rsd0s1f: UNREF FILE I=615053 OWNER=frigid MODE=100644 /dev/rsd0s1f: SIZE=4 MTIME=May 17 03:50 1997 (CLEARED) /dev/rsd0s1f: FREE BLK COUNT(S) WRONG IN SUPERBLK (SALVAGED) /dev/rsd0s1f: BLK(S) MISSING IN BIT MAPS (SALVAGED) /dev/rsd0s1f: SUMMARY INFORMATION BAD (SALVAGED) /dev/rsd0s1f: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED) /dev/rsd0s1f: 91344 files, 2809295 used, 368516 free (4916 frags, 45450 blocks, 0.2% fragmentation) /dev/rsd0s1e: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED) /dev/rsd0s1e: 895 files, 54349 used, 454306 free (370 frags, 56742 blocks, 0.1% fragmentation) /dev/rsd1s1g: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED) /dev/rsd1s1g: 832 files, 1235652 used, 251371 free (643 frags, 31341 blocks, 0.0% fragmentation) /dev/rsd1s1e: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED) /dev/rsd1s1e: 1647 files, 457791 used, 50864 free (800 frags, 6258 blocks, 0.2% fragmentation) /dev/rsd1s1f: CLEAN FLAG NOT SET IN SUPERBLOCK (FIXED) /dev/rsd1s1f: 753 files, 382002 used, 126653 free (253 frags, 15800 bfrags, 15800 blocks, 0.0% fragmentation) lo0: flags=8049 mtu 16384 inet 127.0.0.1 netmask 0xff000000 de0: flags=8843 mtu 1500 inet 207.211.152.2 netmask 0xffffff00 broadcast 207.211.152.255 ether 00:00:f8:01:1d:27 add net default: gateway 207.211.152.1 Nick Grayphics http://www.grayphics.com/ From owner-freebsd-scsi Sun May 18 12:45:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA08815 for freebsd-scsi-outgoing; Sun, 18 May 1997 12:45:30 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA08810; Sun, 18 May 1997 12:45:29 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id NAA19645; Sun, 18 May 1997 13:45:24 -0600 (MDT) Message-Id: <199705181945.NAA19645@pluto.plutotech.com> To: Nick Esborn cc: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: RELENG-22 fatal trap 18 In-reply-to: Your message of "Sun, 18 May 1997 11:31:18 PDT." Date: Sun, 18 May 1997 14:43:45 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >Fatal trap 18: integer divide fault while in kernel mode >instruction pointer = 0x8:0xf01b5eea This doesn't look at all like a SCSI problem. SCSI problems usually show up as transaction timeouts, not integer divide panics. The fact that your filesystem needs to be fscked at boot is simply a consequence of the crash. The next thing for you to do is to find out what routine the instruction pointer is in. Doing an "nm /kernel | sort" will do that for you. The next step is to put DDB into your kernel (options DDB + *full* kernel rebuild) so you can provide a stack trace the next time it happens. My gut feeling is that you shouldn't be overclocking your P6 and that this is the cause of your problem. Overclocking issues are usually very load dependant, and different versions of FreeBSD have different memory/cache load characteristics. You might want to try putting it back to where it's supposed to be to see if this clears up your problem. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Mon May 19 01:51:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA10392 for freebsd-scsi-outgoing; Mon, 19 May 1997 01:51:11 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA10386 for ; Mon, 19 May 1997 01:51:06 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA13590; Mon, 19 May 1997 10:50:38 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id KAA03974; Mon, 19 May 1997 10:36:18 +0200 (MET DST) Message-ID: <19970519103618.LH45116@uriah.heep.sax.de> Date: Mon, 19 May 1997 10:36:18 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG Cc: henrich@crh.cl.msu.edu (Charles Henrich) Subject: Re: scsi library interface References: <19970518184034.10726@crh.cl.msu.edu> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970518184034.10726@crh.cl.msu.edu>; from Charles Henrich on May 18, 1997 18:40:34 -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Charles Henrich wrote: > Who wrote the scsi interface commands? (e.g. scsi_open, scsi_build > ..) I need to bang on them with some questions. Peter Dufault. He's also got a revamped library which he was asking people to test. It's on hub's anon ftp area, if i'm not mistaken. > Also, in general when do you use raw mode devices vs. block mode vs > the .ctl devices? Buffered (`block') devices: to mount a filesystem over them. Nothing else. (Well, swapon(8) is in the same boat.) Raw (`character') devices: any other regular (i.e. read(2)/write(2)) IO. Control devices: raw SCSI commands. State of the device doesn't matter then, e.g. you can open a control device for an unformatted disk, but you can't open the raw or buffered device. -- 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 Mon May 19 07:38:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA24698 for freebsd-scsi-outgoing; Mon, 19 May 1997 07:38:40 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA24677; Mon, 19 May 1997 07:38:34 -0700 (PDT) Received: from mercury.ukc.ac.uk ([129.12.21.10]) by agora.rdrop.com (8.8.5/8.8.5) with SMTP id HAA25304; Mon, 19 May 1997 07:37:50 -0700 (PDT) Received: from crane.ukc.ac.uk by mercury.ukc.ac.uk with SMTP (PP); Mon, 19 May 1997 15:35:02 +0100 Received: from localhost by crane.ukc.ac.uk (SMI-8.6/UKC-2.14) id PAA27231; Mon, 19 May 1997 15:35:00 +0100 Date: Mon, 19 May 1997 15:35:00 +0100 (BST) From: "K.R.Marshall" X-Sender: krm2@crane To: freebsd-current@freebsd.org, freebsd-scsi@freebsd.org Subject: Maximum 32 CD-ROMs..? Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all, I'm running 2.2-STABLE as of around the 15th May, and I've just noticed that there is still a limit of 32 SCSI CD-ROM devices built in somewhere. Can anyone point me to where this is, and tell me whether it is easy to change? I must admit, I thought I'd seen that this had already been changed somewhere down the line, but perhaps it was in 3.0-current. Also, MAKEDEV by default disallows any 'cd' device above 7 - is there a good reason for this? I know it's easy enough to hack, but I was just wondering why it had been set this way. Keith. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "... I was taught from much too | Keith Marshall young to shine and not reflect ..." | Computing Officer, Templeman Library - Marillion, "An Accidental Man" | University of Kent at Canterbury. From owner-freebsd-scsi Mon May 19 08:05:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA26333 for freebsd-scsi-outgoing; Mon, 19 May 1997 08:05:56 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA26328 for ; Mon, 19 May 1997 08:05:53 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.5/8.8.5) id LAA01102; Mon, 19 May 1997 11:05:33 -0400 (EDT) Message-ID: <19970519110533.07999@crh.cl.msu.edu> Date: Mon, 19 May 1997 11:05:33 -0400 From: Charles Henrich To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: scsi library interface References: <19970518184034.10726@crh.cl.msu.edu> <19970519103618.LH45116@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <19970519103618.LH45116@uriah.heep.sax.de>; from J Wunsch on Mon, May 19, 1997 at 10:36:18AM +0200 X-Operating-System: FreeBSD 2.2-970422-RELENG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On the subject of Re: scsi library interface, J Wunsch stated: > As Charles Henrich wrote: > > > Who wrote the scsi interface commands? (e.g. scsi_open, scsi_build > > ..) I need to bang on them with some questions. > > Peter Dufault. He's also got a revamped library which he was asking > people to test. It's on hub's anon ftp area, if i'm not mistaken. Cool. > > Also, in general when do you use raw mode devices vs. block mode vs > > the .ctl devices? > > Buffered (`block') devices: to mount a filesystem over them. Nothing > else. (Well, swapon(8) is in the same boat.) > > Raw (`character') devices: any other regular (i.e. read(2)/write(2)) > IO. > > Control devices: raw SCSI commands. State of the device doesn't > matter then, e.g. you can open a control device for an unformatted > disk, but you can't open the raw or buffered device. Then why is it when you start sending raw SCSI read commands to rcd0.ctl behind which lives a Toshiba, you explode the SCSI bus, yet if you send them to /dev/cd0c things appear to work? (And with a plextor, both work!) Im confused.. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-scsi Mon May 19 08:51:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA28769 for freebsd-scsi-outgoing; Mon, 19 May 1997 08:51:03 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA28764 for ; Mon, 19 May 1997 08:50:55 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id RAA18495; Mon, 19 May 1997 17:50:47 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id RAA00931; Mon, 19 May 1997 17:45:16 +0200 (MET DST) Message-ID: <19970519174516.AT53845@uriah.heep.sax.de> Date: Mon, 19 May 1997 17:45:16 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG Cc: henrich@crh.cl.msu.edu (Charles Henrich) Subject: Re: scsi library interface References: <19970518184034.10726@crh.cl.msu.edu> <19970519103618.LH45116@uriah.heep.sax.de> <19970519110533.07999@crh.cl.msu.edu> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970519110533.07999@crh.cl.msu.edu>; from Charles Henrich on May 19, 1997 11:05:33 -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Charles Henrich wrote: > Then why is it when you start sending raw SCSI read commands to > rcd0.ctl behind which lives a Toshiba, you explode the SCSI bus, yet > if you send them to /dev/cd0c things appear to work? (And with a > plextor, both work!) There is not much difference between both when it comes to passing down raw SCSI commands. They are caught by the upper layers of the SCSI driver and never passed down to the type driver. If you see a difference, it probably means you don't initialize the device correctly. Opening a regular device causes a series of actions like checking for the device being ready, sending a START UNIT command etc., whereas opening the control devices causes nothing of this. Needless to say, no userland program is meant to issue READ or WRITE commands to a CD-ROM drive at all... I would be much more happy if you would think about integrating all this into the type drivers. I've already exchanged a few ideas with Jean-Marc Zucchoni lately, who became very active on the CD-R front. Reading and writing devices in userland when there's a real device driver for it violates the layering principles. Things like jitter correction don't belong in the kernel however. Either you've got a ``good'' device, then you can copy the data with dd(1), or you don't, then you still need cdd(1) doing the error correction for you (but not doing the actual read/write). NB: the above is an ideal picture, and the ultimate goal for the future. It's not immediately reachable, see also my recent discussion about the bogus field b_blkno in the struct buf (it needs to become a b_offset in order to cope with block sizes that are not a power of 2 multiple of 512). -- 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 Mon May 19 10:42:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA06515 for freebsd-scsi-outgoing; Mon, 19 May 1997 10:42:32 -0700 (PDT) Received: from crh.cl.msu.edu (crh.cl.msu.edu [35.8.1.24]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA06509 for ; Mon, 19 May 1997 10:42:28 -0700 (PDT) Received: (from henrich@localhost) by crh.cl.msu.edu (8.8.5/8.8.5) id NAA01270; Mon, 19 May 1997 13:42:00 -0400 (EDT) Message-ID: <19970519134159.60193@crh.cl.msu.edu> Date: Mon, 19 May 1997 13:41:59 -0400 From: Charles Henrich To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: scsi library interface References: <19970518184034.10726@crh.cl.msu.edu> <19970519103618.LH45116@uriah.heep.sax.de> <19970519110533.07999@crh.cl.msu.edu> <19970519174516.AT53845@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <19970519174516.AT53845@uriah.heep.sax.de>; from J Wunsch on Mon, May 19, 1997 at 05:45:16PM +0200 X-Operating-System: FreeBSD 2.2-970422-RELENG Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On the subject of Re: scsi library interface, J Wunsch stated: > Needless to say, no userland program is meant to issue READ or WRITE > commands to a CD-ROM drive at all... I would be much more happy if > you would think about integrating all this into the type drivers. > I've already exchanged a few ideas with Jean-Marc Zucchoni lately, who > became very active on the CD-R front. Reading and writing devices in > userland when there's a real device driver for it violates the > layering principles. The only problem is, you need to code different mechanisms for reading this kind of data for each CD-ROM manufacturer out there. Adding these tables for this special end case seems pointless, and you also make your life much more painful for some mechs who require switching states depending on if reading CDDA or not. -Crh Charles Henrich Michigan State University henrich@msu.edu http://pilot.msu.edu/~henrich From owner-freebsd-scsi Mon May 19 21:28:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA10077 for freebsd-scsi-outgoing; Mon, 19 May 1997 21:28:34 -0700 (PDT) Received: from sendero.i-connect.net (sendero-ppp.i-Connect.Net [206.190.143.100]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA10037 for ; Mon, 19 May 1997 21:28:14 -0700 (PDT) Received: (qmail 13180 invoked by uid 1000); 20 May 1997 04:08:58 -0000 Message-ID: X-Mailer: XFMail 1.1-alpha [p0] on FreeBSD Content-Type: text/plain; charset=iso-8859-8 Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 13 May 1997 10:28:10 -0700 (PDT) Organization: iConnect Corp. From: Simon Shapiro To: freebsd-aic7xxx.freebsd.orf@sendero.i-connect.net, freebsd-scsi@freebsd.org Subject: SCSI Timeouts, again... Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi Y'all, I am again getting plenty of ...timeout while idle... messages from perfectly fine disk drives. As a result, the SCSI bus is being reset, which causes other CCB's form other drives to abort, which causes... the system to behave like Linux... BTW, it causes delays, which cause Linux NFS clients to abort with ``cannot access (some filename)...'' which is bogus of course. Any ideas? Simon timeout while idle... messages from perfectly fine disk drives. As a result, the SCSI bus is being reset, which causes other CCB's form other drives to abort, which causes... the system to behave like Linux... BTW, it causes From owner-freebsd-scsi Mon May 19 22:54:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA14820 for freebsd-scsi-outgoing; Mon, 19 May 1997 22:54:50 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA14815; Mon, 19 May 1997 22:54:47 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id XAA21036; Mon, 19 May 1997 23:54:38 -0600 (MDT) Message-Id: <199705200554.XAA21036@pluto.plutotech.com> To: Simon Shapiro cc: aic7xxx@FreeBSD.org, freebsd-scsi@FreeBSD.org Subject: Re: SCSI Timeouts, again... In-reply-to: Your message of "Tue, 13 May 1997 10:28:10 PDT." Date: Tue, 20 May 1997 00:52:43 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk >Hi Y'all, > >I am again getting plenty of ...timeout while idle... messages from >perfectly fine disk drives. As a result, the SCSI bus is being reset, >which causes other CCB's form other drives to abort, which causes... >the system to behave like Linux... Simon. Since you're a software engineer, I would have expected a better bug report out of you. 8-) I need a dmesg output from a boot -v, a listing of all AHC options in your kernel config file, and, since I know that you guys are playing around with the SCSI code, information about any local mods running on the system. A listing of the exact error messages would be good too. >Any ideas? > >Simon Here's an idea. Stop using an alpha MUA! 8-)i It's leaving junk at the end of your messages again. >timeout while idle... messages from >perfectly fine disk drives. As a result, the SCSI bus is being reset, >which causes other CCB's form other drives to abort, which causes... >the system to behave like Linux... > >BTW, it causes > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Tue May 20 10:51:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA15503 for freebsd-scsi-outgoing; Tue, 20 May 1997 10:51:15 -0700 (PDT) Received: from dilbert.iagnet.net (root@dilbert.iagnet.net [207.206.8.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA15498; Tue, 20 May 1997 10:51:11 -0700 (PDT) Received: (from jamie@localhost) by dilbert.iagnet.net (8.8.5/8.8.5) id NAA20274; Tue, 20 May 1997 13:51:09 -0400 (EDT) Message-Id: <199705201751.NAA20274@dilbert.iagnet.net> Subject: News Server SCSI Problems (SUMMARY) To: freebsd-isp@freebsd.org, freebsd-scsi@freebsd.org Date: Tue, 20 May 1997 13:51:09 -0400 (EDT) RFC_Violation: You saw it here first! From: jamie@dilbert.iagnet.net (Jamie Rishaw) X-PGP-Fingerprint: <921C135D> C4 48 1B 26 18 7B 1F D9 BA C4 9C 7A B1 07 07 E8 Reply-To: jamie@dilbert.iagnet.net Organization: Internet Access Group, Inc. X-No-Archive: yes X-Face: >:-p X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks to all who replied to my SCSI problems.. If anyone remembers, I was getting hard halts on the box with a lot of LAST-PHASE= and "ahc0 timed out while waiting" errors. I was told that it was a buggy ahc driver.. I upgraded to 2.2-RELENG via cvsup, recompiled and the machine has been up and stable for going on ten days now. (It never exceeded two with the old kernel). Thanks all, Jamie Rishaw Internet Access Group -- jamie g.k. rishaw dal/efnet:gavroche Internet Access Group New Network Operations #: 216.902.5460 Network Operations/TSD http://support.iagnet.net __ [http://www.iagnet.net] DID:216.902.5455 FAX:216.623.3566 \/ 800.637.4IAGx5455 From owner-freebsd-scsi Tue May 20 11:37:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA18378 for freebsd-scsi-outgoing; Tue, 20 May 1997 11:37:23 -0700 (PDT) Received: from ady.warp.starnets.ro (ady.warp.starnets.ro [193.226.124.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA18235; Tue, 20 May 1997 11:35:01 -0700 (PDT) Received: from localhost (ady@localhost) by ady.warp.starnets.ro (8.8.5/8.8.5) with SMTP id VAA00468; Tue, 20 May 1997 21:30:11 +0300 (EEST) Date: Tue, 20 May 1997 21:30:10 +0300 (EEST) From: Penisoara Adrian To: Jamie Rishaw cc: freebsd-isp@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: News Server SCSI Problems (SUMMARY) In-Reply-To: <199705201751.NAA20274@dilbert.iagnet.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi ! On Tue, 20 May 1997, Jamie Rishaw wrote: > Thanks to all who replied to my SCSI problems.. If anyone remembers, I > was getting hard halts on the box with a lot of LAST-PHASE= and > "ahc0 timed out while waiting" errors. > > I was told that it was a buggy ahc driver.. > > I upgraded to 2.2-RELENG via cvsup, recompiled and the machine has been > up and stable for going on ten days now. Does this fix occur in 3.0-current too ? I have the same kind of problem (crashing when there is overload on both SCSI and network subsystems). >From what I know the answer should be yes, because some 2.2-RELENG fixes were taken from 3.0-current; anyway I must be sure on that, next month I'll do a full server upgrade (from zero). Thaks. > > (It never exceeded two with the old kernel). Lucky me, I got 12 days at maximum ! :) > > Thanks all, > > Jamie Rishaw > Internet Access Group > -- > jamie g.k. rishaw dal/efnet:gavroche Internet Access Group > New Network Operations #: 216.902.5460 Network Operations/TSD > http://support.iagnet.net __ [http://www.iagnet.net] > DID:216.902.5455 FAX:216.623.3566 \/ 800.637.4IAGx5455 > Ady (@warp.starnets.ro) From owner-freebsd-scsi Tue May 20 17:10:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA05983 for freebsd-scsi-outgoing; Tue, 20 May 1997 17:10:53 -0700 (PDT) Received: from mirage.nlink.com.br (mirage.nlink.com.br [200.238.120.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA05814 for ; Tue, 20 May 1997 17:07:19 -0700 (PDT) Received: (from luiz@localhost) by mirage.nlink.com.br (8.8.5/8.8.5) id VAA26482; Tue, 20 May 1997 21:07:00 -0300 (EST) Date: Tue, 20 May 1997 21:07:00 -0300 (EST) From: Luiz de Barros To: freebsd-scsi@freebsd.org Subject: Adaptec 2940 and 2.1.7 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dear FreeBSD Experts, I am having problems with Adaptec 2940 PCI SCSI-2 adapter under 2.1.7-RELEASE. It seems that a hardware driver bug is expontanely rebooting our system when we have very high disk load. I think somebody made a patch for this. Does anybody know about this patch or if the problem is solved in 2.2.1-RELEASE? Thanks in Advance, Luiz From owner-freebsd-scsi Tue May 20 17:47:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA07623 for freebsd-scsi-outgoing; Tue, 20 May 1997 17:47:10 -0700 (PDT) Received: from dilbert.iagnet.net (root@dilbert.iagnet.net [207.206.8.155]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA07613 for ; Tue, 20 May 1997 17:47:00 -0700 (PDT) Received: (from jamie@localhost) by dilbert.iagnet.net (8.8.5/8.8.5) id UAA03072; Tue, 20 May 1997 20:46:02 -0400 (EDT) Message-Id: <199705210046.UAA03072@dilbert.iagnet.net> Subject: Re: Adaptec 2940 and 2.1.7 To: luiz@nlink.com.br (Luiz de Barros) Date: Tue, 20 May 1997 20:46:02 -0400 (EDT) Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: from Luiz de Barros at "May 20, 97 09:07:00 pm" RFC_Violation: You saw it here first! From: jamie@dilbert.iagnet.net (Jamie Rishaw) X-PGP-Fingerprint: <921C135D> C4 48 1B 26 18 7B 1F D9 BA C4 9C 7A B1 07 07 E8 Reply-To: jamie@dilbert.iagnet.net Organization: Internet Access Group, Inc. X-No-Archive: yes X-Face: >:-p X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Dear FreeBSD Experts, > > I am having problems with Adaptec 2940 PCI SCSI-2 adapter under > 2.1.7-RELEASE. It seems that a hardware driver bug is expontanely > rebooting our system when we have very high disk load. I think somebody > made a patch for this. Does anybody know about this patch or if the > problem is solved in 2.2.1-RELEASE? Upgrade to 2.2-STABLE. > Thanks in Advance, > Luiz > -- jamie g.k. rishaw dal/efnet:gavroche Internet Access Group New Network Operations #: 216.902.5460 Network Operations/TSD http://support.iagnet.net __ [http://www.iagnet.net] DID:216.902.5455 FAX:216.623.3566 \/ 800.637.4IAGx5455 From owner-freebsd-scsi Tue May 20 17:52:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA07886 for freebsd-scsi-outgoing; Tue, 20 May 1997 17:52:08 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA07881 for ; Tue, 20 May 1997 17:52:06 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id SAA13901; Tue, 20 May 1997 18:51:26 -0600 (MDT) Message-Id: <199705210051.SAA13901@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Luiz de Barros cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec 2940 and 2.1.7 In-reply-to: Your message of "Tue, 20 May 1997 21:07:00 -0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 20 May 1997 19:49:22 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Dear FreeBSD Experts, > >I am having problems with Adaptec 2940 PCI SCSI-2 adapter under >2.1.7-RELEASE. It seems that a hardware driver bug is expontanely >rebooting our system when we have very high disk load. I think somebody >made a patch for this. Does anybody know about this patch or if the >problem is solved in 2.2.1-RELEASE? > >Thanks in Advance, >Luiz 2.1.7R had bugs in the aic7xxx driver. You can either use CVSup, CTM, or FTP to obtain newer kernel source for the 2.1 line of releases, upgrade to 2.2.2-RELEASE, or use CVSup, CTM or ftp to track 2.2-STABLE in order to get these bug fixes. 2.2.1-RELEASE still had some aic7xxx related problems. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Tue May 20 23:01:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA20969 for freebsd-scsi-outgoing; Tue, 20 May 1997 23:01:58 -0700 (PDT) Received: from faun.nada.kth.se (faun.nada.kth.se [130.237.222.80]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA20962 for ; Tue, 20 May 1997 23:01:56 -0700 (PDT) Received: from localhost (tege@localhost) by faun.nada.kth.se (8.8.5/8.6.9) with SMTP id IAA04212 for ; Wed, 21 May 1997 08:01:54 +0200 (MET DST) Message-Id: <199705210601.IAA04212@faun.nada.kth.se> X-Authentication-Warning: faun.nada.kth.se: tege@localhost didn't use HELO protocol To: scsi@freebsd.org Subject: Sony SDT-9000 DAT drive Date: Wed, 21 May 1997 08:01:53 +0200 From: Torbjorn Granlund Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I bought a Sony SDT-9000 DDS DAT drive this week after my one year old my HP drive started chowing tapes. The new drive recorded my tape correctly (I used a plain 90m DDS-1 tape) but when I tried `mt -f /dev/nrst0 offline' the tape did not eject. When I retry the command I get HARDWARE FAILUREasc:44,0 Internal target failure and the busy light on the drive flashes forever. I am not terribly familiar with tape drives. Could this be an incompatibility between FreeBSD 2.2.1 and the Sony drive? It does appear strange that a brand new Sony drive would be broken! The system was idle when this happened. The tape stays in the drive even if I powercycle it and press the eject button on it. Hardware info: ASUS P6NP5 128MB FPM w ECC 200MHz Pentium Pro Adaptec 2940UW USCSI and UWSCSI disks Torbjorn From owner-freebsd-scsi Wed May 21 00:34:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA24967 for freebsd-scsi-outgoing; Wed, 21 May 1997 00:34:09 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA24961 for ; Wed, 21 May 1997 00:34:05 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA10842; Wed, 21 May 1997 09:34:04 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA00381; Wed, 21 May 1997 09:31:31 +0200 (MET DST) Message-ID: <19970521093131.UF46868@uriah.heep.sax.de> Date: Wed, 21 May 1997 09:31:31 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: scsi@FreeBSD.ORG Cc: tege@nada.kth.se (Torbjorn Granlund) Subject: Re: Sony SDT-9000 DAT drive References: <199705210601.IAA04212@faun.nada.kth.se> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199705210601.IAA04212@faun.nada.kth.se>; from Torbjorn Granlund on May 21, 1997 08:01:53 +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Torbjorn Granlund wrote: > HARDWARE FAILUREasc:44,0 Internal target failure > I am not terribly familiar with tape drives. Could this be an > incompatibility between FreeBSD 2.2.1 and the Sony drive? No, the drive reports an Internal target failure. This sounds completely like a matter of the drive then. (Of course, this failure code is something like a ``General protection error'', you never know why it happens unless the vendor can explain you.) -- 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 May 21 12:35:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA00792 for freebsd-scsi-outgoing; Wed, 21 May 1997 12:35:14 -0700 (PDT) Received: from faun.nada.kth.se (faun.nada.kth.se [130.237.222.80]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA00782 for ; Wed, 21 May 1997 12:35:09 -0700 (PDT) Received: from localhost (tege@localhost) by faun.nada.kth.se (8.8.5/8.6.9) with SMTP id VAA27676 for ; Wed, 21 May 1997 21:35:03 +0200 (MET DST) Message-Id: <199705211935.VAA27676@faun.nada.kth.se> X-Authentication-Warning: faun.nada.kth.se: tege@localhost didn't use HELO protocol Date: Wed, 21 May 1997 21:35:02 +0200 From: Torbjorn Granlund Subject: Re: Sony SDT-9000 DAT drive To: undisclosed-recipients:; Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk ------- Blind-Carbon-Copy To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: Sony SDT-9000 DAT drive In-reply-to: Your message of "Wed, 21 May 1997 19:01:34 +0200." <19970521190134.FM23604@uriah.heep.sax.de> Date: Wed, 21 May 1997 21:35:02 +0200 From: Torbjorn Granlund I found the problem with my Sony SDT-9000. Blush :-( Before I took the drive in operation, I replaced the front plate in order to fit the unit in a 5" bay. There were no instructions whatsoever on how to do this. I missed that a tiny little lever from the drive needed to be put between the door and a lever on the door. Now when I removed the 5" stuff in order to give back the drive to the supplier, I noticed the problem. If you get one of these new DAT drives, be careful. The drive now works great and is much faster than any DAT drive I have used previously. Torbjorn ------- End of Blind-Carbon-Copy From owner-freebsd-scsi Wed May 21 14:50:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA08700 for freebsd-scsi-outgoing; Wed, 21 May 1997 14:50:29 -0700 (PDT) Received: from wall.jhs.no_domain (vector.muc.ditec.de [194.120.126.35]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA08594; Wed, 21 May 1997 14:49:41 -0700 (PDT) Received: (from jhs@localhost) by desk.jhs.no_domain (8.8.5/8.8.5) id XAA03201; Wed, 21 May 1997 23:37:17 +0200 (MET DST) Date: Wed, 21 May 1997 23:37:17 +0200 (MET DST) Message-Id: <199705212137.XAA03201@desk.jhs.no_domain> To: tomppa@fidata.fi cc: scsi@freebsd.org Cc: fabio@cesar.unicamp.br, fty@mcnc.org, gcrutchr@nightflight.com, j@uriah.heep.sax.de, jc@irbs.com, julian@freebsd.org, kuku@gilberto.physik.rwth-aachen.de, lehey.pad@sni.de, mrm@Sceard.com, nikm@ixa.net, tomppa@fidata.fi, wilko@yedi.iaf.nl, Scott Kelly Subject: 8 * 0xFF bytes at intermittent multiples of 0x1000 From: "Julian H. Stacey" Reply-To: "Julian H. Stacey" Web: http://www.freebsd.org/~jhs/ Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk To scsi@freebsd.org Cc Adaptec 1542A SCSI Adapter People. I & some other 1542A people are probably not on scsi@ list, so please be careful if trimming CC line. Ref. my earlier mail a while ago on [at least my] Adaptec 1542A mis-behaving, writing 8 * 0xFF bytes at intermittent multiples of 0x1000. I had thought it was my (dmesg:) "HP 97548S 8928" type 0 fixed SCSI 1, it's certainly not though, the drive was dismantled just last week (500M 5" individual platters make shiney paperweights ;-) the problem remains on 2 replacement drives, (physically labelled Seagate, but dmesg: "CDC 94191-15 5376" type 0 fixed SCSI 1 I'm sure it is [at least my] 1542A card at fault. I've tried moving 1542C & 1542A cards & discs between systems, & deduced it's not motherboard, ram, cache or over clocking (I don't, never have), nor is it termination. Either just my card is faulty, or the on board eprom code, or freebsd driver does not cope with some 1542A werdity. As tomppa@fidata.fi has seen similar problem, I don't think its just my card. I don't know, I need some 1542A users to run a simple test to deduce that Please :-) NO need to dismantle boxes, no need to be root, guest even will do ! just compile & run my http://www.freebsd.org/~jhs//src/bsd/jhs/bin/public/testblock/ (char sccsID[] ="@(#) testblock.c V2.3 is my latest version localy) _simultaneously_ on 2 seperate discs with cd /usr/tmp;testblock -v -l 20000000 foobar cd /usr1/tmp;testblock -v -l 20000000 foobar If you get an error such as: Error at byte 32769 (0x8001), after 1,536,000 (0x177000)previously read; Read 0xff, expected 0x19. Or even worse .... Error at byte 32769 (0x8001), after 0 previously read; Read 0xff, expected 0x0. you can see bad data with hexdump -C foobar | more # /^00008000 00008000 ff ff ff ff ff ff ff ff 08 09 0a 0b 0c 0d 0e 0f |ÿÿÿÿÿÿÿÿ........| 00008010 10 11 12 13 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f |................| 00008020 20 21 22 23 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f | !"#$%&'()*+,-./| The fault does not materialise on read, only on write (ie you can write good data on a 1542C system & check still good on a 1542A, but not other way around. The fault does not materialise if you only test one disc at a time ! The fault usually seems more noticeable on sd1 & sd2, less on sd0 (yes, I know: deduce bus length & termis ? , but I really don't think so !) The test program: testblock/ .c & .1 merely reads & writes a large file in user mode, you don't need to be root & it does nothing nasty (except it will fill your file system with a single very large file, if you dont use `-l number_of_bytes' ) This could be a good reason for you to run my testblock.c even if you think you have no problem - think of it as a free disk check, that doesnt disrupt, no need to run dos, drop to debugger, be root, repartition, backup the file system or any other hastle :-). This problem exists on FreeBSD-2.1 & 2.2.1 & 2.2-stable ------------ For reference, I'll append parts of my old mail: > Tomi Vainio > Has confirmed he sees the same Adaptec 1542A SCSI adapter bug that I do. > > > I connected sd1 to my 1542A and here are results: > > > > 1. No problems if testblock is only one that generates disk activity. > > 2. I launched couple find processes to sd0 and at same time I > > run testblock. Testblock failed only 1/10 of test runs. > > 3. I copied files with cp to sd1 when running testblock on > > sd1. Testblock failed on every time. > > > > Tomppa Remember if you have a swap partitions on sd*, & you swapped, the swap may be damaged so you might crash, so although my testblock.c is entirely well behaved (read the source if you doubt me :-) , just in case, & certaily if testblock reports data corruption, a reboot might be wise. Comments &/or test results please, Thanks :-) Julian -- Julian H. Stacey jhs@freebsd.org http://www.freebsd.org/~jhs/ From owner-freebsd-scsi Fri May 23 04:00:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA14178 for freebsd-scsi-outgoing; Fri, 23 May 1997 04:00:37 -0700 (PDT) Received: from innocence.interface-business.de (innocence.interface-business.de [193.101.57.202]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA14169 for ; Fri, 23 May 1997 04:00:32 -0700 (PDT) Received: from ida.interface-business.de (ida.interface-business.de [193.101.57.203]) by innocence.interface-business.de (8.6.11/8.6.9) with SMTP id MAA00241 for ; Fri, 23 May 1997 12:59:47 +0200 Received: (from j@localhost) by ida.interface-business.de (8.8.5/8.7.3) id NAA01604; Fri, 23 May 1997 13:00:21 +0200 (MET DST) Message-ID: <19970523130020.GM37769@ida.interface-business.de> Date: Fri, 23 May 1997 13:00:20 +0200 From: j@ida.interface-business.de (J Wunsch) To: scsi@freebsd.org Subject: Can anybody explain? X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-31809-14 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Organization: interface business GmbH, Dresden Reply-To: joerg_wunsch@interface-business.de (Joerg Wunsch) Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk st0(ahc1:4:0): Target Busy st0(ahc1:4:0): Target Busy st0(ahc1:4:0): Target Busy st0(ahc1:4:0): Target Busy st0(ahc1:4:0): Target Busy st0(ahc1:4:0): Target Busy That's after replacing a dead HP-DAT by a Seacrate (Conner) one. The Conner drive reports being busy for an annoying amount of time, even after e.g. closing /dev/nrst0, when starting a second dump. I have a hard time finding where the above message is generated in the kernel. Can anybody explain the spot? (I think of making this case similar to the ``Logical unit is in the process of becoming ready'' case, maybe with a timeout. I simply can't live with not being able to dump a couple of filesystems onto /dev/nrst0 in close sequence.) -- J"org Wunsch Unix support engineer joerg_wunsch@interface-business.de http://www.interface-business.de/~j From owner-freebsd-scsi Fri May 23 09:00:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA26666 for freebsd-scsi-outgoing; Fri, 23 May 1997 09:00:28 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA26637 for ; Fri, 23 May 1997 09:00:21 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id HAA09916 for ; Fri, 23 May 1997 07:20:25 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id IAA15402; Fri, 23 May 1997 08:20:05 -0600 (MDT) Message-Id: <199705231420.IAA15402@pluto.plutotech.com> To: joerg_wunsch@interface-business.de (Joerg Wunsch) cc: scsi@freebsd.org Subject: Re: Can anybody explain? In-reply-to: Your message of "Fri, 23 May 1997 13:00:20 +0200." <19970523130020.GM37769@ida.interface-business.de> Date: Fri, 23 May 1997 09:18:32 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >st0(ahc1:4:0): Target Busy >st0(ahc1:4:0): Target Busy >st0(ahc1:4:0): Target Busy >st0(ahc1:4:0): Target Busy >st0(ahc1:4:0): Target Busy >st0(ahc1:4:0): Target Busy The message is printed in sys/i386/scsi/aic7xxx.c in ahc_handle_seqint. Search for "SCSI_BUSY". The driver prints this error and returns XS_BUSY as the error code for the transfer. You should be able to add your delay or timeout in the XS_BUSY case in scsi_Base.c:sc_err1. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Fri May 23 17:54:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA27611 for freebsd-scsi-outgoing; Fri, 23 May 1997 17:54:14 -0700 (PDT) Received: from cicerone.uunet.ca (root@cicerone.uunet.ca [142.77.1.11]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA27606 for ; Fri, 23 May 1997 17:54:11 -0700 (PDT) Received: from why.whine.com ([205.150.249.1]) by mail.uunet.ca with ESMTP id <115258-16137>; Fri, 23 May 1997 20:53:52 -0400 Received: from why (why [205.150.249.1]) by why.whine.com (8.8.5/8.7.3) with SMTP id UAA00600 for ; Fri, 23 May 1997 20:53:45 -0400 (EDT) Date: Fri, 23 May 1997 20:53:45 -0400 From: Andrew Herdman X-Sender: andrew@why To: scsi@freebsd.org Subject: Oddness with NCR53C810 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a machine running Current as of Feb 1/97 with an ASUS P/I-P55T2P4 motherboard with the 2.02 bios. On this motherboard i have two scsi controllers, a Buslogics 946C and an NCR53C810. I want to replace the Buslogics with another NCR53C810 for consistencies sake. My problem is. When i turn on the NCR bios, it always tries to boot of the NCR card (the OS just happens to be on the Buslogics card). No problem just put the other NCR card in. Good that fixed it. Here's the problem. With the NCR bios turned off, the machine boots fine (off of the buslogics card, without the NCR bios the computer can't find the disks to boot). It probs the NCR card and drives fine. But when I turn on the NCR bios, with or without the buslogics card it hangs the machine (hard) as follows: ncr0 rev 17 int a irq 12 on pci0:11:0 ncr0 waiting for scsi devices to settle scbus1 at ncr0 bus 0 ^^^^^ This is it... it stops here. This is to say the least... annoying. Anyone have any ideas? thanks in advance... Andrew From owner-freebsd-scsi Fri May 23 23:39:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA10330 for freebsd-scsi-outgoing; Fri, 23 May 1997 23:39:23 -0700 (PDT) Received: from tor-adm1.nbc.netcom.ca (taob@tor-adm1.nbc.netcom.ca [207.181.89.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA10324 for ; Fri, 23 May 1997 23:39:16 -0700 (PDT) Received: from localhost (taob@localhost) by tor-adm1.nbc.netcom.ca (8.8.5/8.8.5) with SMTP id CAA23815 for ; Sat, 24 May 1997 02:39:04 -0400 (EDT) Date: Sat, 24 May 1997 02:39:04 -0400 (EDT) From: Brian Tao To: FREEBSD-SCSI Subject: Re: Anyone use a SyJet 1.5GB cartridge drive? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Thu, 1 May 1997, Brian Tao wrote: > > I'm thinking of picking up a Syquest SyJet removeable drive and a > few 1.5GB carts to go with it. They have an external SCSI-2 version > that looks like it should work under FreeBSD, but I wanted to see if > anyone else has successfully used a SyJet drive. Well, I didn't get any responses, so I went ahead and bought a drive anyway. :) Happily, it seems to work great with FreeBSD so far (just got it earlier today). It comes up as: (ncr0:5:0): "SyQuest SyJet-S 0095" type 0 removable SCSI 2 sd1(ncr0:5:0): Direct-Access sd1(ncr0:5:0): 10.0 MB/s (100 ns, offset 8) 1430MB (2929800 512 byte sectors) sd1(ncr0:5:0): with 5258 cyls, 4 heads, and an average 139 sectors/track It newfs to 1419647K total, 1306075K usable. It's also pretty speedy for a removeable: -------Sequential Output-------- ---Sequential Input-- --Random-- -Per Char- --Block--- -Rewrite-- -Per Char- --Block--- --Seeks--- Machine MB K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU K/sec %CPU /sec %CPU p200-syj 256 1961 28.4 1927 5.1 987 4.5 5594 78.0 5540 14.0 45.0 1.5 You can fit two FreeBSD distributions (including packages and ports) per cartridge, and the drive unit is easily portable to other computers to do installs (if you have a SCSI interface; there is also a parallel model, yuck). It's a sharp-looking drive that can lie horizontal or be fitted with a vertical tower stand. -- Brian Tao (BT300, taob@netcom.ca) "Though this be madness, yet there is method in't" From owner-freebsd-scsi Sat May 24 01:50:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA14613 for freebsd-scsi-outgoing; Sat, 24 May 1997 01:50:54 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id BAA14608 for ; Sat, 24 May 1997 01:50:50 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id KAA04992; Sat, 24 May 1997 10:50:48 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id KAA09294; Sat, 24 May 1997 10:29:44 +0200 (MET DST) Message-ID: <19970524102943.GO37893@uriah.heep.sax.de> Date: Sat, 24 May 1997 10:29:43 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: scsi@FreeBSD.ORG Cc: andrew@why.whine.com (Andrew Herdman) Subject: Re: Oddness with NCR53C810 References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Andrew Herdman on May 23, 1997 20:53:45 -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Andrew Herdman wrote: > ncr0 rev 17 int a irq 12 on pci0:11:0 > ncr0 waiting for scsi devices to settle > scbus1 at ncr0 bus 0 > ^^^^^ > This is it... it stops here. Do you have scbus1 hardwired to ncr0 in your kernel? ncr0 rev 18 int a irq 12 on pci0:9:0 scbus0 at ncr0 bus 0 ... ncr1 rev 2 int a irq 11 on pci0:12:0 scbus1 at ncr1 bus 0 Mine are working. scbus1 used to be on an AHA2940 until i had to free up the Adaptec for other purposes. Interesting, i never noticed i've got two different NCRs until now. :) Maybe boot -v would show you some more messages. -- 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 Sat May 24 07:18:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA26700 for freebsd-scsi-outgoing; Sat, 24 May 1997 07:18:26 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA26689 for ; Sat, 24 May 1997 07:18:21 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id QAA08582 for ; Sat, 24 May 1997 16:18:11 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id QAA19883 for scsi@FreeBSD.ORG; Sat, 24 May 1997 16:17:39 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id MAA04978; Sat, 24 May 1997 12:46:26 +0200 (CEST) Message-ID: <19970524124625.07596@keltia.freenix.fr> Date: Sat, 24 May 1997 12:46:25 +0200 From: Ollivier Robert To: scsi@FreeBSD.ORG Subject: Re: Oddness with NCR53C810 References: <19970524102943.GO37893@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 In-Reply-To: <19970524102943.GO37893@uriah.heep.sax.de>; from J Wunsch on Sat, May 24, 1997 at 10:29:43AM +0200 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3323 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to J Wunsch: > Mine are working. scbus1 used to be on an AHA2940 until i had to free > up the Adaptec for other purposes. Interesting, i never noticed i've > got two different NCRs until now. :) I have two NCR as well and this works with bus hardwired. controller pci0 controller ncr0 controller ncr1 controller scbus0 at ncr0 controller scbus1 at ncr1 # NCR0: ibm + tandberg + hp disk sd0 at scbus0 target 0 unit 0 disk sd1 at scbus0 target 1 disk sd2 at scbus0 target 2 disk sd3 at scbus0 target 3 tape st1 at scbus0 target 4 tape st0 at scbus0 target 5 device cd0 at scbus0 target 6 # NCR1: conner + micropolis + CD disk sd10 at scbus1 target 0 disk sd11 at scbus1 target 1 disk sd12 at scbus1 target 2 disk sd13 at scbus1 target 3 device cd1 at scbus1 target 6 The NCR810a is an Ultra-capable version of the NCR810 I think. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #10: Fri May 23 22:47:39 CEST 1997 From owner-freebsd-scsi Sat May 24 16:43:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA25562 for freebsd-scsi-outgoing; Sat, 24 May 1997 16:43:26 -0700 (PDT) Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.6.51]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA25539; Sat, 24 May 1997 16:43:02 -0700 (PDT) Received: from AMPERSAND (ztm04-29.dial.xs4all.nl [194.109.32.126]) by smtp1.xs4all.nl (8.7.6/XS4ALL) with SMTP id BAA20385; Sun, 25 May 1997 01:42:58 +0200 (MET DST) Message-Id: <199705242342.BAA20385@smtp1.xs4all.nl> Comments: Authenticated sender is From: "Jeroen" Organization: Twiddle To: Questions@FreeBSD.ORG, SCSI@FreeBSD.ORG, ISP@FreeBSD.ORG Date: Sun, 25 May 1997 01:41:29 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Some advice needed CC: jh@Twiddle.COM Priority: normal X-mailer: Pegasus Mail for Windows (v2.31) Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi there, I have a question regarding some server setup; I'm planning to use the Adaptec AHA-3940UW PCI adapter in combination with two Quantum AtlasII QM34550ALSW 4.5 GB UW SCSI-3 harddisks. I'd like to know if this is an acceptable choice in your books :-) What mainboard/SCSI controller/SCSI drives do you recommend most? Secondly I'm wondering what EtherExpress PRO card is being used in the wcarchive.cdrom.com machine, there doesn't seem to be any specific information exept that it's a model 100B. The intel site mentioned the Server adapter (with some i960 chip), the T4 PCI adapter and the TX PCI adapter. Which one will work best (full duplex) with the fxp driver? Server setup: Asus P/I-P6RP7D + 200MHz PPro 4 * 64MB Parity SIMMs Adaptec 3940UW PCI SCSI adapter 2 * Quantum AtlasII QM34550ALSW 4.5GB UW SCSI3 harddrives Comments? TIA for sharing experience/knowledge/opinions :-) cheers, Jeroen. PS: sorry if you're subscribed to all three mailinglists ;-)