Click on to meet someone you Click with

From owner-freebsd-scsi Sun Apr 22 10:11:50 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from introsearch.com (host213-123-28-135.btinternet.com [213.123.28.135]) by hub.freebsd.org (Postfix) with SMTP id 685A937B43C for ; Sun, 22 Apr 2001 10:11:36 -0700 (PDT) (envelope-from admin@introsearch.com) From: "Introsearch.Com" To: Subject: Click on to meet someone you Click with Mime-Version: 1.0 Content-Type: text/html; charset="ISO-8859-1" Date: Sun, 22 Apr 2001 18:11:32 +0100 Reply-To: "Introsearch.Com" Content-Transfer-Encoding: 8bit Message-Id: <20010422171136.685A937B43C@hub.freebsd.org> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Click on to meet someone you Click with

Click on to meet someone you Click with

Introsearch does not condone unsolicited Bulk Emailing - Our source email lists comprise only of email addresses which have been obtained through correct legal channels from users who have at some stage authorised third party organisations to contact them via email regarding products or services which the customer may find interesting. To be removed from our mailing list, please send an email to remove@introsearch.com with the word 'remove' in the subject line

Introsearch.com is one of the fastest growing introduction systems on the Internet and you can join online now at a fraction of the cost. Are you looking for a change in your life, or just to busy to find the right person, Introsearch.com has all the answers. Take a look at some of the benefits below that are on offer to all our members.

Twelve months membership
Powerful matching system
For all age groups
Picture upload facility
Voice upload facility
Video upload facility

Members chat rooms
Members forums
Private emailing system
Local party nights
Members have complete control
Confidentiality assured

Join today for an annual membership of only £14:50 (21:00 us dollars) and receive all the benefits above and much much more with introsearch.com. Yes that's an amazing 28p per week.

This is a special promotional offer and valid from 2nd April 2001 to finish on or before the last day of June 2001.
Click on the link below and start meeting new friends today.

http://www.introsearch.com

Click on to meet someone you Click with

Introsearch.com is a member of the Data Protection Act 1974 License Number Z4788975 (c) 2001 Introsearch. All Rights Reserved
If you have any further issues with our advertising policy, contact Introsearch at Tel: +44 (0)1772 798071 or by Post to:
INTROSEARCH, ENGLAND (Use Correct Postage - No letters or correspondence without postage affixed will be opened)
PLEASE NOTE: This address is a licensed Royal Mail Postage Address and WILL be received.

To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 23 16:50:41 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from securitas.net (freebsd.securitas.net [212.66.0.13]) by hub.freebsd.org (Postfix) with ESMTP id 7CB6237B423 for ; Mon, 23 Apr 2001 16:50:37 -0700 (PDT) (envelope-from grossman@securitas.net) Received: from blue.securitas.net (blue.securitas.net [212.66.0.24]) by securitas.net (8.11.1/8.11.2) with ESMTP id f3NNoV161530 for ; Tue, 24 Apr 2001 01:50:31 +0200 (CEST) (envelope-from grossman) Received: (from grossman@localhost) by blue.securitas.net (8.11.3/8.9.3) id f3NNoUp40465; Tue, 24 Apr 2001 01:50:30 +0200 (CEST) Date: Tue, 24 Apr 2001 01:50:30 +0200 (CEST) Message-Id: <200104232350.f3NNoUp40465@blue.securitas.net> From: Rolf Grossmann MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-scsi@freebsd.org Subject: Cann't append to SLR SCSI tape? X-Mailer: VM 6.75 under Emacs 19.34.1 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I'm having a problem with a SLR tape drive. I can't write more than a single file on it. Unfortunately, my experience with that type of tape is rather limited ... I haven't seen such behaviour with the DAT tapes I'm usually using. Can anyone give me an insight here? I'm using a newly installed FreeBSD 4.3-STABLE (from Saturday, shortly after release). Here's the dmesg output: FreeBSD 4.3-STABLE #0: Sun Apr 22 00:28:49 CEST 2001 ahc0: port 0xa400-0xa4ff mem 0xcb000000-0xcb000fff irq 7 at device 9.0 on pci0 aic7892: Wide Channel A, SCSI Id=7, 32/255 SCBs sa1 at ahc0 bus 0 target 11 lun 0 sa1: Removable Sequential Access SCSI-2 device sa1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) (sa1:ahc0:0:11:0): WRITE(06). CDB: a 0 0 80 0 0 (sa1:ahc0:0:11:0): ILLEGAL REQUEST asc:50,0 (sa1:ahc0:0:11:0): Write append error Thanks, Rolf To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 23 17: 4:21 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.clarkson.edu (mail.clarkson.edu [128.153.4.10]) by hub.freebsd.org (Postfix) with SMTP id E2C0837B423 for ; Mon, 23 Apr 2001 17:04:18 -0700 (PDT) (envelope-from cohentl@clarkson.edu) Received: (qmail 12889 invoked by uid 0); 24 Apr 2001 00:04:11 -0000 Received: from isis.aoc.clarkson.edu (128.153.130.35) by mail.clarkson.edu with SMTP; 24 Apr 2001 00:04:11 -0000 Date: Mon, 23 Apr 2001 20:04:10 -0400 (EDT) From: Todd Cohen X-Sender: cohentl@isis.aoc.clarkson.edu To: freebsd-scsi@freebsd.org Subject: is this device bad? 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 Hi, I just bought one of those huge seagate ST410800N hard drives off off e-bay and I'm getting errors trying to make it useable. I've connected it via an external enclosure to my AlphaStation 200. I'm using an active terminator. dmesg reports the following on bootup: da1 at sym0 bus 0 target 4 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 8) da1: Attempt to query device size failed: MEDIUM ERROR, Medium format corrupted and when I try the following commands I get these errors: lizard# dd if=/dev/zero of=/dev/da1 bs=1k count=1 dd: /dev/da1: Input/output error lizard# dd if=/dev/zero of=/dev/rda1 bs=1k count=1 dd: /dev/rda1: Input/output error from dmesg: (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 Is this drive bad? __________________________________________________________________________ ICMP: The protocol that goes PING! I like angles, but only to a degree. cthread. cthread_fork(). Fork, thread, fork! Black holes suck. http://wckn.clarkson.edu/~cohentl/ Real_men_don't_need_spacebars. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 23 17:17: 0 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 65D1637B424 for ; Mon, 23 Apr 2001 17:16:56 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id SAA94403; Mon, 23 Apr 2001 18:16:47 -0600 (MDT) (envelope-from ken) Date: Mon, 23 Apr 2001 18:16:47 -0600 From: "Kenneth D. Merry" To: Todd Cohen Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: is this device bad? Message-ID: <20010423181646.A94378@panzer.kdm.org> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from cohentl@clarkson.edu on Mon, Apr 23, 2001 at 08:04:10PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, Apr 23, 2001 at 20:04:10 -0400, Todd Cohen wrote: > Hi, > I just bought one of those huge seagate ST410800N hard drives off > off e-bay and I'm getting errors trying to make it useable. I've connected > it via an external enclosure to my AlphaStation 200. I'm using an active > terminator. dmesg reports the following on bootup: > > da1 at sym0 bus 0 target 4 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 10.000MB/s transfers (10.000MHz, offset 8) > da1: Attempt to query device size failed: MEDIUM ERROR, Medium format > corrupted > > and when I try the following commands I get these errors: > lizard# dd if=/dev/zero of=/dev/da1 bs=1k count=1 > dd: /dev/da1: Input/output error > lizard# dd if=/dev/zero of=/dev/rda1 bs=1k count=1 > dd: /dev/rda1: Input/output error > > from dmesg: > > (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 > (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 > (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 > (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 > (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 > (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 > (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 > (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 > > Is this drive bad? It might be, although when I've seen 'medium format corrupted' errors before, they're sometimes fixable by low-level formatting the disk. Try formatting the disk like this: camcontrol format da1 Then try accessing the disk again. If that doesn't fix the problem, you might have a bad disk. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Apr 23 17:26: 3 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id ED5F737B423 for ; Mon, 23 Apr 2001 17:26:00 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from beppo (beppo [192.67.166.79]) by feral.com (8.9.3/8.9.3) with ESMTP id RAA28820; Mon, 23 Apr 2001 17:25:47 -0700 Date: Mon, 23 Apr 2001 17:25:46 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Rolf Grossmann Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Cann't append to SLR SCSI tape? In-Reply-To: <200104232350.f3NNoUp40465@blue.securitas.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 Set eotmodel to 1. On Tue, 24 Apr 2001, Rolf Grossmann wrote: > Hi, > > I'm having a problem with a SLR tape drive. I can't write more than a > single file on it. Unfortunately, my experience with that type of tape > is rather limited ... I haven't seen such behaviour with the DAT tapes > I'm usually using. Can anyone give me an insight here? > > I'm using a newly installed FreeBSD 4.3-STABLE (from Saturday, shortly after > release). Here's the dmesg output: > > FreeBSD 4.3-STABLE #0: Sun Apr 22 00:28:49 CEST 2001 > > ahc0: port 0xa400-0xa4ff mem 0xcb000000-0xcb000fff irq 7 at device 9.0 on pci0 > aic7892: Wide Channel A, SCSI Id=7, 32/255 SCBs > > sa1 at ahc0 bus 0 target 11 lun 0 > sa1: Removable Sequential Access SCSI-2 device > sa1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) > > (sa1:ahc0:0:11:0): WRITE(06). CDB: a 0 0 80 0 0 > (sa1:ahc0:0:11:0): ILLEGAL REQUEST asc:50,0 > (sa1:ahc0:0:11:0): Write append error > > Thanks, Rolf > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" 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 Mon Apr 23 20:49:40 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from cs4.cs.ait.ac.th (cs4.cs.ait.ac.th [192.41.170.16]) by hub.freebsd.org (Postfix) with ESMTP id 7C67B37B43F for ; Mon, 23 Apr 2001 20:49:31 -0700 (PDT) (envelope-from on@cs.ait.ac.th) Received: from banyan.cs.ait.ac.th (on@banyan.cs.ait.ac.th [192.41.170.5]) by cs4.cs.ait.ac.th (8.9.3/8.9.3) with ESMTP id KAA27341; Tue, 24 Apr 2001 10:47:46 +0700 (GMT+0700) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.8.5/8.8.5) id KAA05217; Tue, 24 Apr 2001 10:49:35 +0700 (ICT) Date: Tue, 24 Apr 2001 10:49:35 +0700 (ICT) Message-Id: <200104240349.KAA05217@banyan.cs.ait.ac.th> X-Authentication-Warning: banyan.cs.ait.ac.th: on set sender to on@banyan.cs.ait.ac.th using -f From: Olivier Nicole To: grossman@securitas.net Cc: freebsd-scsi@FreeBSD.ORG In-reply-to: <200104232350.f3NNoUp40465@blue.securitas.net> (message from Rolf Grossmann on Tue, 24 Apr 2001 01:50:30 +0200 (CEST)) Subject: Re: Cann't append to SLR SCSI tape? References: <200104232350.f3NNoUp40465@blue.securitas.net> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Rolf, You need to set it with one EOT mark: mt seteotmodel 1 Other solution is to modify the file /usr/src/sys/cam/scsi/scsi_sa.c and remove the space that is in front of the string SLR, then recompile the kernel. Olivier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Apr 24 3:54:10 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 2873137B422 for ; Tue, 24 Apr 2001 03:54:07 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id MAA04423 for freebsd-scsi@freebsd.org; Tue, 24 Apr 2001 12:54:02 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3OAoBP38762; Tue, 24 Apr 2001 12:50:11 +0200 (MET DST) (envelope-from j) Date: Tue, 24 Apr 2001 12:50:11 +0200 (MET DST) Message-Id: <200104241050.f3OAoBP38762@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <20010423181646.A94378@panzer.kdm.org> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: is this device bad? X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" wrote: > It might be, although when I've seen 'medium format corrupted' > errors before, they're sometimes fixable by low-level formatting the > disk. `Medium format corrupted' is normally issued if a previous `format unit' operation had been aborted. Reformatting should help (unless the `format unit' operation itself ends up in another error, of course). -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Apr 24 3:54:18 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 3EEC737B422 for ; Tue, 24 Apr 2001 03:54:13 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id MAA04429 for freebsd-scsi@freebsd.org; Tue, 24 Apr 2001 12:54:09 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3OAok538769; Tue, 24 Apr 2001 12:50:46 +0200 (MET DST) (envelope-from j) Date: Tue, 24 Apr 2001 12:50:46 +0200 (MET DST) Message-Id: <200104241050.f3OAok538769@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <200104232350.f3NNoUp40465@blue.securitas.net> <200104240349.KAA05217@banyan.cs.ait.ac.th> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: Cann't append to SLR SCSI tape? X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Olivier Nicole wrote: > Other solution is to modify the file /usr/src/sys/cam/scsi/scsi_sa.c > and remove the space that is in front of the string SLR, then > recompile the kernel. ....and then submit the patch that was required. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Apr 24 6:33:29 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from ct980320-b.blmngtn1.in.home.com (ct980320-b.blmngtn1.in.home.com [65.8.207.32]) by hub.freebsd.org (Postfix) with ESMTP id 833B237B43E for ; Tue, 24 Apr 2001 06:33:27 -0700 (PDT) (envelope-from mikes@ct980320-b.blmngtn1.in.home.com) Received: (from mikes@localhost) by ct980320-b.blmngtn1.in.home.com (8.11.3/8.11.3) id f3ODXPB08809; Tue, 24 Apr 2001 08:33:25 -0500 (EST) (envelope-from mikes) From: Mike Squires Message-Id: <200104241333.f3ODXPB08809@ct980320-b.blmngtn1.in.home.com> Subject: Re: is this device bad? In-Reply-To: "from Todd Cohen at Apr 23, 2001 08:04:10 pm" To: Todd Cohen Date: Tue, 24 Apr 2001 08:33:25 -0500 (EST) Cc: freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I just bought one of those huge seagate ST410800N hard drives off I have about 20 of the ST410800WD drives here, used with Adaptec, Symbios, and DPT controllers. I would do a low level format, using the controller's low level format option (CTL-A during the boot process for Adaptec). I've always done this with a new or used disk when connected for the first time or to a different controller. This is in part superstitious behaviour learned during the early days of PC SCSI when even Adaptec controllers didn't use interchangeable low level formats. The ST4100800 series has been very reliable for me - no failures, and they clock at a respectable 5MB/sec for an old 5400 RPM drive. MLS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Apr 24 9:13:26 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.clarkson.edu (mail.clarkson.edu [128.153.4.10]) by hub.freebsd.org (Postfix) with SMTP id 25F4737B422 for ; Tue, 24 Apr 2001 09:13:23 -0700 (PDT) (envelope-from cohentl@clarkson.edu) Received: (qmail 8489 invoked by uid 0); 24 Apr 2001 16:13:20 -0000 Received: from vador.aoc.clarkson.edu (128.153.130.33) by mail.clarkson.edu with SMTP; 24 Apr 2001 16:13:20 -0000 Date: Tue, 24 Apr 2001 12:10:27 -0400 (EDT) From: Todd Cohen X-Sender: cohentl@vador.aoc.clarkson.edu To: freebsd-scsi@freebsd.org Subject: Re: is this device bad? In-Reply-To: <200104241333.f3ODXPB08809@ct980320-b.blmngtn1.in.home.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 Well, I don't know how to do a low level format on this machine.. it's an AlphaStation. I ran the following as someone else suggested, it doesn't report any errors.. but later in dmesg I get errors: camcontrol format da1 da1 at sym0 bus 0 target 4 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 10.000MB/s transfers (10.000MHz, offset 8) da1: Attempt to query device size failed: MEDIUM ERROR, Medium format corrupted (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 -Todd On Tue, 24 Apr 2001, Mike Squires wrote: > > I just bought one of those huge seagate ST410800N hard drives off > > I have about 20 of the ST410800WD drives here, used with Adaptec, Symbios, > and DPT controllers. > > I would do a low level format, using the controller's low level format > option (CTL-A during the boot process for Adaptec). > > I've always done this with a new or used disk when connected for the > first time or to a different controller. This is in part superstitious > behaviour learned during the early days of PC SCSI when even Adaptec > controllers didn't use interchangeable low level formats. > > The ST4100800 series has been very reliable for me - no failures, and they > clock at a respectable 5MB/sec for an old 5400 RPM drive. > > MLS > __________________________________________________________________________ ICMP: The protocol that goes PING! I like angles, but only to a degree. cthread. cthread_fork(). Fork, thread, fork! Black holes suck. http://wckn.clarkson.edu/~cohentl/ Real_men_don't_need_spacebars. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Apr 24 9:24:15 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 B8D0637B422 for ; Tue, 24 Apr 2001 09:24:12 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA99349; Tue, 24 Apr 2001 10:24:10 -0600 (MDT) (envelope-from ken) Date: Tue, 24 Apr 2001 10:24:10 -0600 From: "Kenneth D. Merry" To: Todd Cohen Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: is this device bad? Message-ID: <20010424102410.A99321@panzer.kdm.org> References: <200104241333.f3ODXPB08809@ct980320-b.blmngtn1.in.home.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from cohentl@clarkson.edu on Tue, Apr 24, 2001 at 12:10:27PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Apr 24, 2001 at 12:10:27 -0400, Todd Cohen wrote: > Well, I don't know how to do a low level format on this machine.. it's an > AlphaStation. I ran the following as someone else suggested, it doesn't > report any errors.. but later in dmesg I get errors: > > camcontrol format da1 That is a low level format. > da1 at sym0 bus 0 target 4 lun 0 > da1: Fixed Direct Access SCSI-2 device > da1: 10.000MB/s transfers (10.000MHz, offset 8) > da1: Attempt to query device size failed: MEDIUM ERROR, Medium format > corrupted > (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 > (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 > (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 > (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 > (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 > (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 If those errors popped up after the format (you might want to power cycle as well), then you've probably got a bad drive. 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 Tue Apr 24 9:25: 0 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.clarkson.edu (mail.clarkson.edu [128.153.4.10]) by hub.freebsd.org (Postfix) with SMTP id D73A537B42C for ; Tue, 24 Apr 2001 09:24:53 -0700 (PDT) (envelope-from cohentl@clarkson.edu) Received: (qmail 10988 invoked by uid 0); 24 Apr 2001 16:24:51 -0000 Received: from isis.aoc.clarkson.edu (128.153.130.35) by mail.clarkson.edu with SMTP; 24 Apr 2001 16:24:51 -0000 Date: Tue, 24 Apr 2001 12:24:50 -0400 (EDT) From: Todd Cohen X-Sender: cohentl@isis.aoc.clarkson.edu To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: is this device bad? In-Reply-To: <20010424102410.A99321@panzer.kdm.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 Ok.. how long should that format take? it's a 9.x gig drive and that format took about 2 seconds... -Todd On Tue, 24 Apr 2001, Kenneth D. Merry wrote: > On Tue, Apr 24, 2001 at 12:10:27 -0400, Todd Cohen wrote: > > Well, I don't know how to do a low level format on this machine.. it's an > > AlphaStation. I ran the following as someone else suggested, it doesn't > > report any errors.. but later in dmesg I get errors: > > > > camcontrol format da1 > > That is a low level format. > > > da1 at sym0 bus 0 target 4 lun 0 > > da1: Fixed Direct Access SCSI-2 device > > da1: 10.000MB/s transfers (10.000MHz, offset 8) > > da1: Attempt to query device size failed: MEDIUM ERROR, Medium format > > corrupted > > (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > > (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 > > (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 > > (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > > (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 > > (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 > > (da1:sym0:0:4:0): READ CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > > (da1:sym0:0:4:0): MEDIUM ERROR asc:31,0 > > (da1:sym0:0:4:0): Medium format corrupted field replaceable unit: 1 > > If those errors popped up after the format (you might want to power cycle > as well), then you've probably got a bad drive. > > Ken > -- > Kenneth Merry > ken@kdm.org > __________________________________________________________________________ ICMP: The protocol that goes PING! I like angles, but only to a degree. cthread. cthread_fork(). Fork, thread, fork! Black holes suck. http://wckn.clarkson.edu/~cohentl/ Real_men_don't_need_spacebars. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Apr 24 9:55:50 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 41A6137B424 for ; Tue, 24 Apr 2001 09:55:47 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA99580; Tue, 24 Apr 2001 10:55:45 -0600 (MDT) (envelope-from ken) Date: Tue, 24 Apr 2001 10:55:45 -0600 From: "Kenneth D. Merry" To: Todd Cohen Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: is this device bad? Message-ID: <20010424105545.A99553@panzer.kdm.org> References: <20010424102410.A99321@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from cohentl@clarkson.edu on Tue, Apr 24, 2001 at 12:24:50PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Apr 24, 2001 at 12:24:50 -0400, Todd Cohen wrote: > Ok.. how long should that format take? it's a 9.x gig drive and that > format took about 2 seconds... It should have taken a lot longer than that. Try this instead: camcontrol format da1 -v -w That will issue a non-immediate format command. It may be that your drive doesn't like the immediate format command but isn't returning an error. 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 Tue Apr 24 11:44: 8 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.clarkson.edu (mail.clarkson.edu [128.153.4.10]) by hub.freebsd.org (Postfix) with SMTP id 9712F37B422 for ; Tue, 24 Apr 2001 11:44:04 -0700 (PDT) (envelope-from cohentl@clarkson.edu) Received: (qmail 5828 invoked by uid 0); 24 Apr 2001 18:44:01 -0000 Received: from crux.clarkson.edu (128.153.4.132) by mail.clarkson.edu with SMTP; 24 Apr 2001 18:44:01 -0000 Date: Tue, 24 Apr 2001 14:44:02 -0400 (EDT) From: Todd Cohen To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: is this device bad? In-Reply-To: <20010424105545.A99553@panzer.kdm.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 I ran that command... it sat at "Fromatting..." for about 20-30 minutes or so.. then had the following error: lizard# camcontrol format da1 -v -w You are about to REMOVE ALL DATA from the following device: pass1: Fixed Direct Access SCSI-2 device pass1: Serial Number 00337771 pass1: 10.000MB/s transfers (10.000MHz, offset 8) Are you SURE you want to do this? (yes/no) yes Current format timeout is 10800 seconds Enter new timeout in seconds or press return to keep the current timeout [10800] Formatting...camcontrol: error sending format command CAM status is 0xb lizard# -Todd On Tue, 24 Apr 2001, Kenneth D. Merry wrote: > On Tue, Apr 24, 2001 at 12:24:50 -0400, Todd Cohen wrote: > > Ok.. how long should that format take? it's a 9.x gig drive and that > > format took about 2 seconds... > > It should have taken a lot longer than that. > > Try this instead: > > camcontrol format da1 -v -w > > That will issue a non-immediate format command. It may be that your drive > doesn't like the immediate format command but isn't returning an error. > > Ken > -- > Kenneth Merry > ken@kdm.org > __________________________________________________________________________ ICMP: The protocol that goes PING! I like angles, but only to a degree. cthread. cthread_fork(). Fork, thread, fork! Black holes suck. http://wckn.clarkson.edu/~cohentl/ Real_men_don't_need_spacebars. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Apr 24 11:55: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 2D24637B43C for ; Tue, 24 Apr 2001 11:55:38 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA00630; Tue, 24 Apr 2001 12:55:34 -0600 (MDT) (envelope-from ken) Date: Tue, 24 Apr 2001 12:55:34 -0600 From: "Kenneth D. Merry" To: Todd Cohen Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: is this device bad? Message-ID: <20010424125534.A557@panzer.kdm.org> References: <20010424105545.A99553@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from cohentl@clarkson.edu on Tue, Apr 24, 2001 at 02:44:02PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Apr 24, 2001 at 14:44:02 -0400, Todd Cohen wrote: > I ran that command... it sat at "Fromatting..." for about 20-30 minutes or > so.. then had the following error: > > lizard# camcontrol format da1 -v -w > You are about to REMOVE ALL DATA from the following device: > pass1: Fixed Direct Access SCSI-2 device > pass1: Serial Number 00337771 > pass1: 10.000MB/s transfers (10.000MHz, offset 8) > Are you SURE you want to do this? (yes/no) yes > Current format timeout is 10800 seconds > Enter new timeout in seconds or press > return to keep the current timeout [10800] > Formatting...camcontrol: error sending format command > CAM status is 0xb > lizard# That's a command timeout, but the timeout was set to 3 hours, not 20-30 minutes. Was there anything in the dmesg after camcontrol returned? 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 Tue Apr 24 12: 0:26 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.clarkson.edu (mail.clarkson.edu [128.153.4.10]) by hub.freebsd.org (Postfix) with SMTP id 30D5C37B423 for ; Tue, 24 Apr 2001 12:00:23 -0700 (PDT) (envelope-from cohentl@clarkson.edu) Received: (qmail 9836 invoked by uid 0); 24 Apr 2001 19:00:20 -0000 Received: from isis.aoc.clarkson.edu (128.153.130.35) by mail.clarkson.edu with SMTP; 24 Apr 2001 19:00:20 -0000 Date: Tue, 24 Apr 2001 15:00:20 -0400 (EDT) From: Todd Cohen X-Sender: cohentl@isis.aoc.clarkson.edu To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: is this device bad? In-Reply-To: <20010424125534.A557@panzer.kdm.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 (da0:sym0:0:0:0): READ(06). CDB: 8 1f 4e 46 2 0 (da0:sym0:0:0:0): MEDIUM ERROR info:1f4e47 asc:11,0 (da0:sym0:0:0:0): Unrecovered read error (da0:sym0:0:0:0): READ(06). CDB: 8 1f 60 10 10 0 (da0:sym0:0:0:0): MEDIUM ERROR info:1f6017 asc:11,0 (da0:sym0:0:0:0): Unrecovered read error sym0:4:control msgout: 80 6. -Todd On Tue, 24 Apr 2001, Kenneth D. Merry wrote: > On Tue, Apr 24, 2001 at 14:44:02 -0400, Todd Cohen wrote: > > I ran that command... it sat at "Fromatting..." for about 20-30 minutes or > > so.. then had the following error: > > > > lizard# camcontrol format da1 -v -w > > You are about to REMOVE ALL DATA from the following device: > > pass1: Fixed Direct Access SCSI-2 device > > pass1: Serial Number 00337771 > > pass1: 10.000MB/s transfers (10.000MHz, offset 8) > > Are you SURE you want to do this? (yes/no) yes > > Current format timeout is 10800 seconds > > Enter new timeout in seconds or press > > return to keep the current timeout [10800] > > Formatting...camcontrol: error sending format command > > CAM status is 0xb > > lizard# > > That's a command timeout, but the timeout was set to 3 hours, not 20-30 > minutes. Was there anything in the dmesg after camcontrol returned? > > Ken > -- > Kenneth Merry > ken@kdm.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > __________________________________________________________________________ ICMP: The protocol that goes PING! I like angles, but only to a degree. cthread. cthread_fork(). Fork, thread, fork! Black holes suck. http://wckn.clarkson.edu/~cohentl/ Real_men_don't_need_spacebars. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Apr 24 14: 8:26 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 8941237B42C for ; Tue, 24 Apr 2001 14:08:19 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id PAA01487; Tue, 24 Apr 2001 15:08:03 -0600 (MDT) (envelope-from ken) Date: Tue, 24 Apr 2001 15:08:03 -0600 From: "Kenneth D. Merry" To: Todd Cohen Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: is this device bad? Message-ID: <20010424150803.A1146@panzer.kdm.org> References: <20010424125534.A557@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from cohentl@clarkson.edu on Tue, Apr 24, 2001 at 03:00:20PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [ reply moved to the bottom ] On Tue, Apr 24, 2001 at 15:00:20 -0400, Todd Cohen wrote: > On Tue, 24 Apr 2001, Kenneth D. Merry wrote: > > On Tue, Apr 24, 2001 at 14:44:02 -0400, Todd Cohen wrote: > > > I ran that command... it sat at "Fromatting..." for about 20-30 minutes or > > > so.. then had the following error: > > > > > > lizard# camcontrol format da1 -v -w > > > You are about to REMOVE ALL DATA from the following device: > > > pass1: Fixed Direct Access SCSI-2 device > > > pass1: Serial Number 00337771 > > > pass1: 10.000MB/s transfers (10.000MHz, offset 8) > > > Are you SURE you want to do this? (yes/no) yes > > > Current format timeout is 10800 seconds > > > Enter new timeout in seconds or press > > > return to keep the current timeout [10800] > > > Formatting...camcontrol: error sending format command > > > CAM status is 0xb > > > lizard# > > > > That's a command timeout, but the timeout was set to 3 hours, not 20-30 > > minutes. Was there anything in the dmesg after camcontrol returned? > > > (da0:sym0:0:0:0): READ(06). CDB: 8 1f 4e 46 2 0 > (da0:sym0:0:0:0): MEDIUM ERROR info:1f4e47 asc:11,0 > (da0:sym0:0:0:0): Unrecovered read error > (da0:sym0:0:0:0): READ(06). CDB: 8 1f 60 10 10 0 > (da0:sym0:0:0:0): MEDIUM ERROR info:1f6017 asc:11,0 > (da0:sym0:0:0:0): Unrecovered read error > sym0:4:control msgout: 80 6. Isn't the drive you're trying to talk to da1? The last message is the one that might pertain to da1, but I'm not sure what that means. You'll have to ask Gerard what that means, and then we can perhaps figure out why the disk is timing out. Another potential problem is the timeout length may be overflowing a 32-bit integer. IIRC, HZ on the alpha is 1000. The sym(4) driver uses the following to calculate the timeout: ccb->ccb_h.timeout_ch = timeout(sym_timeout, (caddr_t) ccb, ccb->ccb_h.timeout*hz/1000); So with a timeout of 10800 seconds, or 10,800,000 ms, multiplied by hz, which is likely 1000 on the alpha, you would overflow a 32-bit integer. So try a timeout of 4200 seconds instead, and see if that works. That's 70 minutes, but it might be enough for the format to complete. If not, we'll have to adjust the above calculation to use 64-bit math so it won't overflow. 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 Tue Apr 24 14:51:59 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.clarkson.edu (mail.clarkson.edu [128.153.4.10]) by hub.freebsd.org (Postfix) with SMTP id A233237B422 for ; Tue, 24 Apr 2001 14:51:56 -0700 (PDT) (envelope-from cohentl@clarkson.edu) Received: (qmail 26484 invoked by uid 0); 24 Apr 2001 21:51:53 -0000 Received: from isis.aoc.clarkson.edu (128.153.130.35) by mail.clarkson.edu with SMTP; 24 Apr 2001 21:51:53 -0000 Date: Tue, 24 Apr 2001 17:51:54 -0400 (EDT) From: Todd Cohen X-Sender: cohentl@isis.aoc.clarkson.edu To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: is this device bad? In-Reply-To: <20010424150803.A1146@panzer.kdm.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 Yeah, it is da1.. sorry about that.. the other hd is this machine is a loaner and it's not the greatest either :) I'll try a different timeout.. thanks. -Todd > > Isn't the drive you're trying to talk to da1? > > The last message is the one that might pertain to da1, but I'm not sure > what that means. You'll have to ask Gerard what that means, and then we > can perhaps figure out why the disk is timing out. > > Another potential problem is the timeout length may be overflowing a 32-bit > integer. > > IIRC, HZ on the alpha is 1000. The sym(4) driver uses the following to > calculate the timeout: > > ccb->ccb_h.timeout_ch = timeout(sym_timeout, (caddr_t) ccb, > ccb->ccb_h.timeout*hz/1000); > > So with a timeout of 10800 seconds, or 10,800,000 ms, multiplied by hz, > which is likely 1000 on the alpha, you would overflow a 32-bit integer. > > So try a timeout of 4200 seconds instead, and see if that works. That's 70 > minutes, but it might be enough for the format to complete. > > If not, we'll have to adjust the above calculation to use 64-bit math so it > won't overflow. > > Ken > -- > Kenneth Merry > ken@kdm.org > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message > __________________________________________________________________________ ICMP: The protocol that goes PING! I like angles, but only to a degree. cthread. cthread_fork(). Fork, thread, fork! Black holes suck. http://wckn.clarkson.edu/~cohentl/ Real_men_don't_need_spacebars. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 25 2:51:31 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.159.1.85]) by hub.freebsd.org (Postfix) with ESMTP id 035A437B422 for ; Wed, 25 Apr 2001 02:51:29 -0700 (PDT) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id KAA31411; Wed, 25 Apr 2001 10:51:25 +0100 (BST) (envelope-from geoffb) Date: Wed, 25 Apr 2001 10:51:25 +0100 From: Geoff Buckingham To: Greg Rumple Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Dell Poweredge 2550 Message-ID: <20010425105125.A31388@chuggalug.clues.com> References: <20010424230757.C47984@zaphon.llamas.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <20010424230757.C47984@zaphon.llamas.net>; from Greg Rumple on Tue, Apr 24, 2001 at 11:07:57PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Apr 24, 2001 at 11:07:57PM -0700, Greg Rumple wrote: I have moved this to freebsd-scsi > I just purchased a Dell Poweredge 2550 with the on-board Raid Controller > option, and just burned a copy of the 4.3 release CD to install on it. > It comes up stating it has a Dell Perc 3/Di raid controller, and all > looks fine (I have a nice 100+ gig raid 5 array). > > I than boot the install, and it finds no drives. I'm assuming one of > the following messages is the source of my problems. > > pci3: (vendor=0x9005, dev=0x00c5) at 4.0 irq 10 > pci2: (vendor=0x1028, dev=0x0002) at 2.1 irq 10 > pci1: (vendor-0x14e4, dev=0x1644) at 8.0 irq 10 > > I was hoping this would just work out of the box. I'm hoping I can get > this working. Any help would be greatly appreciated. > > It does see the onboard Adaptec aic7899 controller, just not the raid > controller. > > Thanks. > > Greg > > -- > Greg Rumple > grumple@zaphon.llamas.net > I assume from the above, that the Intall saw the disk device and you were, able to install to it, problems only occur when booting from the installed fs ? If so try booting from the CDs kernel. -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 25 4:10: 4 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from k2.vii.p.lodz.pl (k2.vii.p.lodz.pl [212.191.78.186]) by hub.freebsd.org (Postfix) with ESMTP id D306D37B422 for ; Wed, 25 Apr 2001 04:09:57 -0700 (PDT) (envelope-from krzychk2@k2.vii.p.lodz.pl) Received: from localhost (krzychk2@localhost) by k2.vii.p.lodz.pl (8.11.1/8.11.1) with ESMTP id f3PBBqP00744 for ; Wed, 25 Apr 2001 13:12:03 +0200 (CEST) (envelope-from krzychk2@k2.vii.p.lodz.pl) Date: Wed, 25 Apr 2001 13:11:47 +0200 (CEST) From: Krzysztof Kardas To: freebsd-scsi@freebsd.org Subject: Adaptec AHA1520b 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 HI. I'm new, so mayby i'w writing to wrong group. I've got AHA1520b & FreeBSD 4.2. I've compiled kernel with device aic0, and this is the problem. System doesn't recognize my card. When I type dmesg I see nothing about aic0. What should i do? Can someone tell me step by step what should i do? KrzychK2 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 25 6:51: 6 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from zaphon.llamas.net (zaphon.llamas.net [207.203.36.210]) by hub.freebsd.org (Postfix) with SMTP id 83B3B37B423 for ; Wed, 25 Apr 2001 06:51:03 -0700 (PDT) (envelope-from grumple@zaphon.llamas.net) Received: (qmail 5194 invoked by uid 1001); 25 Apr 2001 13:51:01 -0000 Date: Wed, 25 Apr 2001 06:10:43 -0700 From: Greg Rumple To: Geoff Buckingham Subject: Re: Dell Poweredge 2550 Message-ID: <20010425061043.E47984@zaphon.llamas.net> References: <20010424230757.C47984@zaphon.llamas.net> <20010425105125.A31388@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010425105125.A31388@chuggalug.clues.com>; from geoffb@chuggalug.clues.com on Wed, Apr 25, 2001 at 10:51:25AM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org * Geoff Buckingham (geoffb@chuggalug.clues.com) [010425 09:51]: > On Tue, Apr 24, 2001 at 11:07:57PM -0700, Greg Rumple wrote: > > I have moved this to freebsd-scsi > > > I just purchased a Dell Poweredge 2550 with the on-board Raid Controller > > option, and just burned a copy of the 4.3 release CD to install on it. > > It comes up stating it has a Dell Perc 3/Di raid controller, and all > > looks fine (I have a nice 100+ gig raid 5 array). > > > > I than boot the install, and it finds no drives. I'm assuming one of > > the following messages is the source of my problems. > > > > pci3: (vendor=0x9005, dev=0x00c5) at 4.0 irq 10 > > pci2: (vendor=0x1028, dev=0x0002) at 2.1 irq 10 > > pci1: (vendor-0x14e4, dev=0x1644) at 8.0 irq 10 > > > > I was hoping this would just work out of the box. I'm hoping I can get > > this working. Any help would be greatly appreciated. > > > > It does see the onboard Adaptec aic7899 controller, just not the raid > > controller. > > > > Thanks. > > > > Greg > > > > -- > > Greg Rumple > > grumple@zaphon.llamas.net > > > I assume from the above, that the Intall saw the disk device and you were, > able to install to it, problems only occur when booting from the installed > fs ? Nope this was from the install CD. > > If so try booting from the CDs kernel. > > -- > GeoffB -- Greg Rumple grumple@zaphon.llamas.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 25 8:53:55 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.wolves.k12.mo.us (mail.wolves.k12.mo.us [207.160.214.1]) by hub.freebsd.org (Postfix) with ESMTP id A82D837B422 for ; Wed, 25 Apr 2001 08:53:53 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from mail.wolves.k12.mo.us (cdillon@mail.wolves.k12.mo.us [207.160.214.1]) by mail.wolves.k12.mo.us (8.9.3/8.9.3) with ESMTP id KAA62829; Wed, 25 Apr 2001 10:53:41 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Wed, 25 Apr 2001 10:53:41 -0500 (CDT) From: Chris Dillon To: Krzysztof Kardas Cc: Subject: Re: Adaptec AHA1520b 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 Wed, 25 Apr 2001, Krzysztof Kardas wrote: > HI. I'm new, so mayby i'w writing to wrong group. I've got > AHA1520b & FreeBSD 4.2. I've compiled kernel with device aic0, and > this is the problem. System doesn't recognize my card. When I type > dmesg I see nothing about aic0. What should i do? Can someone tell > me step by step what should i do? I can't tell you step-by-step what you need to do, but I can tell you that FreeBSD is probably looking in the wrong place for the card. You need to either set the card to match FreeBSD's idea of where it is, or else tell FreeBSD where it is. The FreeBSD default for the aic controller is port 0x340 irq 11. You can set the jumpers on the card to port 0x340 irq 11, assuming nothing else in your system is using those parameters, or you can recompile the FreeBSD kernel with the appropriate parameters supplied to the aic driver, or you can adjust the parameters using the kernel userconfig before you boot the system. The latter is the easiest thing to do. Just hit a key before the kernel boots (when the loader tells you to), then type 'boot -c' to get into userconfig. -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net FreeBSD: The fastest and most stable server OS on the planet. For IA32 and Alpha architectures. IA64, PPC, and ARM under development. http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 25 13:14:35 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from laime.cs.uchicago.edu (laime.cs.uchicago.edu [128.135.11.244]) by hub.freebsd.org (Postfix) with ESMTP id 2EC8737B422 for ; Wed, 25 Apr 2001 13:14:33 -0700 (PDT) (envelope-from joygila@cs.uchicago.edu) Received: from abyss.cs.uchicago.edu (postfix@abyss.cs.uchicago.edu [128.135.11.27]) by laime.cs.uchicago.edu (8.10.2/8.9.3) with ESMTP id f3PKERe25308 for ; Wed, 25 Apr 2001 15:14:27 -0500 (CDT) Received: by abyss.cs.uchicago.edu (Postfix, from userid 12311) id E24EE5ACD8; Wed, 25 Apr 2001 15:14:26 -0500 (CDT) Received: from localhost (localhost [127.0.0.1]) by abyss.cs.uchicago.edu (Postfix) with ESMTP id 911C85ACD7 for ; Wed, 25 Apr 2001 15:14:26 -0500 (CDT) Date: Wed, 25 Apr 2001 15:14:26 -0500 (CDT) From: Joy Gila To: scsi@freebsd.org Subject: mylex dac 960 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 all-- so, the card i'm talking about is the DAC960PTL1 or at least that's what the RAID configuration software is calling it. So, yeah, the bios is recognizing the card and this Mylex RAID EzAssist 1.00-16 seems to take the config to do mirroring. when i try to keep booting off the freebsd 4.2 cd i get halted at the point where it's waiting for scsi devices to settle i remember noting that there was support for this particular card in freebsd but i have lost the url for that and when i strarting the search again i stumbled across your mail archive and thought i would post to it. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Apr 25 17:37:35 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 A624E37B446 for ; Wed, 25 Apr 2001 17:37:20 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (msmith@localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.2) with ESMTP id f3Q0XKb18948; Wed, 25 Apr 2001 17:33:21 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104260033.f3Q0XKb18948@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Geoff Buckingham Cc: Greg Rumple , freebsd-scsi@freebsd.org Subject: Re: Dell Poweredge 2550 In-reply-to: Your message of "Wed, 25 Apr 2001 10:51:25 BST." <20010425105125.A31388@chuggalug.clues.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 25 Apr 2001 17:33:19 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Tue, Apr 24, 2001 at 11:07:57PM -0700, Greg Rumple wrote: > > I have moved this to freebsd-scsi Chris Csanady just pointed out that this controller has a new PCI ID. Unfortunately, we're a couple of days too late to get this into 4.3. (Why does nobody at Dell tell me these things? 8( ) I'm about to add it to the driver; you'll have to use a post-4.3 snapshot boot floppy set to install, though. If someone with one of these controllers could build a suitably patched install floppy set and GENERIC kernel vis. the 4.2 kit I built for the 'aac' driver and submit it, I'd be very happy to put it up for 4.3 people to use. > > I just purchased a Dell Poweredge 2550 with the on-board Raid Controller > > option, and just burned a copy of the 4.3 release CD to install on it. > > It comes up stating it has a Dell Perc 3/Di raid controller, and all > > looks fine (I have a nice 100+ gig raid 5 array). > > > > I than boot the install, and it finds no drives. I'm assuming one of > > the following messages is the source of my problems. > > > > pci3: (vendor=0x9005, dev=0x00c5) at 4.0 irq 10 > > pci2: (vendor=0x1028, dev=0x0002) at 2.1 irq 10 > > pci1: (vendor-0x14e4, dev=0x1644) at 8.0 irq 10 > > > > I was hoping this would just work out of the box. I'm hoping I can get > > this working. Any help would be greatly appreciated. > > > > It does see the onboard Adaptec aic7899 controller, just not the raid > > controller. > > > > Thanks. > > > > Greg > > > > -- > > Greg Rumple > > grumple@zaphon.llamas.net > > > I assume from the above, that the Intall saw the disk device and you were, > able to install to it, problems only occur when booting from the installed > fs ? -- ... 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 Thu Apr 26 1:57:15 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from chuggalug.clues.com (chuggalug.clues.com [194.159.1.85]) by hub.freebsd.org (Postfix) with ESMTP id CD7E537B423 for ; Thu, 26 Apr 2001 01:57:12 -0700 (PDT) (envelope-from geoffb@chuggalug.clues.com) Received: (from geoffb@localhost) by chuggalug.clues.com (8.9.3/8.9.3) id JAA44381; Thu, 26 Apr 2001 09:57:05 +0100 (BST) (envelope-from geoffb) Date: Thu, 26 Apr 2001 09:57:05 +0100 From: Geoff Buckingham To: Joy Gila Cc: scsi@FreeBSD.ORG Subject: Re: mylex dac 960 Message-ID: <20010426095705.A44337@chuggalug.clues.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: ; from Joy Gila on Wed, Apr 25, 2001 at 03:14:26PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, Apr 25, 2001 at 03:14:26PM -0500, Joy Gila wrote: > hello all-- > > so, the card i'm talking about is the > > DAC960PTL1 > > or at least that's what the RAID configuration software is calling > it. So, yeah, the bios is recognizing the card and this > > Mylex RAID EzAssist 1.00-16 > seems to take the config to do mirroring. > > when i try to keep booting off the freebsd 4.2 cd i get halted at the > point where it's waiting for scsi devices to settle > > i remember noting that there was support for this particular card in > freebsd but i have lost the url for that and when i strarting the search > again i stumbled across your mail archive and thought i would post to it. > Try http://people.freebsd.org/~msmith/RAID/ -- GeoffB To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 26 2: 2:34 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from mail-internal.nextra.de (mail.nextra.de [212.169.184.81]) by hub.freebsd.org (Postfix) with ESMTP id 82B6737B43C for ; Thu, 26 Apr 2001 02:02:31 -0700 (PDT) (envelope-from O.Blasnik@nextra.de) Received: from f-ex-01.intern.nextra.de (f-euro.fw.nextra.de [212.169.184.9]) by mail-internal.nextra.de (8.9.3/8.9.3) with ESMTP id LAA80457 for ; Thu, 26 Apr 2001 11:02:30 +0200 (CEST) Received: from omnilinkw63 ([10.49.96.101]) by f-ex-01.intern.nextra.de with Microsoft SMTPSVC(5.0.2195.1600); Thu, 26 Apr 2001 10:57:52 +0100 Message-ID: <001b01c0ce2e$ed2c6120$6560310a@intern.nextra.de> From: "Oliver Blasnik" To: Subject: ICP Vortex running... Date: Thu, 26 Apr 2001 10:57:30 +0200 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 5.00.2919.6700 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6700 X-OriginalArrivalTime: 26 Apr 2001 09:57:52.0957 (UTC) FILETIME=[5C11D6D0:01C0CE37] Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hiho, I just got an ICP Vortex Raid Controller (GDT6523RS) and took a look at the CD. WOW! They're delivering a FreeBSD4.x/5.x Kernel Module AND complete source for statically linking that driver into the kernel. Mike said sth. about that drivers are going to be implemented into 4.3. I don't see anything in the release notes. What happend? Also on that CD is a console utility for configuring controller and raidsets, really, really exciting. Worked in my 4.2S testbox without any problems in a (the new) Intel SR2100 chassis, fully utilizing the integrated SCA hotswap-controller/ backplane. Errors and status messages are going into syslog, nice to see that. Someone has really thought about this one... And - in diffrence to our in-use AMI Megaraid cards, the devices get "daX"-naming, not that silly amrX. Just to let you know - and to let Mike know that the driver's out ;) Cu, Oliver -- -- http://www.nextra.de - INTERNET@WORK ----- oliver.blasnik@nextra.de -- Nextra Deutschland | Oliver Blasnik Senior System Administrator GmbH & Co KG | Lyoner Strasse 26 D-60528 Frankfurt Engineering TA&S | tel +49-69-66441-0 fax +49-69-66441-199 ------------------------------------------------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 26 2:20:16 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 86BAF37B423 for ; Thu, 26 Apr 2001 02:20:13 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id LAA01911 for freebsd-scsi@freebsd.org; Thu, 26 Apr 2001 11:20:12 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3Q95gb50460 for freebsd-scsi@freebsd.org; Thu, 26 Apr 2001 11:05:42 +0200 (MET DST) (envelope-from j) Date: Thu, 26 Apr 2001 11:05:42 +0200 From: J Wunsch To: freebsd-scsi@freebsd.org Subject: Another problem with the new CAM error handling Message-ID: <20010426110542.A50185@uriah.heep.sax.de> Reply-To: Joerg Wunsch Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Apr 26 11:03:16 uriah /boot/kernel/kernel: (pt0:sym1:0:5:0): SEND(06). CDB: a 0 0 0 2 0 Apr 26 11:03:16 uriah /boot/kernel/kernel: (pt0:sym1:0:5:0): CAM Status: SCSI Status Error Apr 26 11:03:16 uriah /boot/kernel/kernel: (pt0:sym1:0:5:0): SCSI Status: Check Condition Apr 26 11:03:17 uriah /boot/kernel/kernel: (pt0:sym1:0:5:0): UNIT ATTENTION Apr 26 11:03:17 uriah /boot/kernel/kernel: (pt0:sym1:0:5:0): Unretryable error Apr 26 11:03:17 uriah /boot/kernel/kernel: (pt0:sym1:0:5:0): Invalidating device I thought a UA condition would always be retried? In particular, it should never end up in an `invalidating device' message. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 26 7:35:53 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 5FE0F37B43E for ; Thu, 26 Apr 2001 07:35:51 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f3QEZLs23573; Thu, 26 Apr 2001 08:35:47 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200104261435.f3QEZLs23573@aslan.scsiguy.com> To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Another problem with the new CAM error handling In-Reply-To: Your message of "Thu, 26 Apr 2001 11:05:42 +0200." <20010426110542.A50185@uriah.heep.sax.de> Date: Thu, 26 Apr 2001 08:35:21 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Apr 26 11:03:16 uriah /boot/kernel/kernel: (pt0:sym1:0:5:0): SEND(06). CDB: a >0 0 0 2 0 >Apr 26 11:03:16 uriah /boot/kernel/kernel: (pt0:sym1:0:5:0): CAM Status: SCSI >Status Error >Apr 26 11:03:16 uriah /boot/kernel/kernel: (pt0:sym1:0:5:0): SCSI Status: Chec >k Condition >Apr 26 11:03:17 uriah /boot/kernel/kernel: (pt0:sym1:0:5:0): UNIT ATTENTION >Apr 26 11:03:17 uriah /boot/kernel/kernel: (pt0:sym1:0:5:0): Unretryable error >Apr 26 11:03:17 uriah /boot/kernel/kernel: (pt0:sym1:0:5:0): Invalidating devi >ce > >I thought a UA condition would always be retried? In particular, >it should never end up in an `invalidating device' message. The peripheral driver must specify that the UA condition should be retried in its call to cam_periph_error(). The pt driver must not do that. The new error recovery code isn't responsible for this error. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 26 8:11:15 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from k2.vii.p.lodz.pl (k2.vii.p.lodz.pl [212.191.78.186]) by hub.freebsd.org (Postfix) with ESMTP id 606B137B424 for ; Thu, 26 Apr 2001 08:11:12 -0700 (PDT) (envelope-from krzychk2@k2.vii.p.lodz.pl) Received: (from krzychk2@localhost) by k2.vii.p.lodz.pl (8.11.1/8.11.1) id f3QFDIW00274 for freebsd-scsi@freebsd.org; Thu, 26 Apr 2001 17:13:18 +0200 (CEST) (envelope-from krzychk2) Date: Thu, 26 Apr 2001 17:13:18 +0200 (CEST) From: Krzysztof Kardas Message-Id: <200104261513.f3QFDIW00274@k2.vii.p.lodz.pl> To: freebsd-scsi@freebsd.org Subject: AHA 1520b & Yamaha CDR400 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi. I've got problem on FreeBSD4.2. I've got equiptemnt as in topic and there is a problem with cd-recorder. This is my only SCSI device ( ID 0 + terminator). Problem is with my system. When it's booting, it stops on SCSI detection. After a minute I've got something like that : probe0:aic0:0:0:0 ccb 0xc0963400 - timed out phase 0xb6 state 1 and i can wait untill world ends. I worked on Debian with this equiptemnt and all was ok. So hardware is ok. I don't know what to do. Can anybody help me? Thanks. BTW. I've got this message on generic kernel and my own kernel. SCSI is compiled into kernel. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 26 8:12:27 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from otto.oss.uswest.net (otto.oss.uswest.net [204.147.85.81]) by hub.freebsd.org (Postfix) with ESMTP id 50F0837B422 for ; Thu, 26 Apr 2001 08:12:24 -0700 (PDT) (envelope-from pmckenna@otto.oss.uswest.net) Received: (from pmckenna@localhost) by otto.oss.uswest.net (8.11.3/8.11.1) id f3QFB7C43427; Thu, 26 Apr 2001 10:11:07 -0500 (CDT) (envelope-from pmckenna) Date: Thu, 26 Apr 2001 10:11:04 -0500 From: Pete McKenna To: Oliver Blasnik Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ICP Vortex running... Message-ID: <20010426101104.F738@otto.oss.qwest.net> References: <001b01c0ce2e$ed2c6120$6560310a@intern.nextra.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001b01c0ce2e$ed2c6120$6560310a@intern.nextra.de>; from oliver.blasnik@nextra.de on Thu, Apr 26, 2001 at 10:57:30AM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We have a card and drivers in to eval too. Our's happen to be fiber channel which use the same driver. AFAIK this is one of only two or three supported fiber channel cards in FreeBSD. One problem, the fiber channel card / driver is unable to boot FreeBSD from the RAID. This issue was being worked but I have'nt heard an update. Pete On Thu, Apr 26, 2001 at 10:57:30AM +0200, Oliver Blasnik wrote: > Hiho, > > I just got an ICP Vortex Raid Controller (GDT6523RS) and took a look > at the CD. WOW! They're delivering a FreeBSD4.x/5.x Kernel Module AND > complete source for statically linking that driver into the kernel. > > Mike said sth. about that drivers are going to be implemented into 4.3. > I don't see anything in the release notes. What happend? > > Also on that CD is a console utility for configuring controller and > raidsets, really, really exciting. > > Worked in my 4.2S testbox without any problems in a (the new) Intel > SR2100 chassis, fully utilizing the integrated SCA hotswap-controller/ > backplane. Errors and status messages are going into syslog, nice > to see that. Someone has really thought about this one... > > And - in diffrence to our in-use AMI Megaraid cards, the devices > get "daX"-naming, not that silly amrX. > > Just to let you know - and to let Mike know that the driver's out ;) > > Cu, Oliver > -- > -- http://www.nextra.de - INTERNET@WORK ----- oliver.blasnik@nextra.de -- > Nextra Deutschland | Oliver Blasnik Senior System Administrator > GmbH & Co KG | Lyoner Strasse 26 D-60528 Frankfurt > Engineering TA&S | tel +49-69-66441-0 fax +49-69-66441-199 > ------------------------------------------------------------------------- > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message -- Peter McKenna Qwest Internet Solutions pmckenna@qwest.net Main 612-664-4000 FAX 612-664-4770 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 26 9:50: 6 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 1ED3537B423 for ; Thu, 26 Apr 2001 09:50:00 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id SAA11870; Thu, 26 Apr 2001 18:49:59 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3QGgua51919; Thu, 26 Apr 2001 18:42:56 +0200 (MET DST) (envelope-from j) Date: Thu, 26 Apr 2001 18:42:56 +0200 (MET DST) Message-Id: <200104261642.f3QGgua51919@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <200104261513.f3QFDIW00274@k2.vii.p.lodz.pl> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: AHA 1520b & Yamaha CDR400 X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Cc: Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Krzysztof Kardas wrote: > I worked on Debian with this equiptemnt and all was ok. So hardware > is ok. I don't know what to do. Can anybody help me? Drop the 1520. Send me a snail mail address, and i'll get you an AHA1540B. Basically for free, except i don't have an idea about shipping costs. If you incidentally come down here to Dresden, you'll get it. It'll serve you a lot better than the 1520. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 26 10:20:12 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 42CF037B632 for ; Thu, 26 Apr 2001 10:20:05 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id TAA12928 for freebsd-scsi@FreeBSD.ORG; Thu, 26 Apr 2001 19:20:04 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3QH7Eq51997 for freebsd-scsi@FreeBSD.ORG; Thu, 26 Apr 2001 19:07:14 +0200 (MET DST) (envelope-from j) Date: Thu, 26 Apr 2001 19:07:14 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Subject: Re: Another problem with the new CAM error handling Message-ID: <20010426190714.E50185@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: <20010426110542.A50185@uriah.heep.sax.de> <200104261435.f3QEZLs23573@aslan.scsiguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200104261435.f3QEZLs23573@aslan.scsiguy.com>; from gibbs@scsiguy.com on Thu, Apr 26, 2001 at 08:35:21AM -0600 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Justin T. Gibbs wrote: > >I thought a UA condition would always be retried? In particular, > >it should never end up in an `invalidating device' message. > > The peripheral driver must specify that the UA condition should > be retried in its call to cam_periph_error(). The pt driver must > not do that. The new error recovery code isn't responsible for > this error. Hmm, but it used to work with the old CAM error handling code. ;-) Anyway, looking at the pt driver, it seems to go length to handle SF_RETRY_UA, differentiating various cases. I think it would already properly ignore it after a bus reset or bus device reset. In my case however, it's a UA after a device power-on. IMHO that's the only possibility for an UA that has been left out, so why bother and not always ignore them? The other thing that is annoying is that, after the `invalidating device', it takes another power-off, camcontrol rescan, power-on, and camcontrol rescan cycle in order to revive the device, since even a simple rescan leaves the device invalidated. IMHO, there should at least be a `camcontrol forget' option to completely abandon a device without the need to power it off, and rescan the bus. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Apr 26 19:53: 6 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from zaphon.llamas.net (zaphon.llamas.net [207.203.36.210]) by hub.freebsd.org (Postfix) with SMTP id 5E40F37B424 for ; Thu, 26 Apr 2001 19:53:04 -0700 (PDT) (envelope-from grumple@zaphon.llamas.net) Received: (qmail 98568 invoked by uid 1001); 27 Apr 2001 02:52:59 -0000 Date: Thu, 26 Apr 2001 19:52:59 -0700 From: Greg Rumple To: Mike Smith Cc: Marty Moll , freebsd-scsi@FreeBSD.ORG Subject: Re: Dell Poweredge 2550 Message-ID: <20010426195259.B96913@zaphon.llamas.net> References: <000801c0cded$7a8d55c0$256afea9@algol> <200104260120.f3Q1KeL19621@mass.dis.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200104260120.f3Q1KeL19621@mass.dis.org>; from msmith@freebsd.org on Wed, Apr 25, 2001 at 06:20:40PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Thanks for your help and assistance. I am happy to report that I got the machine up. I ended up doing a full make release from another machine that was cvsup'd this AM, and than creating a ISO image from that (what a learning experience this whole task was). It installed flawlessly (and extremely fast). I haven't done any performance numbers yet, but I'll be very curious to see how well it performs. Thanks again, Greg * Mike Smith (msmith@freebsd.org) [010426 01:16]: > > Thanks for the extra PCI IDs, Marty. All committed. > > 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 > -- Greg Rumple grumple@zaphon.llamas.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 27 0:19:57 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 94A1C37B423 for ; Fri, 27 Apr 2001 00:19:54 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id JAA24759 for freebsd-scsi@freebsd.org; Fri, 27 Apr 2001 09:19:53 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3R7Iqj55231 for freebsd-scsi@freebsd.org; Fri, 27 Apr 2001 09:18:52 +0200 (MET DST) (envelope-from j) Date: Fri, 27 Apr 2001 09:18:52 +0200 From: J Wunsch To: freebsd-scsi@freebsd.org Subject: sa(4) jamming Message-ID: <20010427091852.L50185@uriah.heep.sax.de> Reply-To: Joerg Wunsch Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Tonight, my daily backup was completely jamming. The process trying to write to the tape was: 0 54453 54451 0 -8 0 1708 368 physst DWL ?? 0:00.33 team 1m 3 The tape moved occasionally a bit (audible event), but was otherwise stuck. Note that the green LED on the Tandberg is normally flashing when the device is active, and steady green when it's idle -- it was steady green back then. My only remedy was to perform a SCSI bus reset (a BDR didn't help, the "camcontrol reset 1:4:0" went stuck as well). This never ever happened before... When it happens again, does anybody have an idea how to debug why it jams in physstrat()? (DDB is available, CAMDEBUG as well.) -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 27 2:20: 1 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id A198C37B424 for ; Fri, 27 Apr 2001 02:19:56 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id LAA27039 for freebsd-scsi@freebsd.org; Fri, 27 Apr 2001 11:19:55 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3R92V555575; Fri, 27 Apr 2001 11:02:31 +0200 (MET DST) (envelope-from j) Date: Fri, 27 Apr 2001 11:02:31 +0200 (MET DST) Message-Id: <200104270902.f3R92V555575@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <20010427091852.L50185@uriah.heep.sax.de> From: j@uriah.heep.sax.de (J Wunsch) Subject: Re: sa(4) jamming X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org J Wunsch wrote: > Tonight, my daily backup was completely jamming. The process trying > to write to the tape was: > > 0 54453 54451 0 -8 0 1708 368 physst DWL ?? 0:00.33 team 1m 3 The problem seems to be reproducible. After finishing 16 % of the dump, it jammed again. I also noted that the tape is in constant start-stop operation, so completing those 16 % took already 1.5 hours, where normally that filesystem had been dumped completely within half an hour. mt -f /dev/sa0.ctl stat says: Mode Density Blocksize bpi Compression Current: default variable 0 0x3 ---------available modes--------- 0: default variable 0 0x3 1: default variable 0 0x3 2: default variable 0 0x3 3: default variable 0 0x3 --------------------------------- Current Driver State: Writing. --------------------------------- File Number: 0 Record Number: 2101 Residual Count 0 That is after aborting the dump itself, but with the last child process of `team' still jamming in status `D' (physstrat()), I turned on "camcontrol debug -ITc 1:4:0", here are the kernel messages so far: Apr 27 10:49:13 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): saopen(0): dev=0x0 softc=0xc2d Apr 27 10:49:13 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): saopen(0): dev=0x0 softc=0xc2d Apr 27 10:49:13 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): saclose(0): dev=0x0 softc=0xc2d Apr 27 10:53:35 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): xpt_done Apr 27 10:53:35 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): camisr(sa0:sym1:0:4:0): sastrategy: enqueuing a 65536 variable byte write queue count now 1 Apr 27 10:53:35 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): xpt_schedule Apr 27 10:53:35 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): xpt_setup_ccb Apr 27 10:53:35 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): sastart(sa0:sym1:0:4:0): Variable Record Count is 65536 Apr 27 10:53:35 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): xpt_action Apr 27 10:53:35 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): WRITE(06). CDB: a 0 1 0 0 0 Apr 27 10:53:35 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): sym_action That single WRITE(06) occurred all of a sudden. No idea when the next one will happen... The kernel is still from ~ April 01, plus my recent fix for the ILI/filemark handling. Oh, here's another one: Apr 27 11:00:35 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): xpt_done Apr 27 11:00:35 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): camisr(sa0:sym1:0:4:0): sastrategy: enqueuing a 65536 variable byte write queue count now 1 Apr 27 11:00:35 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): xpt_schedule Apr 27 11:00:35 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): xpt_setup_ccb Apr 27 11:00:35 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): sastart(sa0:sym1:0:4:0): Variable Record Count is 65536 Apr 27 11:00:35 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): xpt_action Apr 27 11:00:35 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): WRITE(06). CDB: a 0 1 0 0 0 Apr 27 11:00:36 uriah /boot/kernel/kernel: (sa0:sym1:0:4:0): sym_action Seven minutes pause between writing two records... mt stat increases the record count, still. I aborted the operation by now. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 27 9: 7:15 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from zaphon.llamas.net (zaphon.llamas.net [207.203.36.210]) by hub.freebsd.org (Postfix) with SMTP id 59BA737B422 for ; Fri, 27 Apr 2001 09:07:13 -0700 (PDT) (envelope-from grumple@zaphon.llamas.net) Received: (qmail 9411 invoked by uid 1001); 27 Apr 2001 16:06:57 -0000 Date: Fri, 27 Apr 2001 09:06:57 -0700 From: Greg Rumple To: freebsd-scsi@freebsd.org Subject: one last question (re: dell poweredge 2550) Message-ID: <20010427090656.T96913@zaphon.llamas.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org So I got the machine up, it's working. I just was browsing the dmesg output and wanna verify this is okay. Here is the dmesg lines relevant to the raid controller in this system. su-2.05# dmesg | grep aac aac0: mem 0xf0000000-0xf7ffffff irq 2 at device 2.1 on pci2 aac0: i960RX 100MHz, 126MB total memory, optional battery present (3) aac0: Kernel 2.5-0, S/N fafaf001adc001d2 aacd0: on aac0 aacd0: 104137MB (213274368 sectors) What bothers me is the fact that aac0 is on irq 2. This seems odd. *shrug*. System seems fine. Small test (writing a 20 gig file, and than reading it) shows writes: 20M/sec reads: 47M/sec This is a raid-5 with 4 36 gig drives on it. Greg -- Greg Rumple To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 27 9:19:56 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id DD87537B423 for ; Fri, 27 Apr 2001 09:19:52 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id SAA10883 for freebsd-scsi@FreeBSD.ORG; Fri, 27 Apr 2001 18:19:51 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3RFrlu56807 for freebsd-scsi@FreeBSD.ORG; Fri, 27 Apr 2001 17:53:47 +0200 (MET DST) (envelope-from j) Date: Fri, 27 Apr 2001 17:53:47 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Subject: Re: sa(4) jamming Message-ID: <20010427175347.A56791@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: <20010427091852.L50185@uriah.heep.sax.de> <200104270902.f3R92V555575@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200104270902.f3R92V555575@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Fri, Apr 27, 2001 at 11:02:31AM +0200 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As J Wunsch wrote: > The problem seems to be reproducible. After finishing 16 % of the > dump, it jammed again. Hmm, after unloading and reloading the medium, it works again. The degenerated performance and start-stop behaviour are gone now. Weird. Smells like a bug somewhere, but /where/? Could it be related to the SCSI bus reset that was needed to revive my pt0 device (see other thread)? The tape drive is on the same bus. Of course, the tape was idle while i issued the camcontrol reset command, but the cartridge had not been unloaded afterwards (until right now), so for sure sa(4) must have seen a unit attention when going to access the tape again. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 27 9:49:38 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id C675237B424 for ; Fri, 27 Apr 2001 09:49:35 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f3RGmts35017; Fri, 27 Apr 2001 10:49:31 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200104271649.f3RGmts35017@aslan.scsiguy.com> To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sa(4) jamming In-Reply-To: Your message of "Fri, 27 Apr 2001 17:53:47 +0200." <20010427175347.A56791@uriah.heep.sax.de> Date: Fri, 27 Apr 2001 10:48:55 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Could it be related to the SCSI bus reset that was needed to revive my >pt0 device (see other thread)? The tape drive is on the same bus. Of >course, the tape was idle while i issued the camcontrol reset command, >but the cartridge had not been unloaded afterwards (until right now), >so for sure sa(4) must have seen a unit attention when going to access >the tape again. That depends on whether the sa driver relies on any settings (mode page or otherwise) that are invalidated by a reset, but aren't restored when the bus reset async event occurs. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 27 10: 0:59 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id 28E5237B423 for ; Fri, 27 Apr 2001 10:00:52 -0700 (PDT) (envelope-from gibbs@scsiguy.com) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.2/8.9.3) with ESMTP id f3RH01s35435; Fri, 27 Apr 2001 11:00:28 -0600 (MDT) (envelope-from gibbs@scsiguy.com) Message-Id: <200104271700.f3RH01s35435@aslan.scsiguy.com> To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sa(4) jamming In-Reply-To: Your message of "Fri, 27 Apr 2001 10:48:55 MDT." <200104271649.f3RGmts35017@aslan.scsiguy.com> Date: Fri, 27 Apr 2001 11:00:01 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >That depends on whether the sa driver relies on any settings (mode >page or otherwise) that are invalidated by a reset, but aren't >restored when the bus reset async event occurs. Just to be more clear here, it is the peripheral driver's responsibility to restore any of this state if it needs to. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Apr 27 10: 1:13 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 A745937B62E for ; Fri, 27 Apr 2001 10:00:56 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (msmith@localhost [127.0.0.1]) by mass.dis.org (8.11.3/8.11.2) with ESMTP id f3RH5e001529; Fri, 27 Apr 2001 10:05:40 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200104271705.f3RH5e001529@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: Greg Rumple Cc: freebsd-scsi@freebsd.org Subject: Re: one last question (re: dell poweredge 2550) In-reply-to: Your message of "Fri, 27 Apr 2001 09:06:57 PDT." <20010427090656.T96913@zaphon.llamas.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 27 Apr 2001 10:05:40 -0700 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > So I got the machine up, it's working. I just was browsing the dmesg > output and wanna verify this is okay. > > Here is the dmesg lines relevant to the raid controller in this system. > > aac0: mem 0xf0000000-0xf7ffffff irq 2 at device 2.1 on pci2 > aac0: i960RX 100MHz, 126MB total memory, optional battery present (3) > aac0: Kernel 2.5-0, S/N fafaf001adc001d2 > aacd0: on aac0 > aacd0: 104137MB (213274368 sectors) > > What bothers me is the fact that aac0 is on irq 2. This seems odd. This is an SMP system, right? If so, there's nothing odd about it - in SMP mode the "irq" value doesn't bear any resemblance to the old IRQ scheme. -- ... 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 Fri Apr 27 18:53:18 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from eal.miknet.net (eal.miknet.net [202.174.235.5]) by hub.freebsd.org (Postfix) with ESMTP id 5AA6437B423 for ; Fri, 27 Apr 2001 18:53:13 -0700 (PDT) (envelope-from michael@miknet.net) Received: from michael by eal.miknet.net with local (Exim 3.22 #1 (Debian)) id 14tJpH-0001yh-00 for ; Sat, 28 Apr 2001 11:47:11 +1000 Date: Sat, 28 Apr 2001 11:47:11 +1000 To: freebsd-scsi@freebsd.org Subject: NULL pointer deref in scsi_sense_desc Message-ID: <20010428114711.A7571@miknet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.17i From: Michael Samuel Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I got a "Page fault in kernel mode" which writing to a SCSI tape (which had barfed on me with some SCSI sense messages shortly before the crash). This is in -current from the CVS as of about a week or 2 ago. It stopped at scsi_sense_desc+0x2f, which resolved in gdb -k to cam/scsi/scsi_all.c line 1573, which in my copy of the source tree looks like this: void scsi_sense_desc(int sense_key, int asc, int ascq, struct scsi_inquiry_data *inq_data, const char **sense_key_desc, const char **asc_desc) { const struct asc_table_entry *asc_entry; const struct sense_key_table_entry *sense_entry; fetchtableentries(sense_key, asc, ascq, inq_data, &sense_entry, &asc_entry); *sense_key_desc = sense_entry->desc; It seems as though sense_entry is NULL after fetchtableentries() returns, which when I took a quick peek at fetchtableentries(), it indicates that it couldn't find a match. I'm not subscribed to this list, but if you need more info, feel free to send me an email directly (or Cc me in your follow-ups). -- Michael Samuel To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 28 12:12: 8 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 049AC37B423 for ; Sat, 28 Apr 2001 12:12:06 -0700 (PDT) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id VAA08415 for freebsd-scsi@FreeBSD.ORG; Sat, 28 Apr 2001 21:12:04 +0200 (CEST) Received: (from j@localhost) by uriah.heep.sax.de (8.11.3/8.11.3) id f3SJ3x368101 for freebsd-scsi@FreeBSD.ORG; Sat, 28 Apr 2001 21:03:59 +0200 (MET DST) (envelope-from j) Date: Sat, 28 Apr 2001 21:03:59 +0200 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Subject: Re: sa(4) jamming Message-ID: <20010428210359.Q50185@uriah.heep.sax.de> Reply-To: Joerg Wunsch References: <200104271649.f3RGmts35017@aslan.scsiguy.com> <200104271700.f3RH01s35435@aslan.scsiguy.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0.1i In-Reply-To: <200104271700.f3RH01s35435@aslan.scsiguy.com>; from gibbs@scsiguy.com on Fri, Apr 27, 2001 at 11:00:01AM -0600 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Justin T. Gibbs wrote: > >That depends on whether the sa driver relies on any settings (mode > >page or otherwise) that are invalidated by a reset, but aren't > >restored when the bus reset async event occurs. > > Just to be more clear here, it is the peripheral driver's responsibility > to restore any of this state if it needs to. I don't doubt this. It only surprises me how many driver bugs have been unobscured by the CAM error handling reorg. All those things (sa driver ILI handling, pt driver invalidating the device after a power-on UA, sa driver running into obscure problems after a bus reset without reloading the tape) didn't happen with earlier versions of the CAM subsystem. Please get me right, i don't want to grumble about CAM here, but i'd like to see bugs fixed as they become obvious in -current, and the first step is always to make sure where the bug actually is. Also Justin, you still didn't respond whether the patch for the `NO SENSE' handling i posted i what you were referring to. Right now, cam_periph_error() effectively returns ERESTART in that case. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 28 12:14: 0 2001 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 189C437B423 for ; Sat, 28 Apr 2001 12:13:58 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA17796; Sat, 28 Apr 2001 12:13:52 -0700 Date: Sat, 28 Apr 2001 12:13:50 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sa(4) jamming In-Reply-To: <20010428210359.Q50185@uriah.heep.sax.de> 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 should note that prior to CAM error handling changes, the sa driver lived in a state of a very uneasy truce with CAM. Now that the error handling has changed, this has to be rethought. I also have a wad of suggested changes from lots of people. I need to spend about a week or so on this. I'm trying schedule this for mid or late may. > As Justin T. Gibbs wrote: > > > >That depends on whether the sa driver relies on any settings (mode > > >page or otherwise) that are invalidated by a reset, but aren't > > >restored when the bus reset async event occurs. > > > > Just to be more clear here, it is the peripheral driver's responsibility > > to restore any of this state if it needs to. > > I don't doubt this. It only surprises me how many driver bugs have > been unobscured by the CAM error handling reorg. All those things (sa > driver ILI handling, pt driver invalidating the device after a > power-on UA, sa driver running into obscure problems after a bus reset > without reloading the tape) didn't happen with earlier versions of the > CAM subsystem. > > Please get me right, i don't want to grumble about CAM here, but i'd > like to see bugs fixed as they become obvious in -current, and the > first step is always to make sure where the bug actually is. > > Also Justin, you still didn't respond whether the patch for the `NO > SENSE' handling i posted i what you were referring to. Right now, > cam_periph_error() effectively returns ERESTART in that case. > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 28 22:12:42 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 654AE37B423 for ; Sat, 28 Apr 2001 22:12:37 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA37533; Sat, 28 Apr 2001 23:12:27 -0600 (MDT) (envelope-from ken) Date: Sat, 28 Apr 2001 23:12:27 -0600 From: "Kenneth D. Merry" To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Another problem with the new CAM error handling Message-ID: <20010428231227.A37369@panzer.kdm.org> References: <20010426110542.A50185@uriah.heep.sax.de> <200104261435.f3QEZLs23573@aslan.scsiguy.com> <20010426190714.E50185@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="0F1p//8PRICkK4MW" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010426190714.E50185@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Thu, Apr 26, 2001 at 07:07:14PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thu, Apr 26, 2001 at 19:07:14 +0200, J Wunsch wrote: > As Justin T. Gibbs wrote: > > >I thought a UA condition would always be retried? In particular, > > >it should never end up in an `invalidating device' message. > > > > The peripheral driver must specify that the UA condition should > > be retried in its call to cam_periph_error(). The pt driver must > > not do that. The new error recovery code isn't responsible for > > this error. > > Hmm, but it used to work with the old CAM error handling code. ;-) > > Anyway, looking at the pt driver, it seems to go length to handle > SF_RETRY_UA, differentiating various cases. I think it would already > properly ignore it after a bus reset or bus device reset. In my case > however, it's a UA after a device power-on. IMHO that's the only > possibility for an UA that has been left out, so why bother and not > always ignore them? It looks like the semantics of unit attention handling have changed with the new error recovery code, and that has exposed the way the pt(4) driver handles unit attentions. The old code retried unit attentions unconditionally without decrementing the retry count if SF_RETRY_UA was set. If SF_RETRY_UA wasn't set, it would still retry unit attentions, but would decrement the retry count. The pt(4) driver would have been hitting the second case in the old code. The new code only retries unit attentions if SF_RETRY_UA is set, and it decrements the retry count. I think that's probably the right thing to do, so peripheral drivers can control whether unit attentions are fatal or not. Decrementing the retry count insures that we won't get stuck in an infinite loop with a broken device that continually returns unit attention. Since SF_RETRY_UA isn't set on normal I/O for the pt(4) driver unless a bus reset or BDR has been sent, unit attentions are not being retried. The attached patch should fix your problem. > The other thing that is annoying is that, after the `invalidating > device', it takes another power-off, camcontrol rescan, power-on, and > camcontrol rescan cycle in order to revive the device, since even a > simple rescan leaves the device invalidated. IMHO, there should at > least be a `camcontrol forget' option to completely abandon a device > without the need to power it off, and rescan the bus. A better name might be 'camcontrol detach'. You're right, such an option might help with reviving dead peripherals. Hopefully we can make things robust enough so that a peripheral isn't declared "dead" unless it really is dead. Ken -- Kenneth Merry ken@kdm.org --0F1p//8PRICkK4MW Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="scsi_pt.c.20010428" ==== //depot/FreeBSD-ken/src/sys/cam/scsi/scsi_pt.c#11 - /usr/home/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_pt.c ==== *** /tmp/tmp.50926.0 Sat Apr 28 22:48:07 2001 --- /usr/home/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_pt.c Sat Apr 28 22:47:34 2001 *************** *** 544,550 **** /*sense_len*/SSD_FULL_SIZE, /*timeout*/softc->io_timeout); ! start_ccb->ccb_h.ccb_state = PT_CCB_BUFFER_IO; /* * Block out any asyncronous callbacks --- 544,550 ---- /*sense_len*/SSD_FULL_SIZE, /*timeout*/softc->io_timeout); ! start_ccb->ccb_h.ccb_state = PT_CCB_BUFFER_IO_UA; /* * Block out any asyncronous callbacks --0F1p//8PRICkK4MW-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 28 22:33:13 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 E595D37B423 for ; Sat, 28 Apr 2001 22:33:09 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA37656; Sat, 28 Apr 2001 23:33:06 -0600 (MDT) (envelope-from ken) Date: Sat, 28 Apr 2001 23:33:06 -0600 From: "Kenneth D. Merry" To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: sa(4) jamming Message-ID: <20010428233306.A37621@panzer.kdm.org> References: <200104271649.f3RGmts35017@aslan.scsiguy.com> <200104271700.f3RH01s35435@aslan.scsiguy.com> <20010428210359.Q50185@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="k1lZvvs/B4yU6o8G" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010428210359.Q50185@uriah.heep.sax.de>; from j@uriah.heep.sax.de on Sat, Apr 28, 2001 at 09:03:59PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Apr 28, 2001 at 21:03:59 +0200, J Wunsch wrote: > As Justin T. Gibbs wrote: > > > >That depends on whether the sa driver relies on any settings (mode > > >page or otherwise) that are invalidated by a reset, but aren't > > >restored when the bus reset async event occurs. > > > > Just to be more clear here, it is the peripheral driver's responsibility > > to restore any of this state if it needs to. > > I don't doubt this. It only surprises me how many driver bugs have > been unobscured by the CAM error handling reorg. All those things (sa > driver ILI handling, pt driver invalidating the device after a > power-on UA, sa driver running into obscure problems after a bus reset > without reloading the tape) didn't happen with earlier versions of the > CAM subsystem. I think some problems are inevitable with a rewrite as large as the error recovery rewrite. What surprised me is that we didn't get any bug reports after the changes first went into the tree on March 27th. Your bug reports are (as far as I can remember) the first. > Please get me right, i don't want to grumble about CAM here, but i'd > like to see bugs fixed as they become obvious in -current, and the > first step is always to make sure where the bug actually is. Yep, we definitely want to fix them. > Also Justin, you still didn't respond whether the patch for the `NO > SENSE' handling i posted i what you were referring to. Right now, > cam_periph_error() effectively returns ERESTART in that case. I think your patch was on target, but the action string needs to be set as well. Even with an action of SS_NOP, there are cases where sense will be printed. (e.g. when a block is reallocated and a drive informs us of it) IIRC, in Justin's original patches SS_NOP wasn't even in the case statement. So you'd get a panic whenever SS_NOP came back from scsi_error_action(). I added it to the retry case, which wasn't really the correct thing to do in hindsight. Anyway, I've attached a patch. It needs to be tested. I won't be able to test it until I get one of my machines upgraded to -current. (My buildworld blew up in xlint.) Ken -- Kenneth Merry ken@kdm.org --k1lZvvs/B4yU6o8G Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="cam_periph.c.20010428" ==== //depot/FreeBSD-ken/src/sys/cam/cam_periph.c#12 - /usr/home/ken/perforce/FreeBSD-ken/src/sys/cam/cam_periph.c ==== *** /tmp/tmp.44005.0 Sat Apr 28 23:24:03 2001 --- /usr/home/ken/perforce/FreeBSD-ken/src/sys/cam/cam_periph.c Sat Apr 28 23:23:52 2001 *************** *** 1369,1374 **** --- 1369,1377 ---- switch (err_action & SS_MASK) { case SS_NOP: + action_string = "No Recovery Action Needed"; + error = 0; + break; case SS_RETRY: action_string = "Retrying Command"; error = ERESTART; --k1lZvvs/B4yU6o8G-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Apr 28 22:48:20 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 82EF537B635 for ; Sat, 28 Apr 2001 22:48:15 -0700 (PDT) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA37740; Sat, 28 Apr 2001 23:48:00 -0600 (MDT) (envelope-from ken) Date: Sat, 28 Apr 2001 23:48:00 -0600 From: "Kenneth D. Merry" To: Michael Samuel Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: NULL pointer deref in scsi_sense_desc Message-ID: <20010428234800.A37675@panzer.kdm.org> References: <20010428114711.A7571@miknet.net> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="mYCpIKhGyMATD0i+" Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: <20010428114711.A7571@miknet.net>; from michael@miknet.net on Sat, Apr 28, 2001 at 11:47:11AM +1000 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Sat, Apr 28, 2001 at 11:47:11 +1000, Michael Samuel wrote: > Hi, > > I got a "Page fault in kernel mode" which writing to a SCSI tape (which had > barfed on me with some SCSI sense messages shortly before the crash). > > This is in -current from the CVS as of about a week or 2 ago. > > It stopped at scsi_sense_desc+0x2f, which resolved in gdb -k to > cam/scsi/scsi_all.c line 1573, which in my copy of the source tree looks > like this: > > void > scsi_sense_desc(int sense_key, int asc, int ascq, > struct scsi_inquiry_data *inq_data, > const char **sense_key_desc, const char **asc_desc) > { > const struct asc_table_entry *asc_entry; > const struct sense_key_table_entry *sense_entry; > > fetchtableentries(sense_key, asc, ascq, > inq_data, > &sense_entry, > &asc_entry); > > *sense_key_desc = sense_entry->desc; > > It seems as though sense_entry is NULL after fetchtableentries() returns, > which when I took a quick peek at fetchtableentries(), it indicates that it > couldn't find a match. Hmm, that would cause the code to deference a null pointer, which is bad. It's probably a bug to do that without checking the pointer first, since a drive could theoretically return a bogus sense key and cause a panic. Would it be possible for you to get a stack trace? If you need info on how to get a stack trace: http://www.freebsd.org/doc/en_US.ISO_8859-1/books/handbook/kerneldebug.html What I'm looking for is what the sense key, asc, and ascq are. I think we should have all existing sense keys covered, but if we don't I'd like to know about it. (It would also be useful to know if the drive is just returning a bogus sense key.) The attached patch should fix your problem. Let me know how it works. > I'm not subscribed to this list, but if you need more info, feel free to > send me an email directly (or Cc me in your follow-ups). Ken -- Kenneth Merry ken@kdm.org --mYCpIKhGyMATD0i+ Content-Type: text/plain; charset=us-ascii Content-Disposition: attachment; filename="scsi_all.c.20010428" ==== //depot/FreeBSD-ken/src/sys/cam/scsi/scsi_all.c#9 - /usr/home/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_all.c ==== *** /tmp/tmp.44053.0 Sat Apr 28 23:43:22 2001 --- /usr/home/ken/perforce/FreeBSD-ken/src/sys/cam/scsi/scsi_all.c Sat Apr 28 23:43:11 2001 *************** *** 1570,1576 **** &sense_entry, &asc_entry); ! *sense_key_desc = sense_entry->desc; if (asc_entry != NULL) *asc_desc = asc_entry->desc; --- 1570,1579 ---- &sense_entry, &asc_entry); ! if (sense_entry != NULL) ! *sense_key_desc = sense_entry->desc; ! else ! *sense_key_desc = "Unknown Sense Key"; if (asc_entry != NULL) *asc_desc = asc_entry->desc; --mYCpIKhGyMATD0i+-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message