From owner-freebsd-scsi Sun Jul 30 4:43:11 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id 3A78E37B6BD for ; Sun, 30 Jul 2000 04:43:00 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.144] (helo=mx1.freenet.de) by mout1.freenet.de with esmtp (Exim 3.16 #1) id 13IrUY-0008HG-00; Sun, 30 Jul 2000 13:42:50 +0200 Received: from a368d.pppool.de ([213.6.54.141] helo=Magelan.Leidinger.net) by mx1.freenet.de with esmtp (Exim 3.16 #1) id 13IrUX-00010m-00; Sun, 30 Jul 2000 13:42:49 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id MAA15223; Sun, 30 Jul 2000 12:35:55 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200007301035.MAA15223@Magelan.Leidinger.net> Date: Sun, 30 Jul 2000 12:35:50 +0200 (CEST) From: Alexander Leidinger Subject: Fwd: Panic in xpt_setup_ccb (cam_xpt.c) To: scsi@freebsd.org Cc: Matthew Jacob MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, forwarded to -scsi at request of Matthew Jacob (Note: I'm not subscribed to -scsi). My hardware is: ---snip--- ahc0: port 0xb000-0xb0ff mem 0xd9800000-0xd9800fff irq 9 at device 6.0 on pci0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs cd0 at ahc0 bus 0 target 1 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd1 at ahc0 bus 0 target 2 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 20.000MB/s transfers (20.000MHz, offset 15) ---snip--- The panic happened with cd0. Matthew: It didn't happen because of syncing prior to a reboot, it was a "dd if=/dev/cd0c of=normal_file_on_ad0" (it's a "damaged" cd (someone bought crappy CD-R's and I have to get some data out of them) and I tried to duplicate the contents with dd). I was able to reproduce it, and I'm sure I'm able to reproduce it with an actual kernel (at the moment I'm recovering from a loss of / because of some shit from M$, -> the crashdump is lost). ------ Forwarded message ------ From: Alexander Leidinger Subject: Panic in xpt_setup_ccb (cam_xpt.c) Date: Sat, 29 Jul 2000 10:30:03 +0200 (CEST) To: current@FreeBSD.ORG Message-ID: <200007290830.KAA00512@Magelan.Leidinger.net> Hi, while trying to read (dd if=/dev/cd0c) from a damaged cd (the surface is a little bit damaged), I've got a panic: ---snip--- #0 boot (howto=260) at ../../kern/kern_shutdown.c:303 #1 0xc01a0f19 in panic (fmt=0xc029aa60 "lockmgr: pid %d, not %s %d unlocking") at ../../kern/kern_shutdown.c:553 #2 0xc019b194 in lockmgr (lkp=0xc14f4a00, flags=65542, interlkp=0xd0e2e22c, p=0xd0313ba0) at ../../kern/kern_lock.c:382 #3 0xc01cf2af in vop_stdunlock (ap=0xd0d2ecc8) at ../../kern/vfs_default.c:255 #4 0xc022b641 in ufs_vnoperate (ap=0xd0d2ecc8) at ../../ufs/ufs/ufs_vnops.c:2301 #5 0xc01d22aa in vput (vp=0xd0e2e1c0) at vnode_if.h:794 #6 0xc0222ea7 in ffs_sync (mp=0xc1046a00, waitfor=2, cred=0xc0b3f980, p=0xc037f0a0) at ../../ufs/ffs/ffs_vfsops.c:955 #7 0xc01d4295 in sync (p=0xc037f0a0, uap=0x0) at ../../kern/vfs_syscalls.c:551 #8 0xc01a094f in boot (howto=256) at ../../kern/kern_shutdown.c:225 #9 0xc01a0f19 in panic (fmt=0xc02babef "page fault") at ../../kern/kern_shutdown.c:553 #10 0xc0265846 in trap_fatal (frame=0xd0d2ee10, eva=68) at ../../i386/i386/trap.c:929 #11 0xc02654f9 in trap_pfault (frame=0xd0d2ee10, usermode=0, eva=68) at ../../i386/i386/trap.c:822 #12 0xc02650bf in trap (frame={tf_fs = 16, tf_es = -791543792, tf_ds = -1072562160, tf_edi = 1, tf_esi = -1056803840, tf_ebp = -791482800, tf_isp = -791482820, tf_ebx = 0, tf_edx = 64, tf_ecx = -791482776, tf_eax = 1, tf_trapno = 12, tf_err = 0, tf_eip = -1072541595, tf_cs = 8, tf_eflags = 2163330, tf_esp = -791482664, tf_ss = -1072555584}) at ../../i386/i386/trap.c:427 #13 0xc0125065 in xpt_setup_ccb (ccb_h=0xd0d2ee68, path=0x40, priority=1) at ../../cam/cam_xpt.c:3734 #14 0xc01219c0 in cam_release_devq (path=0x40, relsim_flags=0, openings=0, timeout=0, getcount_only=0) at ../../cam/cam_periph.c:855 ---Type to continue, or q to quit--- #15 0xc0121b37 in camperiphdone (periph=0xc1021480, done_ccb=0xc1027400) at ../../cam/cam_periph.c:1021 #16 0xc0127997 in camisr (queue=0xc03189b0) at ../../cam/cam_xpt.c:6328 #17 0xc01277a9 in swi_cambio () at ../../cam/cam_xpt.c:6231 #18 0xc025b900 in splz_swi () #19 0xc01a7451 in softclock () at ../../kern/kern_timeout.c:131 #20 0xc025b85f in doreti_swi () Cannot access memory at address 0x91992874. (kgdb) up 13 #13 0xc0125065 in xpt_setup_ccb (ccb_h=0xd0d2ee68, path=0x40, priority=1) at ../../cam/cam_xpt.c:3734 3734 ccb_h->path = path; (kgdb) (kgdb) print path $1 = (struct cam_path *) 0x0 (kgdb) print ccb_h $2 = (struct ccb_hdr *) 0x0 (kgdb) up #14 0xc01219c0 in cam_release_devq (path=0x40, relsim_flags=0, openings=0, timeout=0, getcount_only=0) at ../../cam/cam_periph.c:855 855 xpt_setup_ccb(&crs.ccb_h, path, (kgdb) print path $5 = (struct cam_path *) 0x40 (kgdb) print *path Cannot access memory at address 0x40. ---snip--- It's a kernel from yesterday. Bye, Alexander. -- If Bill Gates had a dime for every time a Windows box crashed... ...Oh, wait a minute, he already does. http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" 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 31 21:10:20 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 3822C37BDF0; Mon, 31 Jul 2000 21:10:16 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id VAA23648; Mon, 31 Jul 2000 21:10:13 -0700 Date: Mon, 31 Jul 2000 21:10:16 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Alec Wolman Cc: freebsd-alpha@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: sym driver problem with 4.1 release In-Reply-To: <200008010329.UAA09102@sampras.cs.washington.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org It's not a sym problem- it's a da problem (if that). This is the wrong group to address this in. On Mon, 31 Jul 2000, Alec Wolman wrote: > > The problem that I posted yesterday about sysinstall is now looking to > me as if it is a problem with the sym driver. I managed to view > the boot message before sysinstall runs, and here is the problem: > > da0 at sym0 bus 0 target 0 lun 0 > Fixed Direct Access SCSI-2 device > da0: 10.000MB/sec transfers (10.000MHz, offset 31) Tagged Queueing Enabled > da0: Attempt to query device size failed: NOT READY, > (da0:sym0:0:0:0): . CDB: 25 0 0 0 0 0 0 0 0 0 > (da0:sym0:0:0:0): NOT READY asc:4,2 > (da0:sym0:0:0:0): > > > This disk (da0) has tru64 currently installed on it, and if > I boot off of it, it works fine. > > When I boot off of da1 (which has a version of 4.0-STABLE CVSup'ed around > Jun 18th, 2000), it probes properly at 40MHz, offset 31, 16 bit, with a > size of 8678MB. > > Alec > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-alpha" 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 31 23: 2:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id 9D09D37BDAF for ; Mon, 31 Jul 2000 23:02:25 -0700 (PDT) (envelope-from bright@fw.wintelcom.net) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id e715MEo00572 for scsi@freebsd.org; Mon, 31 Jul 2000 22:22:14 -0700 (PDT) Date: Mon, 31 Jul 2000 22:22:14 -0700 From: Alfred Perlstein To: scsi@freebsd.org Subject: Problems using a QUANTUM DLT 7000 Message-ID: <20000731222214.M4854@fw.wintelcom.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got a 3.5-stable box here that I just hooked a quantum-dlt-7000 to. I started getting IO errors after writing about 200 megabytes or so to it: Unexpected busfree. LASTPHASE == 0x0 SEQADDR == 0x10f (sa0:ahc0:0:14:0): WRITE FILEMARKS. CDB: 10 0 0 0 2 0 (sa0:ahc0:0:14:0): ILLEGAL REQUEST asc:3d,0 (sa0:ahc0:0:14:0): Invalid bits in identify message (sa0:ahc0:0:14:0): failed to write terminating filemark(s) (pass1:ahc0:0:14:0): Bus Device Reset Message Sent ahc0: Bus Device Reset on A:14. 1 SCBs aborted Here's my probe messages, anyone work with this stuff and can give a hint as to what I've messed up? ahc0: rev 0x00 int a irq 9 on pci0.20.0 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs Waiting 15 seconds for SCSI devices to settle sa0 at ahc0 bus 0 target 14 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) da0 at ahc0 bus 0 target 15 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 44884MB (91923356 512 byte sectors: 255H 63S/T 5721C) changing root device to wd0s1a cd0 at ahc0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 10.000MB/s transfers (10.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present sa and da are external devices with a terminator. cd0 is an internal device. I think the problem is that they're all on the same bus and the cd's transfer rate is not the same as the disk and tape. is that the case? What do i need to be doing here? -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 1 0: 2:15 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4B53737BDB3 for ; Tue, 1 Aug 2000 00:02:11 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id AAA24122; Tue, 1 Aug 2000 00:02:04 -0700 Date: Tue, 1 Aug 2000 00:02:07 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Alfred Perlstein Cc: scsi@FreeBSD.ORG Subject: Re: Problems using a QUANTUM DLT 7000 In-Reply-To: <20000731222214.M4854@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 31 Jul 2000, Alfred Perlstein wrote: > I've got a 3.5-stable box here that I just hooked a quantum-dlt-7000 > to. I started getting IO errors after writing about 200 megabytes or > so to it: > > Unexpected busfree. LASTPHASE == 0x0 > SEQADDR == 0x10f > (sa0:ahc0:0:14:0): WRITE FILEMARKS. CDB: 10 0 0 0 2 0 > (sa0:ahc0:0:14:0): ILLEGAL REQUEST asc:3d,0 > (sa0:ahc0:0:14:0): Invalid bits in identify message > (sa0:ahc0:0:14:0): failed to write terminating filemark(s) > (pass1:ahc0:0:14:0): Bus Device Reset Message Sent > ahc0: Bus Device Reset on A:14. 1 SCBs aborted > > Here's my probe messages, anyone work with this stuff and can > give a hint as to what I've messed up? I've seen this before with DLTs- they seem to just go out to lunch. What's happend above is that the DLT dropped the bus unexpectedly- this causes an EIO. The WRITE FILEMARKS (two terminating filemarks) is being blown away because somebody put something funky in an identify message- this may have been a parity error or an ahc bug. Then ahc decides to do a bus device reset on the tape drive. Nothing directly occurs to me on this- it's a cascade effect of something that the DLT does (no known reason) and then some stumbles in ahc. The sa driver is fairly blameless in all of this. My gut feeling says parity error. One response I've seen from targets (I don't think it's valid, but I do know they do this) on detecting a parity error is to drop off the bus. Instead, they should just abort the transaction with a CHECK CONDITION (as a lot of device do- next Sense Key will be ABORTED CMD and Parity Error as the ASC/ASCQ). But what happens next is some garbage is also detected by the target on the IDENTIFY message- seems to me that this is indicative of parity errors on the cable. > > ahc0: rev 0x00 int a irq 9 on pci0.20.0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > Waiting 15 seconds for SCSI devices to settle > sa0 at ahc0 bus 0 target 14 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit) > da0 at ahc0 bus 0 target 15 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 44884MB (91923356 512 byte sectors: 255H 63S/T 5721C) > changing root device to wd0s1a > cd0 at ahc0 bus 0 target 3 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 10.000MB/s transfers (10.000MHz, offset 15) > cd0: Attempt to query device size failed: NOT READY, Medium not present > > sa and da are external devices with a terminator. > cd0 is an internal device. I think the problem is that they're all > on the same bus and the cd's transfer rate is not the same as the > disk and tape. is that the case? What do i need to be doing here? > > -- > -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] > "I have the heart of a child; I keep it in a jar on my desk." > > > 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 Wed Aug 2 10: 5:24 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 1A80A37BD18 for ; Wed, 2 Aug 2000 10:05:13 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id LAA35306; Wed, 2 Aug 2000 11:04:37 -0600 (MDT) (envelope-from ken) Date: Wed, 2 Aug 2000 11:04:37 -0600 From: "Kenneth D. Merry" To: Alexander Leidinger Cc: scsi@FreeBSD.ORG, Matthew Jacob Subject: Re: Fwd: Panic in xpt_setup_ccb (cam_xpt.c) Message-ID: <20000802110437.A35016@panzer.kdm.org> References: <200007301035.MAA15223@Magelan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <200007301035.MAA15223@Magelan.Leidinger.net>; from Alexander@Leidinger.net on Sun, Jul 30, 2000 at 12:35:50PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Jul 30, 2000 at 12:35:50 +0200, Alexander Leidinger wrote: > Hi, > > forwarded to -scsi at request of Matthew Jacob (Note: I'm not subscribed > to -scsi). My hardware is: > ---snip--- > ahc0: port 0xb000-0xb0ff mem 0xd9800000-0xd9800fff irq 9 at device 6.0 on pci0 > ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs > cd0 at ahc0 bus 0 target 1 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 10.000MB/s transfers (10.000MHz, offset 15) > cd1 at ahc0 bus 0 target 2 lun 0 > cd1: Removable CD-ROM SCSI-2 device > cd1: 20.000MB/s transfers (20.000MHz, offset 15) > ---snip--- > > The panic happened with cd0. > > Matthew: > It didn't happen because of syncing prior to a reboot, it was a > "dd if=/dev/cd0c of=normal_file_on_ad0" (it's a "damaged" cd (someone > bought crappy CD-R's and I have to get some data out of them) and I > tried to duplicate the contents with dd). I was able to reproduce it, > and I'm sure I'm able to reproduce it with an actual kernel (at the > moment I'm recovering from a loss of / because of some shit from M$, -> > the crashdump is lost). I think Nick Hibma's analysis of this on -current was on target. The most likely explanation for this is that the device has gone away while there was an I/O pending. In this case, it was the error recovery code that hit the problem. When a device goes away, we return any I/O queued to the peripheral driver (in this case the cd driver) with errors, but we don't return any I/O queued to the card or the device. So the peripheral and path stored in the CCB have been freed, but the CCB is still outstanding, and the error recovery code is using a freed path. This is just a guess at what is going on, though, since we don't know for sure that the device has gone away. If you can get dmesg output from before when the panic happens, that would be helpful. If the device has gone away for some reason, you'll see "lost device" and "removing device entry" printed on the screen. I'm not sure how the device could have gone away, though, since we don't make the device go away automatically anymore. It used to be that if we got selection timeouts, the device would be automatically removed. We don't do that anymore, since it seemed to cause problems, so the only way a device can go away is if it doesn't make it through the probe stage or if someone initiates a rescan. (usually via camcontrol(8)) [ ... ] > #12 0xc02650bf in trap (frame={tf_fs = 16, tf_es = -791543792, > tf_ds = -1072562160, tf_edi = 1, tf_esi = -1056803840, > tf_ebp = -791482800, tf_isp = -791482820, tf_ebx = 0, tf_edx = 64, > tf_ecx = -791482776, tf_eax = 1, tf_trapno = 12, tf_err = 0, > tf_eip = -1072541595, tf_cs = 8, tf_eflags = 2163330, > tf_esp = -791482664, tf_ss = -1072555584}) at ../../i386/i386/trap.c:427 > #13 0xc0125065 in xpt_setup_ccb (ccb_h=0xd0d2ee68, path=0x40, priority=1) > at ../../cam/cam_xpt.c:3734 > #14 0xc01219c0 in cam_release_devq (path=0x40, relsim_flags=0, openings=0, > timeout=0, getcount_only=0) at ../../cam/cam_periph.c:855 > ---Type to continue, or q to quit--- > #15 0xc0121b37 in camperiphdone (periph=0xc1021480, done_ccb=0xc1027400) > at ../../cam/cam_periph.c:1021 > #16 0xc0127997 in camisr (queue=0xc03189b0) at ../../cam/cam_xpt.c:6328 > #17 0xc01277a9 in swi_cambio () at ../../cam/cam_xpt.c:6231 > #18 0xc025b900 in splz_swi () > #19 0xc01a7451 in softclock () at ../../kern/kern_timeout.c:131 > #20 0xc025b85f in doreti_swi () > Cannot access memory at address 0x91992874. > (kgdb) up 13 > #13 0xc0125065 in xpt_setup_ccb (ccb_h=0xd0d2ee68, path=0x40, priority=1) > at ../../cam/cam_xpt.c:3734 > 3734 ccb_h->path = path; > (kgdb) > (kgdb) print path > $1 = (struct cam_path *) 0x0 > (kgdb) print ccb_h > $2 = (struct ccb_hdr *) 0x0 > (kgdb) up > #14 0xc01219c0 in cam_release_devq (path=0x40, relsim_flags=0, openings=0, > timeout=0, getcount_only=0) at ../../cam/cam_periph.c:855 > 855 xpt_setup_ccb(&crs.ccb_h, path, > (kgdb) print path > $5 = (struct cam_path *) 0x40 > (kgdb) print *path > Cannot access memory at address 0x40. > ---snip--- > > It's a kernel from yesterday. [ ... ] Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 2 11:39:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id A283A37C328 for ; Wed, 2 Aug 2000 11:39:31 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA24892 for ; Wed, 2 Aug 2000 14:39:31 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA91830; Wed, 2 Aug 2000 14:39:30 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Wed, 2 Aug 2000 14:39:29 -0400 (EDT) To: freebsd-scsi@freebsd.org Subject: dual channel U160 adapters X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14728.26123.830234.107666@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We're looking for a good dual-channel U160 adapter to plug into a motherboard with multiple 64-bit/66MHz slots and enough I/O bandwidth to comfortably handle over 320MB/sec of DMA transfers. (we've measured over 450MB/sec). Is there anything else out there other than the Tekram DC-390U3D and the Adaptec 39160 which is generally available? Neither of these look ideal because it doesn't look like either one has enough PCI bandwidth available to be able to run both channels flat out at the same time. Adaptec's site says the 39160 is 64-bit but not 66MHz, so it will be limited to 256MB/sec. Tekram claims that the DC-390U3D is 64-bit/66MHz, but then says its limited to 266MB/sec.. Would we be better off with 2 Adaptec 29160's on different PCI busses? Thanks, Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 2 11:48:39 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 9158637B5F5 for ; Wed, 2 Aug 2000 11:48:36 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id LAA31182; Wed, 2 Aug 2000 11:48:35 -0700 Date: Wed, 2 Aug 2000 11:47:19 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Andrew Gallatin Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: dual channel U160 adapters In-Reply-To: <14728.26123.830234.107666@grasshopper.cs.duke.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org QLogic 12160. On Wed, 2 Aug 2000, Andrew Gallatin wrote: > > We're looking for a good dual-channel U160 adapter to plug into a > motherboard with multiple 64-bit/66MHz slots and enough I/O > bandwidth to comfortably handle over 320MB/sec of DMA transfers. > (we've measured over 450MB/sec). > > Is there anything else out there other than the Tekram DC-390U3D and > the Adaptec 39160 which is generally available? > > Neither of these look ideal because it doesn't look like either one > has enough PCI bandwidth available to be able to run both channels > flat out at the same time. Adaptec's site says the 39160 is 64-bit > but not 66MHz, so it will be limited to 256MB/sec. Tekram claims that > the DC-390U3D is 64-bit/66MHz, but then says its limited to > 266MB/sec.. > > Would we be better off with 2 Adaptec 29160's on different PCI busses? > > Thanks, > > Drew > > ------------------------------------------------------------------------------ > Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin > Duke University Email: gallatin@cs.duke.edu > Department of Computer Science Phone: (919) 660-6590 > > > > > 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 Wed Aug 2 12: 1: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-42.dsl.snfc21.pacbell.net [63.202.177.42]) by hub.freebsd.org (Postfix) with ESMTP id B73F437B845 for ; Wed, 2 Aug 2000 12:00:54 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id MAA01274; Wed, 2 Aug 2000 12:11:49 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008021911.MAA01274@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Andrew Gallatin Cc: freebsd-scsi@freebsd.org Subject: Re: dual channel U160 adapters In-reply-to: Your message of "Wed, 02 Aug 2000 14:39:29 EDT." <14728.26123.830234.107666@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Aug 2000 12:11:49 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Would we be better off with 2 Adaptec 29160's on different PCI busses? Try the Symbios Logic SYM22915, or anything else using the 53C1010 in a 64-bit/66MHz configuration. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 2 15:34:54 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from radius.wavefire.com (radius.wavefire.com [139.142.95.252]) by hub.freebsd.org (Postfix) with SMTP id 4E4DE37C09A for ; Wed, 2 Aug 2000 15:34:46 -0700 (PDT) (envelope-from darcy@ok-connect.com) Received: (qmail 481 invoked from network); 2 Aug 2000 22:34:39 -0000 Received: from ccliii.caniserv.com (HELO dbitech) (139.142.95.253) by radius.wavefire.com with SMTP; 2 Aug 2000 22:34:39 -0000 Message-Id: <3.0.32.20000802153723.020fba50@mail.ok-connect.com> X-Sender: darcyb@mail.ok-connect.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Wed, 02 Aug 2000 15:37:23 -0700 To: freebsd-scsi@freebsd.org From: Darcy Buskermolen Subject: AHA29160 Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has Support for the 64bit Adaptec AHA29160 PCI Scsi Controller found it's way into 3.5/4.1/5.0? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 2 16: 5:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id BA34737B50C for ; Wed, 2 Aug 2000 16:05:31 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA38815; Wed, 2 Aug 2000 17:05:27 -0600 (MDT) (envelope-from ken) Date: Wed, 2 Aug 2000 17:05:27 -0600 From: "Kenneth D. Merry" To: Darcy Buskermolen Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: AHA29160 Message-ID: <20000802170527.A38788@panzer.kdm.org> References: <3.0.32.20000802153723.020fba50@mail.ok-connect.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3.0.32.20000802153723.020fba50@mail.ok-connect.com>; from darcy@ok-connect.com on Wed, Aug 02, 2000 at 03:37:23PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Aug 02, 2000 at 15:37:23 -0700, Darcy Buskermolen wrote: > Has Support for the 64bit Adaptec AHA29160 PCI Scsi Controller found it's > way into 3.5/4.1/5.0? No, yes and yes. One note -- in 4.1 and 4.1-stable Adaptec Ultra160 controllers only run at 80MB/sec. They run at 160MB/sec in -current, but the changes haven't been merged to -stable yet. (They need time to make sure they're stable.) Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 3 0:23: 8 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mailgate.Cadence.COM (mailgate.Cadence.COM [158.140.2.1]) by hub.freebsd.org (Postfix) with ESMTP id 1C90637B797 for ; Thu, 3 Aug 2000 00:22:57 -0700 (PDT) (envelope-from ngr@cadence.com) Received: from symnt3.Cadence.COM (symnt3.Cadence.COM [194.32.101.100]) by mailgate.Cadence.COM (8.9.3/8.9.3) with ESMTP id AAA23445 for ; Thu, 3 Aug 2000 00:22:55 -0700 (PDT) Received: by symnt3.cadence.com with Internet Mail Service (5.5.2650.21) id ; Thu, 3 Aug 2000 08:20:08 +0100 Message-ID: <1E485299309FD211A2100090271E27A401AF0999@symnt3.cadence.com> From: Nigel Roles To: freebsd-scsi@FreeBSD.ORG Subject: RE: dual channel U160 adapters Date: Thu, 3 Aug 2000 08:19:59 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2650.21) Content-Type: text/plain; charset="iso-8859-1" X-Received: By mailgate.Cadence.COM as AAA23445 at Thu Aug 3 00:22:55 2000 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org For example, the Tekram DC390U3W works fine. -----Original Message----- From: Mike Smith [mailto:msmith@FreeBSD.ORG] Sent: 02 August 2000 20:12 To: Andrew Gallatin Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: dual channel U160 adapters > Would we be better off with 2 Adaptec 29160's on different PCI busses? Try the Symbios Logic SYM22915, or anything else using the 53C1010 in a 64-bit/66MHz configuration. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] 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 Thu Aug 3 3:18:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mout1.freenet.de (mout1.freenet.de [194.97.50.132]) by hub.freebsd.org (Postfix) with ESMTP id EA34E37B898 for ; Thu, 3 Aug 2000 03:18:22 -0700 (PDT) (envelope-from netchild@leidinger.net) Received: from [194.97.50.144] (helo=mx1.freenet.de) by mout1.freenet.de with esmtp (Exim 3.16 #2) id 13KI4m-0007l0-00; Thu, 03 Aug 2000 12:18:08 +0200 Received: from a394e.pppool.de ([213.6.57.78] helo=Magelan.Leidinger.net) by mx1.freenet.de with esmtp (Exim 3.16 #2) id 13KI4j-0001pZ-00; Thu, 03 Aug 2000 12:18:07 +0200 Received: from Leidinger.net (netchild@localhost [127.0.0.1]) by Magelan.Leidinger.net (8.9.3/8.9.3) with ESMTP id LAA00500; Thu, 3 Aug 2000 11:44:19 +0200 (CEST) (envelope-from netchild@Leidinger.net) Message-Id: <200008030944.LAA00500@Magelan.Leidinger.net> Date: Thu, 3 Aug 2000 11:44:16 +0200 (CEST) From: Alexander Leidinger Subject: Re: Fwd: Panic in xpt_setup_ccb (cam_xpt.c) To: ken@kdm.org Cc: scsi@FreeBSD.ORG, mjacob@feral.com In-Reply-To: <20000802110437.A35016@panzer.kdm.org> MIME-Version: 1.0 Content-Type: TEXT/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 2 Aug, Kenneth D. Merry wrote: > If you can get dmesg output from before when the panic happens, that would > be helpful. If the device has gone away for some reason, you'll see "lost > device" and "removing device entry" printed on the screen. No such message in /var/log/messages, but I have other SCSI-related messages there. > I'm not sure how the device could have gone away, though, since we don't > make the device go away automatically anymore. It used to be that if we > got selection timeouts, the device would be automatically removed. Please see my answer to Nick's mail (sorry, I had a typo in "scsi@freebsd.org", so it's only in -current and not in -scsi), it lists some SCSI-related messages from /var/log/messages. Bye, Alexander. -- Where do you think you're going today? http://www.Leidinger.net Alexander @ Leidinger.net GPG fingerprint = 7423 F3E6 3A7E B334 A9CC B10A 1F5F 130A A638 6E7E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 3 6:47:27 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.utcorp.net (x-montana.utcorp.com [146.145.135.26]) by hub.freebsd.org (Postfix) with ESMTP id 08F9037B72E for ; Thu, 3 Aug 2000 06:47:20 -0700 (PDT) (envelope-from kseel@utcorp.com) Received: from [146.145.135.17] (helo=utcorp.com) by mail.utcorp.net with esmtp (Exim 3.03 #1) id 13KLJ6-00032E-00 for freebsd-scsi@FreeBSD.ORG; Thu, 03 Aug 2000 09:45:08 -0400 Message-ID: <39897BC2.3C8E4048@utcorp.com> Date: Thu, 03 Aug 2000 10:03:46 -0400 From: Kurt Seel Organization: dis X-Mailer: Mozilla 4.5 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: Problem with sysinstall seeing LVD drives Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all. I have been having an awful time trying to put a pair of LVD drives into a server. After much trouble with a pair of barracudas with faulty write caches, I now have 2 IBM drives : da28 at ahc2 bus 0 target 0 lun 0 da28: Fixed Direct Access SCSI-3 device da28: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da28: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) da36 at ahc2 bus 0 target 8 lun 0 da36: Fixed Direct Access SCSI-3 device da36: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da36: 17501MB (35843670 512 byte sectors: 255H 63S/T 2231C) They are running on an adaptec 2940u2w: ahc2: rev 0x00 int a irq 18 on pci0.18.0 ahc2: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs I can newfs the 'c' partition, and mount it. But sysinstall refuses to see the drives. I know it is possible to do this by hand with command line utils, but it has been many years now sense I have done this, I wouldn't relish the idea. A friend told me he had this same trouble, he had IDE drives enabled, he disabled them and it stopped. I have IDE drives, so I tried this, no dice. It has been weeks I been fooling with this, drives being cross shipped, waiting until after 5 (so as not to bother the programmers). I am thinking of joining the french foreign legion soon. -- In theory, there is no difference between theory and practice. In practice, however, there is. - Unknown To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 3 14:38:47 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from june.cs.washington.edu (june.cs.washington.edu [128.95.1.4]) by hub.freebsd.org (Postfix) with ESMTP id 7158037B830 for ; Thu, 3 Aug 2000 14:38:44 -0700 (PDT) (envelope-from wolman@cs.washington.edu) Received: from miles.cs.washington.edu (miles.cs.washington.edu [128.95.4.177]) by june.cs.washington.edu (8.9.3/8.9.3/0.3j) with ESMTP id OAA83956 for ; Thu, 3 Aug 2000 14:38:43 -0700 (PDT) (envelope-from wolman@cs.washington.edu) Received: from miles.cs.washington.edu (localhost [127.0.0.1]) by miles.cs.washington.edu (8.9.3/8.9.3) with ESMTP id OAA02824 for ; Thu, 3 Aug 2000 14:38:42 -0700 (PDT) (envelope-from wolman@miles.cs.washington.edu) Message-Id: <200008032138.OAA02824@miles.cs.washington.edu> X-Mailer: exmh version 2.1.1 10/15/1999 To: freebsd-scsi@freebsd.org Subject: is the message "bad sector table not supported" harmless? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Aug 2000 14:38:42 -0700 From: "Alec Wolman" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I recently upgraded a machine from 3.3-Release to 4.1-Release. I am now getting the following messages on the console: da1: bad sector table not supported da1s1: bad sector table not supported da1: bad sector table not supported da1s1: bad sector table not supported da1: bad sector table not supported da1s1: bad sector table not supported Here is a description of "da1": da1 at ahc0 bus 0 target 3 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 4091MB (8380080 512 byte sectors: 255H 63S/T 521C) I realize that support for bad sector remapping was removed at some point between 3.3 and 4.1, and I was just wondering what the consequences of that removal are. Do I need to worry about the data on this filesystem? Is there anything I should do about this? Thanks in advance, Alec To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 3 14:42:49 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from sun.rhrk.uni-kl.de (sun.rhrk.uni-kl.de [131.246.137.50]) by hub.freebsd.org (Postfix) with SMTP id 331E537B860 for ; Thu, 3 Aug 2000 14:42:37 -0700 (PDT) (envelope-from mheller@rhrk.uni-kl.de) Received: from aixs1.rhrk.uni-kl.de ( exim@aixs1.rhrk.uni-kl.de [131.246.137.3] ) by sun.rhrk.uni-kl.de id aa27723 ; 3 Aug 2000 23:42 MESZ Received: from aixd1.rhrk.uni-kl.de ([131.246.137.210] ident=exim) by aixs1.rhrk.uni-kl.de with esmtp (Exim 3.03 #2) id 13KSl2-000AyO-00; Thu, 03 Aug 2000 23:42:28 +0200 Received: from mheller (helo=localhost) by aixd1.rhrk.uni-kl.de with local-esmtp (Exim 3.03 #2) id 13KSl1-000OJq-00; Thu, 03 Aug 2000 23:42:27 +0200 Date: Thu, 3 Aug 2000 23:42:27 +0200 (MES) From: Martin Heller X-Sender: mheller@aixd1.rhrk.uni-kl.de To: bellefso@execpc.com Cc: freebsd-scsi@freebsd.org Subject: RE: Tekram DC390U3W Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello Brian, I see this behaviour with my UW drive, too. Crazy thing is, my DAT-tape get's 5 MB/s ?? I'll test it tomorrow with a U160 disk. The list freebsd-scsi is perhaps more appropriate. MARTIN To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 3 16:15:46 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from firebat.Bushong.NET (c128625-a.frmt1.sfba.home.com [24.5.196.12]) by hub.freebsd.org (Postfix) with ESMTP id 973D637B5D6 for ; Thu, 3 Aug 2000 16:15:44 -0700 (PDT) (envelope-from dbushong@firebat.Bushong.NET) Received: (from dbushong@localhost) by firebat.Bushong.NET (8.9.3/8.9.3) id QAA18518 for freebsd-scsi@freebsd.org; Thu, 3 Aug 2000 16:15:44 -0700 (PDT) (envelope-from dbushong) Date: Thu, 3 Aug 2000 16:15:44 -0700 From: David Bushong To: freebsd-scsi@freebsd.org Subject: Any solution to 29160 problems? Message-ID: <20000803161544.A18478@bushong.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Floating-Sheep-Port: 0xbaa Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've experienced problems with my onboard Adaptec 29160 on my SuperMicro 370DL3 motherboard, and have noticed previous posts to this group of people with problems of the same type: (da0:ahc0:0:0:0): SCB 0x19 - timed out while idle, SEQADDR == 0xb (da0:ahc0:0:0:0): Queuing a BDR SCB ahc0: WARNING no command for scb 25 (cmdcmplt) QOUTPOS = 8 and ahc0: Issued Channel A Bus Reset. 1 SCBs aborted ahc0:A:1: ahc_intr - referenced scb not valid during seqint 0x71 scb(25) (da0:ahc0:0:0:0): Queuing a BDR SCB and so on. At least one person had this problem the same time as I did, right during the install process. Occasionally, it makes it through these warnings, and sometimes it hangs. I haven't seen any replies of suggestions or solutions to this. Is this a known problem? Is there any fix? If this is fixed in source, what are feasible ways for acutally getting a kernel built with that fixed source? Right now I'm dead in the water with my new machine as it has only LVD U160 drives, and I can't seem to find Adaptec 2940U2W's anymore. --David Bushong To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 3 16:23:26 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 2EB0837B87C for ; Thu, 3 Aug 2000 16:23:20 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA47253; Thu, 3 Aug 2000 17:23:04 -0600 (MDT) (envelope-from ken) Date: Thu, 3 Aug 2000 17:23:04 -0600 From: "Kenneth D. Merry" To: David Bushong Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Any solution to 29160 problems? Message-ID: <20000803172304.A47218@panzer.kdm.org> References: <20000803161544.A18478@bushong.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20000803161544.A18478@bushong.net>; from david@bushong.net on Thu, Aug 03, 2000 at 04:15:44PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Aug 03, 2000 at 16:15:44 -0700, David Bushong wrote: > I've experienced problems with my onboard Adaptec 29160 on my SuperMicro 370DL3 > motherboard, and have noticed previous posts to this group of people with > problems of the same type: > > (da0:ahc0:0:0:0): SCB 0x19 - timed out while idle, SEQADDR == 0xb > (da0:ahc0:0:0:0): Queuing a BDR SCB > ahc0: WARNING no command for scb 25 (cmdcmplt) > QOUTPOS = 8 > > and > > ahc0: Issued Channel A Bus Reset. 1 SCBs aborted > ahc0:A:1: ahc_intr - referenced scb not valid during seqint 0x71 scb(25) > (da0:ahc0:0:0:0): Queuing a BDR SCB > > and so on. At least one person had this problem the same time as I did, > right during the install process. Occasionally, it makes it through these > warnings, and sometimes it hangs. I haven't seen any replies of suggestions > or solutions to this. Is this a known problem? Is there any fix? If this > is fixed in source, what are feasible ways for acutally getting a kernel > built with that fixed source? Right now I'm dead in the water with my new > machine as it has only LVD U160 drives, and I can't seem to find Adaptec > 2940U2W's anymore. What version of FreeBSD are you using? Justin has made a number of changes recently in the -current Adaptec driver, so it is possible that your problem has been fixed. I would suggest pulling down a boot floppy from the latest snapshot on current.freebsd.org, and see if it fixes your problem. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 3 16:24:38 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-42.dsl.snfc21.pacbell.net [63.202.177.42]) by hub.freebsd.org (Postfix) with ESMTP id 40B7037B87C for ; Thu, 3 Aug 2000 16:24:32 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id QAA05084; Thu, 3 Aug 2000 16:35:14 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008032335.QAA05084@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: David Bushong Cc: freebsd-scsi@freebsd.org Subject: Re: Any solution to 29160 problems? In-reply-to: Your message of "Thu, 03 Aug 2000 16:15:44 PDT." <20000803161544.A18478@bushong.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Aug 2000 16:35:14 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've experienced problems with my onboard Adaptec 29160 on my SuperMicro 370DL3 > motherboard, and have noticed previous posts to this group of people with > problems of the same type: > > (da0:ahc0:0:0:0): SCB 0x19 - timed out while idle, SEQADDR == 0xb > (da0:ahc0:0:0:0): Queuing a BDR SCB > ahc0: WARNING no command for scb 25 (cmdcmplt) > QOUTPOS = 8 > > and > > ahc0: Issued Channel A Bus Reset. 1 SCBs aborted > ahc0:A:1: ahc_intr - referenced scb not valid during seqint 0x71 scb(25) > (da0:ahc0:0:0:0): Queuing a BDR SCB > > and so on. At least one person had this problem the same time as I did, > right during the install process. Occasionally, it makes it through these > warnings, and sometimes it hangs. I haven't seen any replies of suggestions > or solutions to this. Is this a known problem? Is there any fix? If this > is fixed in source, what are feasible ways for acutally getting a kernel > built with that fixed source? Right now I'm dead in the water with my new > machine as it has only LVD U160 drives, and I can't seem to find Adaptec > 2940U2W's anymore. You don't bother telling us which disk(s) you're seeing this with, however if they happen to be Seagate Cheetah or Barracuda drives, this is a known problem and the correct fix is to obtain a firmware update from Seagate. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 3 16:33:29 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from firebat.Bushong.NET (c128625-a.frmt1.sfba.home.com [24.5.196.12]) by hub.freebsd.org (Postfix) with ESMTP id 0E43537B87C; Thu, 3 Aug 2000 16:33:23 -0700 (PDT) (envelope-from dbushong@firebat.Bushong.NET) Received: (from dbushong@localhost) by firebat.Bushong.NET (8.9.3/8.9.3) id QAA18987; Thu, 3 Aug 2000 16:33:22 -0700 (PDT) (envelope-from dbushong) Date: Thu, 3 Aug 2000 16:33:22 -0700 From: David Bushong To: Mike Smith Cc: freebsd-scsi@freebsd.org Subject: Re: Any solution to 29160 problems? Message-ID: <20000803163322.B18478@bushong.net> References: <20000803161544.A18478@bushong.net> <200008032335.QAA05084@mass.osd.bsdi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200008032335.QAA05084@mass.osd.bsdi.com>; from msmith@freebsd.org on Thu, Aug 03, 2000 at 04:35:14PM -0700 X-Floating-Sheep-Port: 0xbaa Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Very sorry. More detail: 4x IBM 36ZX (10k rpm, 36GB U160 LVD) 4.1-RELEASE SuperMicro 370DL3 Motherboard Here's the dmesg output: --------8<--------------8<------------8<--------------8<----------------------- Copyright (c) 1992-2000 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.1-RELEASE #0: Thu Jul 27 04:44:16 GMT 2000 root@usw4.freebsd.org:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (732.98-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x683 Stepping = 3 Features=0x383fbff real memory = 536805376 (524224K bytes) config> di pcic0 config> di sn0 config> di lnc0 config> di le0 config> di ie0 config> di fe0 config> di ed0 config> di cs0 config> di bt0 config> di ata1 config> di aic0 config> di aha0 config> di adv0 config> q avail memory = 518033408 (505892K bytes) Preloaded elf kernel "kernel" at 0xc040d000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc040d09c. Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pci0: at 1.0 irq 11 fxp0: port 0xd800-0xd83f mem 0xfe800000-0xfe8fffff,0xfe9fd000-0xfe9fdfff irq 9 at device 6.0 on pci0 fxp0: Ethernet address 00:30:48:10:5d:22 isab0: at device 15.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 15.1 on pci0 ata0: at 0x1f0 irq 14 on atapci0 ohci0: mem 0xfe9fe000-0xfe9fefff irq 10 at device 15.2 on pci0 usb0: OHCI version 1.0, legacy support usb0: on ohci0 usb0: USB revision 1.0 uhub0: (unknown) OHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 4 ports with 4 removable, self powered pcib1: on motherboard pci1: on pcib1 ahc0: port 0xe800-0xe8ff mem 0xfebff000-0xfebfffff irq 10 at device 3.0 on pci1 ahc0: aic7892 Wide Channel A, SCSI Id=7, 16/255 SCBs fdc0: at port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on isa0 fdc0: FIFO enabled, 8 bytes threshold fd0: <1440-KB 3.5" drive> on fdc0 drive 0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: flags 0x1 irq 1 on atkbdc0 kbd0 at atkbd0 vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> sio0 at port 0x3f8-0x3ff irq 4 flags 0x10 on isa0 sio0: type 16550A sio1 at port 0x2f8-0x2ff irq 3 on isa0 sio1: type 16550A ppc0: at port 0x378-0x37f irq 7 on isa0 ppc0: Generic chipset (EPP/NIBBLE) in COMPATIBLE mode ppi0: on ppbus0 lpt0: on ppbus0 lpt0: Interrupt-driven port plip0: on ppbus0 acd0: CDROM at ata0-master using PIO4 Waiting 15 seconds for SCSI devices to settle Mounting root from ufs:/dev/da0s1a da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da0: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da1: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) da2 at ahc0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da2: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) da3 at ahc0 bus 0 target 3 lun 0 da3: Fixed Direct Access SCSI-3 device da3: 80.000MB/s transfers (40.000MHz, offset 63, 16bit), Tagged Queueing Enabled da3: 35003MB (71687340 512 byte sectors: 255H 63S/T 4462C) --------8<--------------8<------------8<--------------8<----------------------- On Thu, Aug 03, 2000 at 04:35:14PM -0700, Mike Smith wrote: > > I've experienced problems with my onboard Adaptec 29160 on my SuperMicro 370DL3 > > motherboard, and have noticed previous posts to this group of people with > > problems of the same type: > > > > (da0:ahc0:0:0:0): SCB 0x19 - timed out while idle, SEQADDR == 0xb > > (da0:ahc0:0:0:0): Queuing a BDR SCB > > ahc0: WARNING no command for scb 25 (cmdcmplt) > > QOUTPOS = 8 > > > > and > > > > ahc0: Issued Channel A Bus Reset. 1 SCBs aborted > > ahc0:A:1: ahc_intr - referenced scb not valid during seqint 0x71 scb(25) > > (da0:ahc0:0:0:0): Queuing a BDR SCB > > > > and so on. At least one person had this problem the same time as I did, > > right during the install process. Occasionally, it makes it through these > > warnings, and sometimes it hangs. I haven't seen any replies of suggestions > > or solutions to this. Is this a known problem? Is there any fix? If this > > is fixed in source, what are feasible ways for acutally getting a kernel > > built with that fixed source? Right now I'm dead in the water with my new > > machine as it has only LVD U160 drives, and I can't seem to find Adaptec > > 2940U2W's anymore. > > You don't bother telling us which disk(s) you're seeing this with, > however if they happen to be Seagate Cheetah or Barracuda drives, this is > a known problem and the correct fix is to obtain a firmware update from > Seagate. > > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 3 16:37:53 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.osd.bsdi.com (adsl-63-202-177-42.dsl.snfc21.pacbell.net [63.202.177.42]) by hub.freebsd.org (Postfix) with ESMTP id A43C437B87C for ; Thu, 3 Aug 2000 16:37:50 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.9.3/8.9.3) with ESMTP id QAA05189; Thu, 3 Aug 2000 16:48:53 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200008032348.QAA05189@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: David Bushong Cc: freebsd-scsi@freebsd.org Subject: Re: Any solution to 29160 problems? In-reply-to: Your message of "Thu, 03 Aug 2000 16:33:22 PDT." <20000803163322.B18478@bushong.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Aug 2000 16:48:53 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Very sorry. More detail: > > 4x IBM 36ZX (10k rpm, 36GB U160 LVD) > 4.1-RELEASE > SuperMicro 370DL3 Motherboard ... > pcib0: on motherboard This more or less directly matches a problem that Dell were seeing with the same disks and motherboard chipset; at that point Justin was thinking that it might even be chipset related. I'm not sure what the current feeling is. -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 4 10:37:37 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from acmeacres.infoscientific.com (acmeacres.infoscientific.com [63.84.120.81]) by hub.freebsd.org (Postfix) with ESMTP id 40A9237BA21; Fri, 4 Aug 2000 10:37:30 -0700 (PDT) (envelope-from harry@infoscientific.com) Received: from furball ([63.84.120.90]) by acmeacres.infoscientific.com (8.8.5/8.7.3) with SMTP id KAA21043; Fri, 4 Aug 2000 10:41:41 -0700 (PDT) Message-ID: <042201bffe3a$8d3e1e80$5a78543f@infoscientific.com> From: "Harry Reed" To: , Subject: Python 4320 DAT + FreeBSD-4.x Date: Fri, 4 Aug 2000 10:36:41 -0700 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, All I am having problems using my Python 4320 DAT drive under FreeBSD-4.x. When I boot either FreeBSD-4.0 or 4.1 the boot hangs when it waits for the SCSI devices to settle. No error messages, etc. - just sits there until I do a reset. I've tried 2 different SCSI controllers - Adaptec 1542c and Advansys ABP5140 - no difference. The drive works fine under FreeBSD-2.x, and 3.x (incl 3.5.1) and various Micro$oft OS's, but is completely useless under 4.x. Any ideas? Thanks, Harry Reed To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 4 11:10:34 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail-2.sjc.telocity.net (mail-2.sjc.telocity.net [216.227.56.42]) by hub.freebsd.org (Postfix) with ESMTP id 06DBC37BAA5; Fri, 4 Aug 2000 11:10:22 -0700 (PDT) (envelope-from otterr@telocity.com) Received: from zoso (dsl-216-227-91-85.telocity.com [216.227.91.85]) by mail-2.sjc.telocity.net (8.9.3/8.9.3) with SMTP id LAA15739; Fri, 4 Aug 2000 11:04:48 -0700 (PDT) From: "Otter" To: "Harry Reed" , , Subject: RE: Python 4320 DAT + FreeBSD-4.x Date: Fri, 4 Aug 2000 14:09:24 -0400 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) In-Reply-To: <042201bffe3a$8d3e1e80$5a78543f@infoscientific.com> X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Importance: Normal Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -----Original Message----- > From: owner-freebsd-questions@FreeBSD.ORG > [mailto:owner-freebsd-questions@FreeBSD.ORG]On Behalf Of Harry Reed > Sent: Friday, August 04, 2000 1:37 PM > To: freebsd-questions@FreeBSD.ORG; freebsd-scsi@FreeBSD.ORG > Subject: Python 4320 DAT + FreeBSD-4.x > > > Hi, All > I am having problems using my Python 4320 DAT drive > under FreeBSD-4.x. > When I boot either FreeBSD-4.0 or 4.1 the boot hangs when > it waits for the > SCSI devices to settle. No error messages, etc. - just sits > there until I do > a reset. I've tried 2 different SCSI controllers - Adaptec 1542c and > Advansys ABP5140 - no difference. The drive works fine > under FreeBSD-2.x, > and 3.x (incl 3.5.1) and various Micro$oft OS's, but is > completely useless > under 4.x. Any ideas? > > Thanks, > Harry Reed > I have an Adaptec 1542CF which worked fine in 2.x and up to 3.3, at which time I replaced it with a 2940U2W controller and moved to the 4.0-current branch. I haven't tested it in 4.0 or 5.0. One of my friends told me he heard that the 154x's don't work in 4.0 if you have more than 32mb. It sounds like BS to poor white trash like myself. Is there any truth to this? If so, what decides the limit? -Otter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 4 11:24:59 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from markl.com (markl.com [209.69.36.90]) by hub.freebsd.org (Postfix) with ESMTP id 07E0D37B66A; Fri, 4 Aug 2000 11:24:55 -0700 (PDT) (envelope-from squirrel@hammis.com) Received: from localhost (squirrel@localhost) by markl.com (8.9.3/8.9.3) with ESMTP id OAA03921; Fri, 4 Aug 2000 14:26:32 -0400 (EDT) (envelope-from squirrel@hammis.com) Date: Fri, 4 Aug 2000 14:26:31 -0400 (EDT) From: Damon Hammis X-Sender: squirrel@markl.com To: Otter Cc: Harry Reed , freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: RE: Python 4320 DAT + FreeBSD-4.x In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have an Adaptec 1542CF which worked fine in 2.x and up to 3.3, at > which time I replaced it with a 2940U2W controller and moved to the > 4.0-current branch. I haven't tested it in 4.0 or 5.0. One of my > friends told me he heard that the 154x's don't work in 4.0 if you have > more than 32mb. It sounds like BS to poor white trash like myself. Is > there any truth to this? If so, what decides the limit? > -Otter I have a 1540 working in 4.0-RELEASE and 4.1-RELEASE with 48 MB of RAM in the systems. The only problem I have with it is that since 4.0 came out my soundblaster won't work with it. --Damon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 4 11:35:30 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by hub.freebsd.org (Postfix) with ESMTP id 476B437B67C; Fri, 4 Aug 2000 11:35:26 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.9.3/8.9.3) with ESMTP id OAA05513; Fri, 4 Aug 2000 14:35:15 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.9.3/8.9.1) id OAA96698; Fri, 4 Aug 2000 14:35:15 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 4 Aug 2000 14:35:14 -0400 (EDT) To: Mike Smith Cc: David Bushong , freebsd-scsi@freebsd.org Subject: Re: Any solution to 29160 problems? In-Reply-To: <200008032348.QAA05189@mass.osd.bsdi.com> References: <20000803163322.B18478@bushong.net> <200008032348.QAA05189@mass.osd.bsdi.com> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14731.2604.380507.580044@grasshopper.cs.duke.edu> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Mike Smith writes: > > Very sorry. More detail: > > > > 4x IBM 36ZX (10k rpm, 36GB U160 LVD) > > 4.1-RELEASE > > SuperMicro 370DL3 Motherboard > ... > > pcib0: on motherboard > > This more or less directly matches a problem that Dell were seeing with > the same disks and motherboard chipset; at that point Justin was thinking > that it might even be chipset related. I'm not sure what the current > feeling is. We don't have IBM drives, but for what its worth, the same chipset (which is used in Dell's PowerEdge servers) works just dandy with adaptec 160 controllers & Cheetahs. I backported Justin's recent U160 ahc driver changes to 4.0-RELEASE & I've been able to max the scsi bus out at over 135MB/sec with 4 ST318404LC cheetahs. (This was using a 29160 controller; the pe4400's onboard 7899 is on a 32-bit pci bus -- oops!). We've been running for months with the on-board aic7899 using 4.0-RELEASE's standard ahc driver (u2 speeds only) & beating on the disks very hard. I have yet to see a complaint from the scsi layer. Drew ------------------------------------------------------------------------------ Andrew Gallatin, Sr Systems Programmer http://www.cs.duke.edu/~gallatin Duke University Email: gallatin@cs.duke.edu Department of Computer Science Phone: (919) 660-6590 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 4 12:36:36 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from alchemy.grabstein.net (rx1072.cip.uni-regensburg.de [132.199.216.168]) by hub.freebsd.org (Postfix) with ESMTP id E229637B78B for ; Fri, 4 Aug 2000 12:36:23 -0700 (PDT) (envelope-from corex@alchemy.grabstein.net) Received: (from corex@localhost) by alchemy.grabstein.net (8.9.3/8.9.3/GRABSTEIN.NET) id VAA87090 for freebsd-scsi@freebsd.org; Fri, 4 Aug 2000 21:36:57 +0200 (CEST) (envelope-from corex) Date: Fri, 4 Aug 2000 21:36:57 +0200 From: marius@soylent-green.org To: freebsd-scsi@freebsd.org Subject: telling CAM to never timeout a transaction Message-ID: <20000804213657.A87057@alchemy.grabstein.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org hi could anyone tell me the parameter to make CAM never timeout a transaction ? i need it to get rid of a problem with a dpt raid controller: Aug 4 13:16:13 newtrinity /kernel: (da0:dpt0:0:0:0): CCB 0xc83fd07c - timed out Aug 4 13:16:13 newtrinity /kernel: (da0:dpt0:0:0:0): CCB 0xc83fd07c - timed out CCB already completed simon shapiro who did the freebsd support for dpt controllers told me to first check if the array has a lost disk which normally causes this problem but it hasn't he told me further this is a classic problem if the dpt firmware takes too long in the opinion of the cam abstraction layer to complete a transaction and then the dpt completes a "non-existing" transaction a while later i already wrote an email to justin gibbs to tell me the parameter but he unfortunately didn't reply i had a look to the cam sources but i didn't see something concerning disabling the timeout for transaction thanks marius To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 4 12:38:35 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 85BEE37B71D for ; Fri, 4 Aug 2000 12:38:32 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo.feral.com (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA07366; Fri, 4 Aug 2000 12:38:29 -0700 Date: Fri, 4 Aug 2000 12:38:32 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: marius@soylent-green.org Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: telling CAM to never timeout a transaction In-Reply-To: <20000804213657.A87057@alchemy.grabstein.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Fix the da driver to have an infinite timeout On Fri, 4 Aug 2000 marius@soylent-green.org wrote: > hi > > could anyone tell me the parameter to make CAM never timeout a transaction ? > i need it to get rid of a problem with a dpt raid controller: > > Aug 4 13:16:13 newtrinity /kernel: (da0:dpt0:0:0:0): CCB 0xc83fd07c - timed out > Aug 4 13:16:13 newtrinity /kernel: (da0:dpt0:0:0:0): CCB 0xc83fd07c - timed out CCB already completed > > simon shapiro who did the freebsd support for dpt controllers told me to first check if the array has a lost disk which normally causes this problem but it hasn't > > he told me further this is a classic problem if the dpt firmware takes too long in the opinion of the cam abstraction layer to complete a transaction and then the dpt completes a "non-existing" transaction a while later > > i already wrote an email to justin gibbs to tell me the parameter but he unfortunately didn't reply > > i had a look to the cam sources but i didn't see something concerning disabling the timeout for transaction > > thanks > marius > > > 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