From owner-freebsd-scsi Sun Dec 26 4:34:20 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from piper.kspu.kr.ua (piper.kspu.kr.ua [195.5.1.122]) by hub.freebsd.org (Postfix) with ESMTP id 6613114CA4 for ; Sun, 26 Dec 1999 04:34:12 -0800 (PST) (envelope-from john@piper.kspu.kr.ua) Received: (from john@localhost) by piper.kspu.kr.ua (8.9.3/8.9.3) id OAA26542 for freebsd-scsi@FreeBSD.ORG; Sun, 26 Dec 1999 14:34:09 +0200 (EET) Date: Sun, 26 Dec 1999 14:34:08 +0200 From: John Savitsky To: freebsd-scsi@FreeBSD.ORG Subject: Re: SCB 0x34 timed out in dataout phase, Again (sorry) Message-ID: <19991226143408.A26528@kspu.kr.ua> Mail-Followup-To: freebsd-scsi@FreeBSD.ORG References: <19991221112014.A5291@kspu.kr.ua> <19991225164151.A24504@kspu.kr.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991225164151.A24504@kspu.kr.ua>; from john@kspu.kr.ua on Sat, Dec 25, 1999 at 04:41:51PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm sorry for the previous posting. Yesterday I cold-reboot the machine and saw that I missed one word from the detected hardware. :-( It is a Ultra2-SE devices (showed by Adaptec SCSI-Setup). Also yesterday I upgraded 3.2-RELEASE to 3.4-STABLE. The nightly backup finished with no errors. Will see... -- Sincerely yours, John Savitsky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 27 3:10:34 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns1.aha.ru (ns1.aha.ru [195.2.80.142]) by hub.freebsd.org (Postfix) with ESMTP id 1B75814EEF for ; Mon, 27 Dec 1999 03:10:28 -0800 (PST) (envelope-from abb@zenon.net) Received: from pb.hq.zenon.net (pb.zenon.net [195.2.64.18]) by ns1.aha.ru (8.9.3/8.9.3/aha-r/0.04B) with ESMTP id OAA00208; Mon, 27 Dec 1999 14:10:23 +0300 (MSK) Received: from zenon.net (abb.hq.zenon.net [192.168.9.25]) by pb.hq.zenon.net (8.9.3/8.9.3) with ESMTP id OAA89852; Mon, 27 Dec 1999 14:10:22 +0300 (MSK) Message-ID: <386749C0.34EBADE5@zenon.net> Date: Mon, 27 Dec 1999 14:13:04 +0300 From: Alexander Bezroutchko X-Mailer: Mozilla 4.6 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: Tom Cc: scsi@freebsd.org Subject: Re: IFT3102 and FreeBSD 3.4-STABLE troubles References: Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tom wrote: > Well, I'm testing a single IFT-3102U2G on a dual-PIII under 3.4 stable. > I'm assuming that the take-over by the redundant controller is similar > in appearance to the host, as resetting a controller. Yes, but take-over takes 4 sec, and resetting takes about 1 minute. > I've done a few resets of the IFT controller until full load (three > instances of postmark). FreeBSD paused, then printed a bunch of errors > and then continued. I have had a incident where FreeBSD just hung after > resetting the controller. I couldn't reproduce it though. I've done a lot of resets and all of them lead to crash or inoperability ;(. For example, take a look on following console snapshots: Example N1: ~~~~~~~~~~~ Host has no local storage, ahc0 connected to IFT (swap resides on da0b): -- before controller reset --- box2# dmesg ... ahc0: rev 0x00 int a irq 19 on pci0.12.0 ahc0: aic7896/97 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 19 on pci0.12.1 ahc1: aic7896/97 Wide Channel B, SCSI Id=7, 16/255 SCBs ... SMP: AP CPU #1 Launched! da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 5120MB (10485760 512 byte sectors: 255H 63S/T 652C) da1 at ahc0 bus 0 target 0 lun 1 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 10000MB (20480000 512 byte sectors: 255H 63S/T 1274C) da2 at ahc0 bus 0 target 0 lun 2 da2: Fixed Direct Access SCSI-2 device da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da2: 5120MB (10485760 512 byte sectors: 255H 63S/T 652C) da3 at ahc0 bus 0 target 0 lun 3 da3: Fixed Direct Access SCSI-2 device da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da3: 10000MB (20480000 512 byte sectors: 255H 63S/T 1274C) changing root device to da0s1a ... box2# mount /dev/da0s1a on / (ufs, local, writes: sync 7 async 62) /dev/da0s1e on /var (ufs, local, writes: sync 100 async 150) /dev/da1a on /usr/obj (ufs, local, writes: sync 2 async 0) procfs on /proc (procfs, local) --- then, I run 'find' and reset controller --- box2# find / > /dev/null (da0:ahc0:0:0:0): Invalidating pack (da0:ahc0:0:0:0): Invalidating pack Dec 27 12:48:03 box2 /kernel: (da0:ahc0:0:0:0): Invalidating pack Dec 27 12:48:03 box2 /kernel: (da0:ahc0:0:0:0): Invalidating pack Dec 27 12:48:35 box2 /kernel: (da0:ahc0:0:0:0): Invalidating pack Dec 27 12:48:35 box2 /kernel: (da0:ahc0:0:0:0): Invalidating pack zsh: device not configured: /var/mail/root box2# --- here controller is up, but freebsd is broken box2# ls spec_getpages: I/O read failure: (error code=6) size: 65536, resid: 65536, a_count: 65536, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 16 spec_getpages: I/O read failure: (error code=6) size: 65536, resid: 65536, a_count: 65536, valid: 0x0 nread: 0, reqpage: 0, pindex: 0, pcount: 16 Dec 27 12:51:54 box2 /kernel: spec_getpages: I/O read failure: (error code=6) zsh: device not configured: ls Dec 27 12:51:54 box2 /kernel: spec_getpages: I/O read failure: (error code=6) Dec 27 12:51:54 box2 /kernel: size: 65536, resid: 65536, a_count: 65536, valid: 0x0 Dec 27 12:51:54 box2 /kernel: size: 65536, resid: 65536, a_count: 65536, valid: 0x0 Dec 27 12:51:54 box2 /kernel: nread: 0, reqpage: 0, pindex: 0, pcount: 16 zsh: device not configured: /var/mail/root Dec 27 12:51:54 box2 /kernel: nread: 0, reqpage: 0, pindex: 0, pcount: 16 Dec 27 12:51:54 box2 /kernel: spec_getpages: I/O read failure: (error code=6) Dec 27 12:51:54 box2 /kernel: spec_getpages: I/O read failure: (error code=6) Dec 27 12:51:54 box2 /kernel: size: 65536, resid: 65536, a_count: 65536, valid: 0x0 Dec 27 12:51:54 box2 /kernel: size: 65536, resid: 65536, a_count: 65536, valid: 0x0 Dec 27 12:51:54 box2 /kernel: nread: 0, reqpage: 0, pindex: 0, pcount: 16 Dec 27 12:51:54 box2 /kernel: nread: 0, reqpage: 0, pindex: 0, pcount: 16 box2# ---------------------------------------------------------------- Example N2: ~~~~~~~~~~~ Host has one local disk (da4) connected to ahc1, ach0 connected to IFT (swap resides on da4b). --- before controller reset --- box1# dmesg ... ahc0: rev 0x00 int a irq 19 on pci0.12.0 ahc0: aic7896/97 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: rev 0x00 int a irq 19 on pci0.12.1 ahc1: aic7896/97 Wide Channel B, SCSI Id=7, 16/255 SCBs SMP: AP CPU #1 Launched! ... da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 5120MB (10485760 512 byte sectors: 255H 63S/T 652C) da4 at ahc1 bus 0 target 0 lun 0 da4: Fixed Direct Access SCSI-2 device da4: 10.000MB/s transfers (5.000MHz, offset 15, 16bit), Tagged Queueing Enabled da4: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) da1 at ahc0 bus 0 target 0 lun 1 da1: Fixed Direct Access SCSI-2 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 10000MB (20480000 512 byte sectors: 255H 63S/T 1274C) da2 at ahc0 bus 0 target 0 lun 2 da2: Fixed Direct Access SCSI-2 device da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da2: 5120MB (10485760 512 byte sectors: 255H 63S/T 652C) da3 at ahc0 bus 0 target 0 lun 3 da3: Fixed Direct Access SCSI-2 device da3: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da3: 10000MB (20480000 512 byte sectors: 255H 63S/T 1274C) changing root device to da4s4a changing root device to da4a ... box1# mount /dev/da4a on / (ufs, local, writes: sync 135 async 294) procfs on /proc (procfs, local) /dev/da0a on /mnt (ufs, local, writes: sync 2 async 1) ... --- then I run 'find' and reset controller --- box1# find /mnt -ls > /dev/null (da0:ahc0:0:0:0): Invalidating pack Dec 27 13:37:21 box1 /kernel: (da0:ahc0:0:0:0): Invalidating pack Dec 27 13:37:21 box1 /kernel: (da0:ahc0:0:0:0): Invalidating pack (da0:ahc0:0:0:0): Invalidating pack (da0:ahc0:0:0:0): Invalidating pack (da0:ahc0:0:0:0): Invalidating pack (da0:ahc0:0:0:0): Invalidating pack Dec 27 13:37:33 box1 last message repeated 4 times Dec 27 13:37:33 box1 last message repeated 4 times find: /mnt/usr/home: Device not configured find: /mnt/usr/obj: Device not configured find: /mnt/usr/games: Device not configured find: /mnt/usr/ports: Device not configured find: sys: Device not configured find: home: Device not configured box1# --- here controller is up, but freebsd is broken box1# ls -la /mnt box1# umount /mnt umount: unmount of /mnt failed: Device not configured box1# ---------------------------------------------------------------- Unfortunately, I have never seen correct behaviour of FreeBSD after controller reset occured during any activity on filesystem mounted from IFT. I have seen about 20 messages related to IFT scsi-to-scsi controllers in this list. Did anybody investigate behaviour of FreeBSD during controller take-over and reset ? SY, Alexander Bezroutchko To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 27 14:35:11 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from slarti.muc.de (slarti.muc.de [193.149.48.10]) by hub.freebsd.org (Postfix) with SMTP id 621C6152D4 for ; Mon, 27 Dec 1999 14:35:08 -0800 (PST) (envelope-from jhs@jhs.muc.de) Received: (qmail 13437 invoked from network); 27 Dec 1999 22:32:48 -0000 Received: from jhs.muc.de (193.149.49.84) by slarti.muc.de with SMTP; 27 Dec 1999 22:32:48 -0000 Received: from wall.jhs.no_domain (localhost [127.0.0.1]) by jhs.muc.de (8.9.3/8.9.3) with ESMTP id CAA10430; Mon, 27 Dec 1999 02:36:20 GMT (envelope-from jhs@wall.jhs.no_domain) Message-Id: <199912270236.CAA10430@jhs.muc.de> To: John Savitsky Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCB 0x34 timed out in dataout phase, Again (sorry) From: "Julian Stacey" Reply-To: "Julian Stacey" X-Net: jhs@muc.de www.jhs.muc.de www.freebsd.org/~jhs/ bim.bsn.com/~jhs/ Organization: Vector Systems Ltd - Unix & Internet consultancy In-reply-to: Your message of "Sun, 26 Dec 1999 14:34:08 +0200." <19991226143408.A26528@kspu.kr.ua> Date: Mon, 27 Dec 1999 03:36:18 +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > From: John Savitsky > Date: Sun, 26 Dec 1999 14:34:08 +0200 > Message-id: <19991226143408.A26528@kspu.kr.ua> > Also yesterday I upgraded 3.2-RELEASE to 3.4-STABLE. The nightly 3.4-STABLE does not exist, (nor 3.3-STABLE etc). 3-STABLE is a moving target, Not tagged as 3.4, 3.3, etc. /usr/cvs/src/Makefile,v has these (& other) tags: RELENG_3_4_0_RELEASE, RELENG_3, RELENG_2_2 A correct precise statement would be: I upgraded 3.2-RELEASE to a [post 3.4] [3-]STABLE [with a CVS checkout date (or cvsup date, or stable mail list ctm feed) of ] I mention this non existence of 3.4-STABLE because while some/most of us know what you really mean, newcomers may not, & the more often we use false nomenclature the greater the confusion (at least to newbies :-) Julian Julian H. Stacey http://www.freebsd.org/~jhs/ http://www.jhs.muc.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 27 16:23: 1 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from reliam.teaser.fr (reliam.teaser.fr [194.51.80.12]) by hub.freebsd.org (Postfix) with ESMTP id E90621529E; Mon, 27 Dec 1999 16:22:51 -0800 (PST) (envelope-from hpc@teaser.fr) Received: from asus.teaser.fr (dip217.teaser.fr [194.51.100.217]) by reliam.teaser.fr (8.9.3/8.9.3) with ESMTP id BAA23933; Tue, 28 Dec 1999 01:22:34 +0100 (MET) Received: from (hpc@localhost) by asus.teaser.fr (8.9.3/jtpda-5.3.1) id BAA00788 ; Tue, 28 Dec 1999 01:19:22 +0100 (CET) Date: Tue, 28 Dec 1999 01:19:22 +0100 From: Charles Henri-Pierre To: freebsd-questions@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Scsi ava 1505 adaptec card for an scsi scanner Message-ID: <19991228011921.A741@asus.teaser.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Mailer: Mutt 0.95.6i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I want to use this card with an scsi scanner. FreeBSD 3.4 seem recognize it, I get this messages during the beginning of the boot : aic0 at 0x340-0x350f irq 9 on isa aic0: aic6360, dma, disconnected, parity check But after, the system hang after the message : Waiting 2 sec for SCSI to settle and I get this message : (probe15:(aic0:0:0:0):ccb 0xc0865000 timed out, phase 0x0, state 1 Any idea ? BTW : Is there a way to store the boot message if the boot fail ? Thanks H-P -- % Henri-Pierre Charles % 80, avenue des États Unis 78000 Versailles % Tél : 01 39 20 02 41 Mél : hpcharles@teaser.fr To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 27 16:25:51 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id F2A9914FBD for ; Mon, 27 Dec 1999 16:25:48 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id RAA87287; Mon, 27 Dec 1999 17:24:58 -0700 (MST) (envelope-from ken) Date: Mon, 27 Dec 1999 17:24:58 -0700 From: "Kenneth D. Merry" To: John Savitsky Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCB 0x34 timed out in dataout phase, Again (sorry) Message-ID: <19991227172458.A87258@panzer.kdm.org> References: <19991221112014.A5291@kspu.kr.ua> <19991225164151.A24504@kspu.kr.ua> <19991226143408.A26528@kspu.kr.ua> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991226143408.A26528@kspu.kr.ua>; from john@kspu.kr.ua on Sun, Dec 26, 1999 at 02:34:08PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Sun, Dec 26, 1999 at 14:34:08 +0200, John Savitsky wrote: > > I'm sorry for the previous posting. Yesterday I cold-reboot the > machine and saw that I missed one word from the detected hardware. > :-( It is a Ultra2-SE devices (showed by Adaptec SCSI-Setup). > > Also yesterday I upgraded 3.2-RELEASE to 3.4-STABLE. The nightly > backup finished with no errors. Will see... It could be that your problem was that you were running 3.2. There is a bug in the 7890 that Justin worked around shortly after 3.3 was released. So with 3.4, you've got the fix. Anyway, if you continue to have problems, send mail to the list. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 27 17:54:39 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from bigphred.greycat.com (bigphred.greycat.com [207.173.133.2]) by hub.freebsd.org (Postfix) with ESMTP id A244A14EEF for ; Mon, 27 Dec 1999 17:54:36 -0800 (PST) (envelope-from dann@bigphred.greycat.com) Received: (from dann@localhost) by bigphred.greycat.com (8.9.3/8.9.3) id RAA17730; Mon, 27 Dec 1999 17:55:09 -0800 (PST) (envelope-from dann) Date: Mon, 27 Dec 1999 17:55:09 -0800 From: Dann Lunsford To: Julian Stacey Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCB 0x34 timed out in dataout phase, Again (sorry) Message-ID: <19991227175509.A17622@greycat.com> References: <19991226143408.A26528@kspu.kr.ua> <199912270236.CAA10430@jhs.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <199912270236.CAA10430@jhs.muc.de> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Dec 27, 1999 at 03:36:18AM +0100, Julian Stacey wrote: > 3.4-STABLE does not exist, (nor 3.3-STABLE etc). 3-STABLE is a moving target, > Not tagged as 3.4, 3.3, etc. /usr/cvs/src/Makefile,v has these (& other) tags: > RELENG_3_4_0_RELEASE, RELENG_3, RELENG_2_2 > A correct precise statement would be: > I upgraded 3.2-RELEASE to a [post 3.4] [3-]STABLE > [with a CVS checkout date (or cvsup date, or stable mail list ctm feed) > of ] > I mention this non existence of 3.4-STABLE because while some/most of us know > what you really mean, newcomers may not, & the more often we use false > nomenclature the greater the confusion (at least to newbies :-) $ uname -a FreeBSD bigphred.greycat.com 3.4-STABLE FreeBSD 3.4-STABLE #0: Mon Dec 20 18:16:43 PST 1999 root@bigphred.greycat.com:/usr/src/sys/compile/PHRED i386 $ Funny, I seem to see *two* occurrences of the non-existant 3.4-STABLE there. Obviously, I need to get my glasses checked... -- Dann Lunsford The only thing necessary for the triumph of evil dann@greycat.com is that men of good will do nothing. -- Cicero To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 27 21:13:24 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (Postfix) with ESMTP id E6E0214E6A for ; Mon, 27 Dec 1999 21:13:20 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom (helo=localhost) by misery.sdf.com with local-esmtp (Exim 2.12 #1) id 122owV-0001va-00; Mon, 27 Dec 1999 21:13:07 -0800 Date: Mon, 27 Dec 1999 21:13:07 -0800 (PST) From: Tom To: Alexander Bezroutchko Cc: scsi@freebsd.org Subject: Re: IFT3102 and FreeBSD 3.4-STABLE troubles In-Reply-To: <386749C0.34EBADE5@zenon.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 27 Dec 1999, Alexander Bezroutchko wrote: > Tom wrote: > > > Well, I'm testing a single IFT-3102U2G on a dual-PIII under 3.4 stable. > > I'm assuming that the take-over by the redundant controller is similar > > in appearance to the host, as resetting a controller. > > Yes, but take-over takes 4 sec, and resetting takes about 1 minute. Well, when doing a controller reset via the terminal interface, I find the controller is back up in about 20 to 30 seconds. Longer if it needs to verify dirty buffers. ... > Unfortunately, I have never seen correct behaviour of FreeBSD after > controller reset occured during any activity on filesystem mounted from IFT. I've done this a few times, and it just works. I've had a few silent hangs, but these very unusual. For instance, once when upgrading firmware during activity, FreeBSD never recovered and never printed any errors. I wouldn't recomend upgrading controller firmware on active system anyway. I find the "invalidating pack" messages that you get interesting. I've never seen them before. It is almost as if the IFT is telling FreeBSD that the disk no longer exists. > I have seen about 20 messages related to IFT scsi-to-scsi controllers in > this list. Did anybody investigate behaviour of FreeBSD during controller > take-over and reset ? > > SY, > Alexander Bezroutchko Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 27 21:57:35 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from smtprch1.nortel.com (smtprch1.nortelnetworks.com [192.135.215.14]) by hub.freebsd.org (Postfix) with ESMTP id 0886F15010 for ; Mon, 27 Dec 1999 21:57:30 -0800 (PST) (envelope-from atrens@nortelnetworks.com) Received: from zmers013 by smtprch1.nortel.com; Mon, 27 Dec 1999 23:57:20 -0600 Received: from hcarp00g.ca.nortel.com by zmers013; Tue, 28 Dec 1999 00:57:11 -0500 Received: from hcarp00g.ca.nortel.com (hcarp00g.ca.nortel.com [47.196.31.114]) by hcarp00g.ca.nortel.com (8.9.3/8.7.3) with ESMTP id BAA50046 for ; Tue, 28 Dec 1999 01:04:49 -0500 (EST) Date: Tue, 28 Dec 1999 01:04:48 -0500 (EST) From: "Andrew Atrens" X-Sender: atrens@hcarp00g.ca.nortel.com Reply-To: "Andrew Atrens" To: scsi@freebsd.org Subject: ava 2906 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Is this puppy supported by `ahc' in -current ? I'm not subscribed to the list so please email me directly. Cheers, Andrew. -- +-- | Andrew Atrens Nortel Networks, Ottawa, Canada. | | All opinions expressed are my own, not those of any employer. | --+ Heller's Law: The first myth of management is that it exists. Johnson's Corollary: Nobody really knows what is going on anywhere within the organization. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 27 22:15:32 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from piper.kspu.kr.ua (piper.kspu.kr.ua [195.5.1.122]) by hub.freebsd.org (Postfix) with ESMTP id BD81E14A1A for ; Mon, 27 Dec 1999 22:15:28 -0800 (PST) (envelope-from john@piper.kspu.kr.ua) Received: (from john@localhost) by piper.kspu.kr.ua (8.9.3/8.9.3) id IAA02484 for freebsd-scsi@FreeBSD.ORG; Tue, 28 Dec 1999 08:15:25 +0200 (EET) Date: Tue, 28 Dec 1999 08:15:25 +0200 From: John Savitsky To: freebsd-scsi@FreeBSD.ORG Subject: Re: SCB 0x34 timed out in dataout phase, Again (sorry) Message-ID: <19991228081525.A2456@kspu.kr.ua> Mail-Followup-To: freebsd-scsi@FreeBSD.ORG References: <19991226143408.A26528@kspu.kr.ua> <199912270236.CAA10430@jhs.muc.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <199912270236.CAA10430@jhs.muc.de>; from jhs@jhs.muc.de on Mon, Dec 27, 1999 at 03:36:18AM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Dec 27, 1999 at 03:36:18AM +0100, Julian Stacey wrote: > > Message-id: <19991226143408.A26528@kspu.kr.ua> > > > Also yesterday I upgraded 3.2-RELEASE to 3.4-STABLE. The nightly [snip] > 3.4-STABLE does not exist, (nor 3.3-STABLE etc). 3-STABLE is a moving target, [snip] > I mention this non existence of 3.4-STABLE because while some/most of us know > what you really mean, newcomers may not, & the more often we use false > nomenclature the greater the confusion (at least to newbies :-) Thanks tor the explanations. ;-) > Julian > Julian H. Stacey http://www.freebsd.org/~jhs/ http://www.jhs.muc.de -- Sincerely yours, John Savitsky DE UR5VIB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Dec 27 22:24: 9 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from piper.kspu.kr.ua (piper.kspu.kr.ua [195.5.1.122]) by hub.freebsd.org (Postfix) with ESMTP id 8A66A153EB for ; Mon, 27 Dec 1999 22:24:05 -0800 (PST) (envelope-from john@piper.kspu.kr.ua) Received: (from john@localhost) by piper.kspu.kr.ua (8.9.3/8.9.3) id IAA02517 for freebsd-scsi@FreeBSD.ORG; Tue, 28 Dec 1999 08:24:03 +0200 (EET) Date: Tue, 28 Dec 1999 08:24:03 +0200 From: John Savitsky To: freebsd-scsi@FreeBSD.ORG Subject: Re: SCB 0x34 timed out in dataout phase, Again (sorry) Message-ID: <19991228082403.B2456@kspu.kr.ua> Mail-Followup-To: freebsd-scsi@FreeBSD.ORG References: <19991221112014.A5291@kspu.kr.ua> <19991225164151.A24504@kspu.kr.ua> <19991226143408.A26528@kspu.kr.ua> <19991227172458.A87258@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <19991227172458.A87258@panzer.kdm.org>; from ken@kdm.org on Mon, Dec 27, 1999 at 05:24:58PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Dec 27, 1999 at 05:24:58PM -0700, Kenneth D. Merry wrote: > On Sun, Dec 26, 1999 at 14:34:08 +0200, John Savitsky wrote: > > > > Also yesterday I upgraded 3.2-RELEASE to 3.4-STABLE. The nightly > > backup finished with no errors. Will see... > > It could be that your problem was that you were running 3.2. There is a > bug in the 7890 that Justin worked around shortly after 3.3 was released. > So with 3.4, you've got the fix. > > Anyway, if you continue to have problems, send mail to the list. Thanks God and Justin, I have no problems after upgrading. All the nightly backups finished successfully. > Ken > -- > Kenneth Merry > ken@kdm.org -- Sincerely yours, John Savitsky DE UR5VIB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 28 3:12:34 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from atlas.rccn.net (atlas.rccn.net [193.136.7.1]) by hub.freebsd.org (Postfix) with SMTP id 1C73D14A0B for ; Tue, 28 Dec 1999 03:12:28 -0800 (PST) (envelope-from jpsp@rccn.net) Received: (qmail 32109 invoked by uid 1021); 28 Dec 1999 11:12:12 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 28 Dec 1999 11:12:12 -0000 Date: Tue, 28 Dec 1999 11:12:12 +0000 (WET) From: Joao Pagaime To: freebsd-scsi@FreeBSD.ORG Cc: angelo@fccn.pt Subject: DAC960 Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=iso-8859-1 Content-Transfer-Encoding: 8BIT Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all Is there a driver for Intel's DAC960 RAID controller? Beta ? Thnks, Joao Pagaime -- FCCN - Fundação para a Computação Científica Nacional - Tel: +351-218440100 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 28 8:39:25 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (castles508.castles.com [208.214.165.72]) by hub.freebsd.org (Postfix) with ESMTP id 462C41551A for ; Tue, 28 Dec 1999 08:39:12 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id IAA03132; Tue, 28 Dec 1999 08:43:43 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <199912281643.IAA03132@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Joao Pagaime Cc: freebsd-scsi@FreeBSD.ORG, angelo@fccn.pt Subject: Re: DAC960 In-reply-to: Your message of "Tue, 28 Dec 1999 11:12:12 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Tue, 28 Dec 1999 08:43:43 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > = > Hello all > = > Is there a driver for Intel's DAC960 RAID controller? > Beta ? The DAC960 is made by Mylex, not Intel, and yes. The DAC960 family are = supported in the 4.x branch, and you can get a driver for the 3.x branch = at http://www.freebsd.org/~msmith/RAID/mylex. It's always worth looking at the BSD Driver Database at = http://www.posi.net/freebsd/drivers/ before asking questions like this. -- = \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 28 14:41: 0 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from ns1.nserver.net (nina.herculeshosting.com [209.69.255.64]) by hub.freebsd.org (Postfix) with ESMTP id 9D43A14A2E for ; Tue, 28 Dec 1999 14:40:56 -0800 (PST) (envelope-from zach@unsecure.net) Received: from nina.herculeshosting.com (foobar@nina.herculeshosting.com [209.69.255.64]) by ns1.nserver.net (8.9.3/8.9.3) with ESMTP id WAA03331 for ; Sun, 26 Dec 1999 22:51:31 -0500 Date: Sun, 26 Dec 1999 22:51:31 -0500 (EST) From: "Zachary M. Smith" X-Sender: zach@ns1.nserver.net To: freebsd-scsi@freebsd.org Subject: IBM DNES-309170 LVD Problems Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just purchased three IBM DNES-309170 drives and planned on using Vinum to configure them in a RAID 0 and/or 5 setup. I have read a bit a vinum and now I am trying to get the drives ready to be used in a few simple vinum tests. however, i am running into some problems that i am hoping you folks can help me with. 1. I can create FDISK partitions on the disk just fine. Once I get an FDISK partition setup, I try to use disklabel to change the partition type to vinum, but when i try to write the changes to the label, disklabel tells me "operation not supported by device" 2. I have also tried to create slices in my FDISK partition just to test the drive, but I am unable to create slices. I get the error "Device rda0s1c: name slot allocation failed (Errno=17)" Any ideas? Bellow I have included output from dmesg, fdisk, and disklabel for reference. Thanks in advance for ANY help! :) dmesg shows me this: ---------------------- (first finds my controller) ahc1: rev 0x00 int a irq 16 on pci0.19.0 ahc1: aic7890/91 Wide Channel A, SCSI Id=5, 16/255 SCBs (then finds my drives) da0 at ahc1 bus 0 target 2 lun 0 da0: Fixed Direct Access SCSI-3 device da0: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da0: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) da2 at ahc1 bus 0 target 6 lun 0 da2: Fixed Direct Access SCSI-3 device da2: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da2: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) da1 at ahc1 bus 0 target 4 lun 0 da1: Fixed Direct Access SCSI-3 device da1: 80.000MB/s transfers (40.000MHz, offset 31, 16bit), Tagged Queueing Enabled da1: 8748MB (17916240 512 byte sectors: 255H 63S/T 1115C) ---------------------- and fdisk /dev/da0 shows me this: ---------------------- ******* Working on device /dev/da0 ******* parameters extracted from in-core disklabel are: cylinders=1115 heads=255 sectors/track=63 (16065 blks/cyl) Figures below won't work with BIOS for partitions not in cyl 1 parameters to be used for BIOS calculations are: cylinders=1115 heads=255 sectors/track=63 (16065 blks/cyl) Media sector size is 512 Warning: BIOS sector numbering starts with sector 1 Information from DOS bootblock is: The data for partition 1 is: sysid 165,(FreeBSD/NetBSD/386BSD) start 63, size 6281352 (3067 Meg), flag 80 (active) beg: cyl 0/ sector 1/ head 1; end: cyl 390/ sector 63/ head 254 The data for partition 2 is: The data for partition 3 is: The data for partition 4 is: ---------------------- and disklabel /dev/da0 shows me this: ---------------------- type: SCSI disk: IBM label: DNES-309170W flags: bytes/sector: 512 sectors/track: 63 tracks/cylinder: 255 sectors/cylinder: 16065 cylinders: 1115 sectors/unit: 17916240 rpm: 3600 interleave: 1 trackskew: 0 cylinderskew: 0 headswitch: 0 # milliseconds track-to-track seek: 0 # milliseconds drivedata: 0 8 partitions: # size offset fstype [fsize bsize bps/cpg] ---------------------- I am fairly new to this so hopefully I am just overlooking something obvious that someone could point out to me. :) ANY help would be appreciated. Zach Smith +-------------------+ | UNIX Nerd | | & | | Professional Geek | +-------------------+ zach@unsecure.net http://www.unsecure.net Public Key Available At http://www.keyserver.net EB0C 89F5 697E FDD5 3AD4 2ADE 33A1 5A5E 50B7 1FA0 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 28 16:21: 6 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id B84FF14EE5; Tue, 28 Dec 1999 16:20:57 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA83706; Wed, 29 Dec 1999 10:50:34 +1030 (CST) Date: Wed, 29 Dec 1999 10:50:34 +1030 From: Greg Lehey To: "Zachary M. Smith" Cc: FreeBSD Questions Subject: Re: IBM DNES-309170 LVD Problems Message-ID: <19991229105034.S1316@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [moved to -questions; this isn't SCSI material] On Sunday, 26 December 1999 at 22:51:31 -0500, Zachary M. Smith wrote: > I just purchased three IBM DNES-309170 drives and planned on using Vinum > to configure them in a RAID 0 and/or 5 setup. I have read a bit a vinum > and now I am trying to get the drives ready to be used in a few simple > vinum tests. however, i am running into some problems that i am hoping > you folks can help me with. > > 1. I can create FDISK partitions on the disk just fine. Once I get an > FDISK partition setup, I try to use disklabel to change the partition type > to vinum, but when i try to write the changes to the label, disklabel > tells me "operation not supported by device" From what you show below, you're running disklabel against /dev/da0. This is not correct; you should run it against the raw complete partition /dev/rda0c. The distinction between /dev/da0c and /dev/rda0c will go away in 4.0, but the distinction between /dev/da0c and /dev/da0 remains important. disklabel gives you a shorthand way to do this: 'disklabel da0'. > 2. I have also tried to create slices in my FDISK partition just to test > the drive, but I am unable to create slices. I get the error > "Device rda0s1c: name slot allocation failed (Errno=17)" I haven't seen this one. It's probably a result of earlier errors. Greg -- When replying to this message, please copy the original recipients. For more information, see http://www.lemis.com/questions.html Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 28 16:23:15 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from magnesium.net (toxic.magnesium.net [207.154.84.15]) by hub.freebsd.org (Postfix) with SMTP id 3D882154E6 for ; Tue, 28 Dec 1999 16:23:13 -0800 (PST) (envelope-from unfurl@magnesium.net) Received: (qmail 15733 invoked by uid 1001); 29 Dec 1999 00:23:11 -0000 Date: 28 Dec 1999 16:23:11 -0800 Date: Tue, 28 Dec 1999 16:23:11 -0800 From: Bill Swingle To: scsi@freebsd.org Cc: Mike Smith Subject: Invalidating pack messages Message-ID: <19991228162311.A15296@dub.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre3i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hey all, I've encountered a strange error. I have a quad PII xeon with a built in dual channel adaptec XXXX scsi controller. I have two 8gb IBM drives and two Toshiba cdrom drives hanging off of it. It's running -current from yesterday evening, around 7pm PST. Today I fired up four copies of ripit.pl and let the machine go crazy rippingand encoding mp3's. Out of the blue I got this error, without any previous errors: (pass2:ahc0:0:5:0): READ(10). CDB: 28 0 0 4 4a 70 0 0 a 0 (pass2:ahc0:0:5:0): ILLEGAL REQUEST asc:21,0 (pass2:ahc0:0:5:0): Logical block address out of range #cd/2 invalid sector size 2352 #cd/2 invalid sector size 2352 Then about 10 minutes later with no other errors inbetween, it barfed this several times: (da0:ahc0:0:0:0): Invalidating pack At which point the machine (obviously) became quite unusable. Here are the boot messages from the drives/controller: ahc0: irq 23 at device 9.0 on pci1 ahc0: aic7896/97 Wide Channel A, SCSI Id=7, 16/255 SCBs ahc1: irq 23 at device 9.1 on pci1 ahc1: aic7896/97 Wide Channel B, SCSI Id=7, 16/255 SCBs da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 11.626MB/s transfers (5.813MHz, offset 15, 16bit), Tagged Queueing Enabled da0: 8683MB (17783240 512 byte sectors: 255H 63S/T 1106C) cd0 at ahc0 bus 0 target 5 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 5.813MB/s transfers (5.813MHz, offset 16) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at ahc0 bus 0 target 6 lun 0 cd1: Removable CD-ROM SCSI-2 device cd1: 5.813MB/s transfers (5.813MHz, offset 16) cd1: Attempt to query device size failed: NOT READY, Medium not present da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 11.626MB/s transfers (5.813MHz, offset 15, 16bit), Tagged Queueing Enabled da1: 8715MB (17850000 512 byte sectors: 255H 63S/T 1111C) Thoughts? -Bill -- -=| --- B i l l S w i n g l e --- http://www.dub.net/ -=| unfurl@dub.net - unfurl@freebsd.org - bill@cdrom.com -=| Different all twisty a of in maze are you, passages little To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 29 17: 5:24 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id BE2EB15105 for ; Wed, 29 Dec 1999 17:05:21 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id RAA51781; Wed, 29 Dec 1999 17:55:18 -0700 (MST) Date: Wed, 29 Dec 1999 17:55:18 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199912300055.RAA51781@narnia.plutotech.com> To: "Andrew Atrens" Cc: scsi@FreeBSD.org Subject: Re: ava 2906 X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > > Is this puppy supported by `ahc' in -current ? > > I'm not subscribed to the list so please email me directly. The driver does not have an entry for that card, but it should be caught by one of the generic entries. If it doesn't work for you, I should be able to get you a patch for it as soon as you can supply the PCI vendor/device/subvendor/subdevice ids from a boot -v. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message