From owner-freebsd-scsi Sun Aug 9 11:47:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA09516 for freebsd-scsi-outgoing; Sun, 9 Aug 1998 11:47:18 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from bryggen.bgnett.no (bryggen.bgnett.no [194.54.96.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA09508 for ; Sun, 9 Aug 1998 11:47:13 -0700 (PDT) (envelope-from erikhb@bgnett.no) Received: from bgnett.no (ti21a96-0110.dialup.online.no [130.67.198.110]) by bryggen.bgnett.no (8.8.8/8.8.5/brage2.1) with ESMTP id SAA08938 for ; Sun, 9 Aug 1998 18:46:42 GMT Message-ID: <35CDEDB9.650BF26C@bgnett.no> Date: Sun, 09 Aug 1998 20:43:05 +0200 From: "Erik H. Bakke" Organization: Habatech AS X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 3.0CAM-19980712-SNAP i386) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: AHC CAM problems solved Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At least on my machine it is solved. I had trouble big time getting CAM up and running on my computer. I got a lot of error messages during boot. (These messages have been discussed previously on the lists, so I will not repeat them here) My problem was solved by replacing the motherboard/CPU. My previous setup was as follows: Adaptec 2940U2W host adapter Seagate Cheetah ST34502LW U2W drive Seagate Barracuda ST34573LW U2W drive Pioneer DR-U06S CDROM drive Spacewalker.603 MB (AMD 640-based) Cyrix 6x86MX-PR200 CPU (Clocked as 2x66 - PR166) When swapping the MB and CPU for an AOpen AP5T (430TX-based) with a P55C-200MHz the problems disappeared. Just a note to the other people out there with similar problems. Try swapping around a bit with MB and CPU. Maybe it works. --- Erik H. Bakke Habatech AS erikhb@bgnett.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Aug 9 18:36:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25161 for freebsd-scsi-outgoing; Sun, 9 Aug 1998 18:36:40 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nash.pubnix.net (Nash.pubnix.net [192.172.250.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA25156 for ; Sun, 9 Aug 1998 18:36:37 -0700 (PDT) (envelope-from aal@pubnix.net) Received: from pubnix.net (aal1.pubnix.net [199.202.137.130]) by nash.pubnix.net (8.8.7/8.8.7) with ESMTP id VAA27583 for ; Sun, 9 Aug 1998 21:36:12 -0400 (EDT) (envelope-from aal@pubnix.net) Message-ID: <35CE4E8E.F9778F7E@pubnix.net> Date: Sun, 09 Aug 1998 21:36:15 -0400 From: Alain Hebert Organization: PubNIX Montreal, Inc. X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-scsi@FreeBSD.ORG" Subject: Re: Heavy CAM Problems... References: <199808080956.LAA01325@father.ludd.luth.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Rolf Larsson wrote: > > Alain Hebert said something like this: > I'm currently running the ancient 980520-version (which works, although > not as good as I'd want :-) and I tried to install the 0712 Snapshot. > > I'll take a look at the timing values as Justin suggested, but it seems > funny the same error comes up on two such similar configs when upgrading > nothing but the source. Try that too... Justin: Is it possible to get the patch sets you've uploaded to ftp.freebsd.org/pub/FreeBSD/cam between the the 0520 and 0712? The 0520 is showing 407 instructions in the sequencer (I really think that the problem is around the sequencer code...) and I cannot find (in FreeBSD CVS) any revision that create a 407 sequencer code... And the date of rev 1.76 is 1997/09/27 19:37:27?!? Have fun... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 10 01:05:45 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28249 for freebsd-scsi-outgoing; Mon, 10 Aug 1998 01:05:45 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from tata.research.rockwell.cz (tata.research.rockwell.cz [193.85.154.66]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA28241 for ; Mon, 10 Aug 1998 01:05:31 -0700 (PDT) (envelope-from mira@rockwell.cz) Received: from rockwell.cz (aja.research.rockwell.cz [193.85.154.75]) by tata.research.rockwell.cz (8.6.9/8.6.5) with ESMTP id KAA19861 for ; Mon, 10 Aug 1998 10:15:20 +0200 Message-ID: <35CEAC95.4286C0DA@rockwell.cz> Date: Mon, 10 Aug 1998 10:17:25 +0200 From: Miroslav Kes Organization: Rockwell Automation Ltd., Research Center Prague X-Mailer: Mozilla 4.04 [en] (X11; I; FreeBSD 2.2.5-RELEASE i386) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: Re: Heavy CAM Problems... References: <199808080956.LAA01325@father.ludd.luth.se> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Rolf Larsson wrote: > > Alain Hebert said something like this: > > Hi! > > > > I'm using CAM with a ASUS P2B-DS (AIC7890AB/3860) mtb, 1x4.5G Cheetah, > > 1x9G Cheetah and a SCSI-2 Yamaha Writer... > > > [snip] > > > > But 19980712 and 19980716 Snapshot are currently giving me a "Data-path > > parity error at 0x17b". > > FWIW, I am getting exactly the same error, on a very similar setup. > ASUS motherboard with AIC7890AB/3860, 2xPII-400 and 256MB ECC memory, > 1x9G Cheetah (LVD) and (when I get the snapshot to work) a Yamaha SCSI-2 > CD-writer. The system is not overclocked. :- Although I have reported successful use of CAM on a machine with U2W disks couple weeks ago. I have the same problem now. I have Micro-star ATX LX6 Motherboard with Intel 82371AB chipset (Pentium II 266MHz) , PCI Adaptec 2940U2W and Seagate 32272W, 32151N and 2x 39173 LW disks. Even if the only disk left is the 32272W (system disk) I'm getting: "ahc0: brkadrint, Data path Parity Error at seqaddr=0x17e" message during the boot. Sometimes (very rarely) I succeed to boot. The behavior is hard to predict. Originally I thought it had something to do with the SCSI termination, cables too close to the power source unit etc. because it usually stopped working after I put the cover on the machine, put it from the table on the floor etc. The discussion 19980716 versus 980520 snapshot made me to try one experiment. When the 980520 snapshot was released Adrzej Bialecki (hopefully I remember the spelling correctly) announced a boot.flp with 980520 CAM snapshot. Now I downloaded the boot.flp from the 19980716 distribution and tried to boot from both. The 980520 booted without problem but the 19980716 resulted in the error message we were talking about. The only difference is that the seqaddr=0x17d and not the 0x17e as I usually get when booting from hard drive. Mira -- ----------------------------------------------------------- | Miroslav Kes | |---------------------------------------------------------| | Rockwell Automation Ltd. | tel.: (+420) 2 2425 6913 | | Research Center Prague | fax: (+420) 2 250467 | | Americka 22 | e-mail: mira@rockwell.cz | | 120 00 Praha 2 - Vinohrady | | | Czech Republic | | ----------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 10 19:59:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA18839 for freebsd-scsi-outgoing; Mon, 10 Aug 1998 19:59:13 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from thelab.hub.org (gw03.mpoweredpc.net [142.177.184.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA18832 for ; Mon, 10 Aug 1998 19:59:11 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.8) with SMTP id UAA00649 for ; Mon, 10 Aug 1998 20:58:20 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Mon, 10 Aug 1998 20:58:19 -0300 (ADT) From: The Hermit Hacker To: scsi@FreeBSD.ORG Subject: CAM support for NCR controller... 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 essentially useless. When the last snapshot came out (19980716), I went through the trouble of upgrading my server to the latest snapshot, and pulled out the source tree based on that date, so that my /usr/src was in sync. Today, I was just forced to boot my machine using kernel.GENERIC, since booting with my CAM kernel wouldn't work...it failed to "see" one of the drives. My machine looks like (6 SCSI devices on my NCR controller, all internal): Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-19980711-SNAP #0: Sat Jul 11 11:04:24 GMT 1998 jkh@make.ican.net:/usr/src/sys/compile/GENERIC Timecounter "i8254" frequency 1193182 Hz cost 2429 ns CPU: Pentium/P54C (167.05-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x52c Stepping=12 Features=0x1bf real memory = 134217728 (131072K bytes) avail memory = 127664128 (124672K bytes) Probing for devices on PCI bus 0: chip0: rev 0x02 on pci0.0.0 chip1: rev 0x01 on pci0.7.0 ide_pci0: rev 0x00 on pci0.7.1 ncr0: rev 0x02 int a irq 11 on pci0.8.0 ncr0: waiting for scsi devices to settle scbus0 at ncr0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access sd0: 10.0 MB/s (100 ns, offset 8) 2049MB (4197405 512 byte sectors) sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access sd1: 10.0 MB/s (100 ns, offset 8) 1222MB (2503872 512 byte sectors) sd2 at scbus0 target 2 lun 0 sd2: type 0 fixed SCSI 2 sd2: Direct-Access sd2: 10.0 MB/s (100 ns, offset 8) 327MB (670506 512 byte sectors) sd3 at scbus0 target 3 lun 0 sd3: type 0 fixed SCSI 2 sd3: Direct-Access sd3: 10.0 MB/s (100 ns, offset 8) 234MB (479350 512 byte sectors) sd4 at scbus0 target 4 lun 0 sd4: type 0 fixed SCSI 2 sd4: Direct-Access sd4: 10.0 MB/s (100 ns, offset 8) 500MB (1025920 512 byte sectors) sd5 at scbus0 target 5 lun 0 sd5: type 0 fixed SCSI 2 sd5: Direct-Access sd5: 10.0 MB/s (100 ns, offset 8) 1013MB (2074880 512 byte sectors) vx0: <3COM 3C590 Etherlink III PCI> rev 0x00 int a irq 10 on pci0.10.0 utp[*utp*]: disable 'auto select' with DOS util! address 00:20:af:f7:8f:d2 Warning! Defective early revision adapter! vga0: rev 0x00 on pci0.11.0 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x278-0x27f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface lpt1 at 0x278-0x27f on isa lpt1 not probed due to I/O address conflict with lpt0 at 0x278 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 2441MB (4999680 sectors), 4960 cyls, 16 heads, 63 S/T, 512 B/S wdc0: unit 1 (atapi): , removable, dma, iordy wcd0: 687Kb/sec, 240Kb cache, audio play, 2 volume levels, ejectable tray wcd0: 80mm data disc loaded, unlocked npx0 on motherboard npx0: INT 16 interface Intel Pentium F00F detected, installing workaround changing root device to sd0s1a I haven't tried it yet, since I want to rebuild my system without the CAM drivers, but I also have an Yamaha SCSI-CDR that, until I switched the system over to CAM, worked great. After CAM, I'm lucky to write 1 CD. I'm pretty much blaming all of this on the NCR drivers, since I'm running a production server 3 provinces away, with the 19980716 CAM drivers, but with two Adaptec controllers in the machine, and haven't noticed any problems with it. As I've always been, I'm more then willing to test code and new snapshots, but other then previous problem reports sent in (re: COMMAND FAILED errors), I haven't got a clue where to start. Actually, I'm going to leave the system "as is" for the next couple of days, while I await some new hardware to arrive. If someone out there working on the NCR drivers has suggestions on what I can try towards providing more debug information on the problem, towards the betterment of the CAM drivers, please speak up...I provide my system as a test bed. Thanks... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 10 22:40:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA11512 for freebsd-scsi-outgoing; Mon, 10 Aug 1998 22:40:46 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA11505 for ; Mon, 10 Aug 1998 22:40:45 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id XAA00192; Mon, 10 Aug 1998 23:34:36 -0600 (MDT) Date: Mon, 10 Aug 1998 23:34:36 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199808110534.XAA00192@narnia.plutotech.com> To: The Hermit Hacker cc: scsi@FreeBSD.ORG Subject: Re: CAM support for NCR controller... Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Actually, I'm going to leave the system "as is" for the next couple of > days, while I await some new hardware to arrive. If someone out there > working on the NCR drivers has suggestions on what I can try towards > providing more debug information on the problem, towards the betterment of > the CAM drivers, please speak up...I provide my system as a test bed. A "boot -v" dmesg from the CAM system would be a place to start. It would also help if you related the errors that are reported during your failed CD-R burn sessions. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Aug 10 22:50:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA12642 for freebsd-scsi-outgoing; Mon, 10 Aug 1998 22:50:07 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA12621 for ; Mon, 10 Aug 1998 22:50:04 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id XAA00268; Mon, 10 Aug 1998 23:44:03 -0600 (MDT) Date: Mon, 10 Aug 1998 23:44:03 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199808110544.XAA00268@narnia.plutotech.com> To: Alain Hebert cc: scsi@FreeBSD.ORG Subject: Re: Heavy CAM Problems... Newsgroups: pluto.freebsd.scsi In-Reply-To: <199808080956.LAA01325@father.ludd.luth.se> <35CE4E8E.F9778F7E@pubnix.net> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Justin: Is it possible to get the patch sets you've uploaded to > ftp.freebsd.org/pub/FreeBSD/cam between the the 0520 and 0712? > > The 0520 is showing 407 instructions in the sequencer (I really think > that the problem is around the sequencer code...) and I cannot find (in > FreeBSD CVS) any revision that create a 407 sequencer code... And the > date of rev 1.76 is 1997/09/27 19:37:27?!? The sequencer code (and all of the CAM code for that matter) are kept in a private Perforce repository until everything is ready for inclusion in the FreeBSD-current. Here's a patch to revert the only sequencer change that applied to the aic7890. It does touch the other DMA fifo, so perhaps it is indirectly causing this problem. -- Justin ==== //depot/cam/sys/dev/aic7xxx/aic7xxx.seq#44 - /a/perforce/src/sys/dev/aic7xxx/aic7xxx.seq ==== *** /tmp/tmp.259.0 Mon Aug 10 23:40:52 1998 --- /a/perforce/src/sys/dev/aic7xxx/aic7xxx.seq Sat Aug 8 09:54:09 1998 *************** *** 1383,1389 **** if ((ahc->features & AHC_ULTRA2) == 0) { mov NONE, DFDAT; } ! test DFCNTRL, HDMAEN jnz dma_halt; return: ret; --- 1383,1389 ---- if ((ahc->features & AHC_ULTRA2) == 0) { mov NONE, DFDAT; } ! test DFCNTRL, (SCSIEN|SDMAEN|HDMAEN) jnz dma_halt; return: ret; To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 11 01:48:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA00991 for freebsd-scsi-outgoing; Tue, 11 Aug 1998 01:48:43 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from tata.research.rockwell.cz (tata.research.rockwell.cz [193.85.154.66]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id BAA00984 for ; Tue, 11 Aug 1998 01:48:36 -0700 (PDT) (envelope-from mira@rockwell.cz) Received: from rockwell.cz (aja.research.rockwell.cz [193.85.154.75]) by tata.research.rockwell.cz (8.6.9/8.6.5) with ESMTP id KAA16041 for ; Tue, 11 Aug 1998 10:58:41 +0200 Message-ID: <35D00840.4EAA70E@rockwell.cz> Date: Tue, 11 Aug 1998 11:00:48 +0200 From: Miroslav Kes Organization: Rockwell Automation Ltd., Research Center Prague X-Mailer: Mozilla 4.5b1 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: scsi@FreeBSD.ORG Subject: Re: Heavy CAM Problems... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I don't know if it can help to track down the problem but I think nobody mentioned it here so far. I tried to boot with the -v option and following messages appeared before the "Data-path parity error" message arrived. ... Device configuration finished bpf: tun0 attached <- just to be accurate bpf: lo0 attached <- SCSI bus reset delivered. 0 SCBs aborted ahc0: Selection. 1SCBs aborted ahc0: Selection. 1SCBs aborted ... repeated 14 times ahc0: brkadrint, Data path Parity Error at seqaddr=0x17d Mira -- ----------------------------------------------------------- | Miroslav Kes | |---------------------------------------------------------| | Rockwell Automation Ltd. | tel.: (+420) 2 2425 6913 | | Research Center Prague | fax: (+420) 2 250467 | | Americka 22 | e-mail: mira@rockwell.cz | | 120 00 Praha 2 - Vinohrady | | | Czech Republic | | ----------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 11 05:45:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA24982 for freebsd-scsi-outgoing; Tue, 11 Aug 1998 05:45:53 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA24976 for ; Tue, 11 Aug 1998 05:45:48 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id IAA09516; Tue, 11 Aug 1998 08:45:17 -0400 (EDT) Date: Tue, 11 Aug 1998 08:45:17 -0400 (EDT) From: The Hermit Hacker To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG Subject: Re: CAM support for NCR controller... In-Reply-To: <199808110534.XAA00192@narnia.plutotech.com> 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, 10 Aug 1998, Justin T. Gibbs wrote: > > Actually, I'm going to leave the system "as is" for the next couple of > > days, while I await some new hardware to arrive. If someone out there > > working on the NCR drivers has suggestions on what I can try towards > > providing more debug information on the problem, towards the betterment of > > the CAM drivers, please speak up...I provide my system as a test bed. > > A "boot -v" dmesg from the CAM system would be a place to start. It > would also help if you related the errors that are reported during > your failed CD-R burn sessions. Will try both tonight when I get home and let you know the results... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 11 07:20:51 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA05468 for freebsd-scsi-outgoing; Tue, 11 Aug 1998 07:20:51 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nash.pubnix.net (Nash.pubnix.net [192.172.250.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA05463 for ; Tue, 11 Aug 1998 07:20:49 -0700 (PDT) (envelope-from aal@pubnix.net) Received: from pubnix.net (aal.pubnix.net [199.202.137.130] (may be forged)) by nash.pubnix.net (8.8.8/8.8.7) with ESMTP id KAA15668 for ; Tue, 11 Aug 1998 10:20:26 -0400 (EDT) (envelope-from aal@pubnix.net) Message-ID: <35D0532E.701A4B05@pubnix.net> Date: Tue, 11 Aug 1998 10:20:30 -0400 From: Alain Hebert Reply-To: aal@pubnix.net Organization: PubNIX Montreal, Inc. X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-scsi@FreeBSD.ORG" Subject: Re: Heavy CAM Problems... References: <199808110544.XAA00268@narnia.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi! Nope... Didn't change anything... But! I was wondering... Your patch mention that fix should be applied to line 1383 to a 1.77 aic7xxx.seq (right)... 1.77 after the CAM patch has 1455 and the line that match the context of your last mail is located at 1124?!? Maybe you and us are not really synced correctly since the 0712 diffs... If you want you can ship the RCS file of aic7xxx.seq and I'll rollback all revision to find out when it happen... Have fun... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 11 10:11:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA04224 for freebsd-scsi-outgoing; Tue, 11 Aug 1998 10:11:03 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from seera.nttlabs.com (seera.nttlabs.com [204.162.36.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA04219 for ; Tue, 11 Aug 1998 10:11:01 -0700 (PDT) (envelope-from gene@nttlabs.com) Received: from localhost (gene@localhost) by seera.nttlabs.com (8.8.8/8.8.7) with SMTP id KAA12749 for ; Tue, 11 Aug 1998 10:10:36 -0700 (PDT) X-Authentication-Warning: seera.nttlabs.com: gene owned process doing -bs Date: Tue, 11 Aug 1998 10:10:35 -0700 (PDT) From: "Eugene M. Kim" To: FreeBSD SCSI Mailing List Subject: CAM patch won't apply to -current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, Yesterday I decided to try CAM on my -current system. I fetched the CAM patch and tried to apply it, but the it wouldn't patch because the interface to dsopen() in sys/kern/subr_diskslice.c had been changed recently. (dsopen() now expects one more argument.) Apparently the CAM patch would not work until it is also revised accordingly. So my question is: when would the new patch be released? Thank you, Gene To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 11 10:48:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA07426 for freebsd-scsi-outgoing; Tue, 11 Aug 1998 10:48:53 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from hub.org (hub.org [209.47.148.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA07414 for ; Tue, 11 Aug 1998 10:48:45 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by hub.org (8.8.8/8.7.5) with SMTP id NAA19223; Tue, 11 Aug 1998 13:48:06 -0400 (EDT) Date: Tue, 11 Aug 1998 13:48:06 -0400 (EDT) From: The Hermit Hacker To: "Eugene M. Kim" cc: FreeBSD SCSI Mailing List Subject: Re: CAM patch won't apply to -current In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 11 Aug 1998, Eugene M. Kim wrote: > Hello, > > Yesterday I decided to try CAM on my -current system. I fetched the > CAM patch and tried to apply it, but the it wouldn't patch because the > interface to dsopen() in sys/kern/subr_diskslice.c had been changed > recently. (dsopen() now expects one more argument.) > > Apparently the CAM patch would not work until it is also revised > accordingly. So my question is: when would the new patch be released? If you download the CVS repository, and do: cvs checkout -D "07/16/1998 02:00:00 PDT" src That will get you the source tree at the time of hte last patch. Then, once patched, do: script cvs -q update -APd src exit more typescript That will update the source tree to today, saving a screen shot of what has been changed. I can pretty much guarantee that you'll see conflicts though, since there have been alot of changes inthe past few weeks... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 11 11:08:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10282 for freebsd-scsi-outgoing; Tue, 11 Aug 1998 11:08:11 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from seera.nttlabs.com (seera.nttlabs.com [204.162.36.81]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10277 for ; Tue, 11 Aug 1998 11:08:10 -0700 (PDT) (envelope-from gene@nttlabs.com) Received: from localhost (gene@localhost) by seera.nttlabs.com (8.8.8/8.8.7) with SMTP id LAA13113; Tue, 11 Aug 1998 11:07:44 -0700 (PDT) X-Authentication-Warning: seera.nttlabs.com: gene owned process doing -bs Date: Tue, 11 Aug 1998 11:07:43 -0700 (PDT) From: "Eugene M. Kim" To: Alain Hebert cc: FreeBSD SCSI Mailing List Subject: Re: CAM patch won't apply to -current In-Reply-To: <35D086A7.2D8C49D6@pubnix.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 Thank you, I will try it right away! Gene On Tue, 11 Aug 1998, Alain Hebert wrote: | Date: Tue, 11 Aug 1998 14:00:07 -0400 | From: Alain Hebert | Reply-To: ahebert@pubnix.net | To: "Eugene M. Kim" | Subject: Re: CAM patch won't apply to -current | | Eugene M. Kim wrote: | > Yesterday I decided to try CAM on my -current system. I fetched the | > CAM patch and tried to apply it, but it wouldn't patch because the | > interface to dsopen() in sys/kern/subr_diskslice.c had been changed | > recently. (dsopen() now expects one more argument.) | | .-< Add this... (Hope you got fixed font (;-} ) | | | `-------------------------------. | | | V | error = dsopen("da", dev, fmt, 0, &softc->dk_slices, &label, | dastrategy, (ds_setgeom_t *)NULL, | &da_cdevsw, &da_cdevsw); | | | In case you don't it is the "0, " between "fmt," and "&softc" | | Have fun... | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 11 12:12:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA19249 for freebsd-scsi-outgoing; Tue, 11 Aug 1998 12:12:25 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA19243 for ; Tue, 11 Aug 1998 12:12:23 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id NAA06851; Tue, 11 Aug 1998 13:06:21 -0600 (MDT) Date: Tue, 11 Aug 1998 13:06:21 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199808111906.NAA06851@narnia.plutotech.com> To: aal@pubnix.net cc: scsi@FreeBSD.ORG Subject: Re: Heavy CAM Problems... Newsgroups: pluto.freebsd.scsi In-Reply-To: <199808110544.XAA00268@narnia.plutotech.com> <35D0532E.701A4B05@pubnix.net> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <35D0532E.701A4B05@pubnix.net> you wrote: > Hi! > > Nope... Didn't change anything... But! > > I was wondering... Your patch mention that fix should be applied to > line 1383 to a 1.77 aic7xxx.seq (right)... 1.77 after the CAM patch has > 1455 and the line that match the context of your last mail is located at > 1124?!? I have lots of other changes to that file right now, mostly having to do with target mode. Development goes on, you know. > Maybe you and us are not really synced correctly since the 0712 > diffs... If you want you can ship the RCS file of aic7xxx.seq and I'll > rollback all revision to find out when it happen... Perforce uses a combination RCS file/database approach. Shipping you a single file that you can decifer isn't really possible. I looked at all changes to the file and the only other change couldn't have any affect on this problem. It is likely other optimizations in the kernel driver file that have changed the transaction queuing rate and caused the problem to show up. The Adaptec folk seem to feel that this error could only be caused hardware. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 11 17:53:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA12317 for freebsd-scsi-outgoing; Tue, 11 Aug 1998 17:53:47 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA12311 for ; Tue, 11 Aug 1998 17:53:40 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id KAA15303; Wed, 12 Aug 1998 10:23:08 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id KAA25365; Wed, 12 Aug 1998 10:23:07 +0930 (CST) Message-ID: <19980812102307.S22754@freebie.lemis.com> Date: Wed, 12 Aug 1998 10:23:07 +0930 From: Greg Lehey To: "Eugene M. Kim" , FreeBSD SCSI Mailing List Subject: Re: CAM patch won't apply to -current References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Eugene M. Kim on Tue, Aug 11, 1998 at 10:10:35AM -0700 WWW-Home-Page: http://www.lemis.com/~grog 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 On Tuesday, 11 August 1998 at 10:10:35 -0700, Eugene M. Kim wrote: > Hello, > > Yesterday I decided to try CAM on my -current system. I fetched the > CAM patch and tried to apply it, but the it wouldn't patch because the > interface to dsopen() in sys/kern/subr_diskslice.c had been changed > recently. (dsopen() now expects one more argument.) > > Apparently the CAM patch would not work until it is also revised > accordingly. So my question is: when would the new patch be released? I sent in a patch for this a couple of days ago. It's relatively trivial, so here it is: --- wd.c.old-perforce Fri Jul 17 05:46:19 1998 +++ wd.c Sun Aug 9 12:22:02 1998 @@ -1469,7 +1469,7 @@ label.d_ncylinders = du->dk_dd.d_ncylinders; label.d_secpercyl = du->dk_dd.d_secpercyl; label.d_secperunit = du->dk_dd.d_secperunit; - error = dsopen("wd", dev, fmt, &du->dk_slices, &label, wdstrategy1, + error = dsopen("wd", dev, fmt, 0, &du->dk_slices, &label, wdstrategy1, (ds_setgeom_t *)NULL, &wd_cdevsw, &wd_cdevsw); } du->dk_flags &= ~DKFL_LABELLING; --- scsi_da.c.old-perforce Mon Aug 3 14:51:23 1998 +++ scsi_da.c Sun Aug 9 12:18:42 1998 @@ -310,7 +310,7 @@ } /* Initialize slice tables. */ - error = dsopen("da", dev, fmt, &softc->dk_slices, &label, + error = dsopen("da", dev, fmt, 0, &softc->dk_slices, &label, dastrategy, (ds_setgeom_t *)NULL, &da_cdevsw, &da_cdevsw); Greg -- See complete headers for address and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 11 18:30:27 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA19386 for freebsd-scsi-outgoing; Tue, 11 Aug 1998 18:30:27 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from thelab.hub.org (gw03.mpoweredpc.net [142.177.184.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA19363; Tue, 11 Aug 1998 18:30:19 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.8) with SMTP id WAA00512; Tue, 11 Aug 1998 22:29:13 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 11 Aug 1998 22:29:13 -0300 (ADT) From: The Hermit Hacker To: Bruce Albrecht cc: scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Odd problems with -current... In-Reply-To: <13766.34658.202254.310696@zuhause.zuhause.mn.org> 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, 3 Aug 1998, Bruce Albrecht wrote: > The Hermit Hacker writes: > > I'm trying to debug a problem that I'm having on my home machine > > that has me totally baffled, and am hoping someone here can "show me the > > way"... > > > > I just put in a 2gig Seagate SCSI drive on my system, to replace a > > 2gig IDE drive, and after running for awhile, it *seems* that the drive is > > powering down, cause when I try to access something on that drive after > > leaving for a period of time, you can hear it power back up again. > > Are you sure that it's not powering down because it's overheating? > I've got a couple of Hawk drives that shut down until I added extra fans. I'm not certain of anything right now, but I've got a larger email to send later tonight with, what I hope, is alot more detail... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 11 18:55:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA23526 for freebsd-scsi-outgoing; Tue, 11 Aug 1998 18:55:07 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from thelab.hub.org (gw03.mpoweredpc.net [142.177.184.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA23516 for ; Tue, 11 Aug 1998 18:55:04 -0700 (PDT) (envelope-from scrappy@hub.org) Received: from localhost (scrappy@localhost) by thelab.hub.org (8.8.8/8.8.8) with SMTP id WAA00556; Tue, 11 Aug 1998 22:52:49 -0300 (ADT) (envelope-from scrappy@hub.org) X-Authentication-Warning: thelab.hub.org: scrappy owned process doing -bs Date: Tue, 11 Aug 1998 22:52:48 -0300 (ADT) From: The Hermit Hacker To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG Subject: Re: CAM support for NCR controller... In-Reply-To: <199808110534.XAA00192@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="0-1677686816-902886768=:487" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. Send mail to mime@docserver.cac.washington.edu for more info. --0-1677686816-902886768=:487 Content-Type: TEXT/PLAIN; charset=US-ASCII On Mon, 10 Aug 1998, Justin T. Gibbs wrote: > > Actually, I'm going to leave the system "as is" for the next couple of > > days, while I await some new hardware to arrive. If someone out there > > working on the NCR drivers has suggestions on what I can try towards > > providing more debug information on the problem, towards the betterment of > > the CAM drivers, please speak up...I provide my system as a test bed. > > A "boot -v" dmesg from the CAM system would be a place to start. It > would also help if you related the errors that are reported during > your failed CD-R burn sessions. Morning... Attached is my 'boot -v' dmesg. I was going to add a 'script' of my cdrecord session, but looking through it, it doesn't tell anything :( The system has changed slightly since my report yesterday. First off, I changed my internal SCSI cable from a 6foot, 8 connector cable (7 drives + 1 adapter) to a shorter cable (4 drives + 1 adapter). I've also added on my external CDR, which, in itself, gives me ~9 feet of SCSI from end-to-end. (yesterday, with the external, it was ~12feet). According to the specs I found on Adaptec's site, at: http://www.adaptec.com/products/guide/ioposter.html I should be good for (assuming the NCR/PCI controller *is* SCSI2?) 4 devices: 3 m 5+ devices: 1.5 m So, with 3 internal and 1 external, I should be well within my 9feet allowed. Now, when I reported the problem last night, I had 6 SCSI drives active on the internal bus, on a 6foot ribbon cable, and the external CDR was not attached, which makes me ~1.5feet over the limit according to Adaptec. The tail end of the dmesg attached shows: (cd1:ncr0:0:6:0): READ(10). CDB: 28 0 0 0 0 27 0 0 1 0 (cd1:ncr0:0:6:0): UNIT ATTENTION asc:29,0 (cd1:ncr0:0:6:0): Power on, reset, or bus device reset occurred cddone: got error 0x6 back (cd1:ncr0:0:6:0): READ(10). CDB: 28 0 0 0 0 27 0 0 1 0 (cd1:ncr0:0:6:0): UNIT ATTENTION asc:28,0 (cd1:ncr0:0:6:0): Not ready to ready change, medium may have changed cddone: got error 0x6 back (cd1:ncr0:0:6:0): READ(10). CDB: 28 0 0 0 9d 7d 0 0 10 0 (cd1:ncr0:0:6:0): UNIT ATTENTION asc:29,0 (cd1:ncr0:0:6:0): Power on, reset, or bus device reset occurred cddone: got error 0x6 back (cd1:ncr0:0:6:0): READ(10). CDB: 28 0 0 0 0 27 0 0 1 0 (cd1:ncr0:0:6:0): UNIT ATTENTION asc:28,0 (cd1:ncr0:0:6:0): Not ready to ready change, medium may have changed cddone: got error 0x6 back this is what comes up after cdrecord successfully writes a CD, and then I try to mount it to look at it. I know the CD was successfully written cause if I take teh same one that causes the errors above and move it to one of my other CD readers, it mounts fine, and I can access all the files on it at will. I've successfully written 3 CDs since booting up in my current configuration, and have just blown my 4th, but I think that is from trying ot do too many other things at the same time...will try a 5th while leaving the system idle, and will report on that as a followup... I saw oen posting back about chip-set's and overloaded buses and whatnot...the problem I have is that before I moved this system over to CAM, the NCR controller worked fine, it is only since moving to the CAM drivers that I've had problems... ...let me know if there is anythign else I can provide or try... Thanks... Marc G. Fournier Systems Administrator @ hub.org primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org --0-1677686816-902886768=:487 Content-Type: TEXT/PLAIN; charset=US-ASCII; name="boot.v" Content-Transfer-Encoding: BASE64 Content-ID: Content-Description: Content-Disposition: attachment; filename="boot.v" YmxlZCwgcHJlL3Bvc3QgZW5hYmxlZCwNCmludGVsX3BpaXhfc3RhdHVzOiAg SU9SRFkgc2FtcGxpbmcgZW5hYmxlZCwNCmludGVsX3BpaXhfc3RhdHVzOiAg ZmFzdCBQSU8gZW5hYmxlZA0KaW50ZWxfcGlpeF9zdGF0dXM6IHByaW1hcnkg c2xhdmUgc2FtcGxlID0gMywgc2xhdmUgcmVjb3ZlcnkgPSAzDQppbnRlbF9w aWl4X3N0YXR1czogcHJpbWFyeSBzbGF2ZSBmYXN0RE1Bb25seSBkaXNhYmxl ZCwgcHJlL3Bvc3QgZW5hYmxlZCwNCmludGVsX3BpaXhfc3RhdHVzOiAgSU9S RFkgc2FtcGxpbmcgZW5hYmxlZCwNCmludGVsX3BpaXhfc3RhdHVzOiAgZmFz dCBQSU8gZW5hYmxlZA0KaWRlX3BjaTogYnVzbWFzdGVyIDAgc3RhdHVzOiAw NCBmcm9tIHBvcnQ6IDAwMDBmMDAyDQppbnRlbF9waWl4X3N0YXR1czogc2Vj b25kYXJ5IG1hc3RlciBzYW1wbGUgPSA1LCBtYXN0ZXIgcmVjb3ZlcnkgPSA0 DQppbnRlbF9waWl4X3N0YXR1czogc2Vjb25kYXJ5IG1hc3RlciBmYXN0RE1B b25seSBkaXNhYmxlZCwgcHJlL3Bvc3QgZGlzYWJsZWQsDQppbnRlbF9waWl4 X3N0YXR1czogIElPUkRZIHNhbXBsaW5nIGRpc2FibGVkLA0KaW50ZWxfcGlp eF9zdGF0dXM6ICBmYXN0IFBJTyBkaXNhYmxlZA0KaW50ZWxfcGlpeF9zdGF0 dXM6IHNlY29uZGFyeSBzbGF2ZSBzYW1wbGUgPSA1LCBzbGF2ZSByZWNvdmVy eSA9IDQNCmludGVsX3BpaXhfc3RhdHVzOiBzZWNvbmRhcnkgc2xhdmUgZmFz dERNQW9ubHkgZGlzYWJsZWQsIHByZS9wb3N0IGRpc2FibGVkLA0KaW50ZWxf cGlpeF9zdGF0dXM6ICBJT1JEWSBzYW1wbGluZyBkaXNhYmxlZCwNCmludGVs X3BpaXhfc3RhdHVzOiAgZmFzdCBQSU8gZGlzYWJsZWQNCmlkZV9wY2k6IGJ1 c21hc3RlciAxIHN0YXR1czogMDQgZnJvbSBwb3J0OiAwMDAwZjAwYQ0KZm91 bmQtPgl2ZW5kb3I9MHgxMDAwLCBkZXY9MHgwMDAxLCByZXZpZD0weDAyDQoJ Y2xhc3M9MDEtMDAtMDAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MA0KCWludHBp bj1hLCBpcnE9MTENCgltYXBbMF06IHR5cGUgNCwgcmFuZ2UgMzIsIGJhc2Ug MDAwMDYxMDAsIHNpemUgIDgNCgltYXBbMV06IHR5cGUgMSwgcmFuZ2UgMzIs IGJhc2UgZTA4MDAwMDAsIHNpemUgIDgNCm5jcjA6IDxuY3IgNTNjODEwIGZh c3QxMCBzY3NpPiByZXYgMHgwMiBpbnQgYSBpcnEgMTEgb24gcGNpMC44LjAN Cm5jcjA6IG1pbnN5bmM9MjUsIG1heHN5bmM9MjA2LCBtYXhvZmZzPTgsIDE2 IGR3b3JkcyBidXJzdCwgbm9ybWFsIGRtYSBmaWZvDQpuY3IwOiBzaW5nbGUt ZW5kZWQsIG9wZW4gZHJhaW4gSVJRIGRyaXZlcg0KZm91bmQtPgl2ZW5kb3I9 MHgxMGI3LCBkZXY9MHg1OTAwLCByZXZpZD0weDAwDQoJY2xhc3M9MDItMDAt MDAsIGhkcnR5cGU9MHgwMCwgbWZkZXY9MA0KCWludHBpbj1hLCBpcnE9MTAN CgltYXBbMF06IHR5cGUgNCwgcmFuZ2UgMzIsIGJhc2UgMDAwMDYyMDAsIHNp emUgIDUNCnZ4MDogPDNDT00gM0M1OTAgRXRoZXJsaW5rIElJSSBQQ0k+IHJl diAweDAwIGludCBhIGlycSAxMCBvbiBwY2kwLjEwLjANCnV0cFsqdXRwKl06 IGRpc2FibGUgJ2F1dG8gc2VsZWN0JyB3aXRoIERPUyB1dGlsISBhZGRyZXNz IDAwOjIwOmFmOmY3OjhmOmQyDQpicGY6IHZ4MCBhdHRhY2hlZA0KV2Fybmlu ZyEgRGVmZWN0aXZlIGVhcmx5IHJldmlzaW9uIGFkYXB0ZXIhDQpmb3VuZC0+ CXZlbmRvcj0weDEwMDIsIGRldj0weDQ3NTgsIHJldmlkPTB4MDANCgljbGFz cz0wMy0wMC0wMCwgaGRydHlwZT0weDAwLCBtZmRldj0wDQoJbWFwWzBdOiB0 eXBlIDEsIHJhbmdlIDMyLCBiYXNlIGUwMDAwMDAwLCBzaXplIDIzDQp2Z2Ew OiA8QVRJIE1hY2g2NC1HWCBncmFwaGljcyBhY2NlbGVyYXRvcj4gcmV2IDB4 MDAgb24gcGNpMC4xMS4wDQpQcm9iaW5nIGZvciBQblAgZGV2aWNlczoNClRy eWluZyBSZWFkX1BvcnQgYXQgMjAzDQpUcnlpbmcgUmVhZF9Qb3J0IGF0IDI0 Mw0KQ1NOIDEgVmVuZG9yIElEOiBDVEwwMGMxIFsweGMxMDA4YzBlXSBTZXJp YWwgMHgwMjRiNTUyZg0KQ2FsbGVkIG51bGxwbnBfcHJvYmUgd2l0aCB0YWcg MHgwMDAwMDAwMSwgdHlwZSAweGMxMDA4YzBlDQpwb3J0IDB4MDIyMCAweDAz MDAgMHgwMzg4IDB4MDAwMCBpcnEgOTowIGRycSAzOjcgZW4gMQ0KcG9ydCAw eDAyMjAgMHgwMzAwIDB4MDM4OCAweDAwMDAgaXJxIDk6MCBkcnEgMzo3IGVu IDENCnBjbTEgKFNCMTZwbnAgPFNCMTYgUG5QPiBzbiAweDAyNGI1NTJmKSBh dCAweDIyMC0weDIyZiBpcnEgOSBkcnEgMyBmbGFncyAweDE3IG9uIGlzYQ0K UHJvYmluZyBmb3IgZGV2aWNlcyBvbiB0aGUgSVNBIGJ1czoNCnNjMDogdGhl IGN1cnJlbnQga2V5Ym9hcmQgY29udHJvbGxlciBjb21tYW5kIGJ5dGUgMDA0 Nw0Ka2JkaW86IERJQUdOT1NFIHN0YXR1czowMDU1DQprYmRpbzogVEVTVF9L QkRfUE9SVCBzdGF0dXM6MDAwMA0Ka2JkaW86IFJFU0VUX0tCRCByZXR1cm4g Y29kZTowMGZhDQprYmRpbzogUkVTRVRfS0JEIHN0YXR1czowMGFhDQpzYzA6 IGtleWJvYXJkIGRldmljZSBJRDogYWI0MQ0Kc2MwIGF0IDB4NjAtMHg2ZiBp cnEgMSBvbiBtb3RoZXJib2FyZA0Kc2MwOiBCSU9TIHZpZGVvIG1vZGU6Mw0K c2MwOiBWR0EgcmVnaXN0ZXJzIHVwb24gcG93ZXItdXANCjUwIDE4IDEwIDAw IDEwIDAwIDAzIDAwIDAyIDY3IDVmIDRmIDUwIDgyIDU1IDgxIA0KYmYgMWYg MDAgNGYgMGUgMGYgMDAgMDAgMDcgODAgOWMgOGUgOGYgMjggMWYgOTYgDQpi OSBhMyBmZiAwMCAwMSAwMiAwMyAwNCAwNSAxNCAwNyAzOCAzOSAzYSAzYiAz YyANCjNkIDNlIDNmIDBjIDAwIDBmIDA4IDAwIDAwIDAwIDAwIDAwIDEwIDBl IDAwIGZmIA0Kc2MwOiB2aWRlbyBtb2RlOjI0DQpzYzA6IFZHQSByZWdpc3Rl cnMgaW4gQklPUyBmb3IgbW9kZToyNA0KNTAgMTggMTAgMDAgMTAgMDAgMDMg MDAgMDIgNjcgNWYgNGYgNTAgODIgNTUgODEgDQpiZiAxZiAwMCA0ZiAwZCAw ZSAwMCAwMCAwMCAwMCA5YyA4ZSA4ZiAyOCAxZiA5NiANCmI5IGEzIGZmIDAw IDAxIDAyIDAzIDA0IDA1IDE0IDA3IDM4IDM5IDNhIDNiIDNjIA0KM2QgM2Ug M2YgMGMgMDAgMGYgMDggMDAgMDAgMDAgMDAgMDAgMTAgMGUgMDAgZmYgDQpz YzA6IFZHQSByZWdpc3RlcnMgdG8gYmUgdXNlZCBmb3IgbW9kZToyNA0KNTAg MTggMTAgMDAgMTAgMDAgMDMgMDAgMDIgNjcgNWYgNGYgNTAgODIgNTUgODEg DQpiZiAxZiAwMCA0ZiAwZCAwZSAwMCAwMCAwMCAwMCA5YyA4ZSA4ZiAyOCAx ZiA5NiANCmI5IGEzIGZmIDAwIDAxIDAyIDAzIDA0IDA1IDE0IDA3IDM4IDM5 IDNhIDNiIDNjIA0KM2QgM2UgM2YgMGMgMDAgMGYgMDggMDAgMDAgMDAgMDAg MDAgMTAgMGUgMDAgZmYgDQpzYzA6IHJvd3Nfb2Zmc2V0OjENCnNjMDogVkdB IGNvbG9yIDwxNiB2aXJ0dWFsIGNvbnNvbGVzLCBmbGFncz0weDA+DQpzaW8w OiBpcnEgbWFwczogMHgxIDB4MTEgMHgxIDB4MQ0Kc2lvMCBhdCAweDNmOC0w eDNmZiBpcnEgNCBmbGFncyAweDEwIG9uIGlzYQ0Kc2lvMDogdHlwZSAxNjU1 MEENCnNpbzE6IGlycSBtYXBzOiAweDEgMHg5IDB4MSAweDENCnNpbzEgYXQg MHgyZjgtMHgyZmYgaXJxIDMgb24gaXNhDQpzaW8xOiB0eXBlIDE2NTUwQQ0K c2lvMjogaXJxIG1hcHM6IDB4MSAweDgxIDB4MSAweDENCnNpbzIgYXQgMHgz ZTgtMHgzZWYgaXJxIDcgb24gaXNhDQpzaW8yOiB0eXBlIDE2NTUwQQ0KbXNz X3Byb2JlOiBubyBhZGRyZXNzIHN1cHBsaWVkLCB0cnkgZGVmYXVsdCAweDUz MA0KbXNzX2RldGVjdCBlcnJvciwgYnVzeSBzdGlsbCBzZXQgKDB4ZmYpDQpz Yl9wcm9iZTogbm8gYWRkcmVzcyBzdXBwbGllZCwgdHJ5IGRlZmF1bHRzICgw eDIyMCwweDI0MCkNCmRldmljZSBhdCAweDIyMCBhbHJlYWR5IGF0dGFjaGVk IGFzIHVuaXQgMQ0KcGNtMCBub3QgZm91bmQNCmZkYzAgYXQgMHgzZjAtMHgz ZjcgaXJxIDYgZHJxIDIgb24gaXNhDQpmZGMwOiBGSUZPIGVuYWJsZWQsIDgg Ynl0ZXMgdGhyZXNob2xkDQpmZDA6IDEuNDRNQiAzLjVpbg0Kd2RjMCBhdCAw eDFmMC0weDFmNyBpcnEgMTQgb24gaXNhDQp3ZGMwOiB1bml0IDAgKHdkMCk6 IDxXREMgQUMyMjUwMEw+DQp3ZDA6IDI0NDFNQiAoNDk5OTY4MCBzZWN0b3Jz KSwgNDk2MCBjeWxzLCAxNiBoZWFkcywgNjMgUy9ULCA1MTIgQi9TDQp3ZDA6 IEFUQSBJTlFVSVJFIHZhbGlkID0gMDAwNywgZG1hbXdvcmQgPSAwNDA3LCBh cGlvID0gMDAwMywgdWRtYSA9IDAwMDcNCndkYzA6IHVuaXQgMSAoYXRhcGkp OiA8QUNFUiBDRC05MTBFL0pBUy8xM04+LCByZW1vdmFibGUsIGRtYSwgaW9y ZHkNCndjZDA6IDY4N0tiL3NlYywgMjQwS2IgY2FjaGUsIGF1ZGlvIHBsYXks IDIgdm9sdW1lIGxldmVscywgZWplY3RhYmxlIHRyYXkNCndjZDA6IDgwbW0g ZGF0YSBkaXNjIGxvYWRlZCwgdW5sb2NrZWQNCndkYzEgbm90IGZvdW5kIGF0 IDB4MTcwDQpzY2QwIG5vdCBmb3VuZCBhdCAweDIzMA0KbnB4MCBvbiBtb3Ro ZXJib2FyZA0KbnB4MDogSU5UIDE2IGludGVyZmFjZQ0KaTU4Nl9iemVybygp IGJhbmR3aWR0aCA9IDE2MTM2ODQwNCBieXRlcy9zZWMNCmJ6ZXJvKCkgYmFu ZHdpZHRoID0gODUxNzE2MjAgYnl0ZXMvc2VjDQppbWFza3M6IGJpbyBjMDA4 NDA0MCwgdHR5IGMwMDMwMjlhLCBuZXQgYzAwNjA0MDANCkJJT1MgR2VvbWV0 cmllczoNCiAwOjAzZjA0MTNmIDAuLjEwMDg9MTAwOSBjeWxpbmRlcnMsIDAu LjY1PTY2IGhlYWRzLCAxLi42Mz02MyBzZWN0b3JzDQogMTowM2Y2MDczYiAw Li4xMDE0PTEwMTUgY3lsaW5kZXJzLCAwLi43PTggaGVhZHMsIDEuLjU5PTU5 IHNlY3RvcnMNCiAyOjAyNmE3ZjNmIDAuLjYxOD02MTkgY3lsaW5kZXJzLCAw Li4xMjc9MTI4IGhlYWRzLCAxLi42Mz02MyBzZWN0b3JzDQogMCBhY2NvdW50 ZWQgZm9yDQpEZXZpY2UgY29uZmlndXJhdGlvbiBmaW5pc2hlZC4NCkludGVs IFBlbnRpdW0gRjAwRiBkZXRlY3RlZCwgaW5zdGFsbGluZyB3b3JrYXJvdW5k DQpicGY6IHR1bjAgYXR0YWNoZWQNCmJwZjogbG8wIGF0dGFjaGVkDQpuY3Iw OiByZXN0YXJ0IChzY3NpIHJlc2V0KS4NCihwcm9iZTY6bmNyMDowOjY6MCk6 IENPTU1BTkQgRkFJTEVEICg2IGZmKSBAZjBhMGJhMDAuDQoocHJvYmU1Om5j cjA6MDo1OjApOiBDT01NQU5EIEZBSUxFRCAoNiBmZikgQGYwYTBhMDAwLg0K KHByb2JlNDpuY3IwOjA6NDowKTogQ09NTUFORCBGQUlMRUQgKDYgZmYpIEBm MGEwYTYwMC4NCihwcm9iZTM6bmNyMDowOjM6MCk6IENPTU1BTkQgRkFJTEVE ICg2IGZmKSBAZjBhMGFjMDAuDQoocHJvYmUyOm5jcjA6MDoyOjApOiBDT01N QU5EIEZBSUxFRCAoNiBmZikgQGYwYTA4MjAwLg0KKHByb2JlMTpuY3IwOjA6 MTowKTogQ09NTUFORCBGQUlMRUQgKDYgZmYpIEBmMGEwODgwMC4NCihwcm9i ZTA6bmNyMDowOjA6MCk6IENPTU1BTkQgRkFJTEVEICg2IGZmKSBAZjBhMDhl MDAuDQpwYXNzMCBhdCBuY3IwIGJ1cyAwIHRhcmdldCAwIGx1biAwDQpwYXNz MDogPFNFQUdBVEUgU1QzMjE1MU4gMDI4ND4gRml4ZWQgRGlyZWN0IEFjY2Vz cyBTQ1NJMiBkZXZpY2UgDQpwYXNzMDogU2VyaWFsIE51bWJlciAwMDA0ODE0 OTBSVE5SWA0KcGFzczA6IDEwLjBNQi9zIHRyYW5zZmVycyAoMTAuME1Ieiwg b2Zmc2V0IDgpLCBUYWdnZWQgUXVldWVpbmcgRW5hYmxlZA0KcGFzczEgYXQg bmNyMCBidXMgMCB0YXJnZXQgMSBsdW4gMA0KcGFzczE6IDxRVUFOVFVNIExQ MjQwUyBHTTI0MFMwMVggNi40PiBGaXhlZCBEaXJlY3QgQWNjZXNzIFNDU0ky IGRldmljZSANCnBhc3MxOiAxMC4wTUIvcyB0cmFuc2ZlcnMgKDEwLjBNSHos IG9mZnNldCA4KQ0KcGFzczIgYXQgbmNyMCBidXMgMCB0YXJnZXQgMyBsdW4g MA0KcGFzczI6IDxTT05ZIENELVJPTSBDRFU2MjUgMS4wcj4gUmVtb3ZhYmxl IENELVJPTSBTQ1NJMiBkZXZpY2UgDQpwYXNzMjogMTAuME1CL3MgdHJhbnNm ZXJzICgxMC4wTUh6LCBvZmZzZXQgOCkNCnBhc3MzIGF0IG5jcjAgYnVzIDAg dGFyZ2V0IDYgbHVuIDANCnBhc3MzOiA8WUFNQUhBIENSVzIyNjAgMS4wZj4g UmVtb3ZhYmxlIENELVJPTSBTQ1NJMiBkZXZpY2UgDQpwYXNzMzogMy4zMDBN Qi9zIHRyYW5zZmVycw0KZGExIGF0IG5jcjAgYnVzIDAgdGFyZ2V0IDEgbHVu IDANCmRhMTogPFFVQU5UVU0gTFAyNDBTIEdNMjQwUzAxWCA2LjQ+IEZpeGVk IERpcmVjdCBBY2Nlc3MgU0NTSTIgZGV2aWNlIA0KZGExOiAxMC4wTUIvcyB0 cmFuc2ZlcnMgKDEwLjBNSHosIG9mZnNldCA4KQ0KZGExOiAyMzRNQiAoNDc5 MzUwIDUxMiBieXRlIHNlY3RvcnM6IDY0SCAzMlMvVCAyMzRDKQ0KZGEwIGF0 IG5jcjAgYnVzIDAgdGFyZ2V0IDAgbHVuIDANCmRhMDogPFNFQUdBVEUgU1Qz MjE1MU4gMDI4ND4gRml4ZWQgRGlyZWN0IEFjY2VzcyBTQ1NJMiBkZXZpY2Ug DQpkYTA6IFNlcmlhbCBOdW1iZXIgMDAwNDgxNDkwUlROUlgNCmRhMDogMTAu ME1CL3MgdHJhbnNmZXJzICgxMC4wTUh6LCBvZmZzZXQgOCksIFRhZ2dlZCBR dWV1ZWluZyBFbmFibGVkDQpkYTA6IDIwNDlNQiAoNDE5NzQwNSA1MTIgYnl0 ZSBzZWN0b3JzOiAyNTVIIDYzUy9UIDI2MUMpDQpjZDAgYXQgbmNyMCBidXMg MCB0YXJnZXQgMyBsdW4gMA0KY2QwOiA8U09OWSBDRC1ST00gQ0RVNjI1IDEu MHI+IFJlbW92YWJsZSBDRC1ST00gU0NTSTIgZGV2aWNlIA0KY2QwOiAxMC4w TUIvcyB0cmFuc2ZlcnMgKDEwLjBNSHosIG9mZnNldCA4KQ0KY2QwOiBjZCBw cmVzZW50IFszMTg2NTkgeCAyMDQ4IGJ5dGUgcmVjb3Jkc10NCkNvbnNpZGVy aW5nIEZGUyByb290IGYvcy4NCmNoYW5naW5nIHJvb3QgZGV2aWNlIHRvIGRh MHMxYQ0KZGEwczE6IHR5cGUgMHhhNSwgc3RhcnQgMCwgZW5kID0gNDE5NzQw NCwgc2l6ZSA0MTk3NDA1IA0KZGEwczE6IEMvSC9TIGVuZCAyNjEvNzAvMzAg KDU1ODA1OSkgIT0gZW5kIDQxOTc0MDQ6IGludmFsaWQNCmRhMXMxOiB0eXBl IDB4YTUsIHN0YXJ0IDAsIGVuZCA9IDQ3OTM0OSwgc2l6ZSA0NzkzNTAgOiBP Sw0Kd2QwczE6IHR5cGUgMHg2LCBzdGFydCA2MywgZW5kID0gMjA5NjYzOSwg c2l6ZSAyMDk2NTc3IDogT0sNCndkMHMyOiB0eXBlIDB4YTUsIHN0YXJ0IDIw OTY2NDAsIGVuZCA9IDQ5OTk2NzksIHNpemUgMjkwMzA0MCA6IE9LDQpkYTFz MTogdHlwZSAweGE1LCBzdGFydCAwLCBlbmQgPSA0NzkzNDksIHNpemUgNDc5 MzUwIDogT0sNCndkMHMxOiB0eXBlIDB4Niwgc3RhcnQgNjMsIGVuZCA9IDIw OTY2MzksIHNpemUgMjA5NjU3NyA6IE9LDQp3ZDBzMjogdHlwZSAweGE1LCBz dGFydCAyMDk2NjQwLCBlbmQgPSA0OTk5Njc5LCBzaXplIDI5MDMwNDAgOiBP Sw0KYXJwbG9va3VwIDE3Mi4yMi40MC4xNiBmYWlsZWQ6IGhvc3QgaXMgbm90 IG9uIGxvY2FsIG5ldHdvcmsNCmNkMSBhdCBuY3IwIGJ1cyAwIHRhcmdldCA2 IGx1biAwDQpjZDE6IDxZQU1BSEEgQ1JXMjI2MCAxLjBmPiBSZW1vdmFibGUg Q0QtUk9NIFNDU0kyIGRldmljZSANCmNkMTogMy4zMDBNQi9zIHRyYW5zZmVy cw0KY2QxOiBjZCBwcmVzZW50IFsxIHggMjA0OCBieXRlIHJlY29yZHNdDQoo Y2QxOm5jcjA6MDo2OjApOiBSRUFEKDEwKS4gQ0RCOiAyOCAwIDAgMCAwIDI3 IDAgMCAxIDAgDQooY2QxOm5jcjA6MDo2OjApOiBVTklUIEFUVEVOVElPTiBh c2M6MjksMA0KKGNkMTpuY3IwOjA6NjowKTogUG93ZXIgb24sIHJlc2V0LCBv ciBidXMgZGV2aWNlIHJlc2V0IG9jY3VycmVkDQpjZGRvbmU6IGdvdCBlcnJv ciAweDYgYmFjaw0KKGNkMTpuY3IwOjA6NjowKTogUkVBRCgxMCkuIENEQjog MjggMCAwIDAgMCAyNyAwIDAgMSAwIA0KKGNkMTpuY3IwOjA6NjowKTogVU5J VCBBVFRFTlRJT04gYXNjOjI4LDANCihjZDE6bmNyMDowOjY6MCk6IE5vdCBy ZWFkeSB0byByZWFkeSBjaGFuZ2UsIG1lZGl1bSBtYXkgaGF2ZSBjaGFuZ2Vk DQpjZGRvbmU6IGdvdCBlcnJvciAweDYgYmFjaw0KYXJwbG9va3VwIDE3Mi4y Mi40MC4xNiBmYWlsZWQ6IGhvc3QgaXMgbm90IG9uIGxvY2FsIG5ldHdvcmsN CihjZDE6bmNyMDowOjY6MCk6IFJFQUQoMTApLiBDREI6IDI4IDAgMCAwIDlk IDdkIDAgMCAxMCAwIA0KKGNkMTpuY3IwOjA6NjowKTogVU5JVCBBVFRFTlRJ T04gYXNjOjI5LDANCihjZDE6bmNyMDowOjY6MCk6IFBvd2VyIG9uLCByZXNl dCwgb3IgYnVzIGRldmljZSByZXNldCBvY2N1cnJlZA0KY2Rkb25lOiBnb3Qg ZXJyb3IgMHg2IGJhY2sNCihjZDE6bmNyMDowOjY6MCk6IFJFQUQoMTApLiBD REI6IDI4IDAgMCAwIDAgMjcgMCAwIDEgMCANCihjZDE6bmNyMDowOjY6MCk6 IFVOSVQgQVRURU5USU9OIGFzYzoyOCwwDQooY2QxOm5jcjA6MDo2OjApOiBO b3QgcmVhZHkgdG8gcmVhZHkgY2hhbmdlLCBtZWRpdW0gbWF5IGhhdmUgY2hh bmdlZA0KY2Rkb25lOiBnb3QgZXJyb3IgMHg2IGJhY2sNCmFycGxvb2t1cCAx NzIuMjIuNDAuMTYgZmFpbGVkOiBob3N0IGlzIG5vdCBvbiBsb2NhbCBuZXR3 b3JrDQo= --0-1677686816-902886768=:487-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 11 23:42:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA29571 for freebsd-scsi-outgoing; Tue, 11 Aug 1998 23:42:54 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nash.pubnix.net (Nash.pubnix.net [192.172.250.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA29565 for ; Tue, 11 Aug 1998 23:42:51 -0700 (PDT) (envelope-from aal@pubnix.net) Received: from pubnix.net (aal.pubnix.net [199.202.137.130] (may be forged)) by nash.pubnix.net (8.8.8/8.8.7) with ESMTP id CAA05021 for ; Wed, 12 Aug 1998 02:42:26 -0400 (EDT) (envelope-from aal@pubnix.net) Message-ID: <35D13957.D52AC90D@pubnix.net> Date: Wed, 12 Aug 1998 02:42:31 -0400 From: Alain Hebert Organization: PubNIX Montreal, Inc. X-Mailer: Mozilla 4.5b1 [en] (X11; I; FreeBSD 3.0-CURRENT i386) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-scsi@FreeBSD.ORG" Subject: Re: Heavy CAM Problems... References: <199808111906.NAA06851@narnia.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (Just in case... I'm not native english some part are more understandable if you read-it as it sound!) SOLVED! (Or at least isolated...) That's what is happening... The new cables (U2W: The one with a terminator and with all the wire independently connecter to the connector (but still in serial fashion) ) are kinda having quite a ride on EMI... Yeap, your PC emit like a small Radio station! So you have to make sure where you route the cable throughout the casing. Like, Justin said: that the Adaptec Guys thinks it hardware... Some timing or access sequence were surely changed between 0520 and 0712 and made that problem appear more frequently. So a good SCSI hygiene and good posture (don't route the cable around the power, but near the casing following a single direction, not to pinch or apply stress to the cable or wire...) might generally solve the problem. (This can explain why some got 0x17d and others 0x17e... I was re-arranging it tonight when I start getting 0x2!) So, I'm mailing from a functional 0712 installation with a 3.0-current kernel (but I still have the patch Justin send us... Will see without it tomorrow, OK!) Have fun with your 3.0-19980716-CAM system. (I will for sure!) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 12 03:52:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA09988 for freebsd-scsi-outgoing; Wed, 12 Aug 1998 03:52:15 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from tata.research.rockwell.cz (tata.research.rockwell.cz [193.85.154.66]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id DAA09981 for ; Wed, 12 Aug 1998 03:52:12 -0700 (PDT) (envelope-from mira@rockwell.cz) Received: from rockwell.cz (aja.research.rockwell.cz [193.85.154.75]) by tata.research.rockwell.cz (8.6.9/8.6.5) with ESMTP id NAA18351 for ; Wed, 12 Aug 1998 13:02:18 +0200 Message-ID: <35D176A6.567EB43C@rockwell.cz> Date: Wed, 12 Aug 1998 13:04:06 +0200 From: Miroslav Kes Organization: Rockwell Automation Ltd., Research Center Prague X-Mailer: Mozilla 4.5b1 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: "freebsd-scsi@FreeBSD.ORG" Subject: Re: Heavy CAM Problems... References: <199808111906.NAA06851@narnia.plutotech.com> <35D13957.D52AC90D@pubnix.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Alain Hebert wrote: > SOLVED! (Or at least isolated...) > > That's what is happening... > > The new cables (U2W: The one with a terminator and with all the wire > independently connecter to the connector (but still in serial fashion) ) > are kinda having quite a ride on EMI... Yeap, your PC emit like a small > Radio station! So you have to make sure where you route the cable > throughout the casing. > > Like, Justin said: that the Adaptec Guys thinks it hardware... Some > timing or access sequence were surely changed between 0520 and 0712 and > made that problem appear more frequently. > > So a good SCSI hygiene and good posture (don't route the cable around > the power, but near the casing following a single direction, not to > pinch or apply stress to the cable or wire...) might generally solve the > problem. > > (This can explain why some got 0x17d and others 0x17e... I was > re-arranging it tonight when I start getting 0x2!) Well, before the discussion on this topic started I thought it was my fault and I checked IRQ conflicts, improper termination and also routing of SCSI cables inside the chassis with respect to the power unit. I have already mentioned it in one of earlier messages. The symptom looked like as long as I had the machine on the table without the cover it worked and it stopped working when I put the cover on and put the machine on the floor. In the meantime I found one problem with termination and after solving it the problem disappeared and I thought I won. Three days later I had to move the computer to another place in our office so I had to stop it and boot again and the problem arose again. Playing with cable routing sometimes helped (for one or two boots). Now I cannot boot it at all. Any of tricks I used before doesn't work any more. The 2940U2W controller has three connectors Ultra2 68 pin, Ultra 68 pin and 50 pin. I'm using all of them so there are three cables with some devices attached. Today I inserted an IDE disk with 0520 snapshot and booted from it. As long as there is no cable with an device attached to the SCSI controller it boots without problems. If I attach ANY device no matter whether it is Ultra or Ultra2 type the boot doesn't complete (BIOS correctly reports which device is attached). I want to point out I have similar experience as you do but I haven't found any solution that would guarantee it was solved forever. Since the computer I'm talking about is intended to be our main fileserver and I need rock solid solution (that's why I have chosen FreeBSD). I would say the problem is still open. Going to play with memory timing. Mira -- ----------------------------------------------------------- | Miroslav Kes | |---------------------------------------------------------| | Rockwell Automation Ltd. | tel.: (+420) 2 2425 6913 | | Research Center Prague | fax: (+420) 2 250467 | | Americka 22 | e-mail: mira@rockwell.cz | | 120 00 Praha 2 - Vinohrady | | | Czech Republic | | ----------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 12 07:54:17 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA06187 for freebsd-scsi-outgoing; Wed, 12 Aug 1998 07:54:17 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from eagle.ais.net (eagle.ais.net [199.0.154.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA06182 for ; Wed, 12 Aug 1998 07:54:14 -0700 (PDT) (envelope-from adoane@eagle.ais.net) Received: (from adoane@localhost) by eagle.ais.net (8.8.8/AIS) id JAA00773 for freebsd-scsi@freebsd.org; Wed, 12 Aug 1998 09:53:48 -0500 (CDT) From: "Andrew J. Doane" Message-Id: <199808121453.JAA00773@eagle.ais.net> Subject: Problems w/CAM (aha and bt issues) To: freebsd-scsi@FreeBSD.ORG Date: Wed, 12 Aug 1998 09:53:47 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, I am currently running: FreeBSD 3.0CAM-19980712-SNAP FreeBSD 3.0CAM-19980712-SNAP #1: Tue Aug 11 23:55:17 CDT 1998 I attempted to apply to 0716 patch but it appears it really was already installed with the 0712 snapshot- cam_ccb.h:#define CAM_VERSION 0x4C /* Hex value for current version */ is the same for both 0712 and 0716 (If this isn't a good way of determining this, please let me know). The patch fails and wants to assume -R, so it really looks like it is already 0716. This is a dual PII-400 box with 4 scsi hosts: 1. Buslogic 958D (ultra/wide/diff) 2. Buslogic 946C (narrow) 3. Qty (2) 2940UW's My problem with the 958D is: da10 at bt1 bus 0 target 1 lun 0 da10: Fix ed Direct Access SCSI2 device da10: 3.300MB/s transfers, Tagged Queueing Enabled da10: 8681MB (17780058 512 byte sectors: 255H 63S/T 1106C) da15 at bt1 bus 0 target 8 lun 0 da15: Fixed Direct Access SCSI2 device da15: 3.300MB/s transfers, Tagged Queueing Enabled da15: 8682MB (17781520 512 byte sectors: 255H 63S/T 1106C) da14 at bt1 bus 0 target 5 lun 0 da14: Fixed Direct Access SCSI2 device da14: 3.300MB/s transfers, Tagged Queueing Enabled da14: 8682MB (17781520 512 byte sectors: 255H 63S/T 1106C) da13 at bt1 bus 0 target 4 lun 0 da13: Fix ed Direct Access SCSI2 device da13: 3.300MB/s transfers, Tagged Queueing Enabled da13: 8681MB (17780058 512 byte sectors: 255H 63S/T 1106C) da12 at bt1 bus 0 target 3 lun 0 da12: Fixed Direct Access SCSI2 device da12: 3.300MB/s transfers, Tagged Queueing Enabled da12: 8682MB (17781520 512 byte sectors: 255H 63S/T 1106C) da11 at bt1 bus 0 target 2 lun 0 da11: Fixed Direct Access SCSI2 device da11: 3.300MB/s transfers, Tagged Queueing Enabled da11: 8682MB (17781520 512 byte sectors: 255H 63S/T 1106C) All disks are recognized (which is new from the standard scsi drivers which don't realize the 958D is a wide controller), but they are syncing at 3.300MB/s ??? These disks should be able to do 40MB/s (ultra wide diff). The second issue is on ahc - I don't have specifics quite yet but I'm getting hangs on this disk which cause the entire system to hang. The next time it hangs I'll capture some console messages. From memory is was something like "Timed out due to another timeout" and referenced aha:da1. I had a similiar issue under linux and was forced to disable tagged queing on my microp 4743SS drives. I'm not quite sure how to do that under fbsd. da1 at ahc0 bus 0 target 2 lun 0 da1: Fixed Direct Access SCSI2 device da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit) da1: 4100MB (8398656 512 byte sectors: 255H 63S/T 522C) Any insight would be appreciated :-) /ajd/ -- _/_/ _/ _/_/_/_/ Andrew J. Doane _/ _/ _/ _/ VP, Access Div; Director, Network Ops _/_/_/_/ _/ _/_/_/_/ American Information Systems, Inc. _/ _/ _/ _/ Mail:adoane@ais.net, http://www.ais.net _/ _/ _/ _/_/_/_/ (312) 255-8500 Voice, (312) 255-8501 Fax For my PGP public key, email me with the subject "pgp request" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 12 09:06:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA18493 for freebsd-scsi-outgoing; Wed, 12 Aug 1998 09:06:58 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pinhead.parag.codegen.com (ppp-asfm08--183.sirius.net [205.134.241.183]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA18466 for ; Wed, 12 Aug 1998 09:06:46 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Received: from pinhead.parag.codegen.com (localhost.parag.codegen.com [127.0.0.1]) by pinhead.parag.codegen.com (8.8.8/8.8.8) with ESMTP id JAA29065 for ; Wed, 12 Aug 1998 09:06:26 -0700 (PDT) (envelope-from parag@pinhead.parag.codegen.com) Message-Id: <199808121606.JAA29065@pinhead.parag.codegen.com> X-Mailer: exmh version 2.0.2 2/24/98 To: freebsd-scsi@FreeBSD.ORG Subject: A couple of low-level (non-CAM) SCSI subsystem problems X-Face: =O'Kj74icvU|oS*<7gS/8'\Pbpm}okVj*@UC!IgkmZQAO!W[|iBiMs*|)n*`X ]pW%m>Oz_mK^Gdazsr.Z0/JsFS1uF8gBVIoChGwOy{EK=<6g?aHE`[\S]C]T0Wm X-URL: http://www.codegen.com Date: Wed, 12 Aug 1998 09:06:26 -0700 From: Parag Patel Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Apologies if you see this twice. I just noticed that there's a separate scsi mailing list. I had originally sent this to -current. If you have any hints, please email me as I'm not on -scsi but am on various other FreeBSD lists. Sorry for any inconvenience. --Parag] I just moved my UMAX 600S scanner from my Mac to FreeBSD 3.0-CURRENT without CAM. It works with the latest sane-0.74 code (which is not yet a port - 0.73 does not work properly for this scanner). Anyway, I started getting a lot (20-50) of these errors from the SCSI subsystem in the kernel whenever it scans an image: uk1: unknown error category from host adapter code After some debug-printfs, this is due to a select-timeout (XS_SELTIMEOUT) presumably because the scanner is busy moving its scan head back to the top or doing other house-keeping, and it isn't sending back a proper busy code. A quick-n-dirty patch to scsi/scsi_ioctl.c seems to eliminate this message without causing any other effects: =================================================================== RCS file: /src/freebsd/src/sys/scsi/scsi_ioctl.c,v retrieving revision 1.31 diff -c -r1.31 scsi_ioctl.c *** scsi_ioctl.c 1998/06/07 17:12:49 1.31 --- scsi_ioctl.c 1998/08/10 18:23:41 *************** *** 121,126 **** --- 121,127 ---- break; case XS_TIMEOUT: + case XS_SELTIMEOUT: SC_DEBUG(xs->sc_link,SDEV_DB3,("timeout\n")); screq->retsts = SCCMD_TIMEOUT; break; =================================================================== Is this OK, or is there a better fix (ie switch to CAM)? The second problem is during boot-up. If the scanner is powered on during boot, FreeBSD seems to think the scanner is at every SCSI address. However, if I leave it powered offduring boot, then do a "scsi -r" after the system is running, it probes the scanner properly (at SCSI ID 4) with no bogus extra LUNs. ahc0: rev 0x00 int a irq 19 on pci0.6.0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 4134MB (8467200 512 byte sectors) ahc0:A:1: refuses WIDE negotiation. Using 8bit transfers sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 3067MB (6281856 512 byte sectors) ahc0:A:4: refuses WIDE negotiation. Using 8bit transfers ahc0:A:4: refuses synchronous negotiation. Using asynchronous transfers uk0 at scbus0 target 4 lun 0 uk0: type 6 fixed SCSI 2 uk0: Unknown uk1 at scbus0 target 4 lun 1 uk1: type 6 fixed SCSI 2 uk1: Unknown uk2 at scbus0 target 4 lun 2 uk2: type 6 fixed SCSI 2 uk2: Unknown uk3 at scbus0 target 4 lun 3 uk3: type 6 fixed SCSI 2 uk3: Unknown uk4 at scbus0 target 4 lun 4 uk4: type 6 fixed SCSI 2 uk4: Unknown uk5 at scbus0 target 4 lun 5 uk5: type 6 fixed SCSI 2 uk5: Unknown uk6 at scbus0 target 4 lun 6 uk6: type 6 fixed SCSI 2 uk6: Unknown uk7 at scbus0 target 4 lun 7 uk7: type 6 fixed SCSI 2 uk7: Unknown ahc0:A:6: refuses WIDE negotiation. Using 8bit transfers uk8 at scbus0 target 6 lun 0 uk8: type 4 removable SCSI 2 uk8: Unknown Perhaps the workaround is to simply switch to CAM? Since CAM isn't the default yet, I was wondering if I should send-pr these two problems or not. Thanks in advance! -- Parag Patel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 12 10:01:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA25839 for freebsd-scsi-outgoing; Wed, 12 Aug 1998 10:01:30 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA25822 for ; Wed, 12 Aug 1998 10:01:27 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id KAA09207; Wed, 12 Aug 1998 10:55:22 -0600 (MDT) Date: Wed, 12 Aug 1998 10:55:22 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199808121655.KAA09207@narnia.plutotech.com> To: "Andrew J. Doane" cc: scsi@FreeBSD.ORG Subject: Re: Problems w/CAM (aha and bt issues) Newsgroups: pluto.freebsd.scsi In-Reply-To: <199808121453.JAA00773@eagle.ais.net> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <199808121453.JAA00773@eagle.ais.net> you wrote: > Hello all, > > I am currently running: > > FreeBSD 3.0CAM-19980712-SNAP FreeBSD > 3.0CAM-19980712-SNAP #1: Tue Aug 11 23:55:17 CDT 1998 > > I attempted to apply to 0716 patch but it appears it really was already > installed with the 0712 snapshot- > > cam_ccb.h:#define CAM_VERSION 0x4C /* Hex value for current version > */ > > is the same for both 0712 and 0716 (If this isn't a good way of > determining this, please let me know). The patch fails and wants > to assume -R, so it really looks like it is already 0716. The CAM_VERSION referes to the version of the CAM specification the code is derived from. I can't recal if I've already modified the value or not, but FreeBSD doesn't exactly match any CAM specification, so we shouldn't be using the standardized version number. The 716 snapshot is different than the 712, but the patches are not cumulative. They are designed (as it states in the README file) to be installed on top of a virgin -current or -stable. > My problem with the 958D is: > > da10 at bt1 bus 0 target 1 lun 0 > da10: P429> Fix > ed Direct Access SCSI2 device > da10: 3.300MB/s transfers, Tagged Queueing Enabled > da10: 8681MB (17780058 512 byte sectors: 255H 63S/T 1106C) This is almost assuradly a reporting problem, not a problem with the transfer rates in effect on the bus. Can you send me the adapter information that FreeBSD prints out at boot? Can you also check the BIOS settings to ensure that they are at the max settings? > The second issue is on ahc - I don't have specifics quite yet but I'm > getting hangs on this disk which cause the entire system to hang. > The next time it hangs I'll capture some console messages. From > memory is was something like "Timed out due to another timeout" and > referenced aha:da1. I had a similiar issue under linux and was forced > to disable tagged queing on my microp 4743SS drives. I'm not quite > sure how to do that under fbsd. Is this an SMP system? There have been other reports of a similar problem and I'm not convinced that it is drive related. > da1 at ahc0 bus 0 target 2 lun 0 > da1: Fixed Direct Access SCSI2 device > da1: 40.0MB/s transfers (20.0MHz, offset 8, 16bit) > da1: 4100MB (8398656 512 byte sectors: 255H 63S/T 522C) Tagged queuing isn't enabled on this drive, most likely because the DQUE bit is set in the control mode page. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 12 12:33:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA26314 for freebsd-scsi-outgoing; Wed, 12 Aug 1998 12:33:06 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from eagle.ais.net (eagle.ais.net [199.0.154.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA26304 for ; Wed, 12 Aug 1998 12:33:05 -0700 (PDT) (envelope-from adoane@eagle.ais.net) Received: (from adoane@localhost) by eagle.ais.net (8.8.8/AIS) id OAA02889; Wed, 12 Aug 1998 14:32:37 -0500 (CDT) From: "Andrew J. Doane" Message-Id: <199808121932.OAA02889@eagle.ais.net> Subject: Re: Problems w/CAM (aha and bt issues) In-Reply-To: <199808121655.KAA09207@narnia.plutotech.com> from "Justin T. Gibbs" at "Aug 12, 98 10:55:22 am" To: gibbs@narnia.plutotech.com (Justin T. Gibbs) Date: Wed, 12 Aug 1998 14:32:37 -0500 (CDT) Cc: adoane@ais.net, scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > The CAM_VERSION referes to the version of the CAM specification the > code is derived from. I can't recal if I've already modified the value > or not, but FreeBSD doesn't exactly match any CAM specification, so we > shouldn't be using the standardized version number. Alrighty. > The 716 snapshot is different than the 712, but the patches are not > cumulative. They are designed (as it states in the README file) to > be installed on top of a virgin -current or -stable. Ah. Well, i upgraded from 3.0-current w/just kernel sources to 3.0CAM-19980712 with full sources. I don't have a 3.0-current usr usr.sbin etc source tree to use the patch against. I'll try to find just 3.0-current sources on the ftp site. I'm still getting comfortable with fbsd's package/cvs system coming from a BSDI/linux/solaris background. > This is almost assuradly a reporting problem, not a problem with the > transfer rates in effect on the bus. Can you send me the adapter > information that FreeBSD prints out at boot? Can you also check the > BIOS settings to ensure that they are at the max settings? Maxed out. Here is the probe: bt1: rev 0x08 int a irq 19 on pci0.19.0 bt1: BT-958D FW Rev. 5.06I Ultra Wide Diff SCSI Host Adapter, SCSI ID 7, 192 CCB s Freeing (NOT implemented) redirected ISA irq 5. > Is this an SMP system? There have been other reports of a similar > problem and I'm not convinced that it is drive related. Yes, dual PII 400 BX, not overclocked. > Tagged queuing isn't enabled on this drive, most likely because the > DQUE bit is set in the control mode page. Ok, forgive my ignorance. Does that mean the drive is reporting that it is not tag queuing capable? Thanks, /ajd/ -- _/_/ _/ _/_/_/_/ Andrew J. Doane _/ _/ _/ _/ VP, Access Div; Director, Network Ops _/_/_/_/ _/ _/_/_/_/ American Information Systems, Inc. _/ _/ _/ _/ Mail:adoane@ais.net, http://www.ais.net _/ _/ _/ _/_/_/_/ (312) 255-8500 Voice, (312) 255-8501 Fax For my PGP public key, email me with the subject "pgp request" To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 12 12:38:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA27236 for freebsd-scsi-outgoing; Wed, 12 Aug 1998 12:38:18 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA27222 for ; Wed, 12 Aug 1998 12:38:10 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.7/8.8.5) with ESMTP id NAA10674; Wed, 12 Aug 1998 13:37:41 -0600 (MDT) Message-Id: <199808121937.NAA10674@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Andrew J. Doane" cc: gibbs@plutotech.com (Justin T. Gibbs), scsi@FreeBSD.ORG Subject: Re: Problems w/CAM (aha and bt issues) In-reply-to: Your message of "Wed, 12 Aug 1998 14:32:37 CDT." <199808121932.OAA02889@eagle.ais.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Aug 1998 13:32:04 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >bt1: rev 0x08 int a irq 19 on >pci0.19.0 >bt1: BT-958D FW Rev. 5.06I Ultra Wide Diff SCSI Host Adapter, SCSI ID 7, >192 CCBs Yeah. I already know of one problem with reporting for the 5.06I firmware, but I would have expected it to show narrow, sync, transfers, but not async transfers. I'll see what I can find. >Yes, dual PII 400 BX, not overclocked. Same problem then. As soon as I get some time, I'll be coordinating with one of the other "victims" to track this down. >> Tagged queuing isn't enabled on this drive, most likely because the >> DQUE bit is set in the control mode page. > >Ok, forgive my ignorance. Does that mean the drive is reporting that >it is not tag queuing capable? It means that although tagged queuing is available on the drive, it has been disabled by the user by editing a mode page on the device. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 12 15:22:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA23899 for freebsd-scsi-outgoing; Wed, 12 Aug 1998 15:22:21 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from fani.fidata.fi (fani.fidata.fi [193.64.102.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA23894 for ; Wed, 12 Aug 1998 15:22:18 -0700 (PDT) (envelope-from tomppa@fidata.fi) Received: from zeta.fidata.fi (zeta.fidata.fi [193.64.103.213]) by fani.fidata.fi (8.8.8/8.8.8) with ESMTP id BAA26969 for ; Thu, 13 Aug 1998 01:21:45 +0300 (EET DST) Received: (from tomppa@localhost) by zeta.fidata.fi (8.9.1/8.9.1) id BAA16296; Thu, 13 Aug 1998 01:21:46 +0300 (EET DST) From: Tomi Vainio MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <13778.5497.881819.859280@zeta.fidata.fi> Date: Thu, 13 Aug 1998 01:21:45 +0300 (EET DST) To: freebsd-scsi@FreeBSD.ORG Subject: How to stay tuned with 2.2 stable and CAM? X-Mailer: VM 6.47 under 20.4 "Emerald" XEmacs Lucid Reply-To: tomppa@fidata.fi Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have used CAM code with stable about two months now. Last time I upgraded to 2.2.7 and over that I installed CAM 19980716-SNAP. If I use cvsup to get latest stable I'll lose all modifications from source tree that CAM SNAP added there. If I run patches again it will complain about lot of CAM stuff that is already on the system. Is there any easy way to get these to work together? Tomppa -- SUN Microsystems Oy PL 102, Niittymentie 9, 02201 ESPOO, Finland Tomi Vainio (System Support Engineer) +358 9 52556300 hotline email: Tomi.Vainio@Sun.COM +358 9 52556252 fax To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 12 18:26:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA16286 for freebsd-scsi-outgoing; Wed, 12 Aug 1998 18:26:43 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA16253 for ; Wed, 12 Aug 1998 18:26:34 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id UAA00653 for ; Wed, 12 Aug 1998 20:24:45 -0400 (EDT) Date: Wed, 12 Aug 1998 20:24:45 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: FreeBSD-scsi@FreeBSD.ORG Subject: disk errors 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've formatted my new 4G IBM scsi disk, and I'm trying to copy the contents of an existing 2G disk onto it before moving the 2G disk out of the machine. During the copy, I got error messages that stopped the copy, and my /var/log shows: Aug 12 20:14:31 picnic /kernel: sd2: MEDIUM ERROR info:0x81007f asc:11,0 Unrecovered read error sks:80,33 Lot's of those errors, as the disk was retried lots of times. I tried redoing the copy, and the same error shows up. This is a new disk, and I've only disklabeled and newfs'ed it; is there any procedure I should have followed to detect and spare out any bad sectors? The controller's a NCR 875, and not yet running CAM. Thanks. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 12 18:45:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA18813 for freebsd-scsi-outgoing; Wed, 12 Aug 1998 18:45:37 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA18795 for ; Wed, 12 Aug 1998 18:45:35 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.8.8/8.8.5) with ESMTP id SAA01685; Wed, 12 Aug 1998 18:43:23 -0700 (PDT) Message-Id: <199808130143.SAA01685@dingo.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Chuck Robey cc: FreeBSD-scsi@FreeBSD.ORG Subject: Re: disk errors In-reply-to: Your message of "Wed, 12 Aug 1998 20:24:45 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 12 Aug 1998 18:43:23 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I've formatted my new 4G IBM scsi disk, and I'm trying to copy the > contents of an existing 2G disk onto it before moving the 2G disk out of > the machine. During the copy, I got error messages that stopped the > copy, and my /var/log shows: > > Aug 12 20:14:31 picnic /kernel: sd2: MEDIUM ERROR info:0x81007f asc:11,0 > Unrecovered read error sks:80,33 > > Lot's of those errors, as the disk was retried lots of times. I tried > redoing the copy, and the same error shows up. This is a new disk, and > I've only disklabeled and newfs'ed it; is there any procedure I should > have followed to detect and spare out any bad sectors? The controller's > a NCR 875, and not yet running CAM. See the SCSI(8) manpage for an example of editing mode page 1; set ARRE and AWRE to 1. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Wed Aug 12 19:11:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21127 for freebsd-scsi-outgoing; Wed, 12 Aug 1998 19:11:23 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA21118 for ; Wed, 12 Aug 1998 19:11:20 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id VAA00841; Wed, 12 Aug 1998 21:09:25 -0400 (EDT) Date: Wed, 12 Aug 1998 21:09:24 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: Mike Smith cc: FreeBSD-scsi@FreeBSD.ORG Subject: Re: disk errors In-Reply-To: <199808130143.SAA01685@dingo.cdrom.com> 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 Wed, 12 Aug 1998, Mike Smith wrote: > > I've formatted my new 4G IBM scsi disk, and I'm trying to copy the > > contents of an existing 2G disk onto it before moving the 2G disk out of > > the machine. During the copy, I got error messages that stopped the > > copy, and my /var/log shows: > > > > Aug 12 20:14:31 picnic /kernel: sd2: MEDIUM ERROR info:0x81007f asc:11,0 > > Unrecovered read error sks:80,33 > > > > Lot's of those errors, as the disk was retried lots of times. I tried > > redoing the copy, and the same error shows up. This is a new disk, and > > I've only disklabeled and newfs'ed it; is there any procedure I should > > have followed to detect and spare out any bad sectors? The controller's > > a NCR 875, and not yet running CAM. > > See the SCSI(8) manpage for an example of editing mode page 1; set ARRE > and AWRE to 1. OK, did that, but they were already set to 1. I still get those errors, so if that ARRE and AWRE set to 1 means that the sectors should be automatically spared out, it's either not happening or maybe there isn't enough bad sector space? Or maybe I formatted it wrong. I did a disklabel, and then a newfs, before mounting it. Is there any kind of surface scan thing, like I've seen from the software provided by other controllers? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 13 06:24:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA27601 for freebsd-scsi-outgoing; Thu, 13 Aug 1998 06:24:50 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from picnic.mat.net (picnic.mat.net [209.118.174.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA27594 for ; Thu, 13 Aug 1998 06:24:46 -0700 (PDT) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id IAA01650 for ; Thu, 13 Aug 1998 08:23:00 -0400 (EDT) Date: Thu, 13 Aug 1998 08:22:59 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@picnic.mat.net To: FreeBSD-SCSI@FreeBSD.ORG Subject: SCSI standard 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 think I need to read the scsi standard in order to figure out how to get scsi(8) to do what I need it to do. I've found a place to get a lot of scsi standards on the net, but there's too many of them, I don't know the name of the one I would really need. Does anyone know either the title or numerical designation of the relevant scsi standard that I'd need to be able to manipulate my wide/fast drive with? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic (FreeBSD-current) (301) 220-2114 | and jaunt (NetBSD). ----------------------------+----------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 13 08:16:31 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA10361 for freebsd-scsi-outgoing; Thu, 13 Aug 1998 08:16:31 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pasebo.nnettown.or.jp (pasebo.nnettown.or.jp [202.229.198.14]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA10325; Thu, 13 Aug 1998 08:16:17 -0700 (PDT) (envelope-from sean@pasebo.nnet.ne.jp) Received: from J ([202.229.198.156]) by pasebo.nnettown.or.jp (8.9.1/3.5Wpl7-pasebo-97/08/31/18) with SMTP id AAA16504; Fri, 14 Aug 1998 00:13:39 +0900 (JST) Message-ID: <00b901bdc6ce$03be2ec0$9cc6e5ca@J.SeanBennett> From: "J. Sean Bennett" To: "The Hermit Hacker" , "Bruce Albrecht" Cc: , Subject: Re: Odd problems with -current... Date: Fri, 14 Aug 1998 00:13:43 +0900 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3115.0 X-Mimeole: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does it only happen when the drive has been inactive for awhile?? It could just be an energy saving mode of the drive, or your bios. Mine powers down if I leave the system on but inactive for awhile, and then spins up as I start working again. Sean sean@mail.nnet.ne.jp -----Original Message----- From: The Hermit Hacker To: Bruce Albrecht Cc: scsi@FreeBSD.ORG ; current@FreeBSD.ORG Date: August 12, 1998 11:02 AM Subject: Re: Odd problems with -current... >On Mon, 3 Aug 1998, Bruce Albrecht wrote: > >> The Hermit Hacker writes: >> > I'm trying to debug a problem that I'm having on my home machine >> > that has me totally baffled, and am hoping someone here can "show me the >> > way"... >> > >> > I just put in a 2gig Seagate SCSI drive on my system, to replace a >> > 2gig IDE drive, and after running for awhile, it *seems* that the drive is >> > powering down, cause when I try to access something on that drive after >> > leaving for a period of time, you can hear it power back up again. >> >> Are you sure that it's not powering down because it's overheating? >> I've got a couple of Hawk drives that shut down until I added extra fans. > >I'm not certain of anything right now, but I've got a larger email to send >later tonight with, what I hope, is alot more detail... > >Marc G. Fournier >Systems Administrator @ hub.org >primary: scrappy@hub.org secondary: scrappy@{freebsd|postgresql}.org > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-current" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 13 09:04:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA17820 for freebsd-scsi-outgoing; Thu, 13 Aug 1998 09:04:21 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from tbuswell.ne.mediaone.net (tbuswell.ne.mediaone.net [24.128.24.62]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA17815 for ; Thu, 13 Aug 1998 09:04:19 -0700 (PDT) (envelope-from tbuswell@tbuswell.ne.mediaone.net) Received: (from tbuswell@localhost) by tbuswell.ne.mediaone.net (8.9.1/8.8.8) id MAA02331; Thu, 13 Aug 1998 12:03:12 -0400 (EDT) (envelope-from tbuswell) From: Ted Buswell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 13 Aug 1998 12:03:12 -0400 (EDT) To: Chuck Robey Cc: FreeBSD-SCSI@FreeBSD.ORG Subject: Re: SCSI standard In-Reply-To: References: X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <13779.3034.474689.856976@tbuswell.ne.mediaone.net> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Chuck Robey writes: > Does anyone know either the title or numerical designation of the > relevant scsi standard that I'd need to be able to manipulate my > wide/fast drive with? Probably the SCSI Primary Commands [SPC or SPC-2] and the SCSI Block Commands [SBC] sections are what you are looking for. Go to http://www.symbios.com/x3t10/ and look at the command sets to get final drafts of the above documents. Also, your drive manufacturer may have published a detailed manual [the one for a quantum drive I have is more than 100 pages] which shows exactly what commands are supported by the drive and how the drive responds. -Ted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 13 09:30:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21338 for freebsd-scsi-outgoing; Thu, 13 Aug 1998 09:30:00 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles250.castles.com [208.214.165.250]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21329 for ; Thu, 13 Aug 1998 09:29:56 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA00449; Thu, 13 Aug 1998 09:27:59 -0700 (PDT) Message-Id: <199808131627.JAA00449@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Chuck Robey cc: Mike Smith , FreeBSD-scsi@FreeBSD.ORG Subject: Re: disk errors In-reply-to: Your message of "Wed, 12 Aug 1998 21:09:24 EDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 13 Aug 1998 09:27:59 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > On Wed, 12 Aug 1998, Mike Smith wrote: > > > > I've formatted my new 4G IBM scsi disk, and I'm trying to copy the > > > contents of an existing 2G disk onto it before moving the 2G disk out of > > > the machine. During the copy, I got error messages that stopped the > > > copy, and my /var/log shows: > > > > > > Aug 12 20:14:31 picnic /kernel: sd2: MEDIUM ERROR info:0x81007f asc:11,0 > > > Unrecovered read error sks:80,33 > > > > > > Lot's of those errors, as the disk was retried lots of times. I tried > > > redoing the copy, and the same error shows up. This is a new disk, and > > > I've only disklabeled and newfs'ed it; is there any procedure I should > > > have followed to detect and spare out any bad sectors? The controller's > > > a NCR 875, and not yet running CAM. > > > > See the SCSI(8) manpage for an example of editing mode page 1; set ARRE > > and AWRE to 1. > > OK, did that, but they were already set to 1. I still get those errors, > so if that ARRE and AWRE set to 1 means that the sectors should be > automatically spared out, it's either not happening or maybe there isn't > enough bad sector space? You won't get a reallocation on an unrecovered read error; you'll have to arrange a write to it first. The best way to do this is just 'dd' over the whole disk. > Or maybe I formatted it wrong. I did a disklabel, and then a newfs, > before mounting it. Is there any kind of surface scan thing, like I've > seen from the software provided by other controllers? See above. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ 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 Thu Aug 13 10:04:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28050 for freebsd-scsi-outgoing; Thu, 13 Aug 1998 10:04:00 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA27983 for ; Thu, 13 Aug 1998 10:03:34 -0700 (PDT) (envelope-from ckempf@singularity.enigami.com) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id NAA04274; Thu, 13 Aug 1998 13:03:00 -0400 (EDT) To: Chuck Robey , freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI standard References: X-Copyright: Copyright (C) 1998 Cory Kempf. All Rights Reserved X-PGP-Fingerprint: 191E 2FB7 E27D 76C3 8E79 4D26 2B3B B20F 2A9C 1E1A X-PGP-Keyloc: ; finger ckempf@enigami.com From: Cory Kempf Date: 13 Aug 1998 13:02:59 -0400 In-Reply-To: Chuck Robey's message of "Thu, 13 Aug 1998 08:22:59 -0400 (EDT)" Message-ID: Lines: 22 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Chuck" == Chuck Robey writes: > I think I need to read the scsi standard in order to figure out how > to get scsi(8) to do what I need it to do. I've found a place to > get a lot of scsi standards on the net, but there's too many of > them, I don't know the name of the one I would really need. Rather than read the actual standard, which is pretty obtuse, you might want to check out the ENDL books... They are expensive, but I find that they make it much easier to locate the stuff you need. I will try and dig up my copy tonight and post contact information. It is Endl publications, somewhere in California, I think (area code 415, if memory serves). +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 13 11:06:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA10495 for freebsd-scsi-outgoing; Thu, 13 Aug 1998 11:06:07 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral.com (gw100.feral.com [192.67.166.129]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA10449 for ; Thu, 13 Aug 1998 11:06:05 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral.com (8.8.6/8.8.6) with SMTP id LAA23629; Thu, 13 Aug 1998 11:04:59 -0700 Date: Thu, 13 Aug 1998 11:04:59 -0700 (PDT) From: Matthew Jacob X-Sender: mjacob@feral-gw To: Cory Kempf cc: Chuck Robey , freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI standard In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 13 Aug 1998, Cory Kempf wrote: > "Chuck" == Chuck Robey writes: > > I think I need to read the scsi standard in order to figure out how > > to get scsi(8) to do what I need it to do. I've found a place to > > get a lot of scsi standards on the net, but there's too many of > > them, I don't know the name of the one I would really need. > > Rather than read the actual standard, which is pretty obtuse, you > might want to check out the ENDL books... They are expensive, but I > find that they make it much easier to locate the stuff you need. Obtuse? Personally I believe that they are models of clarity. > > I will try and dig up my copy tonight and post contact information. > It is Endl publications, somewhere in California, I think (area code > 415, if memory serves). > See http://www.symbios.com/t10 for the PDF files for the latest specifications for SCSI (and others- I think everyone owes Symbios a rising cheer of thanks for keeping this website- it's too bad I don't like the SCRIPTS architecture of their SCSI chips- otherwise I would think they were a *completely* cool company). I have, in the past, paid up to 450$ to Global Engineering Documents for the officially approved specifications- these are free and, if not 'official', so close as to make little never minds. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 13 12:59:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA00620 for freebsd-scsi-outgoing; Thu, 13 Aug 1998 12:59:08 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from itsdsv1.enc.edu (fw1.enc.edu [207.95.42.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA00605 for ; Thu, 13 Aug 1998 12:58:59 -0700 (PDT) (envelope-from owensc@enc.edu) Received: from itsdsv2.enc.edu (itsdsv2.enc.edu [10.1.1.9]) by itsdsv1.enc.edu (8.7.5/8.7.3) with SMTP id PAA17023; Thu, 13 Aug 1998 15:56:33 -0400 (EDT) Date: Thu, 13 Aug 1998 15:56:33 -0400 (EDT) From: Charles Owens Reply-To: Charles Owens To: shimon@simon-shapiro.org cc: freebsd-scsi@FreeBSD.ORG Subject: DPT management binaries for FreeBSD? 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 Simon, I looked under ftp://ftp.simon-shapiro.org/crash/tools and noted a number of FreeBSD binaries with names like "dtp_dm". Could this per chance be the native mgmt software that Tom is talking about below? If so, do I need a /dev/dpt? How can a make one (/dev/MAKEDEV doesn't know anything about it, of course)? I'm running 2.2.6 at the moment, BTW. Thanks much, Charles **** pulled from freebsd-scsi archive : From: Tom To: Geoff Buckingham Subject: Re: DPT storage manager On Mon, 11 May 1998, Geoff Buckingham wrote: > Having noticed the beta version of the DPT storage management software > for BSDI is infact the SCO binary running under emulation. I was wondering if > anyone had tried to get this working under FreeBSD? Well, the Unix Storage Manager apparently works by reading and writing commands to /dev/dpt If you check the archives, Simon posted a way you could send a command to /dev/dtp, and then use cat to display the result. I don't know if the driver has a complete command interface though. I understand that Simon is working on a native FreeBSD storage manager. DPT has apparently given him the code to do the port. > -- > GeoffB Tom --- ------------------------------------------------------------------------- Charles N. Owens Email: owensc@enc.edu http://www.enc.edu/~owensc Network & Systems Administrator Information Technology Services "Outside of a dog, a book is a man's Eastern Nazarene College best friend. Inside of a dog it's too dark to read." - Groucho Marx ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 13 16:03:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA05542 for freebsd-scsi-outgoing; Thu, 13 Aug 1998 16:03:57 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mersey.nt.tas.gov.au (mersey.nt.tas.gov.au [147.109.247.186]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA05531 for ; Thu, 13 Aug 1998 16:03:51 -0700 (PDT) (envelope-from sdd@ntccc.tas.gov.au) Received: from pc62 (pc62.ntccc.tas.gov.au [147.109.247.187]) by mersey.nt.tas.gov.au (8.8.7/8.8.7) with SMTP id HAA22516; Fri, 14 Aug 1998 07:08:16 +1000 (EST) (envelope-from sdd@ntccc.tas.gov.au) Message-Id: <3.0.5.32.19980814085925.009c93f0@mersey.nt.tas.gov.au> X-Sender: sdd@mersey.nt.tas.gov.au X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Fri, 14 Aug 1998 08:59:25 +1000 To: Charles Owens From: Scott Donovan Subject: Re: DPT management binaries for FreeBSD? Cc: freebsd-scsi@FreeBSD.ORG In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I'm running 2.2.6 at the moment, BTW. From memory the driver wasn't included until 2.2.7 :-( To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 13 18:33:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25684 for freebsd-scsi-outgoing; Thu, 13 Aug 1998 18:33:12 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from orion.aye.net (orion.aye.net [206.185.8.9]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id SAA25667 for ; Thu, 13 Aug 1998 18:33:03 -0700 (PDT) (envelope-from rabtter@orion.aye.net) Received: (qmail 1965 invoked by uid 3759); 14 Aug 1998 01:33:45 -0000 Date: Thu, 13 Aug 1998 21:33:45 -0400 (EDT) From: "B. Richardson" To: freebsd-scsi@FreeBSD.ORG Subject: ncr:2: ERROR (0:18) 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 am jinxed. I fought the "Timed out while idle" with and adaptec 3940 for a month and finally ditched it a day before Justin posted the sequencer file and got a Diamond Fireport 40. Played with termination/cables for weeks with a 2.2 6/29 snapshot. Reinstalled 2.2.5 (had a CD handy) with the Diamond Fireport 40, ran some bonnie test for a few hours, and put my cacheing server live today. After about 8 hours this happens (chunks of dmesg output below). Lovely error message is after Drives/controllers. ------------- Drives/controllers -------------------------- ncr0 rev 4 int a irq 9 on pci0:4 ncr0 waiting for scsi devices to settle (ncr0:1:0): "SEAGATE ST15230W SUN4.2G 0738" type 0 fixed SCSI 2 sd0(ncr0:1:0): Direct-Access sd0(ncr0:1:0): WIDE SCSI (16 bit) enabled sd0(ncr0:1:0): 20.0 MB/s (100 ns, offset 15) 4095MB (8386733 512 byte sectors) (ncr0:2:0): "QUANTUM VIKING 4.5 SCA 880R" type 0 fixed SCSI 2 sd1(ncr0:2:0): Direct-Access sd1(ncr0:2:0): WIDE SCSI (16 bit) enabled sd1(ncr0:2:0): 40.0 MB/s (50 ns, offset 16) 4345MB (8899737 512 byte sectors) ahc0 rev 3 int a irq 11 on pci0:5 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "SEAGATE ST15230W SUN4.2G 0738" type 0 fixed SCSI 2 sd2(ahc0:0:0): Direct-Access 4095MB (8386733 512 byte sectors) ------- Lovely error message ------------ ncr0:2: ERROR (0:18) (1-21-302) (10/9d) @ (script 6cc:19000000). ncr0: script cmd = 89030000 ncr0: regdump: da 10 80 9d 47 10 02 0f 03 01 82 21 80 00 01 19. ncr0: have to clear fifos. ncr0: restart (fatal error). sd1(ncr0:2:0): COMMAND FAILED (9 ff) @f0eac400. ncr0: timeout ccb=f0eac400 (skip) ncr0: timeout ccb=f0eac800 (skip) - Barrett Richardson rabtter@orion.aye.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 13 19:38:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA04997 for freebsd-scsi-outgoing; Thu, 13 Aug 1998 19:38:09 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id TAA04992 for ; Thu, 13 Aug 1998 19:38:07 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0z79CX-0001cm-00; Thu, 13 Aug 1998 19:02:45 -0700 Date: Thu, 13 Aug 1998 19:02:44 -0700 (PDT) From: Tom To: Scott Donovan cc: Charles Owens , freebsd-scsi@FreeBSD.ORG Subject: Re: DPT management binaries for FreeBSD? In-Reply-To: <3.0.5.32.19980814085925.009c93f0@mersey.nt.tas.gov.au> 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 Fri, 14 Aug 1998, Scott Donovan wrote: > >I'm running 2.2.6 at the moment, BTW. > > From memory the driver wasn't included until 2.2.7 :-( Not included, but available. Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Aug 13 22:27:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA22935 for freebsd-scsi-outgoing; Thu, 13 Aug 1998 22:27:28 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from misery.sdf.com (misery.sdf.com [204.244.213.49]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id WAA22895 for ; Thu, 13 Aug 1998 22:27:12 -0700 (PDT) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.82 #3) id 0z7Bq2-0001ic-00; Thu, 13 Aug 1998 21:51:42 -0700 Date: Thu, 13 Aug 1998 21:51:40 -0700 (PDT) From: Tom To: Charles Owens cc: shimon@simon-shapiro.org, freebsd-scsi@FreeBSD.ORG Subject: Re: DPT management binaries for FreeBSD? In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 13 Aug 1998, Charles Owens wrote: > Simon, > > I looked under ftp://ftp.simon-shapiro.org/crash/tools and noted > a number of FreeBSD binaries with names like "dtp_dm". Could this per > chance be the native mgmt software that Tom is talking about below? Lets be clear, I didn't say that this software existed yet. I don't know that it does exist, just that Simon is working on it. > If so, do I need a /dev/dpt? How can a make one (/dev/MAKEDEV doesn't > know anything about it, of course)? This was documented in the original dpt patch files. It might be in the archive. You can actually cat some commands into the /dev/dpt device and get back some info. > I'm running 2.2.6 at the moment, BTW. > > Thanks much, > > Charles Tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 14 06:08:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA21909 for freebsd-scsi-outgoing; Fri, 14 Aug 1998 06:08:04 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from singularity.enigami.com (singularity.enigami.com [208.140.182.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA21854 for ; Fri, 14 Aug 1998 06:08:00 -0700 (PDT) (envelope-from ckempf@singularity.enigami.com) Received: (from ckempf@localhost) by singularity.enigami.com (8.9.1/8.9.1) id JAA12354; Fri, 14 Aug 1998 09:07:25 -0400 (EDT) To: Chuck Robey , freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI standard References: X-Copyright: Copyright (C) 1998 Cory Kempf. All Rights Reserved X-PGP-Fingerprint: 191E 2FB7 E27D 76C3 8E79 4D26 2B3B B20F 2A9C 1E1A X-PGP-Keyloc: ; finger ckempf@enigami.com From: Cory Kempf Date: 14 Aug 1998 09:07:25 -0400 In-Reply-To: Chuck Robey's message of "Thu, 13 Aug 1998 08:22:59 -0400 (EDT)" Message-ID: Lines: 16 X-Mailer: Gnus v5.5/XEmacs 20.4 - "Emerald" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The info on ENDL: ENDL Publications 14426 Black Walnut Court Saratoga, CA 95070 408 741 1600 +C -- Thinking of purchasing RAM from the Chip Merchant? Please read this first: Cory Kempf Macintosh / Unix Consulting & Software Development ckempf@enigami.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 14 20:05:07 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA07747 for freebsd-scsi-outgoing; Fri, 14 Aug 1998 20:05:07 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from nomis.simon-shapiro.org (nomis.simon-shapiro.org [209.86.126.163]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id UAA07739 for ; Fri, 14 Aug 1998 20:05:02 -0700 (PDT) (envelope-from shimon@simon-shapiro.org) Received: (qmail 3615 invoked by uid 1000); 15 Aug 1998 04:07:04 -0000 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Sat, 15 Aug 1998 00:07:04 -0400 (EDT) Reply-To: shimon@simon-shapiro.org Organization: The Simon Shapiro Foundation From: Simon Shapiro To: Charles Owens Subject: RE: DPT management binaries for FreeBSD? Cc: freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 13-Aug-98 Charles Owens wrote: > Simon, > > I looked under ftp://ftp.simon-shapiro.org/crash/tools and noted > a number of FreeBSD binaries with names like "dtp_dm". Could this per > chance be the native mgmt software that Tom is talking about below? > > If so, do I need a /dev/dpt? How can a make one (/dev/MAKEDEV doesn't > know anything about it, of course)? These will not work in 2.2, only in 3.0-current; Too much retrofitting for what is considered a stable version of the O/S. Simon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 15 13:33:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA08000 for freebsd-scsi-outgoing; Sat, 15 Aug 1998 13:33:01 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA07979; Sat, 15 Aug 1998 13:32:51 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id WAA02559; Sat, 15 Aug 1998 22:32:16 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id AAA01640; Sat, 15 Aug 1998 00:08:22 +0200 (CEST) X-Face: " Date: Sat, 15 Aug 1998 00:08:22 +0200 From: Stefan Esser To: "B. Richardson" , freebsd-scsi@FreeBSD.ORG Cc: Stefan Esser Subject: Re: ncr:2: ERROR (0:18) References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.1i In-Reply-To: ; from B. Richardson on Thu, Aug 13, 1998 at 09:33:45PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1998-08-13 21:33 -0400, "B. Richardson" wrote: > > I am jinxed. I fought the "Timed out while idle" with and adaptec 3940 > for a month and finally ditched it a day before Justin posted the > sequencer file and got a Diamond Fireport 40. Played with > termination/cables for weeks with a 2.2 6/29 snapshot. Reinstalled > 2.2.5 (had a CD handy) with the Diamond Fireport 40, ran some > bonnie test for a few hours, and put my cacheing server live today. > After about 8 hours this happens (chunks of dmesg output below). > Lovely error message is after Drives/controllers. > ------- Lovely error message ------------ > > ncr0:2: ERROR (0:18) (1-21-302) (10/9d) @ (script 6cc:19000000). SIST = 0x18 => Gross Error + Reselected by Another Device The "Gross Error" condition is what caused the transfer to fail. Seems there is some electrical problem, or the Viking violates the SCSI protocol. The conditions that set the Gross Error bit in the SCSI Interrupt Status Register are: 1) Data Underflow (more data requested by target than available) 2) Data Overflow (more data sent by target than expected) 3) Offset Underflow ([target mode only, does not apply]) 4) Offset Overflow (target exceeded max. sync. offset) 5) Phase Change (with outstanding synchronous offset) 6) Residual data (data left over in sync. FIFO) All these conditions are most probably caused by a lost REQ or ACK. In order to exclude case 4) you could try patching the NCR driver to negotiate a lower "offset". The bus phase seems to have been DATA IN, which corresponds to the NCR command "MOVE TABLE" with DATA IN bus phase (0x19000000). Everything I see indicates, that there is handshake problem on the SCSI bus. Regards, STefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 15 14:40:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA16949 for freebsd-scsi-outgoing; Sat, 15 Aug 1998 14:40:39 -0700 (PDT) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA16937; Sat, 15 Aug 1998 14:40:35 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id PAA00545; Sat, 15 Aug 1998 15:34:16 -0600 (MDT) Date: Sat, 15 Aug 1998 15:34:16 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199808152134.PAA00545@narnia.plutotech.com> To: Stefan Esser cc: scsi@FreeBSD.ORG Subject: Re: ncr:2: ERROR (0:18) Newsgroups: pluto.freebsd.scsi In-Reply-To: <19980815000822.A1587@mi.uni-koeln.de> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > 1) Data Underflow (more data requested by target than available) > 2) Data Overflow (more data sent by target than expected) Most SCSI texts I've seen would characterize both of these conditions as an "Overflow". An underflow usually means that the target did not transfer the full data length, and there is a transfer residual. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message