From owner-freebsd-scsi Tue Dec 2 23:48:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA18350 for freebsd-scsi-outgoing; Tue, 2 Dec 1997 23:48:31 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from inc.net (beta.inc.net [204.95.160.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA18342 for ; Tue, 2 Dec 1997 23:48:27 -0800 (PST) (envelope-from steve@inc.net) Received: (from steve@localhost) by inc.net (8.8.5/8.7.3) id BAA28029; Wed, 3 Dec 1997 01:32:21 -0600 (CST) Date: Wed, 3 Dec 1997 01:32:21 -0600 (CST) From: "Steve R. Kaczkowski" To: freebsd-scsi@freebsd.org Subject: BT-958 ASYNC Lameness fixed? 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 Here's my setup: ABIT IT5H 2.0 P5 166MMX 64Mb Ram Buslogic BT-958 (!) 2x 9.1 GB Fast Wide IBM Drives Everything seems to work fine, but upon bootup I notice: Feb 13 05:01:32 imap /kernel: bt0: Bt958 / 0-(32bit) bus Feb 13 05:01:32 imap /kernel: bt0: reading board settings, busmastering, int=14 Feb 13 05:01:32 imap /kernel: bt0: version 5.06I, async only, parity, 32 mbxs, 32 ccbs Feb 13 05:01:32 imap /kernel: bt0: targ 0 async Feb 13 05:01:32 imap /kernel: bt0: targ 1 async (Guess I should fix the date :) ) Hmmm, ASYNC only (5 Mbps?!?) whats the deal? Checked bios setup on BT-958, everything is cool there,etc,etc,etc... Then I got a bit curious so I dug around the FBSD web pages and found some stuff.... Ahhhh, it *IS* a problem.. Seems that the driver is a BIT behind and the card responds with different info and it defaults to SLOW SLOW mode... So, the question is: WHEN AND WHO is going to fix this little(!!??) problem?? I'd really hate to have to dump the Buslogic for an Adaptec, but if I must, I must... Let me know here or private! -Steve Kaczkowski steve@inc.net From owner-freebsd-scsi Wed Dec 3 05:23:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA07530 for freebsd-scsi-outgoing; Wed, 3 Dec 1997 05:23:48 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from mail.netcetera.dk (root@sleipner.netcetera.dk [194.192.207.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA07523 for ; Wed, 3 Dec 1997 05:23:42 -0800 (PST) (envelope-from leifn@image.dk) Received: (from uucp@localhost) by mail.netcetera.dk (8.8.8/8.8.8) with UUCP id OAA04251 for freebsd-scsi@freebsd.org; Wed, 3 Dec 1997 14:20:51 +0100 Received: by swimsuit.roskildebc.dk (0.99.970109) id AA07706; 03 Dec 97 14:15:01 +0100 From: leifn@image.dk (Leif Neland) Date: 03 Dec 97 14:05:39 +0100 Subject: how to write shorter blocks with Adaptec 1542A? Message-ID: <55f_9712031415@swimsuit.roskildebc.dk> Organization: Fidonet: UNIX-sysadm søger job To: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a problem with my Adaptec 1542A writing bursts of 0xff at block-boundaries (0x2001,0xc001 etc), but only on fbsd-partitions, not on msdos-mounted partitions. The reason should be that the msdos driver only writes in blocks <=4K, whereas the ffs(?) driver writes larger blocks. I have been told to reduce the blocksize by means of minphys(), but I really don't know how. I have searched /usr/src/scsi/*, and have found some mentioning of minphys, but not how to limit the size. If somebody could explain it in simple terms, I would be most gratefull(sp?) Leif Neland leifn@image.dk --- |Fidonet: Leif Neland 2:234/49 |Internet: leifn@image.dk From owner-freebsd-scsi Wed Dec 3 07:16:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA15027 for freebsd-scsi-outgoing; Wed, 3 Dec 1997 07:16:57 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from conductor.synapse.net (conductor.synapse.net [199.84.54.18]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA15012 for ; Wed, 3 Dec 1997 07:16:50 -0800 (PST) (envelope-from evanc@synapse.net) Received: (qmail 10441 invoked from network); 3 Dec 1997 15:16:42 -0000 Received: from cello.synapse.net (199.84.54.81) by conductor.synapse.net with SMTP; 3 Dec 1997 15:16:42 -0000 Date: Wed, 3 Dec 1997 10:16:42 -0500 (EST) From: Evan Champion Reply-To: Evan Champion To: "Steve R. Kaczkowski" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: BT-958 ASYNC Lameness fixed? 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 Wed, 3 Dec 1997, Steve R. Kaczkowski wrote: > Ahhhh, it *IS* a problem.. Seems that the driver is a BIT behind and the > card responds with different info and it defaults to SLOW SLOW mode... It doesn't seem to be a problem on 3.0-current... bt0: rev 0x08 int a irq 14 on pci0.10.0 bt0: Bt958 / 0-(32bit) bus bt0: reading board settings, busmastering, int=14 bt0: version 5.07B, fast sync, parity, 32 mbxs, 32 ccbs bt0: targ 0 sync rate=10.00MB/s(100ns), offset=15 bt0: targ 6 sync rate=10.00MB/s(100ns), offset=15 bt0: Using Strict Round robin scheme scbus0 at bt0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 2047MB (4194058 512 byte sectors) cd0 at scbus0 target 6 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM cd present [272451 x 2048 byte records] (of course, it is misreporting my first target; it is a fast and wide device, so it should be reporting it as 20 MB/s). I suspect a) this problem isn't actually a problem, in that it's not the OS that decides if the device will run async, but the card itself, and b) if you want to get rid of the erroneous output, upgrade to 2.2.5 or 3.0-current. Evan From owner-freebsd-scsi Wed Dec 3 19:20:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA11433 for freebsd-scsi-outgoing; Wed, 3 Dec 1997 19:20:19 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from pos-srv4100.javanet.com (pos-srv4100.javanet.com [205.219.162.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA11405 for ; Wed, 3 Dec 1997 19:20:10 -0800 (PST) (envelope-from harpo@javanet.com) Received: from bluenote.dyn.ml.org (armory-us544.javanet.com [209.94.150.251]) by pos-srv4100.javanet.com (8.8.8/8.7) with SMTP id WAA05970 for ; Wed, 3 Dec 1997 22:20:01 -0500 (EST) Message-ID: <3486212B.2781E494@javanet.com> Date: Wed, 03 Dec 1997 22:19:07 -0500 From: John Szumowski X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 Newsgroups: comp.unix.bsd.freebsd.misc CC: freebsd-scsi@freebsd.org Subject: interpretting SCSI error codes Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [note to freebsd-scsi: please cc me a copy of any response] Can anybody suggest where to look to learn more about what scsi error code vals actually mean? I'm getting error code 0 with my zip drive (running off an adaptec 1535)- - (here's scsi info from boot-) aha0 at 0x330-0x333 irq 11 drq 5 on isa aha0 waiting for scsi devices to settle (aha0:0:0): "FUJITSU M2694ES-512 812A" type 0 fixed SCSI 2 sd0(aha0:0:0): Direct-Access 1033MB (2117025 512 byte sectors) (aha0:5:0): "COMPAQ CD-ROM CR-503BCQ 1.1c" type 5 removable SCSI 2 cd0(aha0:5:0): CD-ROM cd present [328355 x 2048 byte records] (aha0:6:0): "IOMEGA ZIP 100 E.08" type 0 removable SCSI 2 sd1(aha0:6:0): Direct-Access sd1(aha0:6:0): error code 0 ^^^^^^^^^^^^^^^^^^^^^^^^^^^ ? The drive *seems* to work ok...but this error has only started showing up recently- so I'm a little worried that this might be the beginning of the end. sd1 could not mode sense (4). Using ficticious geometry 96MB (196608 512 byte sectors) - thanks. -- -------------------------------------------- John Szumowski - harpo@javanet.com http://bluenote.dyn.ml.org -------------------------------------------- From owner-freebsd-scsi Wed Dec 3 21:20:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA20744 for freebsd-scsi-outgoing; Wed, 3 Dec 1997 21:20:40 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from elvis.mu.org (elvis.mu.org [206.156.231.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA20733 for ; Wed, 3 Dec 1997 21:20:27 -0800 (PST) (envelope-from paul@elvis.mu.org) Received: (from paul@localhost) by elvis.mu.org (8.8.7/8.8.7) id XAA06820 for freebsd-scsi@freebsd.org; Wed, 3 Dec 1997 23:20:26 -0600 (CST) (envelope-from paul) From: Paul Saab Message-Id: <199712040520.XAA06820@elvis.mu.org> Subject: error message To: freebsd-scsi@freebsd.org Date: Wed, 3 Dec 1997 23:20:26 -0600 (CST) X-Mailer: ELM [version 2.4ME+ PL31H (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 I got this message today from a machine which we have never had a problem with and I am befuddled and was hoping someone could tell me what the following means. Thanks, Paul this is from the system log: Dec 3 22:12:34 tranq1 /kernel: aha0: MBO 01 and not 00 (free) FreeBSD 2.1.5-RELEASE #0: Thu Jan 16 22:00:51 CST 1997 kris@tranq1.tranquility.net:/usr/src/sys/compile/TRANQ CPU: 75-MHz Pentium 735\\90 or 815\\100 (Pentium-class CPU) Origin = "GenuineIntel" Id = 0x525 Stepping=5 Features=0x1bf real memory = 67108864 (65536K bytes) avail memory = 63254528 (61772K 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 vga0 rev 227 int a irq 15 on pci0:11 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 10 on isa ed0: address 00:40:05:11:67:39, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa aha0 at 0x330-0x333 irq 11 drq 5 on isa aha0 waiting for scsi devices to settle (aha0:0:0): "HP C3010 0BQ3" type 0 fixed SCSI 2 sd0(aha0:0:0): Direct-Access 1910MB (3912172 512 byte sectors) (aha0:1:0): "HP 02439 0LA4" type 0 fixed SCSI 2 sd1(aha0:1:0): Direct-Access 1910MB (3912172 512 byte sectors) aha1 not found at 0x334 npx0 on motherboard npx0: INT 16 interface From owner-freebsd-scsi Thu Dec 4 03:41:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA14250 for freebsd-scsi-outgoing; Thu, 4 Dec 1997 03:41:49 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from smtp04.primenet.com (smtp04.primenet.com [206.165.5.85]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA14240 for ; Thu, 4 Dec 1997 03:41:46 -0800 (PST) (envelope-from bkogawa@primenet.com) Received: (from daemon@localhost) by smtp04.primenet.com (8.8.7/8.8.7) id EAA00613 for ; Thu, 4 Dec 1997 04:41:45 -0700 (MST) Received: from mailhost02.primenet.com(206.165.5.53), claiming to be "primenet.com" via SMTP by smtp04.primenet.com, id smtpd000602; Thu Dec 4 04:41:40 1997 Received: from foo.primenet.com (ip200.sjc.primenet.com [206.165.96.200]) by primenet.com (8.8.5/8.8.5) with ESMTP id EAA08887 for ; Thu, 4 Dec 1997 04:41:38 -0700 (MST) Received: from localhost (bkogawa@localhost) by foo.primenet.com (8.8.6/8.8.6) with SMTP id DAA00328 for ; Thu, 4 Dec 1997 03:41:43 -0800 (PST) X-Authentication-Warning: foo.primenet.com: bkogawa owned process doing -bs Date: Thu, 4 Dec 1997 03:41:42 -0800 (PST) From: "Bryan K. Ogawa" Reply-To: "Bryan K. Ogawa" To: freebsd-scsi@freebsd.org Subject: Adaptec 1502AE and SCSI Scanner? 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 Hey all, I just picked up a Microtek Scanmaker E3. After a bit of wrestling, I think I've settled my IRQ problems, and have it up and running under Windows 95. Under FreeBSD, though, I'm having some problems running it on the SCSI card it comes with (Adaptec 1502AE). The card is detected as an aic0 card, and with the patch to eliminate multiple detections of devices, I can get it up and turn on debugging. However, when I try to scan, I get a panic. uk0(aic0:6:0): about to sleep aic at line 2308: unexpected busfree phase Debugger("aic6360") called. panic for historical reasons I think I have correctly captured the previous scsi command as 4 0 9 0 8 0 but I don't know what to look for. The other thing is a list of numbers like: 000: 08 00 00 00 00 00 00 00 00 ab d4 5c bf ef f7 Is there something else I should be running here? Anything else to help out with debugging? On a side note, if it does turn out that this won't work, does anyone have any information on the Adaptec 2902 or cheap NCR 8xx cards with an external connector? Since I'm not real fond of ISA, I'm thinking of just going and plunking down some $ for a PCI card and hooking it up with that. Thanks. bryan k ogawa http://www.primenet.com/~bkogawa/ From owner-freebsd-scsi Thu Dec 4 12:40:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA28134 for freebsd-scsi-outgoing; Thu, 4 Dec 1997 12:40:55 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from po6.andrew.cmu.edu (PO6.ANDREW.CMU.EDU [128.2.10.106]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA28057 for ; Thu, 4 Dec 1997 12:40:24 -0800 (PST) (envelope-from yunching+@andrew.cmu.edu) Received: (from postman@localhost) by po6.andrew.cmu.edu (8.8.5/8.8.2) id PAA09508 for freebsd-scsi@freebsd.org; Thu, 4 Dec 1997 15:37:48 -0500 (EST) Received: via switchmail; Thu, 4 Dec 1997 15:37:48 -0500 (EST) Received: from unix12.andrew.cmu.edu via qmail ID ; Thu, 4 Dec 1997 15:37:24 -0500 (EST) Received: from unix12.andrew.cmu.edu via qmail ID ; Thu, 4 Dec 1997 15:37:23 -0500 (EST) Received: from mms.4.60.Jun.27.1996.03.02.53.sun4.51.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.unix12.andrew.cmu.edu.sun4m.54 via MS.5.6.unix12.andrew.cmu.edu.sun4_51; Thu, 4 Dec 1997 15:37:23 -0500 (EST) Message-ID: <0oVlG3W00YUo0eZ0g0@andrew.cmu.edu> Date: Thu, 4 Dec 1997 15:37:23 -0500 (EST) From: Yun-Ching Lee To: freebsd-scsi@freebsd.org Subject: ahc deferred error Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I just added a new drive to the chain (ST410800W), and started to get the following errors: sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x3feb0 asc:10,0 Id CRC or ECC error sks:80,22 sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x3feb0 asc:10,0 Id CRC or ECC error sks:80,22 sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x3feb0 asc:10,0 Id CRC or ECC error sks:80,22 sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x3feb0 asc:10,0 Id CRC or ECC error sks:80,22 sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x3feb0 asc:10,0 Id CRC or ECC error sks:80,22 sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x3feb0 asc:10,0 Id CRC or ECC error sks:80,22 sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x3feb0 asc:10,0 Id CRC or ECC error sks:80,22 sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x3feb0 asc:10,0 Id CRC or ECC error sks:80,22 sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x3feb0 asc:10,0 Id CRC or ECC error sks:80,22 sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x4681 asc:10,0 Id CRC or ECC error sks:80,22 sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x4681 asc:10,0 Id CRC or ECC error sks:80,22 sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x4681 asc:10,0 Id CRC or ECC error sks:80,22 sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x8b781 asc:10,0 Id CRC or ECC error sks:80,22 sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x8b792 asc:10,0 Id CRC or ECC error sks:80,22 sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x8b736 asc:10,0 Id CRC or ECC error sks:80,22 sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x8b736 asc:10,0 Id CRC or ECC error sks:80,22 sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x8b736 asc:10,0 Id CRC or ECC error sks:80,22 The error pops up at random intervals. Just now, I'm beating on the drive with dd, and only 6 (the last 6 of above) errors popped up. All the other showed up during the booting process. I tried to fsck the filesystems, but it checks out all right. sd0 was working perfectly before the upgrade, has never produced any error message since the whole system was put together one year ago. sd1 is connected to the narrow cable in an enclosure a wide-to-narrow adapter. Does anyone have any idea on what's the problem? Here's my dmesg: 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.5-STABLE #0: Fri Nov 28 05:06:33 EST 1997 root@sakura.res.cmu.edu:/usr/src/sys/compile/SAKURA CPU: Cyrix 6x86 (486-class CPU) Origin = "CyrixInstead" DIR=0x1731 Stepping=1 Revision=7 real memory = 67108864 (65536K bytes) avail memory = 63614976 (62124K 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 1 int a irq 9 on pci0:10 ahc0: aic7860 Single Channel, SCSI Id=7, 3 SCBs ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "FUJITSU M2915S-512 0127" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2075MB (4250695 512 byte sectors) sd0(ahc0:0:0): with 3011 cyls, 15 heads, and an average 94 sectors/track ahc0: target 1 Tagged Queuing Device (ahc0:1:0): "SEAGATE ST410800W 4508" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 8669MB (17755614 512 byte sectors) sd1(ahc0:1:0): with 4926 cyls, 27 heads, and an average 133 sectors/track (ahc0:5:0): "FUJITSU M2513A 1600" type 7 removable SCSI 2 od0(ahc0:5:0): Optical od not present od0(ahc0:5:0): with approximate 0 cyls, 0 heads, and 0 sectors/track (ahc0:6:0): "TOSHIBA CD-ROM XM-5701TA 0167" type 5 removable SCSI 2 cd0(ahc0:6:0): CD-ROM can't get the size -- Yun-Ching (Allen) Lee ycl+@cmu.edu "There is no such thing as a good influence... All influence is immoral." -- Lord Henry Wotton From owner-freebsd-scsi Thu Dec 4 17:39:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA24611 for freebsd-scsi-outgoing; Thu, 4 Dec 1997 17:39:46 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from gaia.coppe.ufrj.br (cisigw.coppe.ufrj.br [146.164.5.200]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA24605 for ; Thu, 4 Dec 1997 17:39:43 -0800 (PST) (envelope-from jonny@coppe.ufrj.br) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.8/8.8.8) id XAA11560 for freebsd-scsi@freebsd.org; Thu, 4 Dec 1997 23:39:40 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199712050139.XAA11560@gaia.coppe.ufrj.br> Subject: AHC optimizations To: freebsd-scsi@freebsd.org Date: Thu, 4 Dec 1997 23:39:39 -0200 (EDT) X-Mailer: ELM [version 2.4ME+ PL32 (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 Hi, In 2.2.5 LINT there are the following lines: ... # enable tagged command queueing, which is a major performance win on # devices that support it (and controllers with enough SCB's) # # Note that some drives claim to grok tagged commands, but actually # don't. The HP C3725S is a known offender. options AHC_TAGENABLE # enable SCB paging - See the ahc.4 man page for usage warnings. # (IOW: better don't use it by now.) options AHC_SCBPAGING_ENABLE # The aic7xxx driver will attempt to use memory mapped I/O for all PCI # controllers that have it configured only if this option is set. Unfortunately, # this doesn't work on some motherboards, which prevents it from being the # default. options AHC_ALLOW_MEMIO ... I've read the manual for ahc(4), but could not find anything that could harm my configuration: ... ahc0 rev 0 int a irq 15 on pci0:6 ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "IBM XP34300W !z 81K1" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 4303MB (8813870 512 byte sectors) sd0(ahc0:0:0): with 3907 cyls, 20 heads, and an average 112 sectors/track (ahc0:5:0): "EXABYTE EXB-82058VQANXR1 0781" type 1 removable SCSI 2 st0(ahc0:5:0): Sequential-Access density code 0x0, drive empty ... But, everytime I enable these options, it panics with a page fault in kernel mode while squid is starting (lots of disk access). The process referred in the panic message is squid, if this matters. Isn't it yet safe to use these options ? Reading ahc(4) I could imagine a disk stopping to answer requests or simply not starting to work, but I can not imagine a kernel panic. Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 From owner-freebsd-scsi Thu Dec 4 19:26:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA05245 for freebsd-scsi-outgoing; Thu, 4 Dec 1997 19:26:48 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA05220 for ; Thu, 4 Dec 1997 19:26:40 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xdoG8-0002Dx-00; Thu, 4 Dec 1997 19:16:56 -0800 Date: Thu, 4 Dec 1997 19:16:55 -0800 (PST) From: Tom To: Joao Carlos Mendes Luis cc: freebsd-scsi@freebsd.org Subject: Re: AHC optimizations In-Reply-To: <199712050139.XAA11560@gaia.coppe.ufrj.br> 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, 4 Dec 1997, Joao Carlos Mendes Luis wrote: ... > Isn't it yet safe to use these options ? Reading ahc(4) I could > imagine a disk stopping to answer requests or simply not starting to > work, but I can not imagine a kernel panic. It should be. Try removing one option at a time. Remove MEMIO first, then try without PAGING. > Jonny > > -- > Joao Carlos Mendes Luis jonny@gta.ufrj.br > +55 21 290-4698 jonny@coppe.ufrj.br > Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI > PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 Tom From owner-freebsd-scsi Fri Dec 5 09:51:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA18950 for freebsd-scsi-outgoing; Fri, 5 Dec 1997 09:51:51 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from cx25450-a.dt1.sdca.home.com (cx25450-a.dt1.sdca.home.com [24.0.129.127]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA18939 for ; Fri, 5 Dec 1997 09:51:43 -0800 (PST) (envelope-from schwarz@cx25450-a.dt1.sdca.home.com) Received: (from schwarz@localhost) by sunbear.the-forest.org (8.8.7/8.8.7) id JAA07313; Fri, 5 Dec 1997 09:45:38 -0800 (PST) (envelope-from schwarz) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 05 Dec 1997 09:09:38 -0800 (PST) Organization: Doctor Design From: Steven Schwarz To: freebsd-scsi@freebsd.org Subject: support for AIC 7895 Cc: "Steven T. Schwarz" , Mike Murphy , Mike Murphy Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently put together a system based upon the Tyan Thunder 2 motherboard, which has on-board an Adaptec AIC 7895 SCSI controller. (This is supposed to be "equivalent to a 3940-AUW", to quote the motherboard documentation. Strangely, the Adaptec web site seems to contain no info on the AIC 7895.) I am attempting to get this SCSI controller to play with FreeBSD, starting from 3.0-971022-SNAP. By adding some printf's to the code for aic7870_probe() in aic7870.c, I was able to determine an appropriate PCI ID for the card, and then I added a new constant for that file: #define PCI_DEVICE_ID_ADAPTEC_AIC7895 0x78959004ul I added a new case to aic7870_probe(): case PCI_DEVICE_ID_ADAPTEC_AIC7895: return ("Adaptec aic7895 Ultra SCSI host adapter"); break; And I added a new case to ahc_pci_attach(): case PCI_DEVICE_ID_ADAPTEC_AIC7895: ahc_t = AHC_394U; if ((aic3940_count & 0x01) != 0) { /* Odd count implies second channel */ ahc_f |= AHC_CHNLB; } aic3940_count++; break; This is not enough to get the card working. Here is the dmesg output from a boot with -v: ahc0: rev 0x03 int a irq 19 on pci0.15 .0 ahc0: Reading SEEPROM...checksum error ahc0: No SEEPROM available ahc0: Using left over BIOS settings ahc0: aic7880 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc0: hardware scb 32 bytes; kernel scb 28 bytes; ahc_dma 8 bytes ahc0: Resetting Channel A NEEDSDTR == 0x11 NEEDWDTR == 0x0 DISCENABLE == 0xffff ahc0: Downloading Sequencer Program...ahc0: 409 instructions downloaded Done ahc0: Probing channel A Choosing drivers for scbus configured at 0 ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 scb:0xf066ff20 control:0xc0 tcl:0x0 cmdlen:6 cmdpointer:0x9bed8 datlen:-16777216 data:0x0 segs:0x0 segp:0x0 ahc0: board is not responding scbus0 target 0 lun 0: SCB 0x0 - timed out in command phase, SCSISIGI == 0x86 SEQADDR = 0x14b SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0x3 scbus0 target 0 lun 0: abort message in message buffer ... >From this point on, there is much more of the same, and it appears to be recognizing a device uk#N at every lun of every target of the bus, though the timeouts are so long I have not had the patience to actually let the thing go all the way. Any advice as to what is going wrong and possible next steps would be mightily appreciated.... Thanks, sts ps: I am a freebsd-scsi susbsciber, so replies can just go to the list. From owner-freebsd-scsi Fri Dec 5 10:15:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA21057 for freebsd-scsi-outgoing; Fri, 5 Dec 1997 10:15:49 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA21041 for ; Fri, 5 Dec 1997 10:15:44 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xe28X-0002cP-00; Fri, 5 Dec 1997 10:06:01 -0800 Date: Fri, 5 Dec 1997 10:05:59 -0800 (PST) From: Tom To: Yun-Ching Lee cc: freebsd-scsi@freebsd.org Subject: Re: ahc deferred error In-Reply-To: <0oVlG3W00YUo0eZ0g0@andrew.cmu.edu> 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, 4 Dec 1997, Yun-Ching Lee wrote: > sd0(ahc0:0:0): Deferred Error: MEDIUM ERROR info:0x8b736 asc:10,0 Id CRC > or ECC error sks:80,22 ... > Does anyone have any idea on what's the problem? A medium error means the disk surface has bad sectors. When you read or write those areas, the error will come up. If the sectors are marginal, you will get the error some of the time. You might want to check to see that auto read/write relocation is turned on for the drive. If turned on, the drive may be able to relocated the sectors automatically. If already turned on, the drive has tried and failed to relocated the sectors, and you need to reformat your drive with bad114. Tom From owner-freebsd-scsi Fri Dec 5 12:26:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA04372 for freebsd-scsi-outgoing; Fri, 5 Dec 1997 12:26:35 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from destiny.erols.com (destiny.erols.com [207.96.73.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA04336 for ; Fri, 5 Dec 1997 12:26:24 -0800 (PST) (envelope-from jdowdal@destiny.erols.com) Received: from destiny.erols.com (destiny.erols.com [207.96.73.65]) by destiny.erols.com (8.8.8/8.6.12) with SMTP id PAA24707; Fri, 5 Dec 1997 15:25:39 -0500 (EST) Date: Fri, 5 Dec 1997 15:25:38 -0500 (EST) From: John Dowdal To: Tom cc: Yun-Ching Lee , freebsd-scsi@freebsd.org Subject: Re: ahc deferred error 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 Fri, 5 Dec 1997, Tom wrote: > You might want to check to see that auto read/write relocation is turned > on for the drive. If turned on, the drive may be able to relocated the > sectors automatically. If already turned on, the drive has tried and > failed to relocated the sectors, and you need to reformat your drive with > bad114. Bad144 might be able to work for a week or two, but its not a very good solution. If you at all care about what is on the disk, this is the point where you should either claim its warranty if it has one, or else buy a new disk. Disks which have run out of spare sectors are already bad, and many more bad sectors will generally develop quickly. If you don't have the cash for a high-end scsi drive, you can always check out: http://necxdirect.necx.com:8002/cgi-bin/auth/:guest/simple_q?cifilelnk=0000531 for a $395 Quantum Fireball SCSI 6.4GB drive. Warning: necx's web site likes to crash FreeBSD version of netscape 4. Use windows if necessary :( John From owner-freebsd-scsi Fri Dec 5 12:32:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA05236 for freebsd-scsi-outgoing; Fri, 5 Dec 1997 12:32:34 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from vina-tech.com (vina-tech.com [207.242.96.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA05230; Fri, 5 Dec 1997 12:32:28 -0800 (PST) (envelope-from scott.watters@vina-tech.com) Received: from curious (curious.vina-tech.com [207.242.96.69]) by vina-tech.com (8.8.7/8.8.7) with SMTP id MAA19854; Fri, 5 Dec 1997 12:31:06 -0800 (PST) (envelope-from scott.watters@vina-tech.com) Reply-To: "Scott Watters" From: "Scott Watters" To: Cc: Subject: Questions about mt and SCSI subsystem Date: Fri, 5 Dec 1997 12:30:16 -0800 Message-ID: <01bd01bc$98a6a760$4560f2cf@curious.vina-tech.com> 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 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I am trying to get Xbru 2000 (commercial archive/backup program) to work on FreeBSD 2.2.5 with a Adaptec 2940 and Archive Python. It seems that to append an archive to a tape, the xbru software does several "mt fsf" commands to determine how many "files" are on the tape. It expects, correctly I think, to receive an EOM (end of media) error when the tape gets to the end of recorded data. However mt never returns an error, but the kernel logs a message like this: Dec 3 17:42:14 newserver /kernel: st0(ahc0:6:0): BLANK CHECK req sz: 1 (decimal) asc:0,5 End-of-data detected Has anyone had this problem? Is it a bug in the driver or mt? Any help would be appreciated so I can get multiple backups on a single tape. Thanks, Scott Watters scott.watters@vina-tech.com http://www.vina-tech.com From owner-freebsd-scsi Fri Dec 5 14:06:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA15336 for freebsd-scsi-outgoing; Fri, 5 Dec 1997 14:06:15 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA15331 for ; Fri, 5 Dec 1997 14:06:13 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.7/8.7.3) id PAA27795; Fri, 5 Dec 1997 15:04:34 -0700 (MST) Date: Fri, 5 Dec 1997 15:04:34 -0700 (MST) Message-Id: <199712052204.PAA27795@narnia.plutotech.com> Mime-Version: 1.0 X-Newsreader: knews 0.9.8 References: In-Reply-To: From: gibbs@narnia.plutotech.com (Justin T. Gibbs) Subject: Re: support for AIC 7895 X-Original-Newsgroups: pluto.freebsd.scsi To: scsi@FreeBSD.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In article , Steven Schwarz writes: > I recently put together a system based upon the Tyan Thunder 2 > motherboard, which has on-board an Adaptec AIC 7895 SCSI controller. > (This is supposed to be "equivalent to a 3940-AUW", to quote the > motherboard documentation. Strangely, the Adaptec web site seems to > contain no info on the AIC 7895.) > > I am attempting to get this SCSI controller to play with FreeBSD, > starting from 3.0-971022-SNAP. You probably won't have much luck. The 7895 does away with a few registers that the FreeBSD driver uses, so simply adding the device ID won't get you very far. I actually do have the 7895 up and working here using the CAM SCSI driver, and since you run current, it should be fairly straight forward for you to pull down a CAM snapshot and get this support. The next CAM snapshot (the first to include 7895 support) should be happening this weekend. The 7895 is a really nice chip, and although the CAM driver already supports it, you can expect to see additional performance improvements made to the driver as support is added for all the new features in this chip. -- Justin T. Gibbs =========================================== FreeBSD - Turning PCs into workstations =========================================== From owner-freebsd-scsi Fri Dec 5 14:29:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA17464 for freebsd-scsi-outgoing; Fri, 5 Dec 1997 14:29:03 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from thunderdome.plutotech.com (root@thunderdome.plutotech.com [206.168.67.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA17429 for ; Fri, 5 Dec 1997 14:28:49 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by thunderdome.plutotech.com (8.8.7/8.8.5) with ESMTP id PAA27787; Fri, 5 Dec 1997 15:28:24 -0700 (MST) Received: (from ken@localhost) by panzer.plutotech.com (8.8.7/8.8.5) id PAA09264; Fri, 5 Dec 1997 15:28:21 -0700 (MST) Message-Id: <199712052228.PAA09264@panzer.plutotech.com> Subject: Re: ahc deferred error In-Reply-To: from John Dowdal at "Dec 5, 97 03:25:38 pm" To: jdowdal@destiny.erols.com (John Dowdal) Date: Fri, 5 Dec 1997 15:28:21 -0700 (MST) Cc: tom@sdf.com, ycl+@CMU.EDU, freebsd-scsi@FreeBSD.ORG From: Kenneth Merry X-Mailer: ELM [version 2.4ME+ PL28s (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 John Dowdal wrote... > If you don't have the cash for a high-end scsi drive, you can always check > out: > > http://necxdirect.necx.com:8002/cgi-bin/auth/:guest/simple_q?cifilelnk=0000531 > > for a $395 Quantum Fireball SCSI 6.4GB drive. > > Warning: necx's web site likes to crash FreeBSD version of netscape 4. > Use windows if necessary :( I have found that it is best to turn off Java before going to their site.. That keeps Netscape from crashing. Ken -- Kenneth Merry ken@plutotech.com From owner-freebsd-scsi Fri Dec 5 14:51:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA19648 for freebsd-scsi-outgoing; Fri, 5 Dec 1997 14:51:10 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from gw1.tesys.com (root@gw1.tesys.com [207.5.58.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA19635 for ; Fri, 5 Dec 1997 14:51:03 -0800 (PST) (envelope-from harry@tesys.com) Received: from harry (harry.tesys.com [207.5.58.17]) by gw1.tesys.com (8.7.4/8.7.3) with SMTP id OAA22114; Fri, 5 Dec 1997 14:50:32 -0800 (PST) Message-Id: <3.0.32.19971205144421.009495d0@gw1.tesys.com> X-Sender: harry@gw1.tesys.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Fri, 05 Dec 1997 14:44:22 -0800 To: John Dowdal , Tom From: Harry Aulakh Subject: configuring RAID in FreeBSD 2.2.5 Cc: Yun-Ching Lee , freebsd-scsi@FreeBSD.ORG, raj@gw1.tesys.com Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello Friends I want to configure RAID-1 in FreeBSD2.2.5 either in software based or hardware based.I donot know freebsd 2.2.5 are support software RAID or not. My question are a) Is there any support in freebsd 2.2.5 to configure software RAID (any level)? If YES then how can I do It. b) Is the FreeBSD2.2.5 are supporting any RAID controller card (like DPT).? Harry Aulakh Sr. Engineer Telenet System Solution Inc. 2480 kruse drive San Jose Ca-95131 Phone 408-383-0334 ext 111 fax 408-383-0335 Web www.tesys.com From owner-freebsd-scsi Fri Dec 5 17:20:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA01950 for freebsd-scsi-outgoing; Fri, 5 Dec 1997 17:20:47 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from linux1.americasnet.com (linux1.americasnet.com [207.155.121.128]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA01941 for ; Fri, 5 Dec 1997 17:20:42 -0800 (PST) (envelope-from ricardo@americasnet.com) Received: from localhost (ricardo@localhost) by linux1.americasnet.com (8.8.7/8.7.3) with SMTP id RAA00658 for ; Fri, 5 Dec 1997 17:27:47 -0800 Date: Fri, 5 Dec 1997 17:27:45 -0800 (PST) From: Ricardo Kleemann To: freebsd-scsi@FreeBSD.ORG Subject: unsubscribe 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 unsubscribe freebsd-scsi ricardo@americasnet.com From owner-freebsd-scsi Fri Dec 5 17:45:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA03623 for freebsd-scsi-outgoing; Fri, 5 Dec 1997 17:45:35 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from gaia.coppe.ufrj.br (cisigw.coppe.ufrj.br [146.164.5.200]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA03609 for ; Fri, 5 Dec 1997 17:45:28 -0800 (PST) (envelope-from jonny@coppe.ufrj.br) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.8/8.8.8) id XAA25942; Fri, 5 Dec 1997 23:44:10 -0200 (EDT) (envelope-from jonny) From: Joao Carlos Mendes Luis Message-Id: <199712060144.XAA25942@gaia.coppe.ufrj.br> Subject: Re: AHC optimizations In-Reply-To: <199712052157.OAA27773@narnia.plutotech.com> from "Justin T. Gibbs" at "Dec 5, 97 02:57:38 pm" To: gibbs@narnia.plutotech.com (Justin T. Gibbs) Date: Fri, 5 Dec 1997 23:44:10 -0200 (EDT) Cc: freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL32 (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 Hi Justin, #define quoting(Justin T. Gibbs) // > I've read the manual for ahc(4), but could not find anything that // > could harm my configuration: // // Most likely what is happening is that the IBM drive is returning // QUEUE FULL or has some other queuing problem that causes either the // aic7xxx driver or the SCSI system to fail certain commands. Most // likely the error code isn't properly handling the situation and the // result is a panic. If you want to use tagged queuing with this drive, // you may want to run current and try a CAM kernel. This is a production machine that I still don't want to run current in it, but needs desperately more performance from disk. Do you think that just removing the AHC_TAGENABLE and leaving the others will solve the problem ? Also, do you know if there's a list of boards/disks combinations that work with tagged queueing ? In particular, would the 2940UW with Seagate Barracuda or Cheetah work ? Thanks for your answer, Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 jonny@coppe.ufrj.br Universidade Federal do Rio de Janeiro UFRJ/COPPE/CISI PGP fingerprint: 29 C0 50 B9 B6 3E 58 F2 83 5F E3 26 BF 0F EA 67 From owner-freebsd-scsi Fri Dec 5 19:54:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA12700 for freebsd-scsi-outgoing; Fri, 5 Dec 1997 19:54:38 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from po6.andrew.cmu.edu (PO6.ANDREW.CMU.EDU [128.2.10.106]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA12692 for ; Fri, 5 Dec 1997 19:54:31 -0800 (PST) (envelope-from yunching+@andrew.cmu.edu) Received: (from postman@localhost) by po6.andrew.cmu.edu (8.8.5/8.8.2) id WAA13936; Fri, 5 Dec 1997 22:54:09 -0500 (EST) Received: via switchmail; Fri, 5 Dec 1997 22:54:09 -0500 (EST) Received: from unix10.andrew.cmu.edu via qmail ID ; Fri, 5 Dec 1997 22:53:51 -0500 (EST) Received: from unix10.andrew.cmu.edu via qmail ID ; Fri, 5 Dec 1997 22:53:49 -0500 (EST) Received: from mms.4.60.Jun.27.1996.03.02.53.sun4.51.EzMail.2.0.CUILIB.3.45.SNAP.NOT.LINKED.unix10.andrew.cmu.edu.sun4m.54 via MS.5.6.unix10.andrew.cmu.edu.sun4_51; Fri, 5 Dec 1997 22:53:49 -0500 (EST) Message-ID: Date: Fri, 5 Dec 1997 22:53:49 -0500 (EST) From: Yun-Ching Lee To: freebsd-scsi@freebsd.org Subject: Re: ahc deferred error Cc: tom@sdf.com, freebsd-scsi@freebsd.org In-Reply-To: <199712052228.PAA09264@panzer.plutotech.com> References: <199712052228.PAA09264@panzer.plutotech.com> Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Thanks to everyone who took time to respond to my problem. It seems like it was caused by cabling, as the problem disappeared when I reseated the cables on the hard drives. Nevertheless, the problem scare me for a bit. -- Yun-Ching (Allen) Lee ycl+@cmu.edu "There is no such thing as a good influence... All influence is immoral." -- Lord Henry Wotton From owner-freebsd-scsi Fri Dec 5 22:30:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA23502 for freebsd-scsi-outgoing; Fri, 5 Dec 1997 22:30:50 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA23495 for ; Fri, 5 Dec 1997 22:30:47 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id XAA03061; Fri, 5 Dec 1997 23:30:41 -0700 (MST) Message-Id: <199712060630.XAA03061@pluto.plutotech.com> To: Joao Carlos Mendes Luis cc: gibbs@plutotech.com (Justin T. Gibbs), freebsd-scsi@freebsd.org Subject: Re: AHC optimizations In-reply-to: Your message of "Fri, 05 Dec 1997 23:44:10 -0200." <199712060144.XAA25942@gaia.coppe.ufrj.br> Date: Fri, 05 Dec 1997 23:29:03 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I can make no guarantees if you continue to run stable. There are numerous bugs that I have fixed in the ahc driver and SCSI subsystem with CAM, and if you are running that code, I have many more tools to diagnose and fix problems. I do know, however, that the Seagate Barracudas that I have tested have all worked just fine with tagged queuing turned on. While turning off tagged queuing in the driver may stop your panics, you have effectively removed any chance of getting better performance out of the disk subsystem. -- Justin