From owner-freebsd-scsi Sun Aug 5 22:29:33 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from angryfist.fasttrackmonkey.com (angryfist.fasttrackmonkey.com [216.223.217.166]) by hub.freebsd.org (Postfix) with ESMTP id E269137B403 for ; Sun, 5 Aug 2001 22:29:30 -0700 (PDT) (envelope-from spork@fasttrackmonkey.com) Received: (qmail 4644 invoked by uid 89); 6 Aug 2001 05:24:13 -0000 Message-ID: <20010806052413.4643.qmail@angryfist.fasttrackmonkey.com> References: <200108042029.f74KTHQ00927@mass.dis.org> In-Reply-To: <200108042029.f74KTHQ00927@mass.dis.org> From: freebsd@fasttrackmonkey.com To: Mike Smith Cc: freebsd@fasttrackmonkey.com, freebsd-scsi@freebsd.org Subject: Re: Good Raid Controller? - AMI megaraid 428 Date: Mon, 06 Aug 2001 05:24:13 GMT Mime-Version: 1.0 Content-Type: text/plain; format=flowed; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Mike Smith writes: >> Steal or not? Anyone using this controller? Happy with it? > > They're nothing much to write home about. Ok, but not a great bargain, or > a real performance monster. If you have a bunch of older disks that you > want to RAID up, go for it. For newer stuff (eg. Ultra/Wide or later), > that controller will be a bit of a weak link. OK, just one more, and then I'll leave all of you alone... http://shopping.instaorder.com/servlet/teamx?cart=zzzzzzzzzzzz&dept=controll ers&item=H-AD-AAC364&action=itemdetail This is an Adaptec 4 channel, 64 bit PCI card @$249. Has the pricing on RAID controllers dropped THAT much since I last shopped? Are there any particular mid-level favorites right now? I've got a slew of different controllers installed, A CRD-540 SCSI-SCSI, the old Mylex SCSI-SCSI full-height boxes, Mylex DAC-960 cards, and an Adaptec 320P. I would love to standardize on something, as it's my understanding that if the controller fails, you have to use the same controller to replace it. Sparing all of these is getting silly. Thanks, CS > -- > ... every activity meets with opposition, everyone who acts has his > rivals and unfortunately opponents also. But not because people want > to be opponents, rather because the tasks and relationships force > people to take different points of view. [Dr. Fritz Todt] > V I C T O R Y N O T V E N G E A N C E > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Aug 5 23:15:48 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from puyu.time.net.my (pop.time.net.my [203.121.16.80]) by hub.freebsd.org (Postfix) with SMTP id 5DBFA37B401 for ; Sun, 5 Aug 2001 23:15:41 -0700 (PDT) (envelope-from ttj@dns.kutu.net) Received: (qmail 52852 invoked from network); 6 Aug 2001 05:52:27 -0000 Received: from unknown (HELO Asgard) (203.121.5.159) by 203.121.16.91 with SMTP; 6 Aug 2001 05:52:27 -0000 Message-ID: <001501c11e3e$ed741d20$07db728c@Asgard> From: "Tan Tek Jau @ Kutu" To: Subject: [Problem] SCSI Parity Error Date: Mon, 6 Aug 2001 14:07:25 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, My server encounter a big problem (seems like Adaptec SCSI parity problem) in this morning :- (da0:ahc0:0:0:0): parity error during Data-In phase. SEQADDR == 0x5d SCSIRATE == 0x93 (da0:ahc0:0:0:0): parity error during Data-In phase. SEQADDR == 0x5d SCSIRATE == 0x93 (da0:ahc0:0:0:0): parity error during Data-In phase. SEQADDR == 0x5e SCSIRATE == 0x93 (da0:ahc0:0:0:0): parity error during Data-In phase. SEQADDR == 0x5d SCSIRATE == 0x93 ------------------------------------- Aug 6 08:03:36 dns /kernel: (da0:ahc0:0:0:0): WRITE(10). CDB: 2a 0 0 4f 77 5f 0 0 a 0 Aug 6 08:03:36 dns /kernel: (da0:ahc0:0:0:0): ABORTED COMMAND asc:47,0 Aug 6 08:03:36 dns /kernel: (da0:ahc0:0:0:0): SCSI parity error field replaceable unit: 3 Aug 6 08:03:36 dns /kernel: (da0:ahc0:0:0:0): WRITE(10). CDB: 2a 0 0 4f 77 5f 0 0 a 0 Aug 6 08:03:36 dns /kernel: (da0:ahc0:0:0:0): ABORTED COMMAND asc:47,0 Aug 6 08:03:36 dns /kernel: (da0:ahc0:0:0:0): SCSI parity error field replaceable unit: 3 using dmesg :- ahc0: rev 0x00 int a irq 10 on pci0.9.0 ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs Could anyone help me or tell me what to do ? I have unplug all cable and reconnect it properly to my only SCSI harddrive, and make sure all connection and cable is OK. I'm wondering if this is caused by aic7xxx (as I found the similar problem from some newsgroups) and would it be solved if I change to Tekram SCSI adapter ? Your fast reply will be appreciated. Thank you very much. regards, TTJ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Aug 5 23:21:58 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.dis.org (mass.dis.org [216.240.45.41]) by hub.freebsd.org (Postfix) with ESMTP id 7AEDE37B401 for ; Sun, 5 Aug 2001 23:21:55 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f766Of001063; Sun, 5 Aug 2001 23:24:41 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200108060624.f766Of001063@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: freebsd@fasttrackmonkey.com Cc: freebsd-scsi@freebsd.org Subject: Re: Good Raid Controller? - AMI megaraid 428 In-reply-to: Your message of "Mon, 06 Aug 2001 05:24:13 GMT." <20010806052413.4643.qmail@angryfist.fasttrackmonkey.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 05 Aug 2001 23:24:41 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Mike Smith writes: > > >> Steal or not? Anyone using this controller? Happy with it? > > > > They're nothing much to write home about. Ok, but not a great bargain, or > > a real performance monster. If you have a bunch of older disks that you > > want to RAID up, go for it. For newer stuff (eg. Ultra/Wide or later), > > that controller will be a bit of a weak link. > > OK, just one more, and then I'll leave all of you alone... > > http://shopping.instaorder.com/servlet/teamx?cart=zzzzzzzzzzzz&dept=controll > ers&item=H-AD-AAC364&action=itemdetail > > This is an Adaptec 4 channel, 64 bit PCI card @$249. > > Has the pricing on RAID controllers dropped THAT much since I last > shopped? No, this is just a controller that got dumped. It's an *excellent* unit at that price; it's really a high-end unit comparable with the AMI 1500 or the Mylex EXR2000. You'll want to talk to Scott Long, who now maintains the driver for these controllers, about getting the most recent firmware for it, or you can search Dell's website for firmware for the PERC 2/QC, which is the same card. > Are there any particular mid-level favorites right now? I've got a > slew of different controllers installed, A CRD-540 SCSI-SCSI, the old > Mylex SCSI-SCSI full-height boxes, Mylex DAC-960 cards, and an Adaptec 320P. > I would love to standardize on something, as it's my understanding that if > the controller fails, you have to use the same controller to replace it. Management tools are the gotcha. For that reason, though I'm less fond of the controller or driver, I tend to recommend the Adaptec ASR3200. Alternatively, consider ATA RAID and the 3ware cards. Regards, Mike -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Aug 7 21:12:33 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id EE44D37B403 for ; Tue, 7 Aug 2001 21:12:29 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id WAA50969; Tue, 7 Aug 2001 22:12:21 -0600 (MDT) (envelope-from ken) Date: Tue, 7 Aug 2001 22:12:21 -0600 From: "Kenneth D. Merry" To: "Tan Tek Jau @ Kutu" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: [Problem] SCSI Parity Error Message-ID: <20010807221221.A50944@panzer.kdm.org> References: <001501c11e3e$ed741d20$07db728c@Asgard> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <001501c11e3e$ed741d20$07db728c@Asgard>; from ttj@dns.kutu.net on Mon, Aug 06, 2001 at 02:07:25PM +0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, Aug 06, 2001 at 14:07:25 +0800, Tan Tek Jau @ Kutu wrote: > Hi, > My server encounter a big problem (seems like Adaptec SCSI parity problem) > in this morning :- > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x5d > SCSIRATE == 0x93 > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x5d > SCSIRATE == 0x93 > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x5e > SCSIRATE == 0x93 > (da0:ahc0:0:0:0): parity error during Data-In phase. > SEQADDR == 0x5d > SCSIRATE == 0x93 > ------------------------------------- > Aug 6 08:03:36 dns /kernel: (da0:ahc0:0:0:0): WRITE(10). CDB: 2a 0 0 4f 77 > 5f 0 0 a 0 > Aug 6 08:03:36 dns /kernel: (da0:ahc0:0:0:0): ABORTED COMMAND asc:47,0 > Aug 6 08:03:36 dns /kernel: (da0:ahc0:0:0:0): SCSI parity error field > replaceable unit: 3 > Aug 6 08:03:36 dns /kernel: (da0:ahc0:0:0:0): WRITE(10). CDB: 2a 0 0 4f 77 > 5f 0 0 a 0 > Aug 6 08:03:36 dns /kernel: (da0:ahc0:0:0:0): ABORTED COMMAND asc:47,0 > Aug 6 08:03:36 dns /kernel: (da0:ahc0:0:0:0): SCSI parity error field > replaceable unit: 3 > > using dmesg :- > ahc0: rev 0x00 int a irq 10 on pci0.9.0 > ahc0: aic7890/91 Wide Channel A, SCSI Id=7, 16/255 SCBs > > Could anyone help me or tell me what to do ? I have unplug all cable and > reconnect it properly to my only SCSI harddrive, and make sure all > connection and cable is OK. I'm wondering if this is caused by aic7xxx (as I > found the similar problem from some newsgroups) and would it be solved if I > change to Tekram SCSI adapter ? You almost certainly have a cabling or termination problem. I would suggest replacing the cable and make sure your bus is properly terminated. Also, make sure the cable isn't too close to the power supply. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Aug 8 4:41:47 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sevenislands.net (dialup-226-10.bol.net.in [203.94.226.10]) by hub.freebsd.org (Postfix) with ESMTP id 3A33837B409 for ; Wed, 8 Aug 2001 04:41:40 -0700 (PDT) (envelope-from rohitj@sevenislands.net) Received: (from rohitj@localhost) by sevenislands.net (8.11.4/8.11.4) id f78Bhgs01708; Wed, 8 Aug 2001 17:13:42 +0530 (IST) (envelope-from rohitj) Date: Wed, 8 Aug 2001 17:13:42 +0530 From: Rohit Jalan To: freebsd-scsi@freebsd.org Subject: Initio 1060 chipset - Driver Available Message-ID: <20010808171342.A1486@tintin.monet.prakashcotton.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Organisation: SevenIslands Consulting Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Greetings, A driver for the Initio 1060 U2W (LVD) SCSI chipset is now available. http://www.sevenislands.net/fbsd-initio I have tested this driver under FreeBSD 4.3 and FreeBSD 5.0 but not extensively, hence I suggest that people refrain from using this driver for mission critical work as yet. Rohit To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 10 17:10:15 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp012.mail.yahoo.com (smtp012.mail.yahoo.com [216.136.173.32]) by hub.freebsd.org (Postfix) with SMTP id 7848337B409 for ; Fri, 10 Aug 2001 17:10:12 -0700 (PDT) (envelope-from kc5vdj@yahoo.com) Received: from mkc-65-28-47-209.kc.rr.com (HELO yahoo.com) (65.28.47.209) by smtp.mail.vip.sc5.yahoo.com with SMTP; 11 Aug 2001 00:10:12 -0000 X-Apparently-From: Message-ID: <3B7477E3.81FC089C@yahoo.com> Date: Fri, 10 Aug 2001 19:10:11 -0500 From: Jim Bryant Reply-To: kc5vdj@yahoo.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: mjacob@feral.com Cc: Mike Tancsa , scsi@freebsd.org Subject: Re: SCSI timeout problems going from May23 to July13 kernel References: <20010716092359.F96667-100000@wonky.feral.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Matt, has any progress been made on EOT/EOM detection yet? I haven't tested this recently. Matthew Jacob wrote: > > Timeouts were lengthened, not shortened recently. This looks like it timed out > on the test read in samount...... that's a four (4) minute timeout. > > The tape driver is very broken in a lot of ways. > > Use the scsi_sa.c that's on my web page on freebsd.org > > (http://people.freebsd.org/~mjacob/scsi_sa.c) > > with a CAMDEBUG kernel that has camcontrol -Ic N:0:0 (you'll have to supply > the N for the ordinal bus number the tape is on) and ship me the output. > > -matt > > On Mon, 16 Jul 2001, Justin T. Gibbs wrote: > > > >Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): SCB 0x9 - timed out > > >while idle, SEQADDR == 0x8 > > > > ... > > > > >Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): Queuing a BDR SCB > > >Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): Bus Device Reset Message > > >Sent > > >Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): no longer in timeout, > > >status = 34b > > >Jul 16 09:31:20 backup2 /kernel: ahc0: Bus Device Reset on A:0. 1 SCBs aborted > > >Jul 16 09:31:21 backup2 /kernel: (sa0:ahc0:0:0:0): unable to rewind after > > >test read > > > > I wonder if the timeouts are now too short for your tape drive? Matt > > may have more ideas. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.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 10 17:20:26 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id D694837B407 for ; Fri, 10 Aug 2001 17:20:23 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f7B0KJI36476; Fri, 10 Aug 2001 17:20:19 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Fri, 10 Aug 2001 17:20:12 -0700 (PDT) From: Matthew Jacob Reply-To: To: Jim Bryant Cc: Mike Tancsa , Subject: Re: SCSI timeout problems going from May23 to July13 kernel In-Reply-To: <3B7477E3.81FC089C@yahoo.com> Message-ID: <20010810171111.A64952-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Mike's issue was with -stable. But that in fact *was* a valid timeout (DDS tape wierdness). In terms of EOT/EOM detection- FreeBSD-stable is okay. For FreeBSD-current I've done some work and things are a bit better, but I still: a) Don't handle fixed block mode correctly. b) Probably don't handle single eot model correctly. and, most annoying of all, there seems to be something of a discrepancy about amount of data actually written when early warning shows up. I've had at least one drive report a residual when early warning was detected when in fact it wrote the data- this caused my validation program to fail to check. I need about 4-5 full days more on this. I possibly should do a partial checkin if I can't get that done soon. I'm also waiting for another tape drive I bought on EBay (my 8505XL died, so I needed to get at least one reasonable Exabyte to test with). You're welcome to fool around with the current sa.. http://people.freebsd.org/~mjacob/scsi_sa.c -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 10 17:31:24 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp013.mail.yahoo.com (smtp013.mail.yahoo.com [216.136.173.57]) by hub.freebsd.org (Postfix) with SMTP id 6263B37B406 for ; Fri, 10 Aug 2001 17:31:15 -0700 (PDT) (envelope-from kc5vdj@yahoo.com) Received: from mkc-65-28-47-209.kc.rr.com (HELO yahoo.com) (65.28.47.209) by smtp.mail.vip.sc5.yahoo.com with SMTP; 11 Aug 2001 00:31:15 -0000 X-Apparently-From: Message-ID: <3B747CD2.A7F44851@yahoo.com> Date: Fri, 10 Aug 2001 19:31:14 -0500 From: Jim Bryant Reply-To: kc5vdj@yahoo.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: Matthew Jacob , Martin Aherron , freebsd-scsi@FreeBSD.ORG Subject: Re: what's wrong with this picture :-) References: <01Jul25.213803edt.119044@cyborg.cybernetics.com> <20010725200625.A44606@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org "Kenneth D. Merry" wrote: > > On Wed, Jul 25, 2001 at 18:47:19 -0700, Matthew Jacob wrote: > > > > On Wed, 25 Jul 2001, Martin Aherron wrote: > > > > > > > > > >yorp.feral.com > root camcontrol inquiry sa0 > > > >pass3: Removable Sequential Access SCSI-2 device > > > >pass3: Serial Number ZG61033226 > > > >pass3: 3.300MB/s transfers > > > > > > > >-matt > > > > > > > I'm kind of new to the Freebsd system but why would the pass thru device 3 > > > be providing information for sa0? > > > > ding > > ding > > ding > > ding > > ding > > ding! > > > > We have a winnah! > > That has been the case since day 1. The reason 'pass3' is providing the > information is because that's the peripheral driver you're talking to. > pass3 is the passthrough driver for that tape drive. > > > Very strange... it also is wierd becuase it also has the wrong transfer > > information too. > > See what has been negotiated: > > camcontrol negotiate sa0 -v > > should explain why it thinks the drive is async. My guess is that the sync > offset may be 0. I just did that for the heck of it myself, and came up with some interesting info on ahc0 and ahc1 (identical)... The 3.3 Meg/Sec thing isn't just for tape... FreeBSD 5.0-CURRENT #18: Fri Aug 10 16:51:25 CDT 2001 [cvsupped about 4am CST today] Tyan S1696-DLUA Mobo / 512M / Two Pentium-II/333's See the full dmesg output in the -current thread I'm about to post concerning ACPI tables not being found, boot_verbose was set. The SCSI timeouts have been "normal" here for a couple/few years. Everything comes up fine once it sorts itself out. Could the 3.3MB/Sec message be the reason I have thought that copies between drives have been slow, especially involving the 'Cuda? I haven't said anything about this up to now. ----------------------------- ahc0: port 0xe000-0xe0ff mem 0xfebfd000-0xfebfdfff irq 10 at device 15.0 on pci0 ahc0: Reading SEEPROM...checksum error ahc0: No SEEPROM available. ahc0: Using left over BIOS settings ahc0: External SRAM, fast access, 64bytes/SCB ahc0: Downloading Sequencer Program... 399 instructions downloaded (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. (probe5:ahc0:0:5:0): error 22 (probe5:ahc0:0:5:0): Unretryable Error (ahc0:A:5:0): Sending SDTR period 19, offset f (probe6:ahc0:0:6:0): error 22 (probe6:ahc0:0:6:0): Unretryable Error (ahc0:A:5:0): Received SDTR period 19, offset 8 ahc0: target 5 synchronous at 10.0MHz, offset = 0x8 (ahc0:A:6:0): Sending SDTR period c, offset f (ahc0:A:6:0): Received SDTR period c, offset f ahc0: target 6 synchronous at 20.0MHz, offset = 0xf (ahc0:A:5:0): Sending SDTR period 19, offset 8 (ahc0:A:5:0): Received SDTR period 19, offset 8 (ahc0:A:6:0): Sending SDTR period c, offset f (ahc0:A:6:0): Received SDTR period c, offset f pass0 at ahc0 bus 0 target 5 lun 0 pass1 at ahc0 bus 0 target 6 lun 0 sa0 at ahc0 bus 0 target 5 lun 0 (ahc0:A:6:0): Sending SDTR period c, offset f (ahc0:A:6:0): Received SDTR period c, offset f (cd0:ahc0:0:6:0): error 6 (cd0:ahc0:0:6:0): Unretryable Error cd0 at ahc0 bus 0 target 6 lun 0 ------ ahc1: port 0xec00-0xecff mem 0xfebff000-0xfebfffff irq 11 at device 15.1 on pci0 ahc1: Reading SEEPROM...checksum error ahc1: No SEEPROM available. ahc1: Using left over BIOS settings ahc1: External SRAM, fast access, 64bytes/SCB ahc1: Downloading Sequencer Program... 399 instructions downloaded (noperiph:ahc1:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. (probe15:ahc1:0:0:0): SCB 0x9 - timed out ahc1: Dumping Card State in Data-in phase, at SEQADDR 0x8e (probe15:ahc1:0:0:0): BDR message in message buffer (probe15:ahc1:0:0:0): SCB 0x9 - timed out ahc1: Dumping Card State in Data-in phase, at SEQADDR 0x8c (probe15:ahc1:0:0:0): no longer in timeout, status = 34b ahc1: Issued Channel A Bus Reset. 15 SCBs aborted (probe16:ahc1:0:1:0): Retrying Command (probe20:ahc1:0:5:0): Retrying Command (probe21:ahc1:0:6:0): Retrying Command (probe22:ahc1:0:8:0): Retrying Command (probe26:ahc1:0:12:0): Retrying Command (probe27:ahc1:0:13:0): Retrying Command (probe17:ahc1:0:2:0): Retrying Command (probe18:ahc1:0:3:0): Retrying Command (probe19:ahc1:0:4:0): Retrying Command (probe23:ahc1:0:9:0): Retrying Command (probe24:ahc1:0:10:0): Retrying Command (probe25:ahc1:0:11:0): Retrying Command (probe28:ahc1:0:14:0): Retrying Command (probe29:ahc1:0:15:0): Retrying Command (probe15:ahc1:0:0:0): Retrying Command (ahc1:A:0:0): Received WDTR 0 filtered to 0 (ahc1:A:0:0): Target Initiated WDTR (ahc1:A:0:0): Sending WDTR 0 (ahc1:A:0:0): Received SDTR period 19, offset f (ahc1:A:0:0): Target Initiated SDTR (ahc1:A:0:0): Sending SDTR period 0, offset 0 (probe15:ahc1:0:0:0): Retrying Command (probe15:ahc1:0:0:0): Retrying Command (probe15:ahc1:0:0:0): SCB 0x8 - timed out ahc1: Dumping Card State in Command phase, at SEQADDR 0x163 (probe15:ahc1:0:0:0): BDR message in message buffer (ahc1:A:0:0): Received SDTR period 19, offset f (ahc1:A:0:0): Target Initiated SDTR (ahc1:A:0:0): Sending SDTR period 0, offset 0 (probe15:ahc1:0:0:0): no longer in timeout, status = 300 (ahc1:A:0:0): Sending WDTR 1 (ahc1:A:0:0): Received WDTR 1 filtered to 1 ahc1: target 0 using 16bit transfers (ahc1:A:0:0): Sending SDTR period 19, offset 8 (ahc1:A:0:0): Received SDTR period 19, offset 8 ahc1: target 0 synchronous at 10.0MHz, offset = 0x8 pass2 at ahc1 bus 0 target 0 lun 0 da0 at ahc1 bus 0 target 0 lun 0 ----------------------------- Creating DISK da0 da0 at ahc1 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: Serial Number 00318200 da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled da0: 4094MB (8386000 512 byte sectors: 64H 32S/T 4094C) --------- 7:14:47pm wahoo(103): camcontrol negotiate da0 -v Current Parameters: (pass2:ahc1:0:0:0): sync parameter: 25 (pass2:ahc1:0:0:0): frequency: 10.000MHz (pass2:ahc1:0:0:0): offset: 8 (pass2:ahc1:0:0:0): bus width: 16 bits (pass2:ahc1:0:0:0): disconnection is enabled (pass2:ahc1:0:0:0): tagged queueing is enabled ahc1: SIM/HBA version: 1 ahc1: supports tag queue messages ahc1: supports SDTR message ahc1: supports 16 bit wide SCSI ahc1: HBA engine count: 0 ahc1: maximum target: 15 ahc1: maximum LUN: 63 ahc1: highest path ID in subsystem: 0 ahc1: initiator ID: 7 ahc1: SIM vendor: FreeBSD ahc1: HBA vendor: Adaptec ahc1: bus ID: 0 ahc1: base transfer speed: 3.300MB/sec ----------------------------- Creating DISK cd0 (cd0:ahc0:0:6:0): error 6 (cd0:ahc0:0:6:0): Unretryable Error cd0 at ahc0 bus 0 target 6 lun 0 cd0: Removable CD-ROM SCSI-2 device cd0: 20.000MB/s transfers (20.000MHz, offset 15) cd0: Attempt to query device size failed: NOT READY, Medium not present --------- 7:16:35pm wahoo(105): camcontrol negotiate cd0 -v Current Parameters: (pass1:ahc0:0:6:0): sync parameter: 12 (pass1:ahc0:0:6:0): frequency: 20.000MHz (pass1:ahc0:0:6:0): offset: 15 (pass1:ahc0:0:6:0): bus width: 8 bits (pass1:ahc0:0:6:0): disconnection is enabled (pass1:ahc0:0:6:0): tagged queueing is disabled ahc0: SIM/HBA version: 1 ahc0: supports tag queue messages ahc0: supports SDTR message ahc0: supports 16 bit wide SCSI ahc0: HBA engine count: 0 ahc0: maximum target: 15 ahc0: maximum LUN: 63 ahc0: highest path ID in subsystem: 0 ahc0: initiator ID: 7 ahc0: SIM vendor: FreeBSD ahc0: HBA vendor: Adaptec ahc0: bus ID: 0 ahc0: base transfer speed: 3.300MB/sec ----------------------------- sa0 at ahc0 bus 0 target 5 lun 0 sa0: Removable Sequential Access SCSI-2 device sa0: 10.000MB/s transfers (10.000MHz, offset 8) --------- 7:18:54pm wahoo(106): camcontrol negotiate sa0 -v Current Parameters: (pass0:ahc0:0:5:0): sync parameter: 25 (pass0:ahc0:0:5:0): frequency: 10.000MHz (pass0:ahc0:0:5:0): offset: 8 (pass0:ahc0:0:5:0): bus width: 8 bits (pass0:ahc0:0:5:0): disconnection is enabled (pass0:ahc0:0:5:0): tagged queueing is disabled ahc0: SIM/HBA version: 1 ahc0: supports tag queue messages ahc0: supports SDTR message ahc0: supports 16 bit wide SCSI ahc0: HBA engine count: 0 ahc0: maximum target: 15 ahc0: maximum LUN: 63 ahc0: highest path ID in subsystem: 0 ahc0: initiator ID: 7 ahc0: SIM vendor: FreeBSD ahc0: HBA vendor: Adaptec ahc0: bus ID: 0 ahc0: base transfer speed: 3.300MB/sec jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.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 10 17:47:37 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by hub.freebsd.org (Postfix) with ESMTP id 0B39437B405 for ; Fri, 10 Aug 2001 17:47:36 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from wonky.feral.com (wonky.feral.com [192.67.166.7]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id f7B0lUI36801; Fri, 10 Aug 2001 17:47:30 -0700 (PDT) (envelope-from mjacob@feral.com) Date: Fri, 10 Aug 2001 17:47:23 -0700 (PDT) From: Matthew Jacob Reply-To: To: Jim Bryant Cc: "Kenneth D. Merry" , Martin Aherron , Subject: Re: what's wrong with this picture :-) In-Reply-To: <3B747CD2.A7F44851@yahoo.com> Message-ID: <20010810174708.K64952-100000@wonky.feral.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org 3.3MB/s is the value for 'async' To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 10 18:31:22 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 4719C37B407 for ; Fri, 10 Aug 2001 18:31:16 -0700 (PDT) (envelope-from mike@sentex.net) Received: (from root@localhost) by cage.simianscience.com (8.11.5/8.11.5) id f7B1VEw25443; Fri, 10 Aug 2001 21:31:14 -0400 (EDT) (envelope-from mike@sentex.net) Received: from chimp.sentex.net (fcage [192.168.0.2]) by cage.simianscience.com (8.11.5/8.11.5av) with ESMTP id f7B1V1X25429; Fri, 10 Aug 2001 21:31:02 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <5.1.0.14.0.20010810212917.03450108@192.168.0.12> X-Sender: mdtancsa@192.168.0.12 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Fri, 10 Aug 2001 21:31:00 -0400 To: kc5vdj@yahoo.com, mjacob@feral.com From: Mike Tancsa Subject: Re: SCSI timeout problems going from May23 to July13 kernel Cc: scsi@freebsd.org In-Reply-To: <3B7477E3.81FC089C@yahoo.com> References: <20010716092359.F96667-100000@wonky.feral.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org At 07:10 PM 8/10/2001 -0500, Jim Bryant wrote: >Matt, has any progress been made on EOT/EOM detection yet? I haven't >tested this recently. Hi, I posted a follow up to this. The issue in the end was the tape drive not reliably detecting the density of a blank DDS3 tape in a DDS4 drive when switching tapes back and forth. I think its more of an issue with the hardware than the driver per se. ---Mike >Matthew Jacob wrote: > > > > Timeouts were lengthened, not shortened recently. This looks like it > timed out > > on the test read in samount...... that's a four (4) minute timeout. > > > > The tape driver is very broken in a lot of ways. > > > > Use the scsi_sa.c that's on my web page on freebsd.org > > > > (http://people.freebsd.org/~mjacob/scsi_sa.c) > > > > with a CAMDEBUG kernel that has camcontrol -Ic N:0:0 (you'll have to supply > > the N for the ordinal bus number the tape is on) and ship me the output. > > > > -matt > > > > On Mon, 16 Jul 2001, Justin T. Gibbs wrote: > > > > > >Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): SCB 0x9 - timed out > > > >while idle, SEQADDR == 0x8 > > > > > > ... > > > > > > >Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): Queuing a BDR SCB > > > >Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): Bus Device Reset > Message > > > >Sent > > > >Jul 16 09:31:20 backup2 /kernel: (sa0:ahc0:0:0:0): no longer in timeout, > > > >status = 34b > > > >Jul 16 09:31:20 backup2 /kernel: ahc0: Bus Device Reset on A:0. 1 > SCBs aborted > > > >Jul 16 09:31:21 backup2 /kernel: (sa0:ahc0:0:0:0): unable to rewind > after > > > >test read > > > > > > I wonder if the timeouts are now too short for your tape drive? Matt > > > may have more ideas. > >jim >-- >ET has one helluva sense of humor! >He's always anal-probing right-wing schizos! > >_________________________________________________________ >Do You Yahoo!? >Get your free @yahoo.com address at http://mail.yahoo.com -------------------------------------------------------------------- Mike Tancsa, tel +1 519 651 3400 Network Administration, mike@sentex.net Sentex Communications www.sentex.net Cambridge, Ontario Canada www.sentex.net/mike To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Aug 10 18:48:36 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id ACFD837B407 for ; Fri, 10 Aug 2001 18:48:23 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id TAA74490; Fri, 10 Aug 2001 19:48:07 -0600 (MDT) (envelope-from ken) Date: Fri, 10 Aug 2001 19:48:07 -0600 From: "Kenneth D. Merry" To: Jim Bryant Cc: Matthew Jacob , Martin Aherron , freebsd-scsi@FreeBSD.ORG Subject: Re: what's wrong with this picture :-) Message-ID: <20010810194807.A74472@panzer.kdm.org> References: <01Jul25.213803edt.119044@cyborg.cybernetics.com> <20010725200625.A44606@panzer.kdm.org> <3B747CD2.A7F44851@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3B747CD2.A7F44851@yahoo.com>; from kc5vdj@yahoo.com on Fri, Aug 10, 2001 at 07:31:14PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Fri, Aug 10, 2001 at 19:31:14 -0500, Jim Bryant wrote: > "Kenneth D. Merry" wrote: > > That has been the case since day 1. The reason 'pass3' is providing the > > information is because that's the peripheral driver you're talking to. > > pass3 is the passthrough driver for that tape drive. > > > > > Very strange... it also is wierd becuase it also has the wrong transfer > > > information too. > > > > See what has been negotiated: > > > > camcontrol negotiate sa0 -v > > > > should explain why it thinks the drive is async. My guess is that the sync > > offset may be 0. Watch your line lengths, you're going far over 80 columns. > I just did that for the heck of it myself, and came up with some interesting info on ahc0 and ahc1 (identical)... The 3.3 Meg/Sec > thing isn't just for tape... You're getting the base transfer speed for the bus confused with the actual negotiated transfer speed. 3.3MB/sec is async narrow SCSI, which is the baseline transfer speed for most SCSI controllers. The negotiated transfer speed is printed out when the device probes, and by camcontrol negotiate. > FreeBSD 5.0-CURRENT #18: Fri Aug 10 16:51:25 CDT 2001 [cvsupped about 4am CST today] Tyan S1696-DLUA Mobo / 512M / Two > Pentium-II/333's > > See the full dmesg output in the -current thread I'm about to post concerning ACPI tables not being found, boot_verbose was set. > > The SCSI timeouts have been "normal" here for a couple/few years. Everything comes up fine once it sorts itself out. I don't know why you're getting timeouts, Justin will probably have to comment when he gets back. > Could the 3.3MB/Sec message be the reason I have thought that copies between drives have been slow, especially involving the 'Cuda? > I haven't said anything about this up to now. > > ----------------------------- This looks normal: > ahc0: port 0xe000-0xe0ff mem 0xfebfd000-0xfebfdfff irq 10 at device 15.0 on pci0 > ahc0: Reading SEEPROM...checksum error > ahc0: No SEEPROM available. > ahc0: Using left over BIOS settings > ahc0: External SRAM, fast access, 64bytes/SCB > ahc0: Downloading Sequencer Program... 399 instructions downloaded > (noperiph:ahc0:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. > (probe5:ahc0:0:5:0): error 22 > (probe5:ahc0:0:5:0): Unretryable Error > (ahc0:A:5:0): Sending SDTR period 19, offset f > (probe6:ahc0:0:6:0): error 22 > (probe6:ahc0:0:6:0): Unretryable Error > (ahc0:A:5:0): Received SDTR period 19, offset 8 > ahc0: target 5 synchronous at 10.0MHz, offset = 0x8 > (ahc0:A:6:0): Sending SDTR period c, offset f > (ahc0:A:6:0): Received SDTR period c, offset f > ahc0: target 6 synchronous at 20.0MHz, offset = 0xf > (ahc0:A:5:0): Sending SDTR period 19, offset 8 > (ahc0:A:5:0): Received SDTR period 19, offset 8 > (ahc0:A:6:0): Sending SDTR period c, offset f > (ahc0:A:6:0): Received SDTR period c, offset f > pass0 at ahc0 bus 0 target 5 lun 0 > pass1 at ahc0 bus 0 target 6 lun 0 > sa0 at ahc0 bus 0 target 5 lun 0 > (ahc0:A:6:0): Sending SDTR period c, offset f > (ahc0:A:6:0): Received SDTR period c, offset f > (cd0:ahc0:0:6:0): error 6 > (cd0:ahc0:0:6:0): Unretryable Error > cd0 at ahc0 bus 0 target 6 lun 0 > > ------ This doesn't look normal, but it isn't clear what exactly is timing out. > ahc1: port 0xec00-0xecff mem 0xfebff000-0xfebfffff irq 11 at device 15.1 on pci0 > ahc1: Reading SEEPROM...checksum error > ahc1: No SEEPROM available. > ahc1: Using left over BIOS settings > ahc1: External SRAM, fast access, 64bytes/SCB > ahc1: Downloading Sequencer Program... 399 instructions downloaded > (noperiph:ahc1:0:-1:-1): SCSI bus reset delivered. 0 SCBs aborted. > (probe15:ahc1:0:0:0): SCB 0x9 - timed out > ahc1: Dumping Card State in Data-in phase, at SEQADDR 0x8e > (probe15:ahc1:0:0:0): BDR message in message buffer > (probe15:ahc1:0:0:0): SCB 0x9 - timed out > ahc1: Dumping Card State in Data-in phase, at SEQADDR 0x8c > (probe15:ahc1:0:0:0): no longer in timeout, status = 34b > ahc1: Issued Channel A Bus Reset. 15 SCBs aborted > (probe16:ahc1:0:1:0): Retrying Command > (probe20:ahc1:0:5:0): Retrying Command > (probe21:ahc1:0:6:0): Retrying Command > (probe22:ahc1:0:8:0): Retrying Command > (probe26:ahc1:0:12:0): Retrying Command > (probe27:ahc1:0:13:0): Retrying Command > (probe17:ahc1:0:2:0): Retrying Command > (probe18:ahc1:0:3:0): Retrying Command > (probe19:ahc1:0:4:0): Retrying Command > (probe23:ahc1:0:9:0): Retrying Command > (probe24:ahc1:0:10:0): Retrying Command > (probe25:ahc1:0:11:0): Retrying Command > (probe28:ahc1:0:14:0): Retrying Command > (probe29:ahc1:0:15:0): Retrying Command > (probe15:ahc1:0:0:0): Retrying Command > (ahc1:A:0:0): Received WDTR 0 filtered to 0 > (ahc1:A:0:0): Target Initiated WDTR > (ahc1:A:0:0): Sending WDTR 0 > (ahc1:A:0:0): Received SDTR period 19, offset f > (ahc1:A:0:0): Target Initiated SDTR > (ahc1:A:0:0): Sending SDTR period 0, offset 0 > (probe15:ahc1:0:0:0): Retrying Command > (probe15:ahc1:0:0:0): Retrying Command > (probe15:ahc1:0:0:0): SCB 0x8 - timed out > ahc1: Dumping Card State in Command phase, at SEQADDR 0x163 > (probe15:ahc1:0:0:0): BDR message in message buffer > (ahc1:A:0:0): Received SDTR period 19, offset f > (ahc1:A:0:0): Target Initiated SDTR > (ahc1:A:0:0): Sending SDTR period 0, offset 0 > (probe15:ahc1:0:0:0): no longer in timeout, status = 300 > (ahc1:A:0:0): Sending WDTR 1 > (ahc1:A:0:0): Received WDTR 1 filtered to 1 > ahc1: target 0 using 16bit transfers > (ahc1:A:0:0): Sending SDTR period 19, offset 8 > (ahc1:A:0:0): Received SDTR period 19, offset 8 > ahc1: target 0 synchronous at 10.0MHz, offset = 0x8 > pass2 at ahc1 bus 0 target 0 lun 0 > da0 at ahc1 bus 0 target 0 lun 0 > > ----------------------------- This looks normal. > Creating DISK da0 > da0 at ahc1 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: Serial Number 00318200 > da0: 20.000MB/s transfers (10.000MHz, offset 8, 16bit), Tagged Queueing Enabled > da0: 4094MB (8386000 512 byte sectors: 64H 32S/T 4094C) > > --------- As does this. > 7:14:47pm wahoo(103): camcontrol negotiate da0 -v > Current Parameters: > (pass2:ahc1:0:0:0): sync parameter: 25 Note the frequency, 10MHz: > (pass2:ahc1:0:0:0): frequency: 10.000MHz The offset of 8: > (pass2:ahc1:0:0:0): offset: 8 And the bus width: > (pass2:ahc1:0:0:0): bus width: 16 bits 10MHz * 2 bytes == 20MB/sec, thus the 20MB/sec transfer rate in the dmesg above. > (pass2:ahc1:0:0:0): disconnection is enabled > (pass2:ahc1:0:0:0): tagged queueing is enabled > ahc1: SIM/HBA version: 1 > ahc1: supports tag queue messages > ahc1: supports SDTR message > ahc1: supports 16 bit wide SCSI > ahc1: HBA engine count: 0 > ahc1: maximum target: 15 > ahc1: maximum LUN: 63 > ahc1: highest path ID in subsystem: 0 > ahc1: initiator ID: 7 > ahc1: SIM vendor: FreeBSD > ahc1: HBA vendor: Adaptec > ahc1: bus ID: 0 This is your *base* transfer speed: > ahc1: base transfer speed: 3.300MB/sec > > ----------------------------- > > Creating DISK cd0 It's kinda odd that you aren't getting any more error messages other than "error 6". > (cd0:ahc0:0:6:0): error 6 > (cd0:ahc0:0:6:0): Unretryable Error Again, this is normal: > cd0 at ahc0 bus 0 target 6 lun 0 > cd0: Removable CD-ROM SCSI-2 device > cd0: 20.000MB/s transfers (20.000MHz, offset 15) > cd0: Attempt to query device size failed: NOT READY, Medium not present > > --------- This is normal: > 7:16:35pm wahoo(105): camcontrol negotiate cd0 -v > Current Parameters: > (pass1:ahc0:0:6:0): sync parameter: 12 > (pass1:ahc0:0:6:0): frequency: 20.000MHz > (pass1:ahc0:0:6:0): offset: 15 > (pass1:ahc0:0:6:0): bus width: 8 bits > (pass1:ahc0:0:6:0): disconnection is enabled > (pass1:ahc0:0:6:0): tagged queueing is disabled > ahc0: SIM/HBA version: 1 > ahc0: supports tag queue messages > ahc0: supports SDTR message > ahc0: supports 16 bit wide SCSI > ahc0: HBA engine count: 0 > ahc0: maximum target: 15 > ahc0: maximum LUN: 63 > ahc0: highest path ID in subsystem: 0 > ahc0: initiator ID: 7 > ahc0: SIM vendor: FreeBSD > ahc0: HBA vendor: Adaptec > ahc0: bus ID: 0 As is this: > ahc0: base transfer speed: 3.300MB/sec > > ----------------------------- Nothing wrong with your tape drive either. > sa0 at ahc0 bus 0 target 5 lun 0 > sa0: Removable Sequential Access SCSI-2 device > sa0: 10.000MB/s transfers (10.000MHz, offset 8) > > --------- > > 7:18:54pm wahoo(106): camcontrol negotiate sa0 -v > Current Parameters: > (pass0:ahc0:0:5:0): sync parameter: 25 > (pass0:ahc0:0:5:0): frequency: 10.000MHz > (pass0:ahc0:0:5:0): offset: 8 > (pass0:ahc0:0:5:0): bus width: 8 bits > (pass0:ahc0:0:5:0): disconnection is enabled > (pass0:ahc0:0:5:0): tagged queueing is disabled > ahc0: SIM/HBA version: 1 > ahc0: supports tag queue messages > ahc0: supports SDTR message > ahc0: supports 16 bit wide SCSI > ahc0: HBA engine count: 0 > ahc0: maximum target: 15 > ahc0: maximum LUN: 63 > ahc0: highest path ID in subsystem: 0 > ahc0: initiator ID: 7 > ahc0: SIM vendor: FreeBSD > ahc0: HBA vendor: Adaptec > ahc0: bus ID: 0 > ahc0: base transfer speed: 3.300MB/sec Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 11 1:46:57 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp016.mail.yahoo.com (smtp016.mail.yahoo.com [216.136.174.113]) by hub.freebsd.org (Postfix) with SMTP id EA7E537B403 for ; Sat, 11 Aug 2001 01:46:54 -0700 (PDT) (envelope-from kc5vdj@yahoo.com) Received: from mkc-65-28-47-209.kc.rr.com (HELO yahoo.com) (65.28.47.209) by smtp.mail.vip.sc5.yahoo.com with SMTP; 11 Aug 2001 08:46:54 -0000 X-Apparently-From: Message-ID: <3B74F0FD.BD874B21@yahoo.com> Date: Sat, 11 Aug 2001 03:46:53 -0500 From: Jim Bryant Reply-To: kc5vdj@yahoo.com X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: Matthew Jacob , Martin Aherron , freebsd-scsi@FreeBSD.ORG Subject: Re: what's wrong with this picture :-) References: <01Jul25.213803edt.119044@cyborg.cybernetics.com> <20010725200625.A44606@panzer.kdm.org> <3B747CD2.A7F44851@yahoo.com> <20010810194807.A74472@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org "Kenneth D. Merry" wrote: > You're getting the base transfer speed for the bus confused with the > actual negotiated transfer speed. 3.3MB/sec is async narrow SCSI, which > is the baseline transfer speed for most SCSI controllers. The > negotiated transfer speed is printed out when the device probes, and > by camcontrol negotiate. My bad... oops! > > FreeBSD 5.0-CURRENT #18: Fri Aug 10 16:51:25 CDT 2001 [cvsupped about 4am CST today] Tyan S1696-DLUA Mobo / 512M / Two > > Pentium-II/333's > > > > See the full dmesg output in the -current thread I'm about to post concerning ACPI tables not being found, boot_verbose was set. > > > > The SCSI timeouts have been "normal" here for a couple/few years. Everything comes up fine once it sorts itself out. > > I don't know why you're getting timeouts, Justin will probably have to > comment when he gets back. > I hope he gets a chance to, everything does come up fine after the timeouts sort themselves out on ahc1, but it is still pretty much a pain in the butt having to wait for the boot. Usually it takes a couple of minutes before it gets going after it hits the "waiting for scsi to settle" message.. I had bumped it up to 30 seconds from 15 seconds, but that didn't change a thing as far as the timeouts go. as i recall, seven seconds was too soon, and caused other problems, which i why i normally run a 15 second wait. Once it hits the "waiting..." though, and I haven't physically timed it, I'll guestimate about two minutes before I get to /etc/rc. I don't know if it's just a quirk with my hardware or what... It's been that way for a long time. The 'cuda is the only thing on ahc1, and ahc0 consists of an internal cd-rom, and an external dds-2 [via a mobo to back-panel-socket-insert-thingie that goes like a card bracket]. Both the cd-rom and tape drive are terminated, and the external cable is only a three footer. The SCSI BIOS is set for automatic termination. As far as the "error 6" on cd0 on ahc0, i only grepped on cd0, so i could have missed some messages. jim -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 11 13: 4:40 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 55ECC37B408 for ; Sat, 11 Aug 2001 13:04:35 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id OAA83248; Sat, 11 Aug 2001 14:04:26 -0600 (MDT) (envelope-from ken) Date: Sat, 11 Aug 2001 14:04:26 -0600 From: "Kenneth D. Merry" To: Jim Bryant Cc: Matthew Jacob , Martin Aherron , freebsd-scsi@FreeBSD.ORG Subject: Re: what's wrong with this picture :-) Message-ID: <20010811140426.A83218@panzer.kdm.org> References: <01Jul25.213803edt.119044@cyborg.cybernetics.com> <20010725200625.A44606@panzer.kdm.org> <3B747CD2.A7F44851@yahoo.com> <20010810194807.A74472@panzer.kdm.org> <3B74F0FD.BD874B21@yahoo.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <3B74F0FD.BD874B21@yahoo.com>; from kc5vdj@yahoo.com on Sat, Aug 11, 2001 at 03:46:53AM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org First off -- you're still sending messages with line lengths that are way over 80 columns. It looks like you're using Netscape, so: Edit -> Preferences -> Mail & Newsgroups -> Messages Go to the "Message Wrapping" section, and set it up to wrap outgoing plain text messages at 72 characters. On Sat, Aug 11, 2001 at 03:46:53 -0500, Jim Bryant wrote: > "Kenneth D. Merry" wrote: > > You're getting the base transfer speed for the bus confused with the > > actual negotiated transfer speed. 3.3MB/sec is async narrow SCSI, which > > is the baseline transfer speed for most SCSI controllers. The > > negotiated transfer speed is printed out when the device probes, and > > by camcontrol negotiate. > > My bad... oops! > > > > FreeBSD 5.0-CURRENT #18: Fri Aug 10 16:51:25 CDT 2001 [cvsupped about 4am CST today] Tyan S1696-DLUA Mobo / 512M / Two > > > Pentium-II/333's > > > > > > See the full dmesg output in the -current thread I'm about to post concerning ACPI tables not being found, boot_verbose was set. > > > > > > The SCSI timeouts have been "normal" here for a couple/few years. Everything comes up fine once it sorts itself out. > > > > I don't know why you're getting timeouts, Justin will probably have to > > comment when he gets back. > > > > I hope he gets a chance to, everything does come up fine after the timeouts sort themselves out on ahc1, but it is still pretty much > a pain in the butt having to wait for the boot. Usually it takes a couple of minutes before it gets going after it hits the > "waiting for scsi to settle" message.. I had bumped it up to 30 seconds from 15 seconds, but that didn't change a thing as far as > the timeouts go. as i recall, seven seconds was too soon, and caused other problems, which i why i normally run a 15 second wait. > Once it hits the "waiting..." though, and I haven't physically timed it, I'll guestimate about two minutes before I get to /etc/rc. > > I don't know if it's just a quirk with my hardware or what... It's been that way for a long time. The 'cuda is the only thing on > ahc1, and ahc0 consists of an internal cd-rom, and an external dds-2 [via a mobo to back-panel-socket-insert-thingie that goes like > a card bracket]. Both the cd-rom and tape drive are terminated, and the external cable is only a three footer. > > The SCSI BIOS is set for automatic termination. > > As far as the "error 6" on cd0 on ahc0, i only grepped on cd0, so i could have missed some messages. Please go ahead and send the full dmesg output from your system. Justin will probably need all of that information in order to diagnose your problem. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Aug 11 22:46:15 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from smtp015.mail.yahoo.com (smtp015.mail.yahoo.com [216.136.173.59]) by hub.freebsd.org (Postfix) with SMTP id 2764A37B407 for ; Sat, 11 Aug 2001 22:46:11 -0700 (PDT) (envelope-from kc5vdj@yahoo.com) Received: from mkc-65-28-47-209.kc.rr.com (HELO yahoo.com) (65.28.47.209) by smtp.mail.vip.sc5.yahoo.com with SMTP; 12 Aug 2001 05:46:10 -0000 X-Apparently-From: Message-ID: <3B761821.7050805@yahoo.com> Date: Sun, 12 Aug 2001 00:46:09 -0500 From: Jim Bryant Reply-To: kc5vdj@yahoo.com User-Agent: Mozilla/5.0 (X11; U; Linux i386; en-US; rv:0.9.2) Gecko/20010726 Netscape6/6.1 X-Accept-Language: en-us MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: Matthew Jacob , Martin Aherron , freebsd-scsi@FreeBSD.ORG Subject: Re: what's wrong with this picture :-) References: <01Jul25.213803edt.119044@cyborg.cybernetics.com> <20010725200625.A44606@panzer.kdm.org> <3B747CD2.A7F44851@yahoo.com> <20010810194807.A74472@panzer.kdm.org> <3B74F0FD.BD874B21@yahoo.com> <20010811140426.A83218@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Sorry about the line lengths, but some of my other mail activities require the use of 132 columns for everything. I know what it's like to have to use elm in text mode on a vty or a real terminal without selectable line widths, so no prob dude. I'll have to post the dmesg later tonight or tomorrow, as I did have to reboot due to a netscape-6.10 issue involving the java-vm spawning a gazillion java-vm's and thrashing the system into swap [can you say "reset button"? I thought you could!]... I forgot to do a boot_verbose at the time. Needless to say, current handles such interruptions well... I wasn't sure if I'd have a system when I came up. I'll follow-up on this in a little bit. Kenneth D. Merry wrote: > First off -- you're still sending messages with line lengths that are way > over 80 columns. > > It looks like you're using Netscape, so: > > Edit -> Preferences -> Mail & Newsgroups -> Messages > > Go to the "Message Wrapping" section, and set it up to wrap outgoing plain > text messages at 72 characters. > > On Sat, Aug 11, 2001 at 03:46:53 -0500, Jim Bryant wrote: > >>"Kenneth D. Merry" wrote: >> >>>You're getting the base transfer speed for the bus confused with the >>>actual negotiated transfer speed. 3.3MB/sec is async narrow SCSI, which >>>is the baseline transfer speed for most SCSI controllers. The >>>negotiated transfer speed is printed out when the device probes, and >>>by camcontrol negotiate. >>> >>My bad... oops! >> >> >>>>FreeBSD 5.0-CURRENT #18: Fri Aug 10 16:51:25 CDT 2001 [cvsupped about 4am CST today] Tyan S1696-DLUA Mobo / 512M / Two >>>>Pentium-II/333's >>>> >>>>See the full dmesg output in the -current thread I'm about to post concerning ACPI tables not being found, boot_verbose was set. >>>> >>>>The SCSI timeouts have been "normal" here for a couple/few years. Everything comes up fine once it sorts itself out. >>>> >>>I don't know why you're getting timeouts, Justin will probably have to >>>comment when he gets back. >>> >>> >>I hope he gets a chance to, everything does come up fine after the timeouts sort themselves out on ahc1, but it is still pretty much >>a pain in the butt having to wait for the boot. Usually it takes a couple of minutes before it gets going after it hits the >>"waiting for scsi to settle" message.. I had bumped it up to 30 seconds from 15 seconds, but that didn't change a thing as far as >>the timeouts go. as i recall, seven seconds was too soon, and caused other problems, which i why i normally run a 15 second wait. >>Once it hits the "waiting..." though, and I haven't physically timed it, I'll guestimate about two minutes before I get to /etc/rc. >> >>I don't know if it's just a quirk with my hardware or what... It's been that way for a long time. The 'cuda is the only thing on >>ahc1, and ahc0 consists of an internal cd-rom, and an external dds-2 [via a mobo to back-panel-socket-insert-thingie that goes like >>a card bracket]. Both the cd-rom and tape drive are terminated, and the external cable is only a three footer. >> >>The SCSI BIOS is set for automatic termination. >> >>As far as the "error 6" on cd0 on ahc0, i only grepped on cd0, so i could have missed some messages. >> > > > Please go ahead and send the full dmesg output from your system. Justin > will probably need all of that information in order to diagnose your > problem. > > Ken > -- ET has one helluva sense of humor! He's always anal-probing right-wing schizos! _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message