From owner-freebsd-scsi Mon Feb 10 11: 2:36 2003 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 27BBB37B401 for ; Mon, 10 Feb 2003 11:02:36 -0800 (PST) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38E3343FCB for ; Mon, 10 Feb 2003 11:02:30 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: from freefall.freebsd.org (peter@localhost [127.0.0.1]) by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id h1AJ2UNS085951 for ; Mon, 10 Feb 2003 11:02:30 -0800 (PST) (envelope-from owner-bugmaster@freebsd.org) Received: (from peter@localhost) by freefall.freebsd.org (8.12.6/8.12.6/Submit) id h1AJ2Tfn085945 for scsi@freebsd.org; Mon, 10 Feb 2003 11:02:29 -0800 (PST) Date: Mon, 10 Feb 2003 11:02:29 -0800 (PST) Message-Id: <200302101902.h1AJ2Tfn085945@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: peter set sender to owner-bugmaster@freebsd.org using -f From: FreeBSD bugmaster To: scsi@FreeBSD.org Subject: Current problem reports assigned to you Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Current FreeBSD problem reports Critical problems Serious problems Non-critical problems S Submitted Tracker Resp. Description ------------------------------------------------------------------------------- f [1999/12/21] kern/15608 scsi acd0 / cd0 give inconsistent errors on em 1 problem total. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 12 0:18:30 2003 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3CAB537B401 for ; Wed, 12 Feb 2003 00:18:28 -0800 (PST) Received: from mail.econolodgetulsa.com (mail.econolodgetulsa.com [198.78.66.163]) by mx1.FreeBSD.org (Postfix) with ESMTP id C9E2943F93 for ; Wed, 12 Feb 2003 00:18:27 -0800 (PST) (envelope-from user@mail.econolodgetulsa.com) Received: from mail (user@mail [198.78.66.163]) by mail.econolodgetulsa.com (8.12.3/8.12.3) with ESMTP id h1C8IUdR082013 for ; Wed, 12 Feb 2003 00:18:30 -0800 (PST) (envelope-from user@mail.econolodgetulsa.com) Date: Wed, 12 Feb 2003 00:18:29 -0800 (PST) From: Josh Brooks To: freebsd-scsi@freebsd.org Subject: confusing aaccli output Message-ID: <20030212001508.U39971-100000@mail.econolodgetulsa.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, I am seeing this in aaccli: AAC0> container list Executing: container list Num Total Oth Chunk Scsi Partition Label Type Size Ctr Size Usage B:ID:L Offset:Size ----- ------ ------ --- ------ ------- ------ ------------- 0 Mirror 34.1GB Open 0:01:0 64.0KB:34.1GB /dev/aacd0 array01 0:00:0 64.0KB!34.1GB 1 Mirror 34.1GB Open 0:02:0 64.0KB:34.1GB /dev/aacd1 array02 0:03:0 64.0KB:34.1GB At first glance it looks fine. Two healthy containers. But what is that exclamation point: 0:00:0 64.0KB!34.1GB Interesting. Now I look at /var/log/messages: Feb 9 17:26:36 system /kernel: aac0: **Monitor** Drive 0:0:0 returning error Feb 9 17:26:36 system /kernel: aac0: **Monitor** ID(0:00:0) - drive failure (retries exhausted) Feb 9 17:26:36 system /kernel: aac0: **Monitor** Mirror Container 0 Drive 0:0:0 Failure Feb 9 17:26:46 system /kernel: aac0: **Monitor** Mirror Failover Container 0 no failover assigned So what is going on here ? messages tell me I have a broken mirror, but aaccli shows me a healthy one. Iam afraid to run a: container set failover because aaccli shows it as already belonging to the container... Any advice/comments - especially regarding what I should do next - is appreciated. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 12 0:58:37 2003 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3D92B37B401 for ; Wed, 12 Feb 2003 00:58:35 -0800 (PST) Received: from magic.adaptec.com (magic.adaptec.com [208.236.45.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 854C843F75 for ; Wed, 12 Feb 2003 00:58:34 -0800 (PST) (envelope-from scott_long@btc.adaptec.com) Received: from redfish.adaptec.com (redfish.adaptec.com [162.62.50.11]) by magic.adaptec.com (8.11.6+Sun/8.11.6) with ESMTP id h1C8wSD14954; Wed, 12 Feb 2003 00:58:28 -0800 (PST) Received: from btc.btc.adaptec.com (btc.btc.adaptec.com [10.100.0.52]) by redfish.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id AAA06488; Wed, 12 Feb 2003 00:58:17 -0800 (PST) Received: from btc.adaptec.com (hollin [10.100.253.56]) by btc.btc.adaptec.com (8.8.8+Sun/8.8.8) with ESMTP id BAA03242; Wed, 12 Feb 2003 01:58:14 -0700 (MST) Message-ID: <3E4A0C90.5000600@btc.adaptec.com> Date: Wed, 12 Feb 2003 01:57:52 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.2b) Gecko/20021105 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Josh Brooks Cc: freebsd-scsi@freebsd.org Subject: Re: confusing aaccli output References: <20030212001508.U39971-100000@mail.econolodgetulsa.com> In-Reply-To: <20030212001508.U39971-100000@mail.econolodgetulsa.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Josh Brooks wrote: > Hello, > > I am seeing this in aaccli: > > AAC0> container list > Executing: container list > Num Total Oth Chunk Scsi Partition > Label Type Size Ctr Size Usage B:ID:L Offset:Size > ----- ------ ------ --- ------ ------- ------ ------------- > 0 Mirror 34.1GB Open 0:01:0 64.0KB:34.1GB > /dev/aacd0 array01 0:00:0 64.0KB!34.1GB > > 1 Mirror 34.1GB Open 0:02:0 64.0KB:34.1GB > /dev/aacd1 array02 0:03:0 64.0KB:34.1GB > > > At first glance it looks fine. Two healthy containers. But what is that > exclamation point: > > 0:00:0 64.0KB!34.1GB > > Interesting. Now I look at /var/log/messages: > > > > Feb 9 17:26:36 system /kernel: aac0: **Monitor** Drive 0:0:0 returning > error > Feb 9 17:26:36 system /kernel: aac0: **Monitor** ID(0:00:0) - drive > failure (retries exhausted) > Feb 9 17:26:36 system /kernel: aac0: **Monitor** Mirror Container 0 Drive > 0:0:0 Failure > Feb 9 17:26:46 system /kernel: aac0: **Monitor** Mirror Failover > Container > 0 no failover assigned > > > > So what is going on here ? messages tell me I have a broken mirror, but > aaccli shows me a healthy one. As noted above, the card took scsi driver 0:0:0 offline due to errors, so the mirror is running in degraded mode. I admit that the output from aaccli isn't terribly obvious here... > > Iam afraid to run a: > > container set failover > > because aaccli shows it as already belonging to the container... Eh? 'container set failover' allows you to assign one or more drives as either global or dedicated spares. The firmware won't really let you add the failed drive as a spare (not without some tickery, at least), so you'll need to shove a new drive into the mix and assign it as the spare. You'll also need to enable automatic rebuilds, and then everything will be good to go. If you're really in a bind because you didn't budget for a spare drive (shame on you!), pull out the drive that was marked as failed, put it on a regular scsi controller, do a low-level format of it, then put it back on the aac controller and add it as the spare. There's a good chance, though, that if the drive failed once then it's going to fail again. Scott To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 12 11:56: 5 2003 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F2F937B401 for ; Wed, 12 Feb 2003 11:56:04 -0800 (PST) Received: from catalepsy.pdl.cmu.edu (CATALEPSY.PDL.CMU.EDU [128.2.134.92]) by mx1.FreeBSD.org (Postfix) with ESMTP id CD3E143FE5 for ; Wed, 12 Feb 2003 11:56:02 -0800 (PST) (envelope-from bucy@catalepsy.pdl.cmu.edu) Received: (from bucy@localhost) by catalepsy.pdl.cmu.edu (8.11.4/8.11.4) id h1CJthi18911 for freebsd-scsi@freebsd.org; Wed, 12 Feb 2003 14:55:43 -0500 Date: Wed, 12 Feb 2003 14:55:43 -0500 From: "John S. Bucy" To: freebsd-scsi@freebsd.org Subject: isp target mode Message-ID: <20030212195542.GG24423@catalepsy.pdl.cmu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've been trying to do target mode on QLogic QLA2100F cards using Nate Lawson's driver on 4.7. When I try to enable the target device, I get "isp0: firmware does not support target mode." I tried upgrading the firmware to the latest version but it still doesn't work. Has anyone *verified* that any particular QLAs actually work in target mode? I can probably buy new cards (I was thinking QLA2200F-CK) but I don't want to go on a wild goose chase here ... thanks john To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 12 12:19:44 2003 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65A8337B401 for ; Wed, 12 Feb 2003 12:19:43 -0800 (PST) Received: from freebie.xs4all.nl (freebie.xs4all.nl [213.84.32.253]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43AB743FBF for ; Wed, 12 Feb 2003 12:19:42 -0800 (PST) (envelope-from wkb@freebie.xs4all.nl) Received: from freebie.xs4all.nl (localhost [127.0.0.1]) by freebie.xs4all.nl (8.12.6/8.12.6) with ESMTP id h1CKJRxg061324; Wed, 12 Feb 2003 21:19:32 +0100 (CET) (envelope-from wkb@freebie.xs4all.nl) Received: (from wkb@localhost) by freebie.xs4all.nl (8.12.6/8.12.6/Submit) id h1CKJQhW061323; Wed, 12 Feb 2003 21:19:26 +0100 (CET) Date: Wed, 12 Feb 2003 21:19:26 +0100 From: Wilko Bulte To: "John S. Bucy" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: isp target mode Message-ID: <20030212211926.B61281@freebie.xs4all.nl> References: <20030212195542.GG24423@catalepsy.pdl.cmu.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20030212195542.GG24423@catalepsy.pdl.cmu.edu>; from bucy@ece.cmu.edu on Wed, Feb 12, 2003 at 02:55:43PM -0500 X-OS: FreeBSD 4.7-STABLE X-PGP: finger wilko@freebsd.org Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, Feb 12, 2003 at 02:55:43PM -0500, John S. Bucy wrote: You want to ask Matt Jacob (mjacob@freebsd.org) on this one. > I've been trying to do target mode on QLogic QLA2100F cards using Nate > Lawson's driver on 4.7. When I try to enable the target device, I get > "isp0: firmware does not support target mode." I tried upgrading the > firmware to the latest version but it still doesn't work. Has anyone > *verified* that any particular QLAs actually work in target mode? I > can probably buy new cards (I was thinking QLA2200F-CK) but I don't > want to go on a wild goose chase here ... > > > > thanks > john > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message ---end of quoted text--- -- | / o / /_ _ wilko@freebie.xs4all.nl |/|/ / / /( (_) Bulte To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 12 13:19:27 2003 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1FEB137B405 for ; Wed, 12 Feb 2003 13:19:26 -0800 (PST) Received: from crufty.research.bell-labs.com (ns2.research.bell-labs.com [204.178.16.49]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9E97043F93 for ; Wed, 12 Feb 2003 13:19:20 -0800 (PST) (envelope-from jkf@research.bell-labs.com) Received: from grubby.research.bell-labs.com (H-135-104-2-9.research.bell-labs.com [135.104.2.9]) by crufty.research.bell-labs.com (8.12.5/8.12.5) with ESMTP id h1CLJBLI078534; Wed, 12 Feb 2003 16:19:11 -0500 (EST) Received: from zydeco.research.bell-labs.com (zydeco.research.bell-labs.com [135.104.120.150]) by grubby.research.bell-labs.com (8.11.6/8.11.6) with ESMTP id h1CLJ0Y48339; Wed, 12 Feb 2003 16:19:00 -0500 (EST) Received: from zydeco.research.bell-labs.com (localhost [127.0.0.1]) by zydeco.research.bell-labs.com (8.12.2/8.12.2) with ESMTP id h1CLIxrJ008056; Wed, 12 Feb 2003 16:18:59 -0500 (EST) Received: (from jkf@localhost) by zydeco.research.bell-labs.com (8.12.2/8.12.2/Submit) id h1CLIxju008055; Wed, 12 Feb 2003 16:18:59 -0500 (EST) Date: Wed, 12 Feb 2003 16:18:59 -0500 (EST) From: Jeff Fellin Message-Id: <200302122118.h1CLIxju008055@zydeco.research.bell-labs.com> To: bucy@ece.cmu.edu Subject: Re: isp target mode Cc: freebsd-scsi@FreeBSD.ORG X-Sun-Charset: US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org John, Do you have the following in your kernel config file: device ispfw OPTIONS ISP_TARGET_MODE This has worked for me with the Qlogic ISP 2200 FC-AL adapter and Qlogic ISP 1280 PCI SCSI Adapter. Jeff Fellin > From owner-freebsd-scsi@FreeBSD.ORG Wed Feb 12 14:56:33 2003 > Delivered-To: freebsd-scsi@freebsd.org > Date: Wed, 12 Feb 2003 14:55:43 -0500 > From: "John S. Bucy" > To: freebsd-scsi@FreeBSD.ORG > Subject: isp target mode > > > I've been trying to do target mode on QLogic QLA2100F cards using Nate > Lawson's driver on 4.7. When I try to enable the target device, I get > "isp0: firmware does not support target mode." I tried upgrading the > firmware to the latest version but it still doesn't work. Has anyone > *verified* that any particular QLAs actually work in target mode? I > can probably buy new cards (I was thinking QLA2200F-CK) but I don't > want to go on a wild goose chase here ... > > > > thanks > john > > 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 Wed Feb 12 15: 5:40 2003 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5902F37B401 for ; Wed, 12 Feb 2003 15:05:39 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id 39C2543F85 for ; Wed, 12 Feb 2003 15:05:36 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 34968 invoked by uid 1000); 12 Feb 2003 23:05:36 -0000 Date: Wed, 12 Feb 2003 15:05:36 -0800 (PST) From: Nate Lawson To: Jeff Fellin Cc: bucy@ece.cmu.edu, freebsd-scsi@FreeBSD.ORG Subject: Re: isp target mode In-Reply-To: <200302122118.h1CLIxju008055@zydeco.research.bell-labs.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Wed, 12 Feb 2003, Jeff Fellin wrote: > Do you have the following in your kernel config file: > > device ispfw > OPTIONS ISP_TARGET_MODE > > This has worked for me with the Qlogic ISP 2200 FC-AL adapter > and Qlogic ISP 1280 PCI SCSI Adapter. Right. You have to load firmware each time at boot. The onboard firmware only supports a minimum necessary to do int 13 booting. You can use the above "device" line or put ispfw_load="YES" in /boot/loader.conf Note that for isp(4) you can only enable target mode on the card's initiator id. i.e. if your init id is 7, use 0:7:0 for the id to enable for target mode. -Nate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 13 10:50:59 2003 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3A46B37B401 for ; Thu, 13 Feb 2003 10:50:58 -0800 (PST) Received: from beppo.feral.com (beppo.feral.com [192.67.166.79]) by mx1.FreeBSD.org (Postfix) with ESMTP id 619BA43F75 for ; Thu, 13 Feb 2003 10:50:57 -0800 (PST) (envelope-from mjacob@feral.com) Received: from quaver.feral.com (mjacob@quaver.feral.com [192.67.166.210]) by beppo.feral.com (8.11.3/8.11.3) with ESMTP id h1DIoIV57041; Thu, 13 Feb 2003 10:50:20 -0800 (PST) (envelope-from mjacob@feral.com) Date: Thu, 13 Feb 2003 10:50:14 -0800 (PST) From: Matthew Jacob X-X-Sender: mjacob@mailhost.quaver.net Reply-To: mjacob@feral.com To: "John S. Bucy" Cc: scsi@freebsd.org Subject: Re: isp target mode In-Reply-To: <20030212205355.GH24423@catalepsy.pdl.cmu.edu> Message-ID: <20030213104616.S93556@mailhost.quaver.net> References: <20030212205355.GH24423@catalepsy.pdl.cmu.edu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org [ direct to mjacob@feral.com will get quicker results: I'm kinda on sabbatical from the *BSDs these days and don't read the lists or my *BSD mail very often ] Make sure that you build a kernel with options ISP_TARGET_MODE=1 in the conf file. Also make sure that you either include the ispfw module in the same conf file or make sure it gets loaded via ispfw_load="YES" in /boot/loader.conf. The default firmware doesn't support target mode. ISPFW has to be told which f/w to return to isp when isp wants to download new f/w. And yes, all of them support target mode, with varying levels of incompletely working state (freeware, etc.). I haven't checked it in a month or so. -matt On Wed, 12 Feb 2003, John S. Bucy wrote: > > (refered to you directly from freebsd-scsi) > > I've been trying to do target mode on QLogic QLA2100F cards using Nate > Lawson's driver on 4.7. When I try to enable the target device, I get > "isp0: firmware does not support target mode." I tried upgrading the > firmware to the latest version but it still doesn't work. Has anyone > *verified* that any particular QLAs actually work in target mode? I > can probably buy new cards (I was thinking QLA2200F-CK) but I don't > want to go on a wild goose chase here ... > > > > thanks > john > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 13 20:42:52 2003 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0EFE737B401 for ; Thu, 13 Feb 2003 20:42:52 -0800 (PST) Received: from mail.vinita.lt (mail.vinita.lt [217.147.34.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A91643FA3 for ; Thu, 13 Feb 2003 20:42:51 -0800 (PST) (envelope-from rolnas@takas.lt) Received: from ctv-217-147-36-211.vinita.lt ([217.147.36.211] helo=rolnas.mif.vu.lt) by mail.vinita.lt with esmtp (powered by Init) id 18jXpY-0003lI-00 for ; Fri, 14 Feb 2003 06:52:08 +0200 Received: from rolnas by rolnas.mif.vu.lt with local (Exim 3.35 #1 (Debian)) id 18jXgW-0000El-00 for ; Fri, 14 Feb 2003 06:42:48 +0200 Date: Fri, 14 Feb 2003 06:42:48 +0200 From: Rolandas Naujikas To: scsi@freebsd.org Subject: Problems with IBM xSeries 225 SCSI controller LSILogic 1030 Message-ID: <20030214044248.GA906@rolnas> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline User-Agent: Mutt/1.3.28i Organization: VU MIF Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I have problems with Subject. SCSI controller doesn't work every system restart. It start some times in 10-30% probability. I'm tried without SMP and 4.7-RELEASE there is the same output. There is dmesg output with last panic http://www.mif.vu.lt/~rolnas/freebsd/dmesg.out Kernel config file http://www.mif.vu.lt/~rolnas/freebsd/PARKAS with GENERIC is the same output. Please help somebody with more SCSI knowledge. P.S. It's work, but we cannot wait 1/2 hour to reboot system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 14 22:20:11 2003 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7FEC937B401; Fri, 14 Feb 2003 22:20:04 -0800 (PST) Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4A0DE43FBF; Fri, 14 Feb 2003 22:20:03 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: from panzer.kdm.org (localhost [127.0.0.1]) by panzer.kdm.org (8.12.6/8.12.5) with ESMTP id h1F6K2nU071644; Fri, 14 Feb 2003 23:20:02 -0700 (MST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.12.6/8.12.5/Submit) id h1F6K2Eh071643; Fri, 14 Feb 2003 23:20:02 -0700 (MST) (envelope-from ken) Date: Fri, 14 Feb 2003 23:20:02 -0700 From: "Kenneth D. Merry" To: scsi@FreeBSD.org, current@FreeBSD.org Cc: joe@FreeBSD.org, thomas@FreeBSD.org Subject: call for testers: cd(4) changes Message-ID: <20030214232001.A71462@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Here are patches against -current to add automatic detection of CDROM drives that can't handle 6 byte mode sense and mode select: http://people.FreeBSD.org/~ken/scsi_cd.cmdsize.20030214 These patches will be checked in in a few days if I don't get any negative feedback. Things fixed/changed in this patchset: - Automatically detect CDROM drives that can't handle 6 byte mode sense and mode select, and adjust our command size accordingly. More information on that below. - MODE_SENSE and MODE_SELECT translation removed in ATAPICAM and in the umass(4) driver, since there's no way for that to work properly (see below). - Change the way the da(4) handles the no_6_byte sysctl. There is now a per-drive sysctl to set the minimum command size for that particular disk. (Since you could have multiple disks with multiple requirements in one system.) - Loader tunable support for all the sysctls in the da(4) and cd(4) drivers. - Add a CDIOCCLOSE ioctl (bde pointed this out a long time ago). - Add a media validation routine (cdcheckmedia()) to the cd(4) driver, to fix some problems bde pointed out a long time ago. We now allow open() to succeed no matter what, but if we don't detect valid media, the user can only issue CDIOCCLOSE or CDIOCEJECT ioctls. - The media validation routine also reads the table of contents off the drive. We use the table of contents to implement the CDIOCPLAYTRACKS ioctl using the PLAY AUDIO MSF command. The PLAY AUDIO TRACK INDEX command that we previously used was deprecated after SCSI-2. It works in every SCSI CDROM I've tried, but doesn't seem to work on ATAPI CDROM drives. We still use the play audio track index command if we don't have a valid TOC, but I suppose it'll fail anyway in that case. That's the last issue I know of with using ATAPI/firewire/USB drives with the ioctl interface. (firewire and USB drives are generally ATAPI drives underneath anyway) - Add _len() versions of scsi_mode_sense() and scsi_mode_select(). - Fix a couple of formatting problems in the sense printing code. I'd appreciate it if folks could test this, especially people with CDROM drives running via usb, firewire, or ATAPICAM, but also people with older SCSI CDROM drives. To test this, apply the patch and do the following: cdcontrol status cdcontrol info cdcontrol play (make sure audio comes out) cdcontrol next (make sure it skips to the next track here) If you get an error in response to 'cdcontrol next', definitely let me know what kind of drive you have (dmesg is fine) and how it is hooked up (SCSI, firewire, ATAPICAM, usb, etc.). Reports of success or failure are welcome. ======= Now for more details.... When we get an illegal request in response to a 6 byte mode sense or mode select, we reformat the command to be a 10-byte mode sense or mode select and reissue it. These patches also work with drives that do not return block descriptors (even when dbd is 0 in the mode sense command), and drives that return multiple block descriptors. (They work better with the former than the latter; with the latter, they mostly just bail out.) While commands like READ(6) and WRITE(6) can be translated down in the SIM driver, like the ATAPICAM and usb code do, MODE_SENSE(6) and MODE_SELECT(6) cannot be translated, because the 10-byte version of the parameter list is longer. This means that when, e.g., a MODE_SENSE(6) command is translated to a MODE_SENSE(10) command, the page will likely be truncated (unless more space is allocated than needed), and since the peripheral driver code isn't expecting the returned data to be in MODE_SENSE(10) format, it'll be looking in the wrong place for the mode page. The SIM drivers have no way of knowing how long the buffer is that they've been given for a mode sense or mode select, so they can't just up the dxfer_len, change the CDB and call it good. The only way to do translation effectively for these two commands is where the buffer was originally allocated -- in the peripheral driver. So I have implemented translation and 10-byte mode sense and mode select for the cd(4) driver. Why do translation? Why not just default to 10-byte commands? Because some SCSI CDROM drives, maybe quite a few, don't support 10 byte mode sense and mode select. (The 8x Plextor in my test box doesn't, for example.) The right way to do this, eventually, is with the CAM_NEW_TRAN_CODE. 6byte/10byte can be a function of the protocol, and we can hopefully select the right size command up front. It will take a lot of infrastructure work to make it happen, but that functionality will hopefully solve several problems. Since translation won't work at the SIM level, I have disabled MODE_SENSE(6) and MODE_SELECT translation in ATAPICAM and umass(4). Comments are welcome on the patches; they're more complicated than I would like, but unfortunately that complication seems necessary to get the desired functionality. Many thanks to David Kleiner for testing multiple iterations of these patches, he has been a big help. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 15 3:20:50 2003 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 397D037B401; Sat, 15 Feb 2003 03:20:49 -0800 (PST) Received: from melusine.cuivre.fr.eu.org (melusine.cuivre.fr.eu.org [62.212.105.185]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4B30743FAF; Sat, 15 Feb 2003 03:20:48 -0800 (PST) (envelope-from thomas@FreeBSD.ORG) Received: by melusine.cuivre.fr.eu.org (Postfix, from userid 1000) id 2BC402C3D3; Sat, 15 Feb 2003 12:20:46 +0100 (CET) Date: Sat, 15 Feb 2003 12:20:46 +0100 From: Thomas Quinot To: "Kenneth D. Merry" Cc: scsi@FreeBSD.org, current@FreeBSD.org, joe@FreeBSD.org, thomas@FreeBSD.org Subject: Re: call for testers: cd(4) changes Message-ID: <20030215112046.GA20707@melusine.cuivre.fr.eu.org> Reply-To: Thomas Quinot References: <20030214232001.A71462@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20030214232001.A71462@panzer.kdm.org> User-Agent: Mutt/1.4i X-message-flag: WARNING! Using Outlook can damage your computer. Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Le 2003-02-15, Kenneth D. Merry écrivait : > - Automatically detect CDROM drives that can't handle 6 byte mode > sense and mode select, and adjust our command size accordingly. > More information on that below. > > - MODE_SENSE and MODE_SELECT translation removed in ATAPICAM and in > the umass(4) driver, since there's no way for that to work properly > (see below). I'm afraid things are not as simple as that. Unfortunately you cannot expect ATAPI drives to properly reject MODE_{SENSE,SELECT}_6 and try the _10 variants in that case: the reason why ATAPICAM inconditionnally translates the _6 commands into _10 is because some ATAPI drives have been found to lock up when they rececive the _6 commands, whereas the ATAPI specification only mandates the implementation of the _10 versions. > - The media validation routine also reads the table of contents off > the drive. Great! That could also allow the creation of per-track /dev nodes, as acd has. Thomas. -- Thomas.Quinot@Cuivre.FR.EU.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message