From owner-freebsd-scsi@FreeBSD.ORG Sun Sep 14 09:21:56 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0529816A4BF for ; Sun, 14 Sep 2003 09:21:56 -0700 (PDT) Received: from xeon.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5098D43FDF for ; Sun, 14 Sep 2003 09:21:55 -0700 (PDT) (envelope-from dan@langille.org) Received: by xeon.unixathome.org (Postfix, from userid 1000) id A51D93E5F; Sun, 14 Sep 2003 12:21:51 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by xeon.unixathome.org (Postfix) with ESMTP id 9EA453E58 for ; Sun, 14 Sep 2003 12:21:51 -0400 (EDT) Date: Sun, 14 Sep 2003 12:21:51 -0400 (EDT) From: Dan Langille X-X-Sender: dan@xeon.unixathome.org To: freebsd-scsi@freebsd.org Message-ID: <20030914115126.E44294@xeon.unixathome.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: blocksize error on sa X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2003 16:21:56 -0000 In my attempts to track down the pthreads problem related to EOT not being properly returned, I've installed a QIC tape into my Bacula (http://www.bacula.org/) development box: FreeBSD undef.example.org 5.1-CURRENT FreeBSD 5.1-CURRENT #1: Wed Sep 10 14:43:34 EDT 2003 dan@undef.example.org:/usr/obj/usr/src/sys/UNDEF i386 sa0 at ahc0 bus 0 target 2 lun 0 sa0: Removable Sequential Access SCSI-CCS device sa0: 3.300MB/s transfers With a tape in the drive, I attempt a status: # mt -f /dev/sa0 status mt: /dev/sa0: Invalid argument This appears in /var/log/messages: Sep 14 11:59:23 undef kernel: (sa0:ahc0:0:2:0): unable to set fixed blocksize to 1024 Similar entries appear for rewind, offline, retension. Archive seaches lead me to believe the problem is related to the drive not knowing that the device needs a particular blocksize. But I can't set the blocksize using "mt blocksize" (it gives the error mentioned above). Ideas please? From owner-freebsd-scsi@FreeBSD.ORG Sun Sep 14 15:01:12 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3105F16A4BF; Sun, 14 Sep 2003 15:01:12 -0700 (PDT) Received: from mail1.kanji.com.au (adsl-114-194.swiftdsl.com.au [202.154.114.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2E77F43F75; Sun, 14 Sep 2003 15:01:06 -0700 (PDT) (envelope-from als@kanji.com.au) Received: from kanji.com.au (unknown [10.0.0.209]) by mail1.kanji.com.au (Postfix) with ESMTP id 2FD7C3682; Mon, 15 Sep 2003 08:01:01 +1000 (EST) Message-ID: <3F64E50E.2040608@kanji.com.au> Date: Mon, 15 Sep 2003 08:00:46 +1000 From: Andrew Snow User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: ibm x345 w/ serveraid-5i + freebsd ips driver dramas X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 14 Sep 2003 22:01:12 -0000 Hello, Problem 1: (the annoying setback) I cannot got the serveraid-5i card to work with FreeBSD 5.x (tried 5.1-REL and the latest current.iso). I am using the latest firmware and BIOS for the card from IBM (6.10.24). While the card is detected while the kernel is booting, the drive sizes are incorrectly listed (current number, but they are listed as megabytes instead of bytes) and there is a kernel panic a short time later when (I think) it tries to initialise the card. I its something to do with the fact that it is a "zero channel" card design which uses the on-board LSI-based controller (which works just fine with 5.1-REL). Following the advice of someone on the mailing list, I tried booting from an IDE drive and then loading ips as a KLD. This time it worked: ips0: mem 0xf4000000-0xf7ffffff irq 11 at device 2.0 on pci8 ips0: logical drives: 1 ipsd0: on ips0 ipsd0: Logical Drive (138860MB) Problem 2: (the biggest problem) While the drive size is reported correctly, the geometry is wrong... 472 cyls/254 heads/63 sectors = 7552944 sectors (3687MB) ?! When setting the BIOS to "non-extended" (2GB max) support mode, freebsd then thinks this is the geometry: 1846 cyls/128 heads/32 sectors = 7561216 sectors (3692MB). So I tested a few alternate geometries instead and even though there were no error messages, it seemed to get reset to what FreeBSD was reporting, no matter how many ways I tried to use the fdisk utility. What is the status of development on this driver? Is there anything I can do to help out, before I send this card back? Can anyone advise the best card to get that is comparable to the ServeRaid-5i in features, and that works properly with FreeBSD? Kind regards, Andrew From owner-freebsd-scsi@FreeBSD.ORG Sun Sep 14 21:50:19 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7EA0A16A4BF for ; Sun, 14 Sep 2003 21:50:19 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id D834043FA3 for ; Sun, 14 Sep 2003 21:50:18 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 5231 invoked by uid 1000); 15 Sep 2003 04:50:18 -0000 Date: Sun, 14 Sep 2003 21:50:18 -0700 (PDT) From: Nate Lawson To: Andrew Snow In-Reply-To: <3F64E50E.2040608@kanji.com.au> Message-ID: <20030914214758.W5214@root.org> References: <3F64E50E.2040608@kanji.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org Subject: Re: ibm x345 w/ serveraid-5i + freebsd ips driver dramas X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 04:50:19 -0000 On Mon, 15 Sep 2003, Andrew Snow wrote: > Problem 1: (the annoying setback) > > I cannot got the serveraid-5i card to work with FreeBSD 5.x (tried > 5.1-REL and the latest current.iso). I am using the latest firmware and > BIOS for the card from IBM (6.10.24). While the card is detected while > the kernel is booting, the drive sizes are incorrectly listed (current > number, but they are listed as megabytes instead of bytes) and there is > a kernel panic a short time later when (I think) it tries to initialise > the card. > > I its something to do with the fact that it is a "zero channel" card > design which uses the on-board LSI-based controller (which works just > fine with 5.1-REL). > > Following the advice of someone on the mailing list, I tried booting > from an IDE drive and then loading ips as a KLD. This time it worked: > > ips0: mem 0xf4000000-0xf7ffffff irq 11 at device > 2.0 on pci8 > ips0: logical drives: 1 > ipsd0: on ips0 > ipsd0: Logical Drive (138860MB) This problem was fixed last week by a commit by Paul Saab. You can wait for 5.2R or use -current. > Problem 2: (the biggest problem) > > While the drive size is reported correctly, the geometry is wrong... > 472 cyls/254 heads/63 sectors = 7552944 sectors (3687MB) ?! > > When setting the BIOS to "non-extended" (2GB max) support mode, freebsd > then thinks this is the geometry: > 1846 cyls/128 heads/32 sectors = 7561216 sectors (3692MB). > > So I tested a few alternate geometries instead and even though there > were no error messages, it seemed to get reset to what FreeBSD was > reporting, no matter how many ways I tried to use the fdisk utility. This is not the driver's fault but fdisk's. I really hate FreeBSD's fdisk and do not ever use it. -Nate From owner-freebsd-scsi@FreeBSD.ORG Sun Sep 14 22:18:40 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1593C16A4BF for ; Sun, 14 Sep 2003 22:18:40 -0700 (PDT) Received: from mail1.kanji.com.au (adsl-114-194.swiftdsl.com.au [202.154.114.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 68D1D43FAF for ; Sun, 14 Sep 2003 22:18:36 -0700 (PDT) (envelope-from als@kanji.com.au) Received: from kanji.com.au (unknown [10.0.0.209]) by mail1.kanji.com.au (Postfix) with ESMTP id 5CD8932DD; Mon, 15 Sep 2003 15:18:27 +1000 (EST) Message-ID: <3F654B9B.1010300@kanji.com.au> Date: Mon, 15 Sep 2003 15:18:19 +1000 From: Andrew Snow User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Nate Lawson References: <3F64E50E.2040608@kanji.com.au> <20030914214758.W5214@root.org> In-Reply-To: <20030914214758.W5214@root.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org Subject: Re: ibm x345 w/ serveraid-5i + freebsd ips driver dramas X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 05:18:40 -0000 > This problem was fixed last week by a commit by Paul Saab. You can wait > for 5.2R or use -current. Thanks for the info. If only it was made clearer... >>So I tested a few alternate geometries instead and even though there >>were no error messages, it seemed to get reset to what FreeBSD was >>reporting, no matter how many ways I tried to use the fdisk utility. > This is not the driver's fault but fdisk's. I really hate FreeBSD's fdisk > and do not ever use it. Oh, ok... can you suggest a reasonable work around? Thanks. - Andrew From owner-freebsd-scsi@FreeBSD.ORG Sun Sep 14 23:17:02 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 06D2416A4BF for ; Sun, 14 Sep 2003 23:17:02 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 71A6A43FDF for ; Sun, 14 Sep 2003 23:17:01 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 5384 invoked by uid 1000); 15 Sep 2003 06:17:03 -0000 Date: Sun, 14 Sep 2003 23:17:03 -0700 (PDT) From: Nate Lawson To: Andrew Snow In-Reply-To: <3F654B9B.1010300@kanji.com.au> Message-ID: <20030914231537.W5375@root.org> References: <3F64E50E.2040608@kanji.com.au> <20030914214758.W5214@root.org> <3F654B9B.1010300@kanji.com.au> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org Subject: Re: ibm x345 w/ serveraid-5i + freebsd ips driver dramas X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 06:17:02 -0000 On Mon, 15 Sep 2003, Andrew Snow wrote: > >>So I tested a few alternate geometries instead and even though there > >>were no error messages, it seemed to get reset to what FreeBSD was > >>reporting, no matter how many ways I tried to use the fdisk utility. > > > This is not the driver's fault but fdisk's. I really hate FreeBSD's fdisk > > and do not ever use it. > > Oh, ok... can you suggest a reasonable work around? > > Thanks. Use Linux's fdisk. With FreeBSD's, even if I just change the type of a partition, the whole thing is rewritten (with bogus geometry). Or don't worry about it. It works fine and it's not like you want drive portability to different controllers if you're using hardware RAID. -Nate From owner-freebsd-scsi@FreeBSD.ORG Sun Sep 14 23:18:25 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 01D1F16A4BF for ; Sun, 14 Sep 2003 23:18:25 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 9F53F43F3F for ; Sun, 14 Sep 2003 23:18:23 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 5395 invoked by uid 1000); 15 Sep 2003 06:18:26 -0000 Date: Sun, 14 Sep 2003 23:18:26 -0700 (PDT) From: Nate Lawson To: Dan Langille Message-ID: <20030914231722.I5375@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: scsi@freebsd.org Subject: Re: blocksize error on sa X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 06:18:25 -0000 An anonymous person who knows more about sa(4) than me agreed it's probably a mode select problem with the drive: > The 51000 is a piece of shit. With f/w varying all over the map. > My guess is that, yes, something in mode select isn't happening right. -Nate From owner-freebsd-scsi@FreeBSD.ORG Mon Sep 15 02:54:15 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0474216A4BF for ; Mon, 15 Sep 2003 02:54:15 -0700 (PDT) Received: from mail.darq.net (phear.darq.net [213.253.1.14]) by mx1.FreeBSD.org (Postfix) with SMTP id B372843FE5 for ; Mon, 15 Sep 2003 02:54:13 -0700 (PDT) (envelope-from reflex@darq.net) Received: (qmail 3548 invoked by uid 1000); 15 Sep 2003 09:54:09 -0000 Date: Mon, 15 Sep 2003 10:54:09 +0100 From: Ian Morrison To: scsi@freebsd.org Message-ID: <20030915095409.GA26587@phear.darq.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Url: http://www.darq.net/ User-Agent: Mutt/1.5.4i Subject: IBM ServeRaid-3 on FreeBSD 5.1 (release & current) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 09:54:15 -0000 hiya, i posted this on current@ last week, but haven't heard anything back. i'm reposting it here in the hope that someone might be able to shine some light on the problem.. i've just got hold of an IBM Netfinity 4000R system (8653-45Y) which uses an IBM ServeRaid-3L to control two 9 gig disks. Drives are set up as a standard mirror, and online. Booting from 5.1-RELEASE and the latest snapshot i could find both result in a kernel panic on boot. i've included the dmesg for both kernels below, and would be grateful if anyone could offer any advice. many thanks, ian Copyright (c) 1992-2003 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 5.1-CURRENT-20030908-JPSNAP #0: Mon Sep 8 03:26:52 GMT 2003 root@ushi.jp.freebsd.org:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0b41000. Preloaded mfs_root "/boot/mfsroot" at 0xc0b41200. Timecounter "i8254" frequency 1193182 Hz quality 0 CPU: Intel Pentium III (745.00-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x681 Stepping =3D 1 Features=3D0x387fbff real memory =3D 1073741824 (1024 MB) avail memory =3D 1031286784 (983 MB) Pentium Pro MTRR support enabled md0: Preloaded image 4423680 bytes at 0xc0707670 npx0: [FAST] npx0: on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 pcib0: at pcibus 0 on motherboard pci0: on pcib0 agp0: mem 0xf0000000-0xf3ffffff at devic= e 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 o= n pci0 ata0: at 0x1f0 irq 14 on atapci0 ata0: [MPSAFE] ata1: at 0x170 irq 15 on atapci0 ata1: [MPSAFE] uhci0: port 0x3000-0x301f at devi= ce 7.2 on pci0 uhci0: Could not allocate irq device_probe_and_attach: uhci0 attach returned 6 pci0: at device 7.3 (no driver attached) fxp0: port 0x3040-0x307f mem 0xfea00000-0xfe= afffff,0xfebff000-0xfebfffff irq 10 at device 17.0 on pci0 fxp0: Disabling dynamic standby mode in EEPROM fxp0: New EEPROM ID: 0x4080 fxp0: EEPROM checksum @ 0x3f: 0xd29 -> 0xd29 fxp0: Ethernet address 00:06:29:de:b9:ac miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: port 0x3080-0x30bf mem 0xfe900000-0xfe= 9fffff,0xfebfe000-0xfebfefff irq 11 at device 18.0 on pci0 fxp1: Disabling dynamic standby mode in EEPROM fxp1: New EEPROM ID: 0x4080 fxp1: EEPROM checksum @ 0x3f: 0xe29 -> 0xe29 fxp1: Ethernet address 00:06:29:de:b9:ab miibus1: on fxp1 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcib2: at device 20.0 on pci0 pci2: on pcib2 ips0: port 0x2000-0x20ff mem 0xfe000000-0xfe0fffff = irq 9 at device 15.0 on pci2 ips0: reinitializing adapter, this could take several minutes. ips0: logical drives: 222 ipsd0: on ips0 GEOM: create disk ipsd0 dp=3D0xc6588b90 ipsd0: Logical Drive (1824184MB) ipsd1: on ips0 GEOM: create disk ipsd1 dp=3D0xc6588a90 ipsd1: Logical Drive (1824184MB) ipsd2: on ips0 GEOM: create disk ipsd2 dp=3D0xc6588990 ipsd2: Logical Drive (1824184MB) ipsd3: on ips0 GEOM: create disk ipsd3 dp=3D0xc6588890 ipsd3: Logical Drive (1824184MB) ipsd4: on ips0 GEOM: create disk ipsd4 dp=3D0xc6588790 Memory modified after free 0xc65aa080(124) panic: Most recently used by none Debugger("panic") Stopped at Debugger+0x54: xchgl %ebx,in_Debugger.0 db> reset =00=00=00=00=80=80=00=80=80=80=00=00=00=00=F8=F8=80=00=FE=F8=80=80=00=98=00= =E6=00=F8DS=00=00=00Copyright (c) 1992-2003 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 5.1-RELEASE #0: Thu Jun 5 02:55:42 GMT 2003 root@wv1u.btc.adaptec.com:/usr/obj/usr/src/sys/GENERIC Preloaded elf kernel "/boot/kernel/kernel" at 0xc0ac1000. Preloaded mfs_root "/boot/mfsroot" at 0xc0ac1200. Timecounter "i8254" frequency 1193182 Hz Timecounter "TSC" frequency 744995420 Hz CPU: Intel Pentium III (745.00-MHz 686-class CPU) Origin =3D "GenuineIntel" Id =3D 0x681 Stepping =3D 1 Features=3D0x387fbff real memory =3D 1073741824 (1024 MB) avail memory =3D 1031827456 (984 MB) Pentium Pro MTRR support enabled md0: Preloaded image 4423680 bytes at 0xc06877a4 npx0: on motherboard npx0: INT 16 interface pcibios: BIOS version 2.10 pcib0: at pcibus 0 on motherboard pci0: on pcib0 agp0: mem 0xf0000000-0xf3ffffff at devic= e 0.0 on pci0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at device 0.0 (no driver attached) isab0: at device 7.0 on pci0 isa0: on isab0 atapci0: port 0xffa0-0xffaf at device 7.1 o= n pci0 ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 uhci0: port 0x3000-0x301f at devi= ce 7.2 on pci0 uhci0: Could not allocate irq device_probe_and_attach: uhci0 attach returned 6 pci0: at device 7.3 (no driver attached) fxp0: port 0x3040-0x307f= mem 0xfea00000-0xfeafffff,0xfebff000-0xfebfffff irq 10 at device 17.0 on p= ci0 fxp0: Disabling dynamic standby mode in EEPROM fxp0: New EEPROM ID: 0x4080 fxp0: EEPROM checksum @ 0x3f: 0xd29 -> 0xd29 fxp0: Ethernet address 00:06:29:de:b9:ac miibus0: on fxp0 inphy0: on miibus0 inphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto fxp1: port 0x3080-0x30bf= mem 0xfe900000-0xfe9fffff,0xfebfe000-0xfebfefff irq 11 at device 18.0 on p= ci0 fxp1: Disabling dynamic standby mode in EEPROM fxp1: New EEPROM ID: 0x4080 fxp1: EEPROM checksum @ 0x3f: 0xe29 -> 0xe29 fxp1: Ethernet address 00:06:29:de:b9:ab miibus1: on fxp1 inphy1: on miibus1 inphy1: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto pcib2: at device 20.0 on pci0 pci2: on pcib2 ips0: port 0x2000-0x20ff mem 0xfe000000-0xfe0fffff = irq 9 at device 15.0 on pci2 ips0: reinitializing adapter, this could take several minutes. ips0: logical drives: 0 Fatal trap 12: page fault while in kernel mode fault virtual address =3D 0xffddc399 fault code =3D supervisor read, page not present instruction pointer =3D 0x8:0xc031ce94 stack pointer =3D 0x10:0xc0ae3c14 frame pointer =3D 0x10:0xc0ae3c24 code segment =3D base 0x0, limit 0xfffff, type 0x1b =3D DPL 0, pres 1, def32 1, gran 1 processor eflags =3D interrupt enabled, resume, IOPL =3D 0 current process =3D 0 (swapper) trap number =3D 12 panic: page fault Uptime: 1s Automatic reboot in 15 seconds - press a key on the console to abort --> Press a key on the console to reboot, --> or switch off the system now. -- :: darq.net /#/ :: such swoopy interwords | mnemonica From owner-freebsd-scsi@FreeBSD.ORG Mon Sep 15 03:22:31 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6FFF616A4BF for ; Mon, 15 Sep 2003 03:22:31 -0700 (PDT) Received: from mailman.zeta.org.au (mailman.zeta.org.au [203.26.10.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 08B0843F93 for ; Mon, 15 Sep 2003 03:22:30 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: from gamplex.bde.org (katana.zip.com.au [61.8.7.246]) by mailman.zeta.org.au (8.9.3p2/8.8.7) with ESMTP id UAA11143; Mon, 15 Sep 2003 20:22:01 +1000 Date: Mon, 15 Sep 2003 20:22:00 +1000 (EST) From: Bruce Evans X-X-Sender: bde@gamplex.bde.org To: Nate Lawson In-Reply-To: <20030914214758.W5214@root.org> Message-ID: <20030915193015.V607@gamplex.bde.org> References: <3F64E50E.2040608@kanji.com.au> <20030914214758.W5214@root.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org cc: Andrew Snow Subject: Re: ibm x345 w/ serveraid-5i + freebsd ips driver dramas X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 10:22:31 -0000 On Sun, 14 Sep 2003, Nate Lawson wrote: > On Mon, 15 Sep 2003, Andrew Snow wrote: > > Problem 2: (the biggest problem) > > > > While the drive size is reported correctly, the geometry is wrong... > > 472 cyls/254 heads/63 sectors = 7552944 sectors (3687MB) ?! > > > > When setting the BIOS to "non-extended" (2GB max) support mode, freebsd > > then thinks this is the geometry: > > 1846 cyls/128 heads/32 sectors = 7561216 sectors (3692MB). > > > > So I tested a few alternate geometries instead and even though there > > were no error messages, it seemed to get reset to what FreeBSD was > > reporting, no matter how many ways I tried to use the fdisk utility. > > This is not the driver's fault but fdisk's. I really hate FreeBSD's fdisk > and do not ever use it. Do you mean sysinstall? The fdisk(8) utility returns the geometry set by the driver to a fault. E.g., a drive that is reported by the driver to have (C/H/S) geometry 13328/15/63 is now reported by fdisk to have geometry 13328/15/63 although its BIOS geometry is 784/255/63 and it is partitioned with the BIOS geometry. This is GEOM's fault. I really hate GEOM and only use it to test -current's behaviour. RELENG_4 and my version of -current still use my MBR code in subr_diskmbr.c. This gives the geometry set by the driver if there is no partition table and the geometry that was apparently used for partitioning otherwise. The user is reponsible for using a reasonable geometry for the first partition. It should be whatever the user chose or accepted for the BIOS geometry, but many other reasonable and unreasonable geometries may work if the BIOS reverse-detects the geometry from the partition table like subr_diskmbr.c. It's interesting that Linux now gets the geometry wrong in the same way. Linux-2.0.30 through Linux-2.4.0-test8 gave 784/2555/63, and old (1997 and 1996) versions of fdisk and lilo are happy with this. Linux-2.6.0-test2 gives 13328/15/63, and the old versions of fdisk and lilo are unhappy with it. I needed to run lilo to install new kernels and resorted to 2.4.0 so that it worked. The 1997 Linux fdisk used to run fine in readonly mode at lat under FreeBSD until its libraries went to DLL heaven and it went the other way, except it couldn't detect the geometry automatically. A BIOS geometry of 784/255/63 is a simple case. The drive is larger than the 500+ MB limit (1024/16/63) but smaller than the 8- GB limit (1024/255/63), so sysinstall shouldn't have any problems with it. sysinstall's problems begin at 1024 cylinders. It doesn't like C > 1024 and breaks the default geometry attempting to make C <= 1024. >From libdisk/change.c (unifdef PC98): % void % Sanitize_Bios_Geom(struct disk *disk) % { % int sane; % % sane = 1; % % if (disk->bios_cyl > 1024) % sane = 0; Bogus. C >= 1024 is now normal. Also has an off-by-1 error here or later. C = 1024 may cause problems but is considered sane here. % if (disk->bios_hd > 16) % sane = 0; % if (disk->bios_sect > 63) % sane = 0; These are correct. % if (disk->bios_cyl * disk->bios_hd * disk->bios_sect != % disk->chunks->size) % sane = 0; % if (sane) % return; % % /* First try something that IDE can handle */ % disk->bios_sect = 63; % disk->bios_hd = 16; % disk->bios_cyl = disk->chunks->size / % (disk->bios_sect * disk->bios_hd); Not unreasonable, but it may change a weird but in-use geometry. % % if (disk->bios_cyl < 1024) % return; Off-by-1 error here or above. C = 1024 was accepted above but is rejected here. % % /* Hmm, try harder... */ % disk->bios_hd = 255; % disk->bios_cyl = disk->chunks->size / % (disk->bios_sect * disk->bios_hd); % } Bogus. At least on current model ATA disks which are far too large for C < 1024 to be possible, the normal geometry seems to be the firmware one again (C=big/H=16/S=63). >From sysinstall/disks.c: % #ifdef PC98 % if (d->bios_cyl >= 65536 || d->bios_hd > 16 || d->bios_sect >= 256) { % #else % if (d->bios_cyl > 65536 || d->bios_hd > 256 || d->bios_sect >= 64) { % #endif % dialog_clear_norefresh(); % msgConfirm("WARNING: A geometry of %lu/%lu/%lu for %s is incorrect. Using\n" % "a more likely geometry. If this geometry is incorrect or you\n" This alarming warning is now printed for almost all new disks in the non-PC98 case -- 80GB disks are now small but are 10 times too large to fit the 65535/16/255 limit. Bruce From owner-freebsd-scsi@FreeBSD.ORG Mon Sep 15 04:46:26 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F31A216A4BF for ; Mon, 15 Sep 2003 04:46:25 -0700 (PDT) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3592F43F3F for ; Mon, 15 Sep 2003 04:46:25 -0700 (PDT) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id CBAEF3D28; Mon, 15 Sep 2003 07:46:20 -0400 (EDT) From: "Dan Langille" To: Nate Lawson Date: Mon, 15 Sep 2003 07:52:02 -0400 MIME-Version: 1.0 Message-ID: <3F656FA2.29115.37D1B7DC@localhost> Priority: normal In-reply-to: <20030914231722.I5375@root.org> X-mailer: Pegasus Mail for Windows (v4.02a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body cc: scsi@freebsd.org Subject: Re: blocksize error on sa X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 11:46:26 -0000 On 14 Sep 2003 at 23:18, Nate Lawson wrote: > An anonymous person who knows more about sa(4) than me agreed it's > probably a mode select problem with the drive: > > > The 51000 is a piece of shit. With f/w varying all over the map. > > My guess is that, yes, something in mode select isn't happening right. Is "mode select problem" a reference to blocking modes (ie. variable or fixed)? Is this something I can set at run time? What else can I read? -- Dan Langille : http://www.langille.org/ From owner-freebsd-scsi@FreeBSD.ORG Mon Sep 15 07:10:09 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9A63B16A4BF for ; Mon, 15 Sep 2003 07:10:09 -0700 (PDT) Received: from ndsuext.nodak.edu (ndsuext.NoDak.edu [134.129.92.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id A7B7743F3F for ; Mon, 15 Sep 2003 07:10:08 -0700 (PDT) (envelope-from echriste@ndsuext.nodak.edu) Received: from dyn231.iacc-tm4.ndsu.NoDak.edu (dyn231.iacc-tm4.ndsu.NoDak.edu [134.129.92.231]) by ndsuext.nodak.edu (8.11.6/8.11.6) with ESMTP id h8FE9lk24301; Mon, 15 Sep 2003 09:09:47 -0500 From: Eric To: Dan Langille In-Reply-To: <3F656FA2.29115.37D1B7DC@localhost> References: <3F656FA2.29115.37D1B7DC@localhost> Content-Type: text/plain Message-Id: <1063634982.1847.25.camel@dyn231.iacc-tm4.ndsu.nodak.edu> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.3 Date: 15 Sep 2003 09:09:42 -0500 Content-Transfer-Encoding: 7bit X-MailScanner: Found to be clean cc: scsi@freebsd.org Subject: Re: blocksize error on sa X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 14:10:09 -0000 On Mon, 2003-09-15 at 06:52, Dan Langille wrote: > On 14 Sep 2003 at 23:18, Nate Lawson wrote: > > > An anonymous person who knows more about sa(4) than me agreed it's > > probably a mode select problem with the drive: > > > > > The 51000 is a piece of shit. With f/w varying all over the map. > > > My guess is that, yes, something in mode select isn't happening right. > > > Is "mode select problem" a reference to blocking modes (ie. variable > or fixed)? Is this something I can set at run time? What else can I > read? I had a similar problem with a different drive a few years ago. It turned out to be an incorrect quirk entry. Here's a link to the relevant post. http://docs.freebsd.org/cgi/getmsg.cgi?fetch=21901+0+archive/2000/freebsd-scsi/20000910.freebsd-scsi Eric -- Eric From owner-freebsd-scsi@FreeBSD.ORG Mon Sep 15 07:16:28 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4042A16A4EA for ; Mon, 15 Sep 2003 07:16:28 -0700 (PDT) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 820C343FFB for ; Mon, 15 Sep 2003 07:16:27 -0700 (PDT) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 2F5A93D28; Mon, 15 Sep 2003 10:16:23 -0400 (EDT) From: "Dan Langille" To: Eric Date: Mon, 15 Sep 2003 10:22:05 -0400 MIME-Version: 1.0 Message-ID: <3F6592CD.22142.5D8904@localhost> Priority: normal References: <3F656FA2.29115.37D1B7DC@localhost> In-reply-to: <1063634982.1847.25.camel@dyn231.iacc-tm4.ndsu.nodak.edu> X-mailer: Pegasus Mail for Windows (v4.02a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body cc: scsi@freebsd.org Subject: Re: blocksize error on sa X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 14:16:28 -0000 On 15 Sep 2003 at 9:09, Eric wrote: > On Mon, 2003-09-15 at 06:52, Dan Langille wrote: > > On 14 Sep 2003 at 23:18, Nate Lawson wrote: > > > > > An anonymous person who knows more about sa(4) than me agreed it's > > > probably a mode select problem with the drive: > > > > > > > The 51000 is a piece of shit. With f/w varying all over the map. > > > > My guess is that, yes, something in mode select isn't happening right. > > > > Is "mode select problem" a reference to blocking modes (ie. variable > > or fixed)? Is this something I can set at run time? What else can I > > read? > > I had a similar problem with a different drive a few years ago. It > turned out to be an incorrect quirk entry. > Here's a link to the relevant post. > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=21901+0+archive/2000/freebsd-scsi/20000910.freebsd-scsi Where do I read on quirk entries? apropos quirk gives nothing, and locate quirk gives me: $ locate quirk /usr/include/dev/usb/usb_quirks.h /usr/src/sys/dev/pccard/pccard_cis_quirks.c /usr/src/sys/dev/usb/usb_quirks.c /usr/src/sys/dev/usb/usb_quirks.h Thanks -- Dan Langille : http://www.langille.org/ From owner-freebsd-scsi@FreeBSD.ORG Mon Sep 15 07:23:23 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BE24B16A4BF for ; Mon, 15 Sep 2003 07:23:23 -0700 (PDT) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 13E6F43FB1 for ; Mon, 15 Sep 2003 07:23:23 -0700 (PDT) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 976713D28; Mon, 15 Sep 2003 10:23:15 -0400 (EDT) From: "Dan Langille" To: Eric Date: Mon, 15 Sep 2003 10:28:57 -0400 MIME-Version: 1.0 Message-ID: <3F659469.12666.63D3F7@localhost> Priority: normal In-reply-to: <3F6592CD.22142.5D8904@localhost> References: <1063634982.1847.25.camel@dyn231.iacc-tm4.ndsu.nodak.edu> X-mailer: Pegasus Mail for Windows (v4.02a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body cc: scsi@freebsd.org Subject: Re: blocksize error on sa X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 14:23:23 -0000 On 15 Sep 2003 at 10:22, Dan Langille wrote: > On 15 Sep 2003 at 9:09, Eric wrote: > > > On Mon, 2003-09-15 at 06:52, Dan Langille wrote: > > > On 14 Sep 2003 at 23:18, Nate Lawson wrote: > > > > > > > An anonymous person who knows more about sa(4) than me agreed it's > > > > probably a mode select problem with the drive: > > > > > > > > > The 51000 is a piece of shit. With f/w varying all over the map. > > > > > My guess is that, yes, something in mode select isn't happening right. > > > > > > Is "mode select problem" a reference to blocking modes (ie. variable > > > or fixed)? Is this something I can set at run time? What else can I > > > read? > > > > I had a similar problem with a different drive a few years ago. It > > turned out to be an incorrect quirk entry. > > Here's a link to the relevant post. > > > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=21901+0+archive/2000/freebsd-scsi/20000910.freebsd-scsi > > Where do I read on quirk entries? DOH.... in src/sys/cam/scsi/scsi_sa.c I'll submit a patch if what I come up with solves the problem... -- Dan Langille : http://www.langille.org/ From owner-freebsd-scsi@FreeBSD.ORG Mon Sep 15 09:29:19 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1110616A4BF for ; Mon, 15 Sep 2003 09:29:19 -0700 (PDT) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 607FE43FD7 for ; Mon, 15 Sep 2003 09:29:18 -0700 (PDT) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 23D043D28; Mon, 15 Sep 2003 12:29:10 -0400 (EDT) From: "Dan Langille" To: Eric Date: Mon, 15 Sep 2003 12:34:52 -0400 MIME-Version: 1.0 Message-ID: <3F65B1EC.6654.D71C71@localhost> Priority: normal References: <3F656FA2.29115.37D1B7DC@localhost> In-reply-to: <1063634982.1847.25.camel@dyn231.iacc-tm4.ndsu.nodak.edu> X-mailer: Pegasus Mail for Windows (v4.02a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body cc: scsi@freebsd.org Subject: [PATCH]Re: blocksize error on sa X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 16:29:19 -0000 On 15 Sep 2003 at 9:09, Eric wrote: > On Mon, 2003-09-15 at 06:52, Dan Langille wrote: > > On 14 Sep 2003 at 23:18, Nate Lawson wrote: > > > > > An anonymous person who knows more about sa(4) than me agreed it's > > > probably a mode select problem with the drive: > > > > > > > The 51000 is a piece of shit. With f/w varying all over the map. > > > > My guess is that, yes, something in mode select isn't happening right. > > > > > > Is "mode select problem" a reference to blocking modes (ie. variable > > or fixed)? Is this something I can set at run time? What else can I > > read? > > I had a similar problem with a different drive a few years ago. It > turned out to be an incorrect quirk entry. > Here's a link to the relevant post. > > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=21901+0+archive/2000/freebsd-scsi/20000910.freebsd-scsi Thank you. Patch follows: --- scsi_sa.c~ Wed Sep 10 11:53:01 2003 +++ scsi_sa.c Mon Sep 15 10:30:12 2003 @@ -360,7 +360,7 @@ }, { { T_SEQUENTIAL, SIP_MEDIA_REMOVABLE, "WANGTEK", - "51000*", "*"}, SA_QUIRK_FIXED|SA_QUIRK_1FM, 1024 + "51000*", "*"}, SA_QUIRK_FIXED|SA_QUIRK_1FM, 512 } }; Is this the type of thing which should be PR'd or it is a site by site issue? -- Dan Langille : http://www.langille.org/ From owner-freebsd-scsi@FreeBSD.ORG Mon Sep 15 13:04:44 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2751616A4BF for ; Mon, 15 Sep 2003 13:04:44 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 9FF0C43FA3 for ; Mon, 15 Sep 2003 13:04:43 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 6920 invoked by uid 1000); 15 Sep 2003 20:04:44 -0000 Date: Mon, 15 Sep 2003 13:04:44 -0700 (PDT) From: Nate Lawson To: Ian Morrison In-Reply-To: <20030915095409.GA26587@phear.darq.net> Message-ID: <20030915130226.H6780@root.org> References: <20030915095409.GA26587@phear.darq.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: scsi@freebsd.org Subject: Re: IBM ServeRaid-3 on FreeBSD 5.1 (release & current) X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 20:04:44 -0000 On Mon, 15 Sep 2003, Ian Morrison wrote: > i've just got hold of an IBM Netfinity 4000R system (8653-45Y) which > uses an IBM ServeRaid-3L to control two 9 gig disks. Drives are set up > as a standard mirror, and online. Booting from 5.1-RELEASE and the > latest snapshot i could find both result in a kernel panic on boot. ips(4) was written by David Jeffrey and imported by Scott Long. Since it's pretty new, there are probably a lot of things to be fixed. -Nate From owner-freebsd-scsi@FreeBSD.ORG Mon Sep 15 16:13:21 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 8C42516A4B3 for ; Mon, 15 Sep 2003 16:13:21 -0700 (PDT) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 96A9943FB1 for ; Mon, 15 Sep 2003 16:13:20 -0700 (PDT) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 825303D28 for ; Mon, 15 Sep 2003 19:13:12 -0400 (EDT) From: "Dan Langille" To: scsi@freebsd.org Date: Mon, 15 Sep 2003 19:12:50 -0400 MIME-Version: 1.0 Message-ID: <3F660F32.17694.2490D2C@localhost> Priority: normal X-mailer: Pegasus Mail for Windows (v4.02a) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Subject: is MinBlock == MaxBlock common? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 15 Sep 2003 23:13:21 -0000 How common is it for a device to have a MinBlock == MaxBlock as in the following? I ask this because this is what it showing up after I patched my sa(4). See http://docs.freebsd.org/cgi/getmsg.cgi?fetch=43376+0+current/freebsd- scsi for details. # /usr/local/sbin/tapeinfo -f /dev/pass0 Product Type: Tape Drive Vendor ID: 'WANGTEK ' Product ID: '51000 SCSI M74H' Revision: '12B3' Attached Changer: Yes MinBlock:512 MaxBlock:512 Ready: yes And from dmesg: sa0 at ahc0 bus 0 target 2 lun 0 sa0: Removable Sequential Access SCSI- CCS device sa0: 3.300MB/s transfers Thanks -- Dan Langille : http://www.langille.org/ From owner-freebsd-scsi@FreeBSD.ORG Mon Sep 15 22:38:34 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A7C3716A4B3 for ; Mon, 15 Sep 2003 22:38:34 -0700 (PDT) Received: from w250.z064001178.sjc-ca.dsl.cnc.net (adsl-66.218.45.239.dslextreme.com [66.218.45.239]) by mx1.FreeBSD.org (Postfix) with SMTP id C039F43FBF for ; Mon, 15 Sep 2003 22:38:31 -0700 (PDT) (envelope-from jos@catnook.com) Received: (qmail 1064 invoked by uid 1000); 16 Sep 2003 05:38:51 -0000 Date: Mon, 15 Sep 2003 22:38:28 -0700 From: Jos Backus To: freebsd-scsi@freebsd.org Message-ID: <20030916053850.GA1022@lizzy.catnook.com> Mail-Followup-To: freebsd-scsi@freebsd.org References: <20030911165325.GA826@lizzy.catnook.com> <137850000.1063320278@aslan.btc.adaptec.com> <20030912032034.GA826@lizzy.catnook.com> <20030912184536.GM26878@cicely12.cicely.de> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20030912184536.GM26878@cicely12.cicely.de> User-Agent: Mutt/1.5.4i Subject: Re: "Timedout SCB already complete. Interrupts may not be functioning." X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jos@catnook.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2003 05:38:34 -0000 On Fri, Sep 12, 2003 at 08:45:37PM +0200, Bernd Walter wrote: > Sounds like Int routing got wrong results. > Check if disabling helps you: > Index: sys/dev/pci/pci.c > =================================================================== > RCS file: /home/ncvs/src/sys/dev/pci/pci.c,v > retrieving revision 1.226 > diff -u -r1.226 pci.c > --- sys/dev/pci/pci.c 22 Aug 2003 03:11:53 -0000 1.226 > +++ sys/dev/pci/pci.c 11 Sep 2003 19:01:56 -0000 > @@ -800,7 +800,7 @@ > } > > if (cfg->intpin > 0 && PCI_INTERRUPT_VALID(cfg->intline)) { > -#if defined(__ia64__) || (defined(__i386__) && !defined(SMP)) > +#if defined(__ia64__) || (defined(__noi386__) && !defined(SMP)) > /* > * Try to re-route interrupts. Sometimes the BIOS or > * firmware may leave bogus values in these registers. > My apologies for the late response. Dankeschön Bernd, I'll try this tomorrow and will report back here. > I saw the same yesterday on an Asus T2P4 board and got the impression > about a BIOS bug, but since I installed using old source I did not > mention yet. > In my case the result was the same in that all routing resulted in > beeing IRQ4. > > -- > B.Walter BWCT http://www.bwct.de > ticso@bwct.de info@bwct.de -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ jos at catnook.com _/_/ _/_/_/ require 'std/disclaimer' From owner-freebsd-scsi@FreeBSD.ORG Tue Sep 16 08:38:44 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCACF16A4B3; Tue, 16 Sep 2003 08:38:44 -0700 (PDT) Received: from mail.sandvine.com (sandvine.com [199.243.201.138]) by mx1.FreeBSD.org (Postfix) with ESMTP id 806C743FB1; Tue, 16 Sep 2003 08:38:43 -0700 (PDT) (envelope-from don@sandvine.com) Received: by mail.sandvine.com with Internet Mail Service (5.5.2653.19) id ; Tue, 16 Sep 2003 11:38:41 -0400 Message-ID: From: Don Bowman To: "'freebsd-scsi@freebsd.org'" , "'aic7xxx@freebsd.org'" Date: Tue, 16 Sep 2003 11:38:36 -0400 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" Subject: FYI, Seagate and SCB timed out X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2003 15:38:44 -0000 FYI, there is a new firmware available from seagate for both the 10K(007) and 15K(006) U320 drives. If you are experiencing issues such as 'SCB timed out' messages appearing on your console, [perhaps in conjunction with the ahd (AIC7902) adaptec driver] you may wish to contact seagate and request this firmware. --don From owner-freebsd-scsi@FreeBSD.ORG Tue Sep 16 10:07:05 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9D61816A4B3; Tue, 16 Sep 2003 10:07:05 -0700 (PDT) Received: from ganymede.hub.org (u173n10.eastlink.ca [24.224.173.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4A1743FBD; Tue, 16 Sep 2003 10:07:02 -0700 (PDT) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id 13A2834484; Tue, 16 Sep 2003 14:06:59 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 0FE3933C91; Tue, 16 Sep 2003 14:06:59 -0300 (ADT) Date: Tue, 16 Sep 2003 14:06:59 -0300 (ADT) From: "Marc G. Fournier" To: Don Bowman In-Reply-To: Message-ID: <20030916140611.L17406@ganymede.hub.org> References: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: "'freebsd-scsi@freebsd.org'" cc: "'aic7xxx@freebsd.org'" Subject: Re: FYI, Seagate and SCB timed out X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2003 17:07:05 -0000 'k, 4 out of 6 drives upgraded: neptune# camcontrol devlist at scbus1 target 0 lun 0 (pass0,da0) at scbus1 target 1 lun 0 (pass1,da1) at scbus1 target 2 lun 0 (pass2,da2) at scbus1 target 3 lun 0 (pass3,da3) at scbus1 target 4 lun 0 (pass4,da4) at scbus1 target 5 lun 0 (pass5,da5) at scbus1 target 6 lun 0 (pass6) da2 is the one that I've been noticing it on more frequently, so we'll see what happens over the next few days ... if all is well, will scheduale some time in single user mode for the other two *cross fingers* On Tue, 16 Sep 2003, Don Bowman wrote: > > FYI, there is a new firmware available from seagate > for both the 10K(007) and 15K(006) U320 drives. > If you are experiencing issues such as > 'SCB timed out' messages appearing on your console, > [perhaps in conjunction with the ahd (AIC7902) adaptec > driver] you may wish to contact seagate and request this > firmware. > > --don > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Tue Sep 16 11:20:35 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 589B816A4B3 for ; Tue, 16 Sep 2003 11:20:35 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 02DA643FFB for ; Tue, 16 Sep 2003 11:20:07 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 9640 invoked by uid 1000); 16 Sep 2003 18:20:08 -0000 Date: Tue, 16 Sep 2003 11:20:08 -0700 (PDT) From: Nate Lawson To: Dan Langille In-Reply-To: <3F660F32.17694.2490D2C@localhost> Message-ID: <20030916111926.N9364@root.org> References: <3F660F32.17694.2490D2C@localhost> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: scsi@freebsd.org Subject: Re: is MinBlock == MaxBlock common? X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Sep 2003 18:20:35 -0000 On Mon, 15 Sep 2003, Dan Langille wrote: > How common is it for a device to have a MinBlock == MaxBlock as in > the following? > > I ask this because this is what it showing up after I patched my > sa(4). See > http://docs.freebsd.org/cgi/getmsg.cgi?fetch=43376+0+current/freebsd- > scsi for details. > > # /usr/local/sbin/tapeinfo -f /dev/pass0 > Product Type: Tape Drive > Vendor ID: 'WANGTEK ' > Product ID: '51000 SCSI M74H' > Revision: '12B3' > Attached Changer: Yes > MinBlock:512 > MaxBlock:512 > Ready: yes Since you effectively hard-coded the blocksize to 512 using the quirk, you're just getting that value sent back to you, not the actual device MODE SENSE page. -Nate From owner-freebsd-scsi@FreeBSD.ORG Tue Sep 16 21:36:08 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B55D916A4B3 for ; Tue, 16 Sep 2003 21:36:08 -0700 (PDT) Received: from w250.z064001178.sjc-ca.dsl.cnc.net (adsl-66.218.45.239.dslextreme.com [66.218.45.239]) by mx1.FreeBSD.org (Postfix) with SMTP id 7105D43FBD for ; Tue, 16 Sep 2003 21:36:07 -0700 (PDT) (envelope-from jos@catnook.com) Received: (qmail 28225 invoked by uid 1000); 17 Sep 2003 04:36:29 -0000 Date: Tue, 16 Sep 2003 21:36:07 -0700 From: Jos Backus To: freebsd-scsi@freebsd.org Message-ID: <20030917043629.GA820@lizzy.catnook.com> Mail-Followup-To: freebsd-scsi@freebsd.org References: <20030911165325.GA826@lizzy.catnook.com> <137850000.1063320278@aslan.btc.adaptec.com> <20030912032034.GA826@lizzy.catnook.com> <20030912184536.GM26878@cicely12.cicely.de> <20030916053850.GA1022@lizzy.catnook.com> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20030916053850.GA1022@lizzy.catnook.com> User-Agent: Mutt/1.5.4i Subject: Re: "Timedout SCB already complete. Interrupts may not be functioning." X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jos@catnook.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2003 04:36:08 -0000 On Mon, Sep 15, 2003 at 10:38:28PM -0700, Jos Backus wrote: > On Fri, Sep 12, 2003 at 08:45:37PM +0200, Bernd Walter wrote: > > Sounds like Int routing got wrong results. > > Check if disabling helps you: > > Index: sys/dev/pci/pci.c > > =================================================================== > > RCS file: /home/ncvs/src/sys/dev/pci/pci.c,v > > retrieving revision 1.226 > > diff -u -r1.226 pci.c > > --- sys/dev/pci/pci.c 22 Aug 2003 03:11:53 -0000 1.226 > > +++ sys/dev/pci/pci.c 11 Sep 2003 19:01:56 -0000 > > @@ -800,7 +800,7 @@ > > } > > > > if (cfg->intpin > 0 && PCI_INTERRUPT_VALID(cfg->intline)) { > > -#if defined(__ia64__) || (defined(__i386__) && !defined(SMP)) > > +#if defined(__ia64__) || (defined(__noi386__) && !defined(SMP)) > > /* > > * Try to re-route interrupts. Sometimes the BIOS or > > * firmware may leave bogus values in these registers. > > > > My apologies for the late response. Dankeschön Bernd, I'll try this tomorrow > and will report back here. This patch does indeed fix the problem I was seeing. Thanks Bernd. Jos > > I saw the same yesterday on an Asus T2P4 board and got the impression > > about a BIOS bug, but since I installed using old source I did not > > mention yet. > > In my case the result was the same in that all routing resulted in > > beeing IRQ4. > > > > -- > > B.Walter BWCT http://www.bwct.de > > ticso@bwct.de info@bwct.de -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ jos at catnook.com _/_/ _/_/_/ require 'std/disclaimer' From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 17 10:30:48 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D32C16A4B3 for ; Wed, 17 Sep 2003 10:30:48 -0700 (PDT) Received: from msgbas1x.cos.agilent.com (msgbas1x.cos.agilent.com [192.25.240.36]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8612D43FBF for ; Wed, 17 Sep 2003 10:30:47 -0700 (PDT) (envelope-from ctuffli@cre85086tuf.rose.agilent.com) Received: from relcos1.cos.agilent.com (relcos1.cos.agilent.com [130.29.152.239]) by msgbas1x.cos.agilent.com (Postfix) with ESMTP id 10C62267E4 for ; Wed, 17 Sep 2003 11:30:47 -0600 (MDT) Received: from rtl.rose.agilent.com (rtl.rose.agilent.com [130.30.179.189]) by relcos1.cos.agilent.com (Postfix) with ESMTP id 8F54C13A for ; Wed, 17 Sep 2003 11:30:46 -0600 (MDT) Received: from cre85086tuf.rose.agilent.com (cre85086tuf.rose.agilent.com [130.30.174.150])ESMTP id KAA02685 for ; Wed, 17 Sep 2003 10:30:45 -0700 (PDT) Received: by cre85086tuf.rose.agilent.com (Postfix, from userid 1001) id D2E1419E179; Wed, 17 Sep 2003 10:32:11 -0700 (PDT) Date: Wed, 17 Sep 2003 10:32:11 -0700 From: Chuck Tuffli To: freebsd-scsi@freebsd.org Message-ID: <20030917173211.GB37253@cre85086tuf.rose.agilent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Subject: difference between scsi_target and scsi_targ_bh X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2003 17:30:48 -0000 I'm in the process of trying to understand how the targ(4) emulator works from top to bottom and ran into some confusion over scsi_target.c vs. scsi_targ_bh.c. From Nate's README, it appears that you need both of these drivers for the target to work. What confuses me is that there seems to be some hefty overlap between the two. For example, the LUN enable/disable code is almost identical, the constructors are similar, and the "start" functions are similar. My questions are 1) are both scsi_target and scsi_targ_bh needed 2) if so what is the general difference Thanks! -- Chuck Tuffli Agilent Technologies, Storage Area Networking From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 17 12:42:41 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id B95E416A4B3 for ; Wed, 17 Sep 2003 12:42:41 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 2EB4543FB1 for ; Wed, 17 Sep 2003 12:42:41 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 12651 invoked by uid 1000); 17 Sep 2003 19:42:42 -0000 Date: Wed, 17 Sep 2003 12:42:42 -0700 (PDT) From: Nate Lawson To: Chuck Tuffli In-Reply-To: <20030917173211.GB37253@cre85086tuf.rose.agilent.com> Message-ID: <20030917124026.Q12649@root.org> References: <20030917173211.GB37253@cre85086tuf.rose.agilent.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org Subject: Re: difference between scsi_target and scsi_targ_bh X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 17 Sep 2003 19:42:41 -0000 On Wed, 17 Sep 2003, Chuck Tuffli wrote: > I'm in the process of trying to understand how the targ(4) emulator > works from top to bottom and ran into some confusion over > scsi_target.c vs. scsi_targ_bh.c. From Nate's README, it appears that > you need both of these drivers for the target to work. What confuses > me is that there seems to be some hefty overlap between the two. For > example, the LUN enable/disable code is almost identical, the > constructors are similar, and the "start" functions are similar. > > My questions are > 1) are both scsi_target and scsi_targ_bh needed > 2) if so what is the general difference > > Thanks! The scsi_target kernel driver enables target mode and then passes CCBs back and forth between a userland component. The scsi_targ_bh driver auto-attaches to any LUNs that are enabled but don't have a listener. It returns valid "device not here" reponses. On isp(4), for instance, you can't just enable one LUN. The firmware enables all LUNs when it gets an enable commands. The scsi_targ_bh device handles the LUNs that you didn't really want. -Nate From owner-freebsd-scsi@FreeBSD.ORG Wed Sep 17 18:39:27 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 73D1B16A4B3 for ; Wed, 17 Sep 2003 18:39:27 -0700 (PDT) Received: from mail1.kanji.com.au (adsl-114-194.swiftdsl.com.au [202.154.114.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8C3A43FBD for ; Wed, 17 Sep 2003 18:39:21 -0700 (PDT) (envelope-from als@kanji.com.au) Received: from kanji.com.au (unknown [10.0.0.209]) by mail1.kanji.com.au (Postfix) with ESMTP id BD1173711 for ; Thu, 18 Sep 2003 11:39:15 +1000 (EST) Message-ID: <3F690CB5.6000001@kanji.com.au> Date: Thu, 18 Sep 2003 11:39:01 +1000 From: Andrew Snow User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: adaptec 2120S report X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2003 01:39:27 -0000 After my failure to get the Serveraid-5i working, I have put in an Adaptec 2120S. This card has very similar features to the Serveraid card, with the addition that it actually works in FreeBSD. After a couple of days of testing I can recommend this card. I have 6x36GB IBM 10krpm drives running in RAID 50 configuration with FreeBSD 5.1-REL. The only downside was I cannot get it working at Ultra-320 with this IBM x345 hotswap backplane, but it is working great at Ultra-160. With my configuration, a quick test of file system sequential access speed shows reads at 47mb/s and writes at 27mb/s. The good news is, while the array is degraded and rebuilding, read is 10mb/s and write is 6mb/s which is still quite respectable. The box still feels fast enough while the array is rebuilding. The downside is rebuilding the RAID5 containers took 5 hours - each. Two problems with this controller in FreeBSD 5.1: 1. FreeBSD won't boot while the array is rebuilding. It hangs after detecting aacd0. I did not try waiting 5 hours to see if it continued after the array rebuild finished. Workaround is to only hot swap drives while FreeBSD is running, and do not reboot until rebuild is finished. Alternatively, boot into the controller BIOS and wait for rebuild to finish there. 2. I could not get SMP kernel to work - its a Xeon 2.6ghz supporting hyperthreading. SMP worked without the controller, but hangs during boot with the controller. Luckily this is not a big problem for us as we only need a single CPU and hyperthreading is of minor/dubious advantage. Workaround is to simply not use an SMP kernel. Other than that, it seems to be working very nicely. I look forward to seeing the Serveraid / ips driver issues resolved in 5.2... - Andrew From owner-freebsd-scsi@FreeBSD.ORG Thu Sep 18 01:29:17 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A38F416A4B3 for ; Thu, 18 Sep 2003 01:29:17 -0700 (PDT) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id BF2C643F85 for ; Thu, 18 Sep 2003 01:29:16 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: (qmail 22987 invoked by uid 1002); 18 Sep 2003 08:29:15 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 18 Sep 2003 08:29:15 -0000 Message-ID: <3F696CD4.20602@freebsd.org> Date: Thu, 18 Sep 2003 02:29:08 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Snow References: <3F690CB5.6000001@kanji.com.au> In-Reply-To: <3F690CB5.6000001@kanji.com.au> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@freebsd.org Subject: Re: adaptec 2120S report X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2003 08:29:17 -0000 Andrew Snow wrote: > > After my failure to get the Serveraid-5i working, I have put in an > Adaptec 2120S. This card has very similar features to the Serveraid > card, with the addition that it actually works in FreeBSD. > > After a couple of days of testing I can recommend this card. I have > 6x36GB IBM 10krpm drives running in RAID 50 configuration with FreeBSD > 5.1-REL. The only downside was I cannot get it working at Ultra-320 > with this IBM x345 hotswap backplane, but it is working great at Ultra-160. What tool are you using to report the speed? I haven't tried the IBM backplanes much, but it wouldn't surprise me if it didn't support packetized mode and therefore not support Ultra320. > > With my configuration, a quick test of file system sequential access > speed shows reads at 47mb/s and writes at 27mb/s. The good news is, > while the array is degraded and rebuilding, read is 10mb/s and write is > 6mb/s which is still quite respectable. The box still feels fast enough > while the array is rebuilding. The downside is rebuilding the RAID5 > containers took 5 hours - each. > > Two problems with this controller in FreeBSD 5.1: > > 1. FreeBSD won't boot while the array is rebuilding. It hangs after > detecting aacd0. I did not try waiting 5 hours to see if it continued > after the array rebuild finished. > Workaround is to only hot swap drives while FreeBSD is running, and do > not reboot until rebuild is finished. Alternatively, boot into the > controller BIOS and wait for rebuild to finish there. > This should not happen, and I cannot reproduce this locally. What circumstances surrounded the build? Was it initiated by the BIOS? Would it be possible to enable 'bootverbose' and send me a transcript of the boot log? > 2. I could not get SMP kernel to work - its a Xeon 2.6ghz supporting > hyperthreading. SMP worked without the controller, but hangs during boot > with the controller. Luckily this is not a big problem for us as we > only need a single CPU and hyperthreading is of minor/dubious advantage. > Workaround is to simply not use an SMP kernel. Again, this is quite serious. I've fixed several bugs since 5.1 was released that could contribute to this. However, it's another case of not being able to reliably reproduce the problem locally. Would you be able to test a very recent 5-current snapshot? > > Other than that, it seems to be working very nicely. I look forward to > seeing the Serveraid / ips driver issues resolved in 5.2... It's on my TODO list. I apologize for not being responsive, I've been quite buried under other projects. Scott From owner-freebsd-scsi@FreeBSD.ORG Thu Sep 18 02:48:33 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 531BD16A4B3; Thu, 18 Sep 2003 02:48:33 -0700 (PDT) Received: from mail1.kanji.com.au (adsl-114-194.swiftdsl.com.au [202.154.114.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 67C2D43FB1; Thu, 18 Sep 2003 02:48:31 -0700 (PDT) (envelope-from als@kanji.com.au) Received: from kanji.com.au (unknown [10.0.0.209]) by mail1.kanji.com.au (Postfix) with ESMTP id 03EC036F8; Thu, 18 Sep 2003 19:48:29 +1000 (EST) Message-ID: <3F697F6D.4050108@kanji.com.au> Date: Thu, 18 Sep 2003 19:48:29 +1000 From: Andrew Snow User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org References: <3F690CB5.6000001@kanji.com.au> <3F696CD4.20602@freebsd.org> In-Reply-To: <3F696CD4.20602@freebsd.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: adaptec 2120S report X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Sep 2003 09:48:33 -0000 >> The only downside was I cannot get it working at Ultra-320 >> with this IBM x345 hotswap backplane, but it is working great at >> Ultra-160. Scott Long wrote: > What tool are you using to report the speed? I haven't tried the IBM > backplanes much, but it wouldn't surprise me if it didn't support > packetized mode and therefore not support Ultra320. I use aaccli to report the speed - combined with the fact that if I try to set the speed in the BIOS to 320, I get SCSI parity errors and failure messages all over the place, where 160 works fine (with "Packetized" enabled, too) The backplane is supposed to support Ultra-320. It works with the motherboard LSI Ultra-320 controller. However, the docs for the board say "Data integrity cannot be guaranteed when using third party controller" or something to that effect. It doesn't help that the backplane has the weirdest connector I have ever seen, so I was forced to use another SCSI cable with no terminator and a female-to-female adaptor (the supplied SCSI cable is very short!). >> FreeBSD won't boot during rebuild > This should not happen, and I cannot reproduce this locally. What > circumstances surrounded the build? Was it initiated by the BIOS? > Would it be possible to enable 'bootverbose' and send me a transcript > of the boot log? Scenario: pull a drive out (I pulled out SCSI ID#5), wait, push it back in, and a rebuild begins automatically. The freebsd driver happily logs the messages explaining what is going on. Then, reboot freebsd. When it boots again you get this: ----- pcib6: at pcibus 6 on motherboard pci6: on pcib6 aac0: mem 0xf4000000-0xf7ffffff irq 9 at device 1.0 on pci6 aac0: i960RX 100MHz, 48MB cache memory, optional battery present aac0: Kernel 4.0-0, Build 6008, S/N b88205 aac0: Supported Options=1f7e aacp0: on aac0 .............. ata0-master: piomode=12 dmamode=34 udmamode=66 dmaflag=1 ata0-master: success setting PIO4 on ServerWorks CSB5 chip acd0: CDROM drive at ata0 as master acd0: read 4125KB/s (32015KB/s), 128KB buffer, PIO4 acd0: Reads: CD-R, CD-RW, CD-DA stream, packet acd0: Writes: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray, unlocked acd0: Medium: no/blank disc aacd0: on aac0 aacd0: 138850MB (284364800 sectors) GEOM: new disk aacd0 [0] f:80 typ:165 s(CHS):0/1/1 e(CHS):1023/254/63 s:63 l:284350437 [1] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [2] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 [3] f:00 typ:0 s(CHS):0/0/0 e(CHS):0/0/0 s:0 l:0 GEOM: Configure aacd0s1, start 32256 length 145587423744 end 145587455999 GEOM: Configure aacd0s1a, start 0 length 536870912 end 536870911 GEOM: Configure aacd0s1b, start 143344533504 length 1073741824 end 144418275327 GEOM: Configure aacd0s1c, start 0 length 145587423744 end 145587423743 GEOM: Configure aacd0s1d, start 536870912 length 10737418240 end 11274289151 GEOM: Configure aacd0s1e, start 11274289152 length 132070244352 end 143344533503 GEOM: Configure aacd0s1f, start 144418275328 length 1169148416 end 145587423743 (probe3:aacp0:0:3:0): Data Overrun (probe3:aacp0:0:3:0): Retrying Command (probe5:aacp0:0:5:0): Data Overrun (probe5:aacp0:0:5:0): Retrying Command (probe4:aacp0:0:4:0): Data Overrun (probe4:aacp0:0:4:0): Retrying Command (probe0:aacp0:0:0:0): Data Overrun (probe0:aacp0:0:0:0): Retrying Command (probe1:aacp0:0:1:0): Data Overrun (probe1:aacp0:0:1:0): Retrying Command (probe2:aacp0:0:2:0): Data Overrun (probe2:aacp0:0:2:0): Retrying Command (probe3:aacp0:0:3:0): Data Overrun (probe3:aacp0:0:3:0): Retrying Command (probe5:aacp0:0:5:0): Data Overrun (probe5:aacp0:0:5:0): Retrying Command (probe4:aacp0:0:4:0): Data Overrun (probe4:aacp0:0:4:0): Retrying Command (probe0:aacp0:0:0:0): Data Overrun (probe0:aacp0:0:0:0): Retrying Command (probe1:aacp0:0:1:0): Data Overrun (probe1:aacp0:0:1:0): Retrying Command (probe2:aacp0:0:2:0): Data Overrun (probe2:aacp0:0:2:0): Retrying Command (probe3:aacp0:0:3:0): Data Overrun (probe3:aacp0:0:3:0): Retrying Command (probe5:aacp0:0:5:0): Data Overrun (probe5:aacp0:0:5:0): Retrying Command (probe4:aacp0:0:4:0): Data Overrun (probe4:aacp0:0:4:0): Retrying Command (probe0:aacp0:0:0:0): Data Overrun (probe0:aacp0:0:0:0): Retrying Command (probe1:aacp0:0:1:0): Data Overrun (probe1:aacp0:0:1:0): Retrying Command (probe2:aacp0:0:2:0): Data Overrun (probe2:aacp0:0:2:0): Retrying Command (probe3:aacp0:0:3:0): Data Overrun (probe3:aacp0:0:3:0): Retrying Command (probe5:aacp0:0:5:0): Data Overrun (probe5:aacp0:0:5:0): Retrying Command (probe4:aacp0:0:4:0): Data Overrun (probe4:aacp0:0:4:0): Retrying Command (probe0:aacp0:0:0:0): Data Overrun (probe0:aacp0:0:0:0): Retrying Command (probe1:aacp0:0:1:0): Data Overrun (probe1:aacp0:0:1:0): Retrying Command (probe2:aacp0:0:2:0): Data Overrun (probe2:aacp0:0:2:0): Retrying Command (probe3:aacp0:0:3:0): Data Overrun (probe3:aacp0:0:3:0): error 5 (probe3:aacp0:0:3:0): Retries Exausted (probe5:aacp0:0:5:0): Data Overrun (probe5:aacp0:0:5:0): error 5 (probe5:aacp0:0:5:0): Retries Exausted (probe4:aacp0:0:4:0): Data Overrun (probe4:aacp0:0:4:0): error 5 (probe4:aacp0:0:4:0): Retries Exausted (probe0:aacp0:0:0:0): Data Overrun (probe0:aacp0:0:0:0): error 5 (probe0:aacp0:0:0:0): Retries Exausted (probe1:aacp0:0:1:0): Data Overrun (probe1:aacp0:0:1:0): error 5 (probe1:aacp0:0:1:0): Retries Exausted (probe2:aacp0:0:2:0): Data Overrun (probe2:aacp0:0:2:0): error 5 (probe2:aacp0:0:2:0): Retries Exausted stray irq 7 got 5 stray irq 7's: not logging anymore ses0 at aacp0 bus 0 target 8 lun 0 ses0: Fixed unknown SCSI-2 device ses0: Serial Number 1 ses0: 3.300MB/s transfers ses0: SAF-TE Compliant Device pass0 at aacp0 bus 0 target 0 lun 0 pass0: Fixed unknown SCSI-3 device pass0: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass1 at aacp0 bus 0 target 1 lun 0 pass1: Fixed unknown SCSI-3 device pass1: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass2 at aacp0 bus 0 target 2 lun 0 pass2: Fixed unknown SCSI-3 device pass2: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass3 at aacp0 bus 0 target 3 lun 0 pass3: Fixed unknown SCSI-3 device pass3: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass4 at aacp0 bus 0 target 4 lun 0 pass4: Fixed unknown SCSI-3 device pass4: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass5 at aacp0 bus 0 target 5 lun 0 pass5: Fixed unknown SCSI-3 device pass5: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass6 at aacp0 bus 0 target 8 lun 0 pass6: Fixed unknown SCSI-2 device pass6: Serial Number 1 pass6: 3.300MB/s transfers pass0 at aacp0 bus 0 target 0 lun 0 pass0: Fixed unknown SCSI-3 device pass0: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass1 at aacp0 bus 0 target 1 lun 0 pass1: Fixed unknown SCSI-3 device pass1: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass2 at aacp0 bus 0 target 2 lun 0 pass2: Fixed unknown SCSI-3 device pass2: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass3 at aacp0 bus 0 target 3 lun 0 pass3: Fixed unknown SCSI-3 device pass3: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass4 at aacp0 bus 0 target 4 lun 0 pass4: Fixed unknown SCSI-3 device pass4: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) pass5 at aacp0 bus 0 target 5 lun 0 pass5: Fixed unknown SCSI-3 device pass5: 160.000MB/s transfers (80.000MHz, offset 127, 16bit) Mounting root from ufs:/dev/aacd0s1a ----- Above shows one time it got through OK, wasn't able to reproduce this. It normally locks up after "got 5 stray irq 7's: not logging anymore" When I say it locks up, the keyboard still works (scroll lock, page up, page down) and the RAID continues to rebuild (the drive access LEDs show activity). But even waiting 5-10 minutes doesn't show any more console messages... I can either pull the drive out and then boot-up continues OK. Or, hard reset the machine, pull the drive out, and FreeBSD boots. With verbose logging disabled, I see: ----- aacd0: on aac0 aacd0: 138850MB (284364800 sectors) stray irq 7 stray irq 7 stray irq 7 stray irq 7 stray irq 7 got 5 stray irq 7's: not logging anymore ----- followed by the locking up. >> 2. I could not get SMP kernel to work > Would you be > able to test a very recent 5-current snapshot? Sadly this machine is going into production shortly and I don't think I can afford to mess around with anything newer than RELENG_5_1.... is it worth playing around patches to the aac driver while leaving the rest of the system at 5.1 state? >> Other than that, it seems to be working very nicely. I look forward >> to seeing the Serveraid / ips driver issues resolved in 5.2... > It's on my TODO list. I apologize for not being responsive, I've been > quite buried under other projects. No problem at all - the fact that these SCSI cards and servers work as well as they do in a FREE operating system that the vendor refuses to acknowledge amazes me. Thanks for all your excellent work. From owner-freebsd-scsi@FreeBSD.ORG Fri Sep 19 01:57:16 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C9DE516A4B3 for ; Fri, 19 Sep 2003 01:57:16 -0700 (PDT) Received: from mail.webjockey.net (mail.webjockey.net [208.141.46.3]) by mx1.FreeBSD.org (Postfix) with ESMTP id C620843FAF for ; Fri, 19 Sep 2003 01:57:15 -0700 (PDT) (envelope-from gary@outloud.org) Received: from nebula-evojtguv.outloud.org (wv-mrtnbrg-cmts1a-a-210.shphwv.adelphia.net [68.67.224.210]) by mail.webjockey.net (8.12.9/8.12.8) with ESMTP id h8J8vZ3D077741; Fri, 19 Sep 2003 04:57:43 -0400 (EDT) (envelope-from gary@outloud.org) Message-Id: <6.0.0.14.0.20030919045155.0357ab10@localhost> X-Sender: ancient/208.141.46.254@localhost X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.14 (Beta) Date: Fri, 19 Sep 2003 04:57:00 -0400 To: Andrew Snow From: Gary Stanley In-Reply-To: <3F690CB5.6000001@kanji.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed cc: freebsd-scsi@freebsd.org Subject: Re: adaptec 2120S report X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2003 08:57:16 -0000 At 09:39 PM 9/17/2003, you wrote: >After my failure to get the Serveraid-5i working, I have put in an Adaptec >2120S. This card has very similar features to the Serveraid card, with the >addition that it actually works in FreeBSD. > >After a couple of days of testing I can recommend this card. I have >6x36GB IBM 10krpm drives running in RAID 50 configuration with FreeBSD >5.1-REL. The only downside was I cannot get it working at Ultra-320 with >this IBM x345 hotswap backplane, but it is working great at Ultra-160. > >With my configuration, a quick test of file system sequential access speed >shows reads at 47mb/s and writes at 27mb/s. The good news is, while the >array is degraded and rebuilding, read is 10mb/s and write is 6mb/s which >is still quite respectable. The box still feels fast enough while the >array is rebuilding. The downside is rebuilding the RAID5 containers took >5 hours - each. > >Two problems with this controller in FreeBSD 5.1: > >1. FreeBSD won't boot while the array is rebuilding. It hangs after >detecting aacd0. I did not try waiting 5 hours to see if it continued >after the array rebuild finished. >Workaround is to only hot swap drives while FreeBSD is running, and do not >reboot until rebuild is finished. Alternatively, boot into the controller >BIOS and wait for rebuild to finish there. > >2. I could not get SMP kernel to work - its a Xeon 2.6ghz supporting >hyperthreading. SMP worked without the controller, but hangs during boot >with the controller. Luckily this is not a big problem for us as we only >need a single CPU and hyperthreading is of minor/dubious advantage. >Workaround is to simply not use an SMP kernel. > >Other than that, it seems to be working very nicely. I look forward to >seeing the Serveraid / ips driver issues resolved in 5.2... > The issues you are having are something similar to what I experience. When installing FreeBSD 4.x/5.2 onto a building array, the machine panic's and then the background initialization restarts. (Building a 500GB RAID5 array takes me 12 hours, lol) Issues #2 is something I'm not familiar with on 5, but with 4 I am using a 2120S with SMP (Not hyperthreading) From owner-freebsd-scsi@FreeBSD.ORG Fri Sep 19 04:01:19 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 317B516A4B3 for ; Fri, 19 Sep 2003 04:01:19 -0700 (PDT) Received: from mail.komin.lv (www.juris.komin.lv [195.244.131.41]) by mx1.FreeBSD.org (Postfix) with ESMTP id 22B3243F3F for ; Fri, 19 Sep 2003 04:01:16 -0700 (PDT) (envelope-from juriskr@komin.lv) Received: from ntbdc by komin.lv with SMTP (MDaemon.v3.0.2.R) for ; Fri, 19 Sep 2003 13:59:19 +0300 Message-ID: <003601c37e9c$f31bcff0$0201010a@ntbdc> From: "Juris Krumins" To: Date: Fri, 19 Sep 2003 13:58:22 +0300 MIME-Version: 1.0 Content-Type: text/plain; charset="koi8-r" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 X-MDaemon-Deliver-To: freebsd-scsi@freebsd.org X-Return-Path: juriskr@komin.lv X-MDRcpt-To: freebsd-scsi@freebsd.org Subject: aci79xx driver problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2003 11:01:19 -0000 I have a new server with Adaptec SCSI chip 7901 with Ultra 320 support. I'v installed FreeBSD 5.1 on that server, but I have problems with SCSI system. If I stay default (Ultra 320 mode with Packetized mode on ) then I have kernel panic or different erros from ahd driver. If I change mode (Ultra160 with Packetized mode on ) I also have lots of errors for example when copy big directory If I change mode (Ultra160 with Packetized mode off ) I have all working correctly and no errors. So i wonder are there any ways to force SCSI subsysten work correctly in Ultra 320 mode. The Packetized mode in Ultra320 mode is necessery that's why I can't turn it off. Hardware: MB Intel SE7501BR2 Adaptec aic7901 chip Maxtor ATLAS10K4_36WLS scsi disk Any ideas ? Any answer would be apreciated. From owner-freebsd-scsi@FreeBSD.ORG Fri Sep 19 06:36:28 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 46E4F16A4B3 for ; Fri, 19 Sep 2003 06:36:28 -0700 (PDT) Received: from ganymede.hub.org (u173n10.eastlink.ca [24.224.173.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C72143F3F for ; Fri, 19 Sep 2003 06:36:23 -0700 (PDT) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id 2F449341DF; Fri, 19 Sep 2003 10:36:34 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id 26D4E34014; Fri, 19 Sep 2003 10:36:34 -0300 (ADT) Date: Fri, 19 Sep 2003 10:36:34 -0300 (ADT) From: "Marc G. Fournier" To: Juris Krumins In-Reply-To: <003601c37e9c$f31bcff0$0201010a@ntbdc> Message-ID: <20030919103538.U80883@ganymede.hub.org> References: <003601c37e9c$f31bcff0$0201010a@ntbdc> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org Subject: Re: aci79xx driver problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2003 13:36:28 -0000 sounds like the problem(s) we've been experiencing with the Seagate U320 drives ... have you checked with Maxtor about latest firmware revision on the drives themselves? I've gone up two revs so far with Seagate since we put the drives live (latest one *appears* to have eliminated the problem) ... On Fri, 19 Sep 2003, Juris Krumins wrote: > I have a new server with Adaptec SCSI chip 7901 with Ultra 320 support. > I'v installed FreeBSD 5.1 on that server, but I have problems with SCSI > system. > If I stay default (Ultra 320 mode with Packetized mode on ) then I have > kernel panic or different erros from ahd driver. > If I change mode (Ultra160 with Packetized mode on ) I also have lots of > errors for example when copy big directory > If I change mode (Ultra160 with Packetized mode off ) I have all working > correctly and no errors. > > So i wonder are there any ways to force SCSI subsysten work correctly in > Ultra 320 mode. The Packetized mode in Ultra320 mode is necessery that's why > I can't turn it off. > > Hardware: > MB Intel SE7501BR2 > Adaptec aic7901 chip > Maxtor ATLAS10K4_36WLS scsi disk > > Any ideas ? > Any answer would be apreciated. > > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Fri Sep 19 07:45:27 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1979916A4B3 for ; Fri, 19 Sep 2003 07:45:27 -0700 (PDT) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id EEE5B43F75 for ; Fri, 19 Sep 2003 07:45:22 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: (qmail 74597 invoked by uid 1002); 19 Sep 2003 14:45:14 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 19 Sep 2003 14:45:14 -0000 Message-ID: <3F6B1670.4040706@freebsd.org> Date: Fri, 19 Sep 2003 08:45:04 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Gary Stanley References: <6.0.0.14.0.20030919045155.0357ab10@localhost> In-Reply-To: <6.0.0.14.0.20030919045155.0357ab10@localhost> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@FreeBSD.org cc: Andrew Snow Subject: Re: adaptec 2120S report X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2003 14:45:27 -0000 Gary Stanley wrote: > At 09:39 PM 9/17/2003, you wrote: > >> After my failure to get the Serveraid-5i working, I have put in an >> Adaptec 2120S. This card has very similar features to the Serveraid >> card, with the addition that it actually works in FreeBSD. >> >> After a couple of days of testing I can recommend this card. I have >> 6x36GB IBM 10krpm drives running in RAID 50 configuration with FreeBSD >> 5.1-REL. The only downside was I cannot get it working at Ultra-320 >> with this IBM x345 hotswap backplane, but it is working great at >> Ultra-160. >> >> With my configuration, a quick test of file system sequential access >> speed shows reads at 47mb/s and writes at 27mb/s. The good news is, >> while the array is degraded and rebuilding, read is 10mb/s and write >> is 6mb/s which is still quite respectable. The box still feels fast >> enough while the array is rebuilding. The downside is rebuilding the >> RAID5 containers took 5 hours - each. >> >> Two problems with this controller in FreeBSD 5.1: >> >> 1. FreeBSD won't boot while the array is rebuilding. It hangs after >> detecting aacd0. I did not try waiting 5 hours to see if it continued >> after the array rebuild finished. >> Workaround is to only hot swap drives while FreeBSD is running, and do >> not reboot until rebuild is finished. Alternatively, boot into the >> controller BIOS and wait for rebuild to finish there. >> >> 2. I could not get SMP kernel to work - its a Xeon 2.6ghz supporting >> hyperthreading. SMP worked without the controller, but hangs during >> boot with the controller. Luckily this is not a big problem for us as >> we only need a single CPU and hyperthreading is of minor/dubious >> advantage. >> Workaround is to simply not use an SMP kernel. >> >> Other than that, it seems to be working very nicely. I look forward >> to seeing the Serveraid / ips driver issues resolved in 5.2... >> > > The issues you are having are something similar to what I experience. > When installing FreeBSD 4.x/5.2 onto a building array, the machine > panic's and then the background initialization restarts. (Building a > 500GB RAID5 array takes me 12 hours, lol) I've having trouble reproducing this. The most obvious question that comes to mind is, which method of building the array are you using? Creation via the 'Clear' method would likely cause the problems that you are seeing. Creation via the 'Quick Init' method might cause problems too; I don't really trust it and haven't tested it much. Scott From owner-freebsd-scsi@FreeBSD.ORG Fri Sep 19 09:04:46 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5E54B16A4B3 for ; Fri, 19 Sep 2003 09:04:46 -0700 (PDT) Received: from hotmail.com (bay2-dav56.bay2.hotmail.com [65.54.246.191]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AFC343FCB for ; Fri, 19 Sep 2003 09:04:45 -0700 (PDT) (envelope-from nihaopaul@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Fri, 19 Sep 2003 09:04:45 -0700 Received: from 61.171.233.220 by bay2-dav56.bay2.hotmail.com with DAV; Fri, 19 Sep 2003 16:04:45 +0000 X-Originating-IP: [61.171.233.220] X-Originating-Email: [nihaopaul@hotmail.com] From: "nihaopaul" To: "Marc G. Fournier" , "Juris Krumins" References: <003601c37e9c$f31bcff0$0201010a@ntbdc> <20030919103538.U80883@ganymede.hub.org> Date: Sat, 20 Sep 2003 00:04:36 +0800 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 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: X-OriginalArrivalTime: 19 Sep 2003 16:04:45.0450 (UTC) FILETIME=[BE66B6A0:01C37EC7] cc: freebsd-scsi@freebsd.org Subject: Re: aci79xx driver problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2003 16:04:46 -0000 just to let you know Maxtor doesn't do firmware for there drives infact they don't have them. same problem here Paul From: "Marc G. Fournier" To: "Juris Krumins" Cc: Sent: Friday, September 19, 2003 9:36 PM Subject: Re: aci79xx driver problem > > sounds like the problem(s) we've been experiencing with the Seagate U320 > drives ... have you checked with Maxtor about latest firmware revision on > the drives themselves? I've gone up two revs so far with Seagate since we > put the drives live (latest one *appears* to have eliminated the problem) > ... > > > > On Fri, 19 Sep 2003, Juris Krumins wrote: > > > I have a new server with Adaptec SCSI chip 7901 with Ultra 320 support. > > I'v installed FreeBSD 5.1 on that server, but I have problems with SCSI > > system. > > If I stay default (Ultra 320 mode with Packetized mode on ) then I have > > kernel panic or different erros from ahd driver. > > If I change mode (Ultra160 with Packetized mode on ) I also have lots of > > errors for example when copy big directory > > If I change mode (Ultra160 with Packetized mode off ) I have all working > > correctly and no errors. > > > > So i wonder are there any ways to force SCSI subsysten work correctly in > > Ultra 320 mode. The Packetized mode in Ultra320 mode is necessery that's why > > I can't turn it off. > > > > Hardware: > > MB Intel SE7501BR2 > > Adaptec aic7901 chip > > Maxtor ATLAS10K4_36WLS scsi disk > > > > Any ideas ? > > Any answer would be apreciated. > > > > > > _______________________________________________ > > freebsd-scsi@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" From owner-freebsd-scsi@FreeBSD.ORG Fri Sep 19 10:36:39 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id CCA9816A4B3; Fri, 19 Sep 2003 10:36:39 -0700 (PDT) Received: from melusine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org [62.212.105.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id B92C543F85; Fri, 19 Sep 2003 10:36:38 -0700 (PDT) (envelope-from thomas@FreeBSD.ORG) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id CDEED2C3D0; Fri, 19 Sep 2003 19:36:36 +0200 (CEST) Date: Fri, 19 Sep 2003 19:36:36 +0200 From: Thomas Quinot To: freebsd-scsi@freebsd.org, ken@freebsd.org Message-ID: <20030919173636.GA867@melusine.cuivre.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-message-flag: WARNING! Using Outlook can damage your computer. Subject: cam_periph recovered sense handling X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2003 17:36:39 -0000 When the cam_periph layer automagically recovers sense data by issuing a REQUEST SENSE command, it must set the CAM_AUTOSNS_VALID bit in the original CCB's status. Currently, it errouneously sets that bit in the flags field instead. This causes an endless loop of REQUEST SENSE actions, eventually leading to memory exhaustion. The following patch resolves the problem for me; please review. Thomas. Index: cam_periph.c =================================================================== RCS file: /home/ncvs/src/sys/cam/cam_periph.c,v retrieving revision 1.52 diff -u -r1.52 cam_periph.c --- cam_periph.c 10 Sep 2003 18:23:43 -0000 1.52 +++ cam_periph.c 19 Sep 2003 17:25:58 -0000 @@ -975,7 +975,7 @@ sense_key = saved_ccb->csio.sense_data.flags; sense_key &= SSD_KEY; if (sense_key != SSD_KEY_NO_SENSE) { - saved_ccb->ccb_h.flags |= + saved_ccb->ccb_h.status |= CAM_AUTOSNS_VALID; xpt_print_path(saved_ccb->ccb_h.path); printf("Recovered Sense\n"); -- Thomas.Quinot@Cuivre.FR.EU.ORG From owner-freebsd-scsi@FreeBSD.ORG Fri Sep 19 10:50:35 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F1CD816A4D5; Fri, 19 Sep 2003 10:50:34 -0700 (PDT) Received: from melusine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org [62.212.105.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id B027C43FB1; Fri, 19 Sep 2003 10:50:33 -0700 (PDT) (envelope-from thomas@FreeBSD.ORG) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id 8737F2C3D4; Fri, 19 Sep 2003 19:50:32 +0200 (CEST) Date: Fri, 19 Sep 2003 19:50:32 +0200 From: Thomas Quinot To: freebsd-scsi@freebsd.org, ken@freebsd.org Message-ID: <20030919175032.GA2430@melusine.cuivre.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-message-flag: WARNING! Using Outlook can damage your computer. Subject: Defend against calling sysctl_ctx_free on uninitialized context X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2003 17:50:35 -0000 If a fatal error occurs while cd(4) is attaching, before the sysctl_ctx has been initialized, then it must not be freed. The following patch resolves this problem, please review. Thanks, Thomas. Index: scsi_cd.c =================================================================== RCS file: /home/ncvs/src/sys/cam/scsi/scsi_cd.c,v retrieving revision 1.83 diff -u -r1.83 scsi_cd.c --- scsi_cd.c 11 Sep 2003 19:27:24 -0000 1.83 +++ scsi_cd.c 19 Sep 2003 17:47:03 -0000 @@ -91,17 +91,18 @@ } cd_quirks; typedef enum { - CD_FLAG_INVALID = 0x001, - CD_FLAG_NEW_DISC = 0x002, - CD_FLAG_DISC_LOCKED = 0x004, - CD_FLAG_DISC_REMOVABLE = 0x008, - CD_FLAG_TAGGED_QUEUING = 0x010, - CD_FLAG_CHANGER = 0x040, - CD_FLAG_ACTIVE = 0x080, - CD_FLAG_SCHED_ON_COMP = 0x100, - CD_FLAG_RETRY_UA = 0x200, - CD_FLAG_VALID_MEDIA = 0x400, - CD_FLAG_VALID_TOC = 0x800 + CD_FLAG_INVALID = 0x0001, + CD_FLAG_NEW_DISC = 0x0002, + CD_FLAG_DISC_LOCKED = 0x0004, + CD_FLAG_DISC_REMOVABLE = 0x0008, + CD_FLAG_TAGGED_QUEUING = 0x0010, + CD_FLAG_CHANGER = 0x0040, + CD_FLAG_ACTIVE = 0x0080, + CD_FLAG_SCHED_ON_COMP = 0x0100, + CD_FLAG_RETRY_UA = 0x0200, + CD_FLAG_VALID_MEDIA = 0x0400, + CD_FLAG_VALID_TOC = 0x0800, + CD_FLAG_SCTX_INIT = 0x1000 } cd_flags; typedef enum { @@ -458,7 +459,8 @@ xpt_print_path(periph->path); printf("removing device entry\n"); - if (sysctl_ctx_free(&softc->sysctl_ctx) != 0) { + if ((softc->flags & CD_FLAG_SCTX_INIT) != 0 + && sysctl_ctx_free(&softc->sysctl_ctx) != 0) { xpt_print_path(periph->path); printf("can't remove sysctl context\n"); } @@ -622,6 +624,7 @@ mtx_lock(&Giant); sysctl_ctx_init(&softc->sysctl_ctx); + softc->flags |= CD_FLAG_SCTX_INIT; softc->sysctl_tree = SYSCTL_ADD_NODE(&softc->sysctl_ctx, SYSCTL_STATIC_CHILDREN(_kern_cam_cd), OID_AUTO, tmpstr2, CTLFLAG_RD, 0, tmpstr); -- Thomas.Quinot@Cuivre.FR.EU.ORG From owner-freebsd-scsi@FreeBSD.ORG Fri Sep 19 13:12:16 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 70E7116A4B3 for ; Fri, 19 Sep 2003 13:12:16 -0700 (PDT) Received: from natrium.plan-ix.de (natrium.plan-ix.de [212.37.39.36]) by mx1.FreeBSD.org (Postfix) with SMTP id 749D543F85 for ; Fri, 19 Sep 2003 13:12:13 -0700 (PDT) (envelope-from braukmann@tse-online.de) Received: (qmail 28766 invoked from network); 19 Sep 2003 20:24:44 -0000 Received: from unknown (HELO ?192.168.222.11?) (ab%plan-ix.de@212.37.49.203) by natrium.plan-ix.de with SMTP; 19 Sep 2003 20:24:44 -0000 Date: Fri, 19 Sep 2003 22:12:15 +0200 From: Andreas Braukmann To: Scott Long Message-ID: <2147483647.1064009535@[192.168.222.11]> In-Reply-To: <3F6B1670.4040706@freebsd.org> References: <6.0.0.14.0.20030919045155.0357ab10@localhost> <3F6B1670.4040706@freebsd.org> X-Mailer: Mulberry/3.1.0b6 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline cc: freebsd-scsi@FreeBSD.org Subject: Re: adaptec 2120S report X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2003 20:12:16 -0000 -- Scott Long wrote: > I've having trouble reproducing this. The most obvious question that > comes to mind is, which method of building the array are you using? > Creation via the 'Clear' method would likely cause the problems that > you are seeing. The 2200S in the box besides me is in the process of building a 20 GByte RAID 5 volume ("build/verify"-method). Booting -current (a rather old [ca. 2003/03] snapshot install cd) fails. The kernel freezes after announcing the presence of the raid-volume and two error messages: | [...] | aac0: mem [...] irq 11 at device 10 on pci0 | aac0: i960RX 100MHz, 48MB cache memory, optional battery present | aac0: Kernel 4.0-0, Build 6003, S/N b8**** | aac0: Suupported Options=1f7e<[...]> | [...] | aacd0: on aac0 | aacd0: 20480 MB (41943040 sectors) | aac0: Error 5 sending GetDeviceProbeInfo command | aac0: Error 5 sending GetDeviceProbeInfo command | [...] I hope, that I get a fresh -current on my test machine, to provide further testing information. [... a few minutes later ...] Booting from a 2003/09/13 current-snapshot-cd yields nearly the same result. | aac0 Error 5 sending GetDeviceProbeInfo command | [...] | COMMAND 0xc28d80a4 TIMEOUT AFTER 51 SECONDS | COMMAND 0xc28d80a4 TIMEOUT AFTER 116 SECONDS | [... and so on ...] -Andreas From owner-freebsd-scsi@FreeBSD.ORG Fri Sep 19 13:42:40 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9481616A4B3 for ; Fri, 19 Sep 2003 13:42:40 -0700 (PDT) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 7E72443FE0 for ; Fri, 19 Sep 2003 13:42:39 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: (qmail 30358 invoked by uid 1002); 19 Sep 2003 20:42:38 -0000 Received: from unknown (HELO ?10.4.1.5?) (64.58.1.252) by smtp.mho.net with SMTP; 19 Sep 2003 20:42:38 -0000 Date: Fri, 19 Sep 2003 14:44:50 -0600 (MDT) From: Scott Long X-X-Sender: scottl@pooker.samsco.home To: Andreas Braukmann In-Reply-To: <2147483647.1064009535@[192.168.222.11]> Message-ID: <20030919144329.T13111@pooker.samsco.home> References: <6.0.0.14.0.20030919045155.0357ab10@localhost> <3F6B1670.4040706@freebsd.org> <2147483647.1064009535@[192.168.222.11]> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org Subject: Re: adaptec 2120S report X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Sep 2003 20:42:40 -0000 On Fri, 19 Sep 2003, Andreas Braukmann wrote: > > -- Scott Long wrote: > > > I've having trouble reproducing this. The most obvious question that > > comes to mind is, which method of building the array are you using? > > Creation via the 'Clear' method would likely cause the problems that > > you are seeing. > > The 2200S in the box besides me is in the process of building > a 20 GByte RAID 5 volume ("build/verify"-method). > Booting -current (a rather old [ca. 2003/03] snapshot install > cd) fails. The kernel freezes after announcing the presence > of the raid-volume and two error messages: > > | [...] > | aac0: mem [...] irq 11 at device 10 on pci0 > | aac0: i960RX 100MHz, 48MB cache memory, optional battery present > | aac0: Kernel 4.0-0, Build 6003, S/N b8**** > | aac0: Suupported Options=1f7e<[...]> > | [...] > | aacd0: on aac0 > | aacd0: 20480 MB (41943040 sectors) > | aac0: Error 5 sending GetDeviceProbeInfo command > | aac0: Error 5 sending GetDeviceProbeInfo command > | [...] > > I hope, that I get a fresh -current on my test machine, to > provide further testing information. > > [... a few minutes later ...] > > Booting from a 2003/09/13 current-snapshot-cd yields nearly the > same result. > | aac0 Error 5 sending GetDeviceProbeInfo command > | [...] > | COMMAND 0xc28d80a4 TIMEOUT AFTER 51 SECONDS > | COMMAND 0xc28d80a4 TIMEOUT AFTER 116 SECONDS > | [... and so on ...] > Disable the 'aacp' device from your kernel config. It is known to be dodgy. Scott From owner-freebsd-scsi@FreeBSD.ORG Fri Sep 19 19:02:39 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E51E16A4B3 for ; Fri, 19 Sep 2003 19:02:39 -0700 (PDT) Received: from ganymede.hub.org (u173n10.eastlink.ca [24.224.173.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3B01F43FEC for ; Fri, 19 Sep 2003 19:02:34 -0700 (PDT) (envelope-from scrappy@hub.org) Received: by ganymede.hub.org (Postfix, from userid 1000) id C8CB134285; Fri, 19 Sep 2003 23:02:47 -0300 (ADT) Received: from localhost (localhost [127.0.0.1]) by ganymede.hub.org (Postfix) with ESMTP id C59B733C8E; Fri, 19 Sep 2003 23:02:47 -0300 (ADT) Date: Fri, 19 Sep 2003 23:02:47 -0300 (ADT) From: "Marc G. Fournier" To: nihaopaul In-Reply-To: Message-ID: <20030919225955.V6867@ganymede.hub.org> References: <003601c37e9c$f31bcff0$0201010a@ntbdc> <20030919103538.U80883@ganymede.hub.org> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org cc: Juris Krumins Subject: Re: aci79xx driver problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Sep 2003 02:02:39 -0000 k, but the Atlas10Ks were the old Quantum line ... did Quantum not do firmware either? And isn't not doing firmware 'risque'? do they get it right the first time, all the time? :) On Sat, 20 Sep 2003, nihaopaul wrote: > just to let you know Maxtor doesn't do firmware for there drives infact they > don't have them. same problem here > > Paul > > > From: "Marc G. Fournier" > To: "Juris Krumins" > Cc: > Sent: Friday, September 19, 2003 9:36 PM > Subject: Re: aci79xx driver problem > > > > > > sounds like the problem(s) we've been experiencing with the Seagate U320 > > drives ... have you checked with Maxtor about latest firmware revision on > > the drives themselves? I've gone up two revs so far with Seagate since we > > put the drives live (latest one *appears* to have eliminated the problem) > > ... > > > > > > > > On Fri, 19 Sep 2003, Juris Krumins wrote: > > > > > I have a new server with Adaptec SCSI chip 7901 with Ultra 320 support. > > > I'v installed FreeBSD 5.1 on that server, but I have problems with SCSI > > > system. > > > If I stay default (Ultra 320 mode with Packetized mode on ) then I have > > > kernel panic or different erros from ahd driver. > > > If I change mode (Ultra160 with Packetized mode on ) I also have lots of > > > errors for example when copy big directory > > > If I change mode (Ultra160 with Packetized mode off ) I have all working > > > correctly and no errors. > > > > > > So i wonder are there any ways to force SCSI subsysten work correctly in > > > Ultra 320 mode. The Packetized mode in Ultra320 mode is necessery that's > why > > > I can't turn it off. > > > > > > Hardware: > > > MB Intel SE7501BR2 > > > Adaptec aic7901 chip > > > Maxtor ATLAS10K4_36WLS scsi disk > > > > > > Any ideas ? > > > Any answer would be apreciated. > > > > > > > > > _______________________________________________ > > > freebsd-scsi@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > > > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > > > > > _______________________________________________ > > freebsd-scsi@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Fri Sep 19 21:42:10 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F004516A4B3 for ; Fri, 19 Sep 2003 21:42:09 -0700 (PDT) Received: from russell.hamline.edu (russell.hamline.edu [138.192.24.94]) by mx1.FreeBSD.org (Postfix) with ESMTP id C94B643F85 for ; Fri, 19 Sep 2003 21:42:08 -0700 (PDT) (envelope-from rjohanne@piper.hamline.edu) Received: from piper.hamline.edu (piper.hamline.edu [138.192.2.101]) by russell.hamline.edu (8.11.6+Sun/8.11.6) with ESMTP id h8K4ftm10779; Fri, 19 Sep 2003 23:41:55 -0500 (CDT) Received: from kovalevskaya (kovalevskaya [138.192.2.116]) by piper.hamline.edu (8.12.6/8.12.6) with ESMTP id h8K4h60o032450; Fri, 19 Sep 2003 23:43:06 -0500 (CDT) Date: Fri, 19 Sep 2003 23:42:22 -0500 (CDT) From: Robert Johannes X-X-Sender: rjohanne@kovalevskaya.hamline.edu To: "Marc G. Fournier" In-Reply-To: <20030919225955.V6867@ganymede.hub.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org cc: Juris Krumins cc: nihaopaul Subject: Re: aci79xx driver problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Sep 2003 04:42:10 -0000 The original quantum scsi drives were all firmware upgradable. I know because I've had to upgrade firmware on several quantum scsi drive models, from the fireball line to their atlas line. robert On Fri, 19 Sep 2003, Marc G. Fournier wrote: > > k, but the Atlas10Ks were the old Quantum line ... did Quantum not do > firmware either? > > And isn't not doing firmware 'risque'? do they get it right the first > time, all the time? :) > > On Sat, 20 Sep 2003, nihaopaul wrote: > > > just to let you know Maxtor doesn't do firmware for there drives infact they > > don't have them. same problem here > > > > Paul > > > > > > From: "Marc G. Fournier" > > To: "Juris Krumins" > > Cc: > > Sent: Friday, September 19, 2003 9:36 PM > > Subject: Re: aci79xx driver problem > > > > > > > > > > sounds like the problem(s) we've been experiencing with the Seagate U320 > > > drives ... have you checked with Maxtor about latest firmware revision on > > > the drives themselves? I've gone up two revs so far with Seagate since we > > > put the drives live (latest one *appears* to have eliminated the problem) > > > ... > > > > > > > > > > > > On Fri, 19 Sep 2003, Juris Krumins wrote: > > > > > > > I have a new server with Adaptec SCSI chip 7901 with Ultra 320 support. > > > > I'v installed FreeBSD 5.1 on that server, but I have problems with SCSI > > > > system. > > > > If I stay default (Ultra 320 mode with Packetized mode on ) then I have > > > > kernel panic or different erros from ahd driver. > > > > If I change mode (Ultra160 with Packetized mode on ) I also have lots of > > > > errors for example when copy big directory > > > > If I change mode (Ultra160 with Packetized mode off ) I have all working > > > > correctly and no errors. > > > > > > > > So i wonder are there any ways to force SCSI subsysten work correctly in > > > > Ultra 320 mode. The Packetized mode in Ultra320 mode is necessery that's > > why > > > > I can't turn it off. > > > > > > > > Hardware: > > > > MB Intel SE7501BR2 > > > > Adaptec aic7901 chip > > > > Maxtor ATLAS10K4_36WLS scsi disk > > > > > > > > Any ideas ? > > > > Any answer would be apreciated. > > > > > > > > > > > > _______________________________________________ > > > > freebsd-scsi@freebsd.org mailing list > > > > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > > > > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > > > > > > > _______________________________________________ > > > freebsd-scsi@freebsd.org mailing list > > > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > > > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > > > _______________________________________________ > freebsd-scsi@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-scsi > To unsubscribe, send any mail to "freebsd-scsi-unsubscribe@freebsd.org" > From owner-freebsd-scsi@FreeBSD.ORG Fri Sep 19 22:05:36 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 897DE16A4B3 for ; Fri, 19 Sep 2003 22:05:36 -0700 (PDT) Received: from w250.z064001178.sjc-ca.dsl.cnc.net (adsl-66.218.45.239.dslextreme.com [66.218.45.239]) by mx1.FreeBSD.org (Postfix) with SMTP id A266543FCB for ; Fri, 19 Sep 2003 22:05:35 -0700 (PDT) (envelope-from jos@catnook.com) Received: (qmail 50088 invoked by uid 1000); 20 Sep 2003 05:05:56 -0000 Date: Fri, 19 Sep 2003 22:05:34 -0700 From: Jos Backus To: freebsd-scsi@freebsd.org Message-ID: <20030920050556.GA49402@lizzy.catnook.com> Mail-Followup-To: freebsd-scsi@freebsd.org References: <20030911165325.GA826@lizzy.catnook.com> <137850000.1063320278@aslan.btc.adaptec.com> <20030912032034.GA826@lizzy.catnook.com> <20030912184536.GM26878@cicely12.cicely.de> <20030916053850.GA1022@lizzy.catnook.com> <20030917043629.GA820@lizzy.catnook.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030917043629.GA820@lizzy.catnook.com> User-Agent: Mutt/1.5.4i Subject: Re: "Timedout SCB already complete. Interrupts may not be functioning." X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jos@catnook.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Sep 2003 05:05:36 -0000 On Tue, Sep 16, 2003 at 09:36:07PM -0700, Jos Backus wrote: > On Mon, Sep 15, 2003 at 10:38:28PM -0700, Jos Backus wrote: > > On Fri, Sep 12, 2003 at 08:45:37PM +0200, Bernd Walter wrote: > > > Sounds like Int routing got wrong results. > > > Check if disabling helps you: > > > Index: sys/dev/pci/pci.c > > > =================================================================== > > > RCS file: /home/ncvs/src/sys/dev/pci/pci.c,v > > > retrieving revision 1.226 > > > diff -u -r1.226 pci.c > > > --- sys/dev/pci/pci.c 22 Aug 2003 03:11:53 -0000 1.226 > > > +++ sys/dev/pci/pci.c 11 Sep 2003 19:01:56 -0000 > > > @@ -800,7 +800,7 @@ > > > } > > > > > > if (cfg->intpin > 0 && PCI_INTERRUPT_VALID(cfg->intline)) { > > > -#if defined(__ia64__) || (defined(__i386__) && !defined(SMP)) > > > +#if defined(__ia64__) || (defined(__noi386__) && !defined(SMP)) > > > /* > > > * Try to re-route interrupts. Sometimes the BIOS or > > > * firmware may leave bogus values in these registers. Any plans to commit this? -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ jos at catnook.com _/_/ _/_/_/ require 'std/disclaimer' From owner-freebsd-scsi@FreeBSD.ORG Sat Sep 20 04:01:34 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C211816A4B3; Sat, 20 Sep 2003 04:01:34 -0700 (PDT) Received: from melusine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org [62.212.105.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01A0243FB1; Sat, 20 Sep 2003 04:01:34 -0700 (PDT) (envelope-from thomas@FreeBSD.ORG) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id 0671F2C3D4; Sat, 20 Sep 2003 13:01:31 +0200 (CEST) Date: Sat, 20 Sep 2003 13:01:31 +0200 From: Thomas Quinot To: freebsd-scsi@freebsd.org, ken@freebsd.org, gibbs@freebsd.org Message-ID: <20030920110131.GA41062@melusine.cuivre.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i X-message-flag: WARNING! Using Outlook can damage your computer. Subject: Missing length specification in scsi_request_sense X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Sep 2003 11:01:34 -0000 The CDB built by scsi_request_sense always has a zero length indication, preventing correct transfer of sense data during recovery action by cam_periph. The following change resolves the problem, please review. Thomas. Index: scsi/scsi_all.c =================================================================== RCS file: /home/ncvs/src/sys/cam/scsi/scsi_all.c,v retrieving revision 1.42 diff -u -r1.42 scsi_all.c --- scsi/scsi_all.c 10 Jun 2003 18:14:04 -0000 1.42 +++ scsi/scsi_all.c 20 Sep 2003 10:53:38 -0000 @@ -2408,6 +2408,7 @@ scsi_cmd = (struct scsi_request_sense *)&csio->cdb_io.cdb_bytes; bzero(scsi_cmd, sizeof(*scsi_cmd)); scsi_cmd->opcode = REQUEST_SENSE; + scsi_cmd->length = dxfer_len; } void -- Thomas.Quinot@Cuivre.FR.EU.ORG From owner-freebsd-scsi@FreeBSD.ORG Sat Sep 20 09:32:35 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D46C916A4B3 for ; Sat, 20 Sep 2003 09:32:35 -0700 (PDT) Received: from hotmail.com (bay2-dav67.bay2.hotmail.com [65.54.246.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 73D6243FDD for ; Sat, 20 Sep 2003 09:32:34 -0700 (PDT) (envelope-from nihaopaul@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Sat, 20 Sep 2003 09:32:34 -0700 Received: from 61.170.226.93 by bay2-dav67.bay2.hotmail.com with DAV; Sat, 20 Sep 2003 16:32:34 +0000 X-Originating-IP: [61.170.226.93] X-Originating-Email: [nihaopaul@hotmail.com] From: "nihaopaul" To: "Robert Johannes" , "Marc G. Fournier" Date: Sun, 21 Sep 2003 00:32:28 +0800 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Message-ID: X-OriginalArrivalTime: 20 Sep 2003 16:32:34.0276 (UTC) FILETIME=[CB831A40:01C37F94] Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.1 cc: freebsd-scsi@freebsd.org cc: Juris Krumins Subject: Re: aci79xx driver problem X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Sep 2003 16:32:36 -0000 Maxtor atlas 10k iv 36gb driveswhen i contacted them about this the = other day this is what they replied me. will be very intrested if you can firmware from them. paul //979//Nan-Suzhou-Road//Space-301//Shanghai//200001//PRC//Office//(86)-21= //6360-5418//Fax//(86)-21//6350-7147//mp//130.2329.1471//paul@chaos-studi= o.com// ----- Original Message -----=20 From: Maxtor Support=20 To: paul@chaos-studio.com=20 Sent: Tuesday, September 16, 2003 11:59 PM Subject: Maxtor atlas 10k iv 36gb drives [Incident: 030916-000056] Recently you requested personal assistance from our on-line support = center. Below is a summary of your request and our response. If this issue is not resolved to your satisfaction, you may reopen it = within the next 20 days. Thank you for allowing us to be of service to you. You may also update this question by replying to this message. Because = your reply will be automatically processed, you MUST enter your reply in = the space below. Text entered into any other part of this message will = be discarded. [=3D=3D=3D> Please enter your reply below this line <=3D=3D=3D] [=3D=3D=3D> Please enter your reply above this line <=3D=3D=3D] If your issue remains unresolved, please update this question here Subject=20 Maxtor atlas 10k iv 36gb drives=20 =20 Discussion Thread=20 Response (TSAlan44) 09/16/2003 08:59 AM=20 Dear Paul Adams, I see, firmware, not BIOS. Unfortunately we do not have any = firmware upgrades for this drive either. I'm sorry about that. If you have any additional information, please let me know. Thank you, Alan TS44 1-(800)-2-MAXTOR (voice) 353 1 204 1111 (International) http://www.Maxtor.com (web) http://www.MaxStore.com (shop)=20 Response (TSAlan44) 09/16/2003 08:54 AM=20 Dear Paul Adams, A BIOS upgrade is not something we provide. The BIOS resides on = the controller that you are using, the AIC 7902 controller. You would go = through them to obtain the BIOS upgrade. If you have any additional questions, please let me know. Thank you, Alan TS44 1-(800)-2-MAXTOR (voice) 353 1 204 1111 (International) http://www.Maxtor.com (web) http://www.MaxStore.com (shop)=20 Customer 09/16/2003 08:52 AM=20 i mean firmware not bios=20 =20 -------------------------------------------- Maxtor Corporation -------------------------------------------- From owner-freebsd-scsi@FreeBSD.ORG Sat Sep 20 17:17:09 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DAC4216A4B3 for ; Sat, 20 Sep 2003 17:17:09 -0700 (PDT) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id 4A48543FE1 for ; Sat, 20 Sep 2003 17:17:07 -0700 (PDT) (envelope-from scottl@freebsd.org) Received: (qmail 65542 invoked by uid 1002); 21 Sep 2003 00:17:06 -0000 Received: from unknown (HELO freebsd.org) (64.58.1.252) by smtp.mho.net with SMTP; 21 Sep 2003 00:17:06 -0000 Message-ID: <3F6CEDF8.5070803@freebsd.org> Date: Sat, 20 Sep 2003 18:16:56 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3) Gecko/20030425 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Thomas Quinot References: <20030920110131.GA41062@melusine.cuivre.fr.eu.org> In-Reply-To: <20030920110131.GA41062@melusine.cuivre.fr.eu.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-scsi@FreeBSD.org cc: gibbs@FreeBSD.org cc: ken@FreeBSD.org Subject: Re: Missing length specification in scsi_request_sense X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2003 00:17:10 -0000 Thomas Quinot wrote: > The CDB built by scsi_request_sense always has a zero length indication, > preventing correct transfer of sense data during recovery action by > cam_periph. The following change resolves the problem, please review. > > Thomas. > > Index: scsi/scsi_all.c > =================================================================== > RCS file: /home/ncvs/src/sys/cam/scsi/scsi_all.c,v > retrieving revision 1.42 > diff -u -r1.42 scsi_all.c > --- scsi/scsi_all.c 10 Jun 2003 18:14:04 -0000 1.42 > +++ scsi/scsi_all.c 20 Sep 2003 10:53:38 -0000 > @@ -2408,6 +2408,7 @@ > scsi_cmd = (struct scsi_request_sense *)&csio->cdb_io.cdb_bytes; > bzero(scsi_cmd, sizeof(*scsi_cmd)); > scsi_cmd->opcode = REQUEST_SENSE; > + scsi_cmd->length = dxfer_len; > } > > void > Since just about every driver in existance does auto-sense, it doesn't surprise me that you're finding these bugs. This patch looks reasonable to me. Scott From owner-freebsd-scsi@FreeBSD.ORG Sat Sep 20 20:31:35 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D6DCB16A4B3 for ; Sat, 20 Sep 2003 20:31:35 -0700 (PDT) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 38DA043FAF for ; Sat, 20 Sep 2003 20:31:35 -0700 (PDT) (envelope-from nate@rootlabs.com) Received: (qmail 32449 invoked by uid 1000); 21 Sep 2003 03:31:37 -0000 Date: Sat, 20 Sep 2003 20:31:37 -0700 (PDT) From: Nate Lawson To: Jos Backus In-Reply-To: <20030920050556.GA49402@lizzy.catnook.com> Message-ID: <20030920203052.Q32361@root.org> References: <20030911165325.GA826@lizzy.catnook.com> <137850000.1063320278@aslan.btc.adaptec.com> <20030912184536.GM26878@cicely12.cicely.de> <20030917043629.GA820@lizzy.catnook.com> <20030920050556.GA49402@lizzy.catnook.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: freebsd-scsi@freebsd.org Subject: Re: "Timedout SCB already complete. Interrupts may not be functioning." X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2003 03:31:36 -0000 On Fri, 19 Sep 2003, Jos Backus wrote: > On Tue, Sep 16, 2003 at 09:36:07PM -0700, Jos Backus wrote: > > On Mon, Sep 15, 2003 at 10:38:28PM -0700, Jos Backus wrote: > > > On Fri, Sep 12, 2003 at 08:45:37PM +0200, Bernd Walter wrote: > > > > Sounds like Int routing got wrong results. > > > > Check if disabling helps you: > > > > --- sys/dev/pci/pci.c 22 Aug 2003 03:11:53 -0000 1.226 > > > > +++ sys/dev/pci/pci.c 11 Sep 2003 19:01:56 -0000 > > > > @@ -800,7 +800,7 @@ > > > > } > > > > > > > > if (cfg->intpin > 0 && PCI_INTERRUPT_VALID(cfg->intline)) { > > > > -#if defined(__ia64__) || (defined(__i386__) && !defined(SMP)) > > > > +#if defined(__ia64__) || (defined(__noi386__) && !defined(SMP)) > > > > /* > > > > * Try to re-route interrupts. Sometimes the BIOS or > > > > * firmware may leave bogus values in these registers. > > Any plans to commit this? Uh, I should sure hope not. Disabling interrupt routing globally is not the right fix. Finding out what's wrong on your mobo is. -Nate From owner-freebsd-scsi@FreeBSD.ORG Sat Sep 20 21:39:06 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E203216A4B3; Sat, 20 Sep 2003 21:39:06 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAD8343FAF; Sat, 20 Sep 2003 21:38:59 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.9/8.12.5) with ESMTP id h8L4cp64022873; Sat, 20 Sep 2003 22:38:51 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id h8L4cp2v022872; Sat, 20 Sep 2003 22:38:51 -0600 (MDT) (envelope-from ken) Date: Sat, 20 Sep 2003 22:38:51 -0600 From: "Kenneth D. Merry" To: Thomas Quinot Message-ID: <20030921043851.GA22790@panzer.kdm.org> References: <20030919173636.GA867@melusine.cuivre.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030919173636.GA867@melusine.cuivre.fr.eu.org> User-Agent: Mutt/1.4.1i cc: freebsd-scsi@FreeBSD.ORG Subject: Re: cam_periph recovered sense handling X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2003 04:39:07 -0000 On Fri, Sep 19, 2003 at 19:36:36 +0200, Thomas Quinot wrote: > When the cam_periph layer automagically recovers sense data by issuing a > REQUEST SENSE command, it must set the CAM_AUTOSNS_VALID bit in the > original CCB's status. Currently, it errouneously sets that bit in the > flags field instead. This causes an endless loop of REQUEST SENSE > actions, eventually leading to memory exhaustion. The following patch > resolves the problem for me; please review. > > Thomas. > > Index: cam_periph.c > =================================================================== > RCS file: /home/ncvs/src/sys/cam/cam_periph.c,v > retrieving revision 1.52 > diff -u -r1.52 cam_periph.c > --- cam_periph.c 10 Sep 2003 18:23:43 -0000 1.52 > +++ cam_periph.c 19 Sep 2003 17:25:58 -0000 > @@ -975,7 +975,7 @@ > sense_key = saved_ccb->csio.sense_data.flags; > sense_key &= SSD_KEY; > if (sense_key != SSD_KEY_NO_SENSE) { > - saved_ccb->ccb_h.flags |= > + saved_ccb->ccb_h.status |= > CAM_AUTOSNS_VALID; > xpt_print_path(saved_ccb->ccb_h.path); > printf("Recovered Sense\n"); > > -- Looks like the correct fix, good catch. Feel free to commit it. Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Sat Sep 20 21:39:50 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0DD0716A4B3; Sat, 20 Sep 2003 21:39:50 -0700 (PDT) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id BA23A43FE3; Sat, 20 Sep 2003 21:39:46 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.9/8.12.5) with ESMTP id h8L4dg64022900; Sat, 20 Sep 2003 22:39:42 -0600 (MDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.9/8.12.5/Submit) id h8L4dgsU022899; Sat, 20 Sep 2003 22:39:42 -0600 (MDT) (envelope-from ken) Date: Sat, 20 Sep 2003 22:39:42 -0600 From: "Kenneth D. Merry" To: Thomas Quinot Message-ID: <20030921043942.GB22790@panzer.kdm.org> References: <20030920110131.GA41062@melusine.cuivre.fr.eu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030920110131.GA41062@melusine.cuivre.fr.eu.org> User-Agent: Mutt/1.4.1i cc: freebsd-scsi@FreeBSD.ORG cc: gibbs@FreeBSD.ORG Subject: Re: Missing length specification in scsi_request_sense X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2003 04:39:50 -0000 On Sat, Sep 20, 2003 at 13:01:31 +0200, Thomas Quinot wrote: > The CDB built by scsi_request_sense always has a zero length indication, > preventing correct transfer of sense data during recovery action by > cam_periph. The following change resolves the problem, please review. > > Thomas. > > Index: scsi/scsi_all.c > =================================================================== > RCS file: /home/ncvs/src/sys/cam/scsi/scsi_all.c,v > retrieving revision 1.42 > diff -u -r1.42 scsi_all.c > --- scsi/scsi_all.c 10 Jun 2003 18:14:04 -0000 1.42 > +++ scsi/scsi_all.c 20 Sep 2003 10:53:38 -0000 > @@ -2408,6 +2408,7 @@ > scsi_cmd = (struct scsi_request_sense *)&csio->cdb_io.cdb_bytes; > bzero(scsi_cmd, sizeof(*scsi_cmd)); > scsi_cmd->opcode = REQUEST_SENSE; > + scsi_cmd->length = dxfer_len; > } > > void Looks good, please commit. Ken -- Kenneth Merry ken@kdm.org From owner-freebsd-scsi@FreeBSD.ORG Sat Sep 20 22:32:35 2003 Return-Path: Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4D2E016A4B3 for ; Sat, 20 Sep 2003 22:32:35 -0700 (PDT) Received: from w250.z064001178.sjc-ca.dsl.cnc.net (adsl-66.218.45.239.dslextreme.com [66.218.45.239]) by mx1.FreeBSD.org (Postfix) with SMTP id 16D1943F75 for ; Sat, 20 Sep 2003 22:32:32 -0700 (PDT) (envelope-from jos@catnook.com) Received: (qmail 99779 invoked by uid 1000); 21 Sep 2003 05:32:53 -0000 Date: Sat, 20 Sep 2003 22:32:31 -0700 From: Jos Backus To: freebsd-scsi@freebsd.org Message-ID: <20030921053253.GA98711@lizzy.catnook.com> Mail-Followup-To: freebsd-scsi@freebsd.org References: <20030911165325.GA826@lizzy.catnook.com> <137850000.1063320278@aslan.btc.adaptec.com> <20030912032034.GA826@lizzy.catnook.com> <20030912184536.GM26878@cicely12.cicely.de> <20030916053850.GA1022@lizzy.catnook.com> <20030917043629.GA820@lizzy.catnook.com> <20030920050556.GA49402@lizzy.catnook.com> <20030920203052.Q32361@root.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030920203052.Q32361@root.org> User-Agent: Mutt/1.5.4i Subject: Re: "Timedout SCB already complete. Interrupts may not be functioning." X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: jos@catnook.com List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 21 Sep 2003 05:32:35 -0000 On Sat, Sep 20, 2003 at 08:31:37PM -0700, Nate Lawson wrote: > On Fri, 19 Sep 2003, Jos Backus wrote: [patch snipped] > > Any plans to commit this? > > Uh, I should sure hope not. Disabling interrupt routing globally is not > the right fix. Finding out what's wrong on your mobo is. > > -Nate Okay. How do I go about doing this? It's a standard Asus CUBX motherboard running the latest BIOS revision. -- Jos Backus _/ _/_/_/ Sunnyvale, CA _/ _/ _/ _/ _/_/_/ _/ _/ _/ _/ jos at catnook.com _/_/ _/_/_/ require 'std/disclaimer'