From owner-freebsd-scsi Sun Nov 29 00:22:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA06082 for freebsd-scsi-outgoing; Sun, 29 Nov 1998 00:22:11 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA06077 for ; Sun, 29 Nov 1998 00:22:08 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id JAA11277; Sun, 29 Nov 1998 09:21:45 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id JAA11603; Sun, 29 Nov 1998 09:14:42 +0100 (MET) (envelope-from j) Message-ID: <19981129091441.16610@uriah.heep.sax.de> Date: Sun, 29 Nov 1998 09:14:41 +0100 From: J Wunsch To: Ken Murchison Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: user-level (pass-thru) scsi programming Reply-To: Joerg Wunsch References: <36605E69.F72A3224@oceana.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <36605E69.F72A3224@oceana.com>; from Ken Murchison on Sat, Nov 28, 1998 at 03:34:49PM -0500 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 Ken Murchison wrote: > I've read the scsi(3) man page and found the appropriate functions, but > I'm having a hard time figuring out which devices to use. It looks like > I'm supposed to be able to use the su(4) devices, but I don't have any > configured on my system. I have even recompiled my kernel with > > pseudo-device su > pseudo-device ssc > > but still no devices. Which was the right thing to do. However, you also need to run the script MAKEDEV in /dev in order to create the actual device nodes. Alas, MAKEDEV only contains a description for the ssc device, but not for the su devices. su has major number 18, so you can create the device nodes like mknod /dev/sub0t0u0 c 18 0x0 # bus 0 target 0 lun 0 mknod /dev/sub0t0u1 c 18 0x1 # ... lun 1 mknod /dev/sub0t1u0 c 18 0x8 # bus 0 target 1 lun 0 mknod /dev/sub0t7u0 c 18 0x38 # bus 0 target 7 lun 0 mknod /dev/sub1t0u0 c 18 0x40 # bus 1 target 0 lun 0 One note of a warning however: FreeBSD's SCSI subsystem is currently being restructured. FreeBSD 3.0 already ships with the new subsystem (called CAM -- common access method) now, and the access to passtrough devices is different there. (I would assume it's easier than previously, but i'm not knowledgable.) So it depends on your intented target system and timeframe whether you're going to use the above old scheme at all, or whether you'd better concentrate on the new one. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- 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 Sun Nov 29 14:20:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA09564 for freebsd-scsi-outgoing; Sun, 29 Nov 1998 14:20:54 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from wopr.caltech.edu (wopr.caltech.edu [131.215.240.222]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA09559 for ; Sun, 29 Nov 1998 14:20:52 -0800 (PST) (envelope-from mph@wopr.caltech.edu) Received: (from mph@localhost) by wopr.caltech.edu (8.9.1/8.9.1) id OAA09730 for freebsd-scsi@freebsd.org; Sun, 29 Nov 1998 14:20:28 -0800 (PST) (envelope-from mph) Message-ID: <19981129142027.A9664@wopr.caltech.edu> Date: Sun, 29 Nov 1998 14:20:27 -0800 From: Matthew Hunt To: freebsd-scsi@FreeBSD.ORG Subject: tosha reports random errors after transition to CAM Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Since upgrading from 2.2-STABLE to 3.0-CURRENT, and hence CAM, I have observed random errors when using tosha to read CD audio data from my CD-ROM drive. The drive is branded IBM, but when I purchased it, I was told that it is a Toshiba XM-4101. When I try to rip CD audio, tosha emits the following error: wopr:~/tmp$ tosha -v -t 1 -o out.pcm Device: /dev/cd0c IBM CDRM00201 !F 0724 tosha: WARNING: Drive type not recognized. Output file: out.pcm track playing start end raw size mp3 size # of number time sector sector in bytes 128 kbps frames -------------------------------------------------------------- 1 4:22'18 0 19667 46259136 4196675 10039 error returned from CD-DA read command: (pass1:ahc0:0:3:0): Vendor Specific Command. CDB: d8 (pass1:ahc0:0:3:0): ILLEGAL REQUEST asc:bf,0 (pass1:ahc0:0:3:0): Vendor Specific ASC The error is always the same, but it occurs at random places and does not appear to depend on what CD or track I am ripping. I never had any problems pre-CAM. I have (obviously) recompiled tosha to support the CAM architecture. Can anyone provide illumination? Matt -- Matthew Hunt * Inertia is a property of matter. http://www.pobox.com/~mph/pgp.key for PGP public key 0x67203349. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 29 16:45:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23904 for freebsd-scsi-outgoing; Sun, 29 Nov 1998 16:45:01 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23891 for ; Sun, 29 Nov 1998 16:44:58 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id LAA08506 for ; Mon, 30 Nov 1998 11:14:44 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.1/8.9.0) id LAA01240; Mon, 30 Nov 1998 11:14:18 +1030 (CST) Message-ID: <19981130111418.D831@freebie.lemis.com> Date: Mon, 30 Nov 1998 11:14:18 +1030 From: Greg Lehey To: FreeBSD SCSI Mailing List Subject: Formatting disks under CAM Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i WWW-Home-Page: http://www.lemis.com/~grog Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've got a disk which has developed a number of bad spots, and I want to format it. I've tried scsiformat, but it hasn't been converted for CAM. scsiformat uses the following command to perform the format: scsi -f /dev/rsd0.ctl -v -c 12 0 0 0 v 0 96 -i 96 s8 z8 z16 z4 I've tried: camcontrol cmd -n da -u 0 -c 12 0 0 0 v 0 96 -i 96 s8 z8 z16 z4 which appears to be the equivalent camcontrol command, but I only get the error message camcontrol: error sending command I've ktraced camcontrol, and find that it calls a number of CAMIOCOMMAND ioctls just before this message. All of the CAMIOCOMMANDs are successful, so I assume it's the device returning some error indication. Obviously I'm getting the command parameters screwed up. Does camcontrol use scsi(3)? How do I specify this command? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sun Nov 29 21:50:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA20256 for freebsd-scsi-outgoing; Sun, 29 Nov 1998 21:50:42 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA20250 for ; Sun, 29 Nov 1998 21:50:40 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id GAA24348; Mon, 30 Nov 1998 06:50:29 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id GAA18098; Mon, 30 Nov 1998 06:35:10 +0100 (MET) (envelope-from j) Message-ID: <19981130063508.59638@uriah.heep.sax.de> Date: Mon, 30 Nov 1998 06:35:08 +0100 From: J Wunsch To: FreeBSD SCSI Mailing List Cc: Greg Lehey Subject: Re: Formatting disks under CAM Reply-To: Joerg Wunsch References: <19981130111418.D831@freebie.lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19981130111418.D831@freebie.lemis.com>; from Greg Lehey on Mon, Nov 30, 1998 at 11:14:18AM +1030 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 Greg Lehey wrote: > I've got a disk which has developed a number of bad spots, and I want > to format it. I've tried scsiformat, but it hasn't been converted for > CAM. scsiformat uses the following command to perform the format: > > scsi -f /dev/rsd0.ctl -v -c 12 0 0 0 v 0 96 -i 96 s8 z8 z16 z4 You err on this. That's only the INQUIRY command. Peter (Dufault) only added this to the scsiformt script in order to remain API-compatible with the 4.4BSD scsiformat(8) command (that never ran under FreeBSD). The actual formatting command is -c "4 0 0 0 0 0", and should work with camcontrol as well. You might need to bump the timeout though. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- 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 Mon Nov 30 03:07:38 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA14696 for freebsd-scsi-outgoing; Mon, 30 Nov 1998 03:07:38 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ms-18sptg1.kadena.af.mil (ms-18sptg1.kadena.af.mil [132.15.75.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA14691 for ; Mon, 30 Nov 1998 03:07:36 -0800 (PST) (envelope-from Wayne.Baety@kadena.af.mil) Received: by ms-18sptg1.kadena.af.mil with Internet Mail Service (5.5.2232.9) id ; Mon, 30 Nov 1998 20:07:24 +0900 Message-ID: <06A98ECF2D0FD211AA240060B0681211F6CBB0@ms-18sptg1.kadena.af.mil> From: Baety Wayne Amn 18CS/SCBD To: "'FreeBSD SCSI'" Subject: CAM Date: Mon, 30 Nov 1998 20:07:24 +0900 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Where's documentation on properly configuring a kernel for use with this new CAM SCSI subsystem. I have a Mylex DAC960PL (uses Symbios 53C720SE controller) and am wondering how to enable it in the kernel. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 30 12:39:46 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA12035 for freebsd-scsi-outgoing; Mon, 30 Nov 1998 12:39:46 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from PacHell.TelcoSucks.org (PacHell.TelcoSucks.org [207.90.181.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA12030; Mon, 30 Nov 1998 12:39:44 -0800 (PST) (envelope-from ulf@PacHell.TelcoSucks.org) Received: (from ulf@localhost) by PacHell.TelcoSucks.org (8.9.1/8.9.1) id MAA01172; Mon, 30 Nov 1998 12:39:42 -0800 (PST) (envelope-from ulf) Message-ID: <19981130123942.A856@TelcoSucks.org> Date: Mon, 30 Nov 1998 12:39:42 -0800 From: Ulf Zimmermann To: current@FreeBSD.ORG, scsi@FreeBSD.ORG Subject: [ulf@Alameda.net: Re: CAM] Reply-To: ulf@Alameda.net Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i Organization: Alameda Networks, Inc. X-Operating-System: FreeBSD 3.0-19980930-BETA Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Forgot to copy the lists on it. ----- Forwarded message from Ulf Zimmermann ----- Date: Mon, 30 Nov 1998 12:36:59 -0800 From: Ulf Zimmermann To: Baety Wayne Amn 18CS/SCBD Subject: Re: CAM On Mon, Nov 30, 1998 at 08:04:59PM +0900, Baety Wayne Amn 18CS/SCBD wrote: > > Where's documentation on properly configuring a kernel for use with this new > CAM SCSI subsystem. I have a Mylex DAC960PL (uses Symbios 53C720SE > controller) and am wondering how to enable it in the kernel. CAM does not support the Mylex DAC960 Raid controllers. I have been on and off working on a driver, but I am stuck about understanding certain kernel things and I am low on time right now. -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 ----- End forwarded message ----- -- Regards, Ulf. --------------------------------------------------------------------- Ulf Zimmermann, 1525 Pacific Ave., Alameda, CA-94501, #: 510-769-2936 Alameda Networks, Inc. | http://www.Alameda.net | Fax#: 510-521-5073 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 30 14:46:00 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA26857 for freebsd-scsi-outgoing; Mon, 30 Nov 1998 14:46:00 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA26846 for ; Mon, 30 Nov 1998 14:45:57 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id XAA20558; Mon, 30 Nov 1998 23:45:38 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA04181 (5.67b/IDA-1.5); Mon, 30 Nov 1998 23:18:34 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id VAA01718; Mon, 30 Nov 1998 21:30:49 +0100 (CET) From: Wilko Bulte Message-Id: <199811302030.VAA01718@yedi.iaf.nl> Subject: Re: CAM In-Reply-To: <06A98ECF2D0FD211AA240060B0681211F6CBB0@ms-18sptg1.kadena.af.mil> from Baety Wayne Amn 18CS/SCBD at "Nov 30, 98 08:07:24 pm" To: Wayne.Baety@kadena.af.mil (Baety Wayne Amn 18CS/SCBD) Date: Mon, 30 Nov 1998 21:30:49 +0100 (CET) Cc: freebsd-scsi@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As Baety Wayne Amn 18CS/SCBD wrote... > > Where's documentation on properly configuring a kernel for use with this new > CAM SCSI subsystem. I have a Mylex DAC960PL (uses Symbios 53C720SE > controller) and am wondering how to enable it in the kernel. I'd be surprised if Ulf already A. finished the DAC driver and B. put it into the mainstream -current tree. Ulf, care to comment? Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 30 15:38:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04189 for freebsd-scsi-outgoing; Mon, 30 Nov 1998 15:38:56 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ms-18sptg1.kadena.af.mil (ms-18sptg1.kadena.af.mil [132.15.75.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA04165 for ; Mon, 30 Nov 1998 15:38:48 -0800 (PST) (envelope-from Wayne.Baety@kadena.af.mil) Received: by ms-18sptg1.kadena.af.mil with Internet Mail Service (5.5.2232.9) id ; Tue, 1 Dec 1998 08:38:31 +0900 Message-ID: <06A98ECF2D0FD211AA240060B0681211F6CBB1@ms-18sptg1.kadena.af.mil> From: Baety Wayne Amn 18CS/SCBD To: "'FreeBSD SCSI'" Date: Tue, 1 Dec 1998 08:38:30 +0900 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ok, I guess I misunderstood, I thought CAM was more chip based rather than card based, what about the DTC3280AS (Data Technology) it uses an NCR 53C400A controller chip, btw is there more documentation for CAM besides LINT. I'd like to know how to set it up, and what cards/chips it supports. Wayne A. Baety, Amn, USAF (18CS/SCBDC) Web Administration Team IPO Technician / WWW Administrator wayne.baety@kadena.af.mil To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 30 15:56:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA06775 for freebsd-scsi-outgoing; Mon, 30 Nov 1998 15:56:30 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA06737 for ; Mon, 30 Nov 1998 15:56:22 -0800 (PST) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id RAA22677 for ; Mon, 30 Nov 1998 17:55:53 -0600 (CST) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma022553; Mon, 30 Nov 98 17:55:19 -0600 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with ESMTP id RAA06853 for ; Mon, 30 Nov 1998 17:55:17 -0600 (CST) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Mon, 30 Nov 1998 17:55:16 -0600 (CST) From: Kyle Mestery To: freebsd-scsi@FreeBSD.ORG Subject: Problems in current with a CD-ROM drive 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 am running current as of 11-30 at about 4PM or so. I have a Sony 4x SCSI CD-ROM running on a dual Pentium machine that suddenly has stopped working. What I mean is, it no longer can correctly play audio CDs. Here is the relevant dmesg output: bt0: rev 0x00 int a irq 17 on pci0.19.0 bt0: BT-946C FW Rev. 4.25J Narrow SCSI Host Adapter, SCSI ID 7, 100 CCBs cd0 at bt0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 5.0MB/s transfers (5.0MHz, offset 15) cd0: cd present [214790 x 2048 byte records] There is also one 1GB HP disk on that controller. What happens is, if I load an audio CD into the drive, and use cdcontrol to play it, the CD plays fine initially, but when I type stop in cdcontrol to stop it, the process gets hung. I cannot kill it or anything. It gets stuck in cbwait, as is shown below from top: PID USERNAME PRI NICE SIZE RES STATE C TIME WCPU CPU COMMAND 417 mestery -6 0 944K 432K cbwait 0 0:00 0.00% 0.00% cdcontrol If I type eject from cdcontrol, it will eject, but never close again until reset. THe drive's light continues to flicker from busy to not busy, and once again cdcontrol is stuck in cbwait. Is this a known problem with the above setup? Is anyone else seeing this? I tried using workman to play audio CDs, but it hangs upon pressing play. Not sure if it also hangs in cbwait. Any pointers would be appreciated! Thanks! -- Kyle Mestery StorageTek's Storage Networking Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 30 16:10:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10449 for freebsd-scsi-outgoing; Mon, 30 Nov 1998 16:10:11 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10372 for ; Mon, 30 Nov 1998 16:10:01 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id TAA17057; Mon, 30 Nov 1998 19:07:27 -0500 (EST) Date: Mon, 30 Nov 1998 19:07:27 -0500 (EST) From: "Matthew N. Dodd" To: Wilko Bulte cc: Baety Wayne Amn 18CS/SCBD , freebsd-scsi@FreeBSD.ORG Subject: Re: CAM In-Reply-To: <199811302030.VAA01718@yedi.iaf.nl> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 30 Nov 1998, Wilko Bulte wrote: > As Baety Wayne Amn 18CS/SCBD wrote... > > Where's documentation on properly configuring a kernel for use with this new > > CAM SCSI subsystem. I have a Mylex DAC960PL (uses Symbios 53C720SE > > controller) and am wondering how to enable it in the kernel. > > I'd be surprised if Ulf already A. finished the DAC driver and B. put it > into the mainstream -current tree. The 53c7xx is a subset of the 53c8xx chips which are supported by the 'ncr' driver. I don't think the DAC driver is the same thing though I could be wrong. I've got a copy of the 53c7xx manuals laying around but no time to play with it. (And only a Compaq to test against.) -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 30 16:20:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA11946 for freebsd-scsi-outgoing; Mon, 30 Nov 1998 16:20:29 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ms-18sptg1.kadena.af.mil (ms-18sptg1.kadena.af.mil [132.15.75.200]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA11934 for ; Mon, 30 Nov 1998 16:20:21 -0800 (PST) (envelope-from Wayne.Baety@kadena.af.mil) Received: by ms-18sptg1.kadena.af.mil with Internet Mail Service (5.5.2232.9) id ; Tue, 1 Dec 1998 09:02:11 +0900 Message-ID: <06A98ECF2D0FD211AA240060B0681211F6CBB2@ms-18sptg1.kadena.af.mil> From: Baety Wayne Amn 18CS/SCBD To: "'FreeBSD SCSI'" Subject: CAM Information Date: Tue, 1 Dec 1998 09:02:10 +0900 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2232.9) Content-Type: text/plain; charset="iso-8859-1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ok, I guess I misunderstood, I thought CAM was more chip based rather than card based, what about the DTC3280AS (Data Technology) it uses an NCR 53C400A controller chip, btw is there more documentation for CAM besides LINT. I'd like to know how to set it up, and what cards/chips it supports. Wayne A. Baety, Amn, USAF (18CS/SCBDC) Web Administration Team IPO Technician / WWW Administrator wayne.baety@kadena.af.mil To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 30 16:45:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA16057 for freebsd-scsi-outgoing; Mon, 30 Nov 1998 16:45:33 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA16049 for ; Mon, 30 Nov 1998 16:45:31 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id RAA12339; Mon, 30 Nov 1998 17:45:08 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812010045.RAA12339@panzer.plutotech.com> Subject: Re: CAM Information In-Reply-To: <06A98ECF2D0FD211AA240060B0681211F6CBB2@ms-18sptg1.kadena.af.mil> from Baety Wayne Amn 18CS/SCBD at "Dec 1, 98 09:02:10 am" To: Wayne.Baety@kadena.af.mil (Baety Wayne Amn 18CS/SCBD) Date: Mon, 30 Nov 1998 17:45:07 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Baety Wayne Amn 18CS/SCBD wrote... > ok, I guess I misunderstood, I thought CAM was more chip based rather than > card based, what about the DTC3280AS (Data Technology) it uses an NCR > 53C400A controller chip, btw is there more documentation for CAM besides > LINT. I'd like to know how to set it up, and what cards/chips it supports. The list of supported chips/cards is in the 3.0 release notes. The HARDWARE.TXT is incorrect as far as its list of supported SCSI controllers. If you want more details on setting up your kernel config file, see scsi(4). Here are some other man pages: adv(4), adw(4), aha(4), ahb(4), ahc(4), bt(4), cd(4), ch(4), da(4), dpt(4), ncr(4), pass(4), pt(4), sa(4), xpt(4), camcontrol(8) If you want a recommendation on what SCSI controller to get, I would suggest getting an Adaptec 7890 or 7895-based controller. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 30 17:05:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA18604 for freebsd-scsi-outgoing; Mon, 30 Nov 1998 17:05:47 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18596 for ; Mon, 30 Nov 1998 17:05:43 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id SAA12477; Mon, 30 Nov 1998 18:05:08 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812010105.SAA12477@panzer.plutotech.com> Subject: Re: Formatting disks under CAM In-Reply-To: <19981130111418.D831@freebie.lemis.com> from Greg Lehey at "Nov 30, 98 11:14:18 am" To: grog@lemis.com (Greg Lehey) Date: Mon, 30 Nov 1998 18:05:08 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greg Lehey wrote... > I've got a disk which has developed a number of bad spots, and I want > to format it. I've tried scsiformat, but it hasn't been converted for > CAM. scsiformat uses the following command to perform the format: > > scsi -f /dev/rsd0.ctl -v -c 12 0 0 0 v 0 96 -i 96 s8 z8 z16 z4 > > I've tried: > > camcontrol cmd -n da -u 0 -c 12 0 0 0 v 0 96 -i 96 s8 z8 z16 z4 > > which appears to be the equivalent camcontrol command, but I only get > the error message > > camcontrol: error sending command Joerg already pointed out that that isn't the format command, but rather the inquiry command. The reason it doesn't work is because you need to quote things. This works: camcontrol cmd -n da -u 0 -c "12 0 0 0 v 0" 96 -i 96 "s8 z8 z16 z4" You've eliminated the quotes even from the command you copied out of scsiformat(8). Of course it's much easier to just type 'camcontrol inquiry'. I plan on adding a 'camcontrol format' subcommand that will provide better functionality than the old scsiformat utility. I also plan on getting Joerg Schilling's sformat utility to work with CAM. It appears to do far more formatting/remapping things than I plan on implementing within camcontrol. > I've ktraced camcontrol, and find that it calls a number of > CAMIOCOMMAND ioctls just before this message. All of the > CAMIOCOMMANDs are successful, so I assume it's the device returning > some error indication. Obviously I'm getting the command parameters > screwed up. Does camcontrol use scsi(3)? How do I specify this > command? The syntax is the same as the syntax described in scsi(3). With CAM, the man pages you want are cam(3) and cam_cdbparse(3). You can also reference those pages via the names of the functions they describe. (e.g., cam_open_btl(3), csio_build(3), etc.) The cam_cdbparse(3) man page is based on the old scsi(3) man page, since it describes a lot of the functionality that I ported from the old SCSI library. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Nov 30 21:29:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA14987 for freebsd-scsi-outgoing; Mon, 30 Nov 1998 21:29:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA14982 for ; Mon, 30 Nov 1998 21:29:32 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id WAA13755; Mon, 30 Nov 1998 22:28:59 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812010528.WAA13755@panzer.plutotech.com> Subject: Re: tosha reports random errors after transition to CAM In-Reply-To: <19981129142027.A9664@wopr.caltech.edu> from Matthew Hunt at "Nov 29, 98 02:20:27 pm" To: mph@pobox.com (Matthew Hunt) Date: Mon, 30 Nov 1998 22:28:58 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Hunt wrote... > Since upgrading from 2.2-STABLE to 3.0-CURRENT, and hence CAM, I > have observed random errors when using tosha to read CD audio data > from my CD-ROM drive. The drive is branded IBM, but when I purchased > it, I was told that it is a Toshiba XM-4101. > > When I try to rip CD audio, tosha emits the following error: > > wopr:~/tmp$ tosha -v -t 1 -o out.pcm > Device: /dev/cd0c IBM CDRM00201 !F 0724 > tosha: WARNING: Drive type not recognized. > Output file: out.pcm > > track playing start end raw size mp3 size # of > number time sector sector in bytes 128 kbps frames > -------------------------------------------------------------- > 1 4:22'18 0 19667 46259136 4196675 10039 > error returned from CD-DA read command: > (pass1:ahc0:0:3:0): Vendor Specific Command. CDB: d8 > (pass1:ahc0:0:3:0): ILLEGAL REQUEST asc:bf,0 > (pass1:ahc0:0:3:0): Vendor Specific ASC > > The error is always the same, but it occurs at random places and does > not appear to depend on what CD or track I am ripping. I never had > any problems pre-CAM. I have (obviously) recompiled tosha to support > the CAM architecture. > > Can anyone provide illumination? It's kinda difficult to decipher vendor-specific error messages. I would suggest contacting Oliver Fromme . He is the author of tosha, and he may know what that error code means. He may also want to explicitly define that particular IBM CDROM drive as a Toshiba-like drive. I'm not sure why it would behave differently under CAM than under the old SCSI subsystem. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 1 05:31:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA27396 for freebsd-scsi-outgoing; Tue, 1 Dec 1998 05:31:44 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from thing.dyn.ml.org (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA27388 for ; Tue, 1 Dec 1998 05:31:38 -0800 (PST) (envelope-from bsdx@spawnet.com) Received: from spawnet.com (bsdx [192.168.1.2]) by thing.dyn.ml.org (8.9.1/8.8.7) with ESMTP id IAA06361 for ; Tue, 1 Dec 1998 08:31:15 -0500 (EST) (envelope-from bsdx@spawnet.com) Message-ID: <3663EFA0.BD143233@spawnet.com> Date: Tue, 01 Dec 1998 08:31:12 -0500 From: Adam McDougall X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: scsi@FreeBSD.ORG Subject: Re: tosha reports random errors after transition to CAM References: <19981129142027.A9664@wopr.caltech.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Matthew Hunt wrote: > > Since upgrading from 2.2-STABLE to 3.0-CURRENT, and hence CAM, I > have observed random errors when using tosha to read CD audio data > from my CD-ROM drive. The drive is branded IBM, but when I purchased > it, I was told that it is a Toshiba XM-4101. > > When I try to rip CD audio, tosha emits the following error: > > wopr:~/tmp$ tosha -v -t 1 -o out.pcm > Device: /dev/cd0c IBM CDRM00201 !F 0724 > tosha: WARNING: Drive type not recognized. > Output file: out.pcm > > track playing start end raw size mp3 size # of > number time sector sector in bytes 128 kbps frames > -------------------------------------------------------------- > 1 4:22'18 0 19667 46259136 4196675 10039 > error returned from CD-DA read command: > (pass1:ahc0:0:3:0): Vendor Specific Command. CDB: d8 > (pass1:ahc0:0:3:0): ILLEGAL REQUEST asc:bf,0 > (pass1:ahc0:0:3:0): Vendor Specific ASC > > The error is always the same, but it occurs at random places and does > not appear to depend on what CD or track I am ripping. I never had > any problems pre-CAM. I have (obviously) recompiled tosha to support > the CAM architecture. > > Can anyone provide illumination? > Matt > > -- > Matthew Hunt * Inertia is a property of matter. > http://www.pobox.com/~mph/pgp.key for PGP public key 0x67203349. > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-scsi" in the body of the message I think I notice the same thing too. (well, similar) It started happening when I changed HD's from a Atlas II to a Viking UW. Seems like my symptoms are more drastic though, because when I run tosha (even when not storing the data being read on da0) I will get something like this: 1 63:07'00 33 284057 668026800 60592835 144972 (output file: track01.pcm) (da0:dpt0:0:0:0): WRITE(06). CDB: a 9 e0 40 10 0 (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:24,0 (da0:dpt0:0:0:0): Invalid field in CDB field replaceable unit: 80 sks:c0,9 (da0:dpt0:0:0:0): READ(06). CDB: 8 2 95 58 8 0 (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:24,0 (da0:dpt0:0:0:0): Invalid field in CDB field replaceable unit: 80 sks:c0,9 swap_pager: I/O error - pagein failed; blkno 46424, size 4096, error 22 vm_fault: pager read error, pid 96 (syslogd) (da0:dpt0:0:0:0): WRITE(06). CDB: a 1 0 50 10 0 (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:24,0 (da0:dpt0:0:0:0): Invalid field in CDB field replaceable unit: 80 sks:c0,9 ^C (da0:dpt0:0:0:0): READ(06). CDB: 8 2 9 b0 28 0 (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:24,0 (da0:dpt0:0:0:0): Invalid field in CDB field replaceable unit: 80 sks:c0,9 swap_pager: I/O error - pagein failed; blkno 10672, size 20480, error 22 vm_fault: pager read error, pid 257 (tcsh) pid 257 (tcsh), uid 1001: exited on signal 11 (core dumped) FreeBSD/i386 (hostname.domain.com) (ttyv0) login: Seems that tosha is stealing complete control of the drive, any programs including the kernel blow up if they try to use the disk while im using tosha. panic messages vary all over since its acting like the disk is screwed up, even though everything is happy when I dont run tosha :/ Turning off tagged queueing didn't help, turning off softupdates didn't help, its not overclocked. Termination is correct. Insight would be appreciated! :) FreeBSD 3.0-CURRENT #0: Sun Nov 29 13:15:37 EST 1998 dpt0: rev 0x02 int a irq 12 on pci0.17.0 dpt0: DPT PM2144UW FW Rev. 07LY, 1 channel, 64 CCBs da0: Fixed Direct Access SCSI2 device da0: Tagged Queueing Enabled da0: 4345MB (8899736 512 byte sectors: 255H 63S/T 553C) cd0 at dpt0 bus 0 target 3 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: cd present [328542 x 2048 byte records] To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 1 10:46:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00570 for freebsd-scsi-outgoing; Tue, 1 Dec 1998 10:46:11 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00560 for ; Tue, 1 Dec 1998 10:46:08 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id LAA21068; Tue, 1 Dec 1998 11:45:47 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812011845.LAA21068@panzer.plutotech.com> Subject: Re: tosha reports random errors after transition to CAM In-Reply-To: <3663EFA0.BD143233@spawnet.com> from Adam McDougall at "Dec 1, 98 08:31:12 am" To: bsdx@spawnet.com (Adam McDougall) Date: Tue, 1 Dec 1998 11:45:47 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Adam McDougall wrote... > Matthew Hunt wrote: > > > > Since upgrading from 2.2-STABLE to 3.0-CURRENT, and hence CAM, I > > have observed random errors when using tosha to read CD audio data > > from my CD-ROM drive. The drive is branded IBM, but when I purchased > > it, I was told that it is a Toshiba XM-4101. > > > > When I try to rip CD audio, tosha emits the following error: > > > > wopr:~/tmp$ tosha -v -t 1 -o out.pcm > > Device: /dev/cd0c IBM CDRM00201 !F 0724 > > tosha: WARNING: Drive type not recognized. > > Output file: out.pcm > > > > track playing start end raw size mp3 size # of > > number time sector sector in bytes 128 kbps frames > > -------------------------------------------------------------- > > 1 4:22'18 0 19667 46259136 4196675 10039 > > error returned from CD-DA read command: > > (pass1:ahc0:0:3:0): Vendor Specific Command. CDB: d8 > > (pass1:ahc0:0:3:0): ILLEGAL REQUEST asc:bf,0 > > (pass1:ahc0:0:3:0): Vendor Specific ASC > > > > The error is always the same, but it occurs at random places and does > > not appear to depend on what CD or track I am ripping. I never had > > any problems pre-CAM. I have (obviously) recompiled tosha to support > > the CAM architecture. > > > > Can anyone provide illumination? > > Matt > > > > -- > > Matthew Hunt * Inertia is a property of matter. > > http://www.pobox.com/~mph/pgp.key for PGP public key 0x67203349. > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-scsi" in the body of the message > > > I think I notice the same thing too. (well, similar) > It started happening when I changed HD's from a Atlas II to a Viking UW. That could be your problem...I'll explain below. > Seems like my symptoms are more drastic though, because when I run tosha > (even when not storing the data being read on da0) I will get something > like this: > 1 63:07'00 33 284057 668026800 60592835 144972 > (output file: track01.pcm) > (da0:dpt0:0:0:0): WRITE(06). CDB: a 9 e0 40 10 0 > (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:24,0 > (da0:dpt0:0:0:0): Invalid field in CDB field replaceable unit: 80 > sks:c0,9 > (da0:dpt0:0:0:0): READ(06). CDB: 8 2 95 58 8 0 > (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:24,0 > (da0:dpt0:0:0:0): Invalid field in CDB field replaceable unit: 80 > sks:c0,9 > swap_pager: I/O error - pagein failed; blkno 46424, size 4096, error 22 > vm_fault: pager read error, pid 96 (syslogd) > (da0:dpt0:0:0:0): WRITE(06). CDB: a 1 0 50 10 0 > (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:24,0 > (da0:dpt0:0:0:0): Invalid field in CDB field replaceable unit: 80 > sks:c0,9 > ^C > (da0:dpt0:0:0:0): READ(06). CDB: 8 2 9 b0 28 0 > (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:24,0 > (da0:dpt0:0:0:0): Invalid field in CDB field replaceable unit: 80 > sks:c0,9 This is rather bizzare, since the drive is complaining about byte 9 of a 6 byte CDB. Justin suspects that the drive may not be handling 6-byte reads and writes properly. > dpt0: rev 0x02 int a irq 12 on > pci0.17.0 > dpt0: DPT PM2144UW FW Rev. 07LY, 1 channel, 64 CCBs > da0: Fixed Direct Access SCSI2 device > da0: Tagged Queueing Enabled > da0: 4345MB (8899736 512 byte sectors: 255H 63S/T 553C) Try this -- go into sys/cam/scsi/scsi_da.c, and on about line 1079, adjust the minimum_cmd_size for the read and write commands to 10 bytes. It could be that the disk isn't handling 6-byte reads and writes. It could also be some problem with the DPT driver, or the DPT firmware. (Simon would probably have a better idea on this one.) I suspect, though, that it may be a drive firmware problem. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 1 12:26:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13033 for freebsd-scsi-outgoing; Tue, 1 Dec 1998 12:26:39 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from vidar.erilab.com (mpk104.erilab.com [208.224.156.104]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13028 for ; Tue, 1 Dec 1998 12:26:36 -0800 (PST) (envelope-from Rainer.Enders@erilab.com) Received: from erilab.com (willow.erilab.com [192.168.174.2]) by vidar.erilab.com (8.9.1a/8.9.1) with ESMTP id MAA04161 for ; Tue, 1 Dec 1998 12:26:21 -0800 (PST) Message-ID: <366451AD.C20837ED@erilab.com> Date: Tue, 01 Dec 1998 12:29:33 -0800 From: Rainer Enders Organization: Ericsson Cyberlab West X-Mailer: Mozilla 4.06 [en] (X11; U; SunOS 5.6 sun4m) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: Which RAID controllers? Content-Type: multipart/mixed; boundary="------------A8F5905F15DCE21295E2B4C1" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. --------------A8F5905F15DCE21295E2B4C1 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Which RAID Controllers work best with FreeBSD 2.2.7/2.2.8? Any different answer for 3.0? I would like to use either Mylex or DPT if at all possible. Thanks, Rainer. --------------A8F5905F15DCE21295E2B4C1 Content-Type: text/x-vcard; charset=us-ascii; name="vcard.vcf" Content-Transfer-Encoding: 7bit Content-Description: Card for Rainer Enders Content-Disposition: attachment; filename="vcard.vcf" begin: vcard fn: Rainer Enders n: Enders;Rainer org: Ericsson Inc. adr: 1555 Adams Drive;;;Menlo Park;CA;94025;U.S.A. email;internet: Rainer.Enders@erilab.com title: Senior Systems Engineer tel;work: (650) 853-4303 tel;fax: (650) 853-4333 tel;home: (510) 409-1365 x-mozilla-cpt: ;0 x-mozilla-html: FALSE version: 2.1 end: vcard --------------A8F5905F15DCE21295E2B4C1-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 1 12:45:40 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA14653 for freebsd-scsi-outgoing; Tue, 1 Dec 1998 12:45:40 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA14644 for ; Tue, 1 Dec 1998 12:45:37 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id NAA21624; Tue, 1 Dec 1998 13:45:13 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812012045.NAA21624@panzer.plutotech.com> Subject: Re: Which RAID controllers? In-Reply-To: <366451AD.C20837ED@erilab.com> from Rainer Enders at "Dec 1, 98 12:29:33 pm" To: Rainer.Enders@erilab.com (Rainer Enders) Date: Tue, 1 Dec 1998 13:45:13 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Rainer Enders wrote... > Which RAID Controllers work best with > FreeBSD 2.2.7/2.2.8? > > Any different answer for 3.0? For 2.2.7/2.2.8, or 3.0, your choices are: - DPT, if you want an internal RAID controller - Any external SCSI-SCSI RAID controller. > I would like to use either Mylex or DPT if at > all possible. DPT cards are supported. The Mylex internal RAID controllers are not supported, but their SCSI-SCSI controllers should work fine with a supported SCSI controller. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 1 16:13:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA10446 for freebsd-scsi-outgoing; Tue, 1 Dec 1998 16:13:22 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from thing.dyn.ml.org (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA10435 for ; Tue, 1 Dec 1998 16:13:20 -0800 (PST) (envelope-from bsdx@spawnet.com) Received: from spawnet.com (bsdx [192.168.1.2]) by thing.dyn.ml.org (8.9.1/8.8.7) with ESMTP id TAA24561 for ; Tue, 1 Dec 1998 19:13:07 -0500 (EST) (envelope-from bsdx@spawnet.com) Message-ID: <36648612.693004F7@spawnet.com> Date: Tue, 01 Dec 1998 19:13:06 -0500 From: Adam McDougall X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: scsi@FreeBSD.ORG Subject: Re: tosha reports random errors after transition to CAM References: <199812011845.LAA21068@panzer.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry wrote: > > Adam McDougall wrote... > > I think I notice the same thing too. (well, similar) > > It started happening when I changed HD's from a Atlas II to a Viking UW. > > That could be your problem...I'll explain below. > > (da0:dpt0:0:0:0): READ(06). CDB: 8 2 9 b0 28 0 > > (da0:dpt0:0:0:0): ILLEGAL REQUEST asc:24,0 > > (da0:dpt0:0:0:0): Invalid field in CDB field replaceable unit: 80 > > sks:c0,9 > > This is rather bizzare, since the drive is complaining about byte 9 of a 6 > byte CDB. > > Justin suspects that the drive may not be handling 6-byte reads and writes > properly. > > > dpt0: rev 0x02 int a irq 12 on > > pci0.17.0 > > dpt0: DPT PM2144UW FW Rev. 07LY, 1 channel, 64 CCBs > > da0: Fixed Direct Access SCSI2 device > > da0: Tagged Queueing Enabled > > da0: 4345MB (8899736 512 byte sectors: 255H 63S/T 553C) > > Try this -- go into sys/cam/scsi/scsi_da.c, and on about line 1079, adjust > the minimum_cmd_size for the read and write commands to 10 bytes. > THANK YOU!!!! works PERFECT now :) So, what does this mean the problem might be? > It could be that the disk isn't handling 6-byte reads and writes. It could > also be some problem with the DPT driver, or the DPT firmware. (Simon > would probably have a better idea on this one.) I suspect, though, that > it may be a drive firmware problem. > > Ken > -- > Kenneth Merry > ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 1 17:58:28 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA20495 for freebsd-scsi-outgoing; Tue, 1 Dec 1998 17:58:28 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA20488 for ; Tue, 1 Dec 1998 17:58:26 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id SAA23279; Tue, 1 Dec 1998 18:58:09 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812020158.SAA23279@panzer.plutotech.com> Subject: Re: tosha reports random errors after transition to CAM In-Reply-To: <36648612.693004F7@spawnet.com> from Adam McDougall at "Dec 1, 98 07:13:06 pm" To: bsdx@spawnet.com (Adam McDougall) Date: Tue, 1 Dec 1998 18:58:09 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM912563889-23232-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ELM912563889-23232-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Adam McDougall wrote... > Kenneth D. Merry wrote: > > Adam McDougall wrote... > > Justin suspects that the drive may not be handling 6-byte reads and writes > > properly. > > > > > dpt0: rev 0x02 int a irq 12 on > > > pci0.17.0 > > > dpt0: DPT PM2144UW FW Rev. 07LY, 1 channel, 64 CCBs > > > da0: Fixed Direct Access SCSI2 device > > > da0: Tagged Queueing Enabled > > > da0: 4345MB (8899736 512 byte sectors: 255H 63S/T 553C) > > > > Try this -- go into sys/cam/scsi/scsi_da.c, and on about line 1079, adjust > > the minimum_cmd_size for the read and write commands to 10 bytes. > > > > THANK YOU!!!! works PERFECT now :) > > So, what does this mean the problem might be? It means you're the victim of yet another high quality Quantum drive. (i.e., it's a firmware bug) Next time, buy Seagate or IBM. Try the attached patch, and see if it works for you. If it does, I'll probably commit it or something close to it. Also -- please CC your mail to me, and don't send it just to the list. You may get a faster response that way. Ken -- Kenneth Merry ken@plutotech.com --ELM912563889-23232-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=scsi_da.no_6_byte.120198 Content-Description: scsi_da.no_6_byte.120198 Content-Transfer-Encoding: 7bit ==== //depot/cam/sys/cam/scsi/scsi_da.c#89 - /usr/home/ken/perforce/cam/sys/cam/scsi/scsi_da.c ==== *** /tmp/tmp.12080.0 Tue Dec 1 18:52:26 1998 --- /usr/home/ken/perforce/cam/sys/cam/scsi/scsi_da.c Tue Dec 1 18:40:29 1998 *************** *** 75,81 **** typedef enum { DA_Q_NONE = 0x00, ! DA_Q_NO_SYNC_CACHE = 0x01 } da_quirks; typedef enum { --- 75,82 ---- typedef enum { DA_Q_NONE = 0x00, ! DA_Q_NO_SYNC_CACHE = 0x01, ! DA_Q_NO_6_BYTE = 0x02 } da_quirks; typedef enum { *************** *** 107,112 **** --- 108,114 ---- da_state state; da_flags flags; da_quirks quirks; + int minimum_cmd_size; int ordered_tag_count; struct disk_params params; struct diskslices *dk_slices; /* virtual drives */ *************** *** 146,151 **** --- 148,170 ---- */ {T_DIRECT, SIP_MEDIA_FIXED, "NEC", "D3847*", "*"}, /*quirks*/ DA_Q_NO_SYNC_CACHE + }, + { + /* + * Doesn't work correctly with 6 byte reads/writes. + * Returns illegal request, and points to byte 9 of the + * 6-byte CDB. + * Reported by: Adam McDougall + */ + {T_DIRECT, SIP_MEDIA_FIXED, "QUANTUM", "VIKING 4*", "*"}, + /*quirks*/ DA_Q_NO_6_BYTE + }, + { + /* + * See above. + */ + {T_DIRECT, SIP_MEDIA_FIXED, "QUANTUM", "VIKING 2*", "*"}, + /*quirks*/ DA_Q_NO_6_BYTE } }; *************** *** 648,654 **** MSG_ORDERED_Q_TAG, /*read*/FALSE, /*byte2*/0, ! /*minimum_cmd_size*/ 6, blknum, blkcnt, /*data_ptr*/CADDR1, --- 667,673 ---- MSG_ORDERED_Q_TAG, /*read*/FALSE, /*byte2*/0, ! /*minimum_cmd_size*/ softc->minimum_cmd_size, blknum, blkcnt, /*data_ptr*/CADDR1, *************** *** 977,982 **** --- 996,1006 ---- else softc->quirks = DA_Q_NONE; + if (softc->quirks & DA_Q_NO_6_BYTE) + softc->minimum_cmd_size = 10; + else + softc->minimum_cmd_size = 6; + /* * Block our timeout handler while we * add this softc to the dev list. *************** *** 1076,1082 **** tag_code, bp->b_flags & B_READ, /*byte2*/0, ! /*minimum_cmd_size*/ 6, bp->b_pblkno, bp->b_bcount / softc->params.secsize, bp->b_data, --- 1100,1106 ---- tag_code, bp->b_flags & B_READ, /*byte2*/0, ! softc->minimum_cmd_size, bp->b_pblkno, bp->b_bcount / softc->params.secsize, bp->b_data, --ELM912563889-23232-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Dec 1 19:28:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA28308 for freebsd-scsi-outgoing; Tue, 1 Dec 1998 19:28:11 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from thing.dyn.ml.org (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA28303 for ; Tue, 1 Dec 1998 19:28:08 -0800 (PST) (envelope-from bsdx@spawnet.com) Received: from spawnet.com (bsdx [192.168.1.2]) by thing.dyn.ml.org (8.9.1/8.8.7) with ESMTP id WAA29959; Tue, 1 Dec 1998 22:27:52 -0500 (EST) (envelope-from bsdx@spawnet.com) Message-ID: <3664B3B7.1ABB1D6E@spawnet.com> Date: Tue, 01 Dec 1998 22:27:51 -0500 From: Adam McDougall X-Mailer: Mozilla 4.06 [en] (X11; I; FreeBSD 3.0-CURRENT i386) MIME-Version: 1.0 To: "Kenneth D. Merry" , scsi@FreeBSD.ORG Subject: Re: tosha reports random errors after transition to CAM References: <199812020158.SAA23279@panzer.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kenneth D. Merry wrote: > > Adam McDougall wrote... > > Kenneth D. Merry wrote: > > > Adam McDougall wrote... > > > Justin suspects that the drive may not be handling 6-byte reads and writes > > > properly. > > > > > > > dpt0: rev 0x02 int a irq 12 on > > > > pci0.17.0 > > > > dpt0: DPT PM2144UW FW Rev. 07LY, 1 channel, 64 CCBs > > > > da0: Fixed Direct Access SCSI2 device > > > > da0: Tagged Queueing Enabled > > > > da0: 4345MB (8899736 512 byte sectors: 255H 63S/T 553C) > > > > > > Try this -- go into sys/cam/scsi/scsi_da.c, and on about line 1079, adjust > > > the minimum_cmd_size for the read and write commands to 10 bytes. > > > > > > > THANK YOU!!!! works PERFECT now :) > > > > So, what does this mean the problem might be? > > It means you're the victim of yet another high quality Quantum drive. > (i.e., it's a firmware bug) Next time, buy Seagate or IBM. > > Try the attached patch, and see if it works for you. If it does, I'll > probably commit it or something close to it. > > Also -- please CC your mail to me, and don't send it just to the list. > You may get a faster response that way. > > Ken > -- > Kenneth Merry > ken@plutotech.com > > ------------------------------------------------------------------------ > > Name: scsi_da.no_6_byte.120198 > scsi_da.no_6_byte.120198 Type: Plain Text (text/plain) > Encoding: 7bit > Description: scsi_da.no_6_byte.120198 yup that applies and works good. Thanks for the help! And no more quantums for me, I've had my share of goofyness. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 2 19:53:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA21096 for freebsd-scsi-outgoing; Wed, 2 Dec 1998 19:53:35 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA21091 for ; Wed, 2 Dec 1998 19:53:33 -0800 (PST) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id VAA20941 for ; Wed, 2 Dec 1998 21:53:15 -0600 (CST) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma020903; Wed, 2 Dec 98 21:52:48 -0600 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with ESMTP id VAA27809 for ; Wed, 2 Dec 1998 21:52:47 -0600 (CST) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Wed, 2 Dec 1998 21:52:47 -0600 (CST) From: Kyle Mestery To: freebsd-scsi@FreeBSD.ORG Subject: Still errors stopping audio CDs in current Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Greetings, I am still seeing the same problems trying to stop audio CDs in my SCSI CD-ROM drive. I am now running a 3.0 kernel from about 6:30AM CST. The machine is a dual Pentium machine, with a Buslogic BT-946c SCSI controller, one 1GB HP SCSI-2 disk, and a Sony 4x SCSI CD-ROM attached. It also has an IDE disk in it. Here is dmesg info for the controller, disk, and cd-rom: bt0: rev 0x00 int a irq 16 on pci0.20.0 bt0: BT-946C FW Rev. 4.25J Narrow SCSI Host Adapter, SCSI ID 7, 100 CCBs da0 at bt0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled da0: 1003MB (2054864 512 byte sectors: 64H 32S/T 1003C) cd0 at bt0 bus 0 target 4 lun 0 cd0: Removable CD-ROM SCSI2 device cd0: 5.0MB/s transfers (5.0MHz, offset 15) cd0: cd present [316932 x 2048 byte records] I have now verified the problem persists with cdcontrol and cdplay from the ports collection. What happens is, when the drive is issued a stop command from one of those programs, the program hangs in cbwait. Looking into the cdcontrol code, when stop is issued, a CDIOCSTOP is sent to the drive. Is that correct? Also, cdplay managed to get this out through syslog, which cdcontrol had never previously done: (cd0:bt0:0:4:0): PLAY AUDIO MSF. CDB: 47 0 0 0 0 0 42 f 19 0 (cd0:bt0:0:4:0): ILLEGAL REQUEST asc:24,0 (cd0:bt0:0:4:0): Invalid field in CDB I tried issuing some camcontrol commands to the drive, but they all return the above illegal request. I never had these problems with rev 1.7 of /sys/cam/scsi/scsi_cd.c. Is there anything else I can do to debug this problem? -- Kyle Mestery StorageTek's Storage Networking Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 2 20:58:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA28195 for freebsd-scsi-outgoing; Wed, 2 Dec 1998 20:58:32 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA28189 for ; Wed, 2 Dec 1998 20:58:30 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id VAA00595; Wed, 2 Dec 1998 21:58:12 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812030458.VAA00595@panzer.plutotech.com> Subject: Re: Still errors stopping audio CDs in current In-Reply-To: from Kyle Mestery at "Dec 2, 98 09:52:47 pm" To: mestery@winternet.com (Kyle Mestery) Date: Wed, 2 Dec 1998 21:58:12 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kyle Mestery wrote... > > Greetings, > > I am still seeing the same problems trying to stop audio CDs in my SCSI CD-ROM > drive. I am now running a 3.0 kernel from about 6:30AM CST. The machine is a > dual Pentium machine, with a Buslogic BT-946c SCSI controller, one 1GB HP > SCSI-2 disk, and a Sony 4x SCSI CD-ROM attached. It also has an IDE disk in > it. Here is dmesg info for the controller, disk, and cd-rom: > > bt0: rev 0x00 int a irq 16 on pci0.20.0 > bt0: BT-946C FW Rev. 4.25J Narrow SCSI Host Adapter, SCSI ID 7, 100 CCBs > da0 at bt0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI2 device > da0: 10.0MB/s transfers (10.0MHz, offset 8), Tagged Queueing Enabled > da0: 1003MB (2054864 512 byte sectors: 64H 32S/T 1003C) > cd0 at bt0 bus 0 target 4 lun 0 > cd0: Removable CD-ROM SCSI2 device > cd0: 5.0MB/s transfers (5.0MHz, offset 15) > cd0: cd present [316932 x 2048 byte records] > > I have now verified the problem persists with cdcontrol and cdplay from the > ports collection. What happens is, when the drive is issued a stop command > from one of those programs, the program hangs in cbwait. Looking into the > cdcontrol code, when stop is issued, a CDIOCSTOP is sent to the drive. Is that > correct? That's correct. > Also, cdplay managed to get this out through syslog, which cdcontrol > had never previously done: > > (cd0:bt0:0:4:0): PLAY AUDIO MSF. CDB: 47 0 0 0 0 0 42 f 19 0 > (cd0:bt0:0:4:0): ILLEGAL REQUEST asc:24,0 > (cd0:bt0:0:4:0): Invalid field in CDB > > I tried issuing some camcontrol commands to the drive, but they all return > the above illegal request. I never had these problems with rev 1.7 of > /sys/cam/scsi/scsi_cd.c. Is there anything else I can do to debug this > problem? That's rather odd. Could you show me some of the errors? For instance, what happens when you type: camcontrol inquiry -v -n cd -u 0 or camcontrol tur -v -n cd -u 0 One question I have is which command is hanging. It could be that one of the commands in the CD driver's open routine is hanging. Try enabling CDB debugging: - put 'options CAMDEBUG' in your kernel - before you try playing anything on your CDROM drive, use the following camcontrol command to enable debugging for that device: camcontrol debug -c 0:4:0 (this assumes that your BusLogic controller is the only controller in the system. If not, you'll need to type 'camcontrol devlist' to get the proper bus number.) You should get a kernel printf for each SCSI command that is issued. I'd also like to see the exact sequence of commands you give to cdcontrol. cut-and-paste will be fine. Do you have the same trouble when you use xmcd? If you don't have motif, you can download a precompiled version of xmcd 2.3 from the 3.0 packages tree. You can also download a precompiled version of xmcd 2.4 from: http://metalab.unc.edu/tkan/xmcd/downloads.html It also includes a command line cd playing utility, cda, that is quite nice. I'm not sure why revision 1.7 wouldn't cause any problems, but revision 1.9 would. Revision 1.8 mainly concerned probe code fixes, which wouldn't affect you. Revision 1.9 moved some spl() protection around in the open routine. But it wouldn't have caused the driver to get hung in the cbwait state. The 'cbwait' state indicates that the kernel is waiting for a transaction to complete. So it almost sounds like the request isn't coming back. That's why I'd like to see *which* request isn't coming back. The debugging printf code will print out the SCSI CDB of the request before it is sent to the drive, so we'll be able to see just what is hanging. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Dec 2 21:26:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA00611 for freebsd-scsi-outgoing; Wed, 2 Dec 1998 21:26:13 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA00606 for ; Wed, 2 Dec 1998 21:26:11 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id WAA58219; Wed, 2 Dec 1998 22:18:34 -0700 (MST) Date: Wed, 2 Dec 1998 22:18:34 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199812030518.WAA58219@narnia.plutotech.com> To: Kyle Mestery cc: scsi@FreeBSD.ORG Subject: Re: Still errors stopping audio CDs in current X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > > Greetings, > > I am still seeing the same problems trying to stop audio CDs in my SCSI CD-ROM > drive. I am now running a 3.0 kernel from about 6:30AM CST. The machine is a > dual Pentium machine, with a Buslogic BT-946c SCSI controller, one 1GB HP > SCSI-2 disk, and a Sony 4x SCSI CD-ROM attached. It also has an IDE disk in > it. Here is dmesg info for the controller, disk, and cd-rom: I've been too swamped with 'real work' to really look into this, which is why I haven't commented so far. Sorry about that. I took a quick look at the cd ioctl code and did find at least one potential problem. When performing a CDIOEJECT, an allow media removal operation is not performed before issuing the stop unit command. This may confuse the device. This doesn't explain why we would hang waiting to get a CCB though. That indicates a resource tracking bug somewhere in the driver most likely triggered by something cdcontrol or cdplay is doing before the eject. A ktrace of what these programs do would be useful. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 04:00:30 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA01807 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 04:00:30 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA01802 for ; Thu, 3 Dec 1998 04:00:28 -0800 (PST) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id GAA03106; Thu, 3 Dec 1998 06:00:10 -0600 (CST) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma003064; Thu, 3 Dec 98 05:59:54 -0600 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with ESMTP id FAA29442; Thu, 3 Dec 1998 05:59:52 -0600 (CST) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Thu, 3 Dec 1998 05:59:52 -0600 (CST) From: Kyle Mestery To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Still errors stopping audio CDs in current In-Reply-To: <199812030458.VAA00595@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, Here are some answers to some of the questions you posed. I am limited for time this morning (I have to go to work), but will answer the rest tonite. Thanks! On Wed, 2 Dec 1998, Kenneth D. Merry wrote: > > That's rather odd. Could you show me some of the errors? For instance, > what happens when you type: > > camcontrol inquiry -v -n cd -u 0 > su-2.00# camcontrol inquiry -v -n cd -u 0 Removable CD-ROM SCSI2 device (pass1:bt0:0:4:0): INQUIRY. CDB: 12 1 80 0 ff 0 (pass1:bt0:0:4:0): ILLEGAL REQUEST asc:24,0 (pass1:bt0:0:4:0): Invalid field in CDB Serial Number 5.0MB/s transfers (5.0MHz, offset 15) > or > > camcontrol tur -v -n cd -u 0 > su-2.00# camcontrol tur -v -n cd -u 0 Unit is not ready (pass1:bt0:0:4:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 (pass1:bt0:0:4:0): NOT READY asc:3a,0 (pass1:bt0:0:4:0): Medium not present > I'd also like to see the exact sequence of commands you give to cdcontrol. > cut-and-paste will be fine. > su-2.00# cdcontrol cdcontrol: no CD device name specified, defaulting to /dev/cd0c Compact Disc Control utility, version 2.0 Type `?' for command list cdcontrol> p 6 cdcontrol> stop It hangs at that point. Here is debugging info once I enabled debugging on the drive. It looks like the kernel is continually trying to send a STOP command to the drive: (cd0:bt0:0:4:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (cd0:bt0:0:4:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (cd0:bt0:0:4:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:bt0:0:4:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:bt0:0:4:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (cd0:bt0:0:4:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 (cd0:bt0:0:4:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 (cd0:bt0:0:4:0): READ TOC/PMA/ATIP {MMC Proposed}. CDB: 43 0 0 0 0 0 0 0 4 0 (cd0:bt0:0:4:0): READ TOC/PMA/ATIP {MMC Proposed}. CDB: 43 0 0 0 0 0 0 0 4 0 (cd0:bt0:0:4:0): READ TOC/PMA/ATIP {MMC Proposed}. CDB: 43 2 0 0 0 0 1 0 94 0 (cd0:bt0:0:4:0): READ TOC/PMA/ATIP {MMC Proposed}. CDB: 43 2 0 0 0 0 aa 0 c 0 (cd0:bt0:0:4:0): MODE SENSE(06). CDB: 1a 0 e 0 1c 0 (cd0:bt0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 1c 0 (cd0:bt0:0:4:0): PLAY AUDIO TRACK INDEX. CDB: 48 0 0 0 6 1 0 12 1 0 (cd0:bt0:0:4:0): STOP START UNIT. CDB: 1b 0 0 0 0 0 (cd0:bt0:0:4:0): STOP START UNIT. CDB: 1b 0 0 0 0 0 (cd0:bt0:0:4:0): STOP START UNIT. CDB: 1b 0 0 0 0 0 (cd0:bt0:0:4:0): STOP START UNIT. CDB: 1b 0 0 0 0 0 (cd0:bt0:0:4:0): STOP START UNIT. CDB: 1b 0 0 0 0 0 Those continue until I turn debugging off. > Do you have the same trouble when you use xmcd? If you don't have motif, > you can download a precompiled version of xmcd 2.3 from the 3.0 packages > tree. You can also download a precompiled version of xmcd 2.4 from: > > http://metalab.unc.edu/tkan/xmcd/downloads.html > > It also includes a command line cd playing utility, cda, that is quite > nice. > I'll try xmcd tonite after work, and see what happens. > I'm not sure why revision 1.7 wouldn't cause any problems, but revision > 1.9 would. Revision 1.8 mainly concerned probe code fixes, which wouldn't > affect you. Revision 1.9 moved some spl() protection around in the open > routine. But it wouldn't have caused the driver to get hung in the cbwait > state. > You're right, 1.7 didn't matter. I tried that last nite. The kernel that ran fine was from about the beginning of October, if that helps. > The 'cbwait' state indicates that the kernel is waiting for a transaction > to complete. So it almost sounds like the request isn't coming back. > That's why I'd like to see *which* request isn't coming back. The > debugging printf code will print out the SCSI CDB of the request before it > is sent to the drive, so we'll be able to see just what is hanging. > This would be consistent with the debugging messages it appears. So the device is never returning a command? I'll try xmcd tonite, let me know if you need more debugging info. Thanks! -- Kyle Mestery StorageTek's Storage Networking Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 06:34:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA13715 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 06:34:04 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA13708 for ; Thu, 3 Dec 1998 06:34:02 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id HAA59829; Thu, 3 Dec 1998 07:26:06 -0700 (MST) Date: Thu, 3 Dec 1998 07:26:06 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199812031426.HAA59829@narnia.plutotech.com> To: Kyle Mestery cc: scsi@FreeBSD.ORG, ken@plutotech.com Subject: Re: Still errors stopping audio CDs in current X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: >> camcontrol inquiry -v -n cd -u 0 >> > su-2.00# camcontrol inquiry -v -n cd -u 0 > Removable CD-ROM SCSI2 device > (pass1:bt0:0:4:0): INQUIRY. CDB: 12 1 80 0 ff 0 > (pass1:bt0:0:4:0): ILLEGAL REQUEST asc:24,0 > (pass1:bt0:0:4:0): Invalid field in CDB > Serial Number 5.0MB/s transfers (5.0MHz, offset 15) camcontrol shouldn't print the 'Serial Number' header if the device doesn't have one. > It hangs at that point. Here is debugging info once I enabled debugging on > the drive. It looks like the kernel is continually trying to send a STOP > command to the drive: > > (cd0:bt0:0:4:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 > (cd0:bt0:0:4:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 Bug #1: cdopen doesn't do an ALLOW MEDIA REMOVAL before returning an error if an open fails. Bug #2: We almost want to mark the media as potentially invalid if the user issues an ALLOW MEDIA REMOVAL ioctl so we don't get confused when I/O starts up again. This isn't a problem you are seeing... yet. > (cd0:bt0:0:4:0): PLAY AUDIO TRACK INDEX. CDB: 48 0 0 0 6 1 0 12 1 0 > (cd0:bt0:0:4:0): STOP START UNIT. CDB: 1b 0 0 0 0 0 > (cd0:bt0:0:4:0): STOP START UNIT. CDB: 1b 0 0 0 0 0 Hmm. Perhaps the drive is returning a unit attention condition each time we perform a stop? That might explain why the kernel is constantly retrying the command. It could also be that the client program is performing the retries because of an error returned by the ioctl. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 07:42:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA18667 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 07:42:54 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mushi.colo.neosoft.com (mushi.colo.neosoft.com [206.109.6.82]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id HAA18662 for ; Thu, 3 Dec 1998 07:42:52 -0800 (PST) (envelope-from peter@bonkers.taronga.com) Received: (qmail 4560 invoked from network); 3 Dec 1998 15:42:29 -0000 Received: from bonkers.neosoft.com (HELO bonkers.taronga.com) (206.109.2.48) by mushi.colo.neosoft.com with SMTP; 3 Dec 1998 15:42:29 -0000 Received: (from peter@localhost) by bonkers.taronga.com (8.9.1/8.9.1) id IAA01462 for scsi@freebsd.org; Thu, 3 Dec 1998 08:09:59 -0600 (CST) (envelope-from peter) From: Peter da Silva Message-Id: <199812031409.IAA01462@bonkers.taronga.com> Subject: IBM DCHS woes To: scsi@FreeBSD.ORG Date: Thu, 3 Dec 1998 08:09:58 -0600 (CST) Reply-To: nick@Taronga.COM X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (forwarded from a bounce message for a local user) From: nick@Taronga.COM (Nick Danger) Subject: IBM DCHS woes Reply-To: nick@Taronga.COM I've got this oemed IBM DCHS 34550 that is being naughty. It refuses to operate reliably at synchronous transfers rates and does this regardless of what HBA or OS I'm running it off of. If I instruct the HBA to not negiotate for synchronous transfers it runs flawlessly (albeit inefficiently). I'm under the impression it's a firmware problem. I'm only concerned with it being functional on a FreeBSD-current machine (-current as of late last week). These logs are from earlier but the error is the same. Drive is reported as: Nov 19 21:00:56 engylion /kernel: da1 at ahc0 bus 0 target 2 lun 0 Nov 19 21:00:56 engylion /kernel: da1: Fixed Direct Acce ss SCSI2 device Nov 19 21:00:56 engylion /kernel: da1: 40.0MB/s transfers (20.0MHz, offset 8, 16 bit), Tagged Queueing Enabled Nov 19 21:00:56 engylion /kernel: da1: 4340MB (8888543 512 byte sectors: 64H 32S /T 4340C) Errors begin about five minutes later as I start doing a bunch of simultaneous copies to it: /kernel: (da1:ahc0:0:2:0): SCB 0x5 - timed out while id le, LASTPHASE == 0x1, SCSISIGI == 0x0 /kernel: SEQADDR == 0x8 /kernel: SSTAT1 == 0xa /kernel: (da1:ahc0:0:2:0): Queuing a BDR SCB /kernel: (da1:ahc0:0:2:0): Bus Device Reset Message Sent /kernel: (da1:ahc0:0:2:0): no longer in timeout, status = 34b /kernel: ahc0: Bus Device Reset on A:2. 16 SCBs aborted /kernel: (da1:ahc0:0:2:0): SCB 0xc - timed out while id le, LASTPHASE == 0x1, SCSISIGI == 0x0 /kernel: SSTAT1 == 0xa /kernel: (da1:ahc0:0:2:0): Queuing a BDR SCB /kernel: (da1:ahc0:0:2:0): Bus Device Reset Message Sent /kernel: (da1:ahc0:0:2:0): no longer in timeout, status = 34b /kernel: ahc0: Bus Device Reset on A:2. 15 SCBs aborted /kernel: (da1:ahc0:0:2:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCS ISIGI == 0x0 /kernel: SEQADDR == 0xb /kernel: SSTAT1 == 0xa /kernel: (da1:ahc0:0:2:0): Queuing a BDR SCB /kernel: (da1:ahc0:0:2:0): Bus Device Reset Message Sent /kernel: (da1:ahc0:0:2:0): no longer in timeout, status = 34b /kernel: ahc0: Bus Device Reset on A:2. 14 SCBs aborted /kernel: (da1:ahc0:0:2:0): READ(06). CDB: 8 d ca f0 80 0 /kernel: (da1:ahc0:0:2:0): ABORTED COMMAND asc:1b,0 /kernel: (da1:ahc0:0:2:0): Synchronous data transfer error /kernel: (da1:ahc0:0:2:0): READ(06). CDB: 8 d ca f0 60 0 /kernel: (da1:ahc0:0:2:0): ABORTED COMMAND asc:1b,0 /kernel: (da1:ahc0:0:2:0): Synchronous data transfer error /kernel: (da1:ahc0:0:2:0): SCB 0xd - timed out while idle, LASTPHASE == 0x1, SCS ISIGI == 0x0 /kernel: SEQADDR == 0x8 /kernel: SSTAT1 == 0xa /kernel: (da1:ahc0:0:2:0): Queuing a BDR SCB /kernel: (da1:ahc0:0:2:0): Bus Device Reset Message Sent /kernel: (da1:ahc0:0:2:0): no longer in timeout, status = 34b /kernel: ahc0: Bus Device Reset on A:2. 13 SCBs aborted I've got oodles and oodles of logs of this. Would someone more SCSI-clueful than I mind telling me if this is something I can try to work around with a quirk entry or if I should just write it off? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 10:19:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA03872 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 10:19:58 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA03866 for ; Thu, 3 Dec 1998 10:19:54 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id LAA03245; Thu, 3 Dec 1998 11:19:38 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812031819.LAA03245@panzer.plutotech.com> Subject: Re: Still errors stopping audio CDs in current In-Reply-To: from Kyle Mestery at "Dec 3, 98 05:59:52 am" To: mestery@winternet.com (Kyle Mestery) Date: Thu, 3 Dec 1998 11:19:38 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kyle Mestery wrote... > Hi, > Here are some answers to some of the questions you posed. I am limited for > time this morning (I have to go to work), but will answer the rest tonite. > Thanks! > > On Wed, 2 Dec 1998, Kenneth D. Merry wrote: > > > > > That's rather odd. Could you show me some of the errors? For instance, > > what happens when you type: > > > > camcontrol inquiry -v -n cd -u 0 > > > su-2.00# camcontrol inquiry -v -n cd -u 0 > Removable CD-ROM SCSI2 device > (pass1:bt0:0:4:0): INQUIRY. CDB: 12 1 80 0 ff 0 > (pass1:bt0:0:4:0): ILLEGAL REQUEST asc:24,0 > (pass1:bt0:0:4:0): Invalid field in CDB > Serial Number 5.0MB/s transfers (5.0MHz, offset 15) That's a normal error. Your CDROM drive doesn't support the serial number inquiry. There's a bug in camcontrol that I haven't bothered to fix, though -- it prints out "Serial Number" even when the serial number request failed. > > or > > > > camcontrol tur -v -n cd -u 0 > > > su-2.00# camcontrol tur -v -n cd -u 0 > Unit is not ready > (pass1:bt0:0:4:0): TEST UNIT READY. CDB: 0 0 0 0 0 0 > (pass1:bt0:0:4:0): NOT READY asc:3a,0 > (pass1:bt0:0:4:0): Medium not present Looks fine to me. You don't have a CD in the drive. What happens when you have a CD in the drive? > > I'd also like to see the exact sequence of commands you give to cdcontrol. > > cut-and-paste will be fine. > > > su-2.00# cdcontrol > cdcontrol: no CD device name specified, defaulting to /dev/cd0c > Compact Disc Control utility, version 2.0 > Type `?' for command list > > cdcontrol> p 6 > cdcontrol> stop > > It hangs at that point. Here is debugging info once I enabled debugging on > the drive. It looks like the kernel is continually trying to send a STOP > command to the drive: > > (cd0:bt0:0:4:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 > (cd0:bt0:0:4:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 > (cd0:bt0:0:4:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (cd0:bt0:0:4:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (cd0:bt0:0:4:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 > (cd0:bt0:0:4:0): PREVENT ALLOW MEDIUM REMOVAL. CDB: 1e 0 0 0 1 0 > (cd0:bt0:0:4:0): READ CD RECORDED CAPACITY. CDB: 25 0 0 0 0 0 0 0 0 0 > (cd0:bt0:0:4:0): READ TOC/PMA/ATIP {MMC Proposed}. CDB: 43 0 0 0 0 0 0 0 4 0 > (cd0:bt0:0:4:0): READ TOC/PMA/ATIP {MMC Proposed}. CDB: 43 0 0 0 0 0 0 0 4 0 > (cd0:bt0:0:4:0): READ TOC/PMA/ATIP {MMC Proposed}. CDB: 43 2 0 0 0 0 1 0 94 0 > (cd0:bt0:0:4:0): READ TOC/PMA/ATIP {MMC Proposed}. CDB: 43 2 0 0 0 0 aa 0 c 0 > (cd0:bt0:0:4:0): MODE SENSE(06). CDB: 1a 0 e 0 1c 0 > (cd0:bt0:0:4:0): MODE SELECT(06). CDB: 15 10 0 0 1c 0 > (cd0:bt0:0:4:0): PLAY AUDIO TRACK INDEX. CDB: 48 0 0 0 6 1 0 12 1 0 > (cd0:bt0:0:4:0): STOP START UNIT. CDB: 1b 0 0 0 0 0 > (cd0:bt0:0:4:0): STOP START UNIT. CDB: 1b 0 0 0 0 0 > (cd0:bt0:0:4:0): STOP START UNIT. CDB: 1b 0 0 0 0 0 > (cd0:bt0:0:4:0): STOP START UNIT. CDB: 1b 0 0 0 0 0 > (cd0:bt0:0:4:0): STOP START UNIT. CDB: 1b 0 0 0 0 0 > > Those continue until I turn debugging off. That's quite interesting. Something is causing the stop unit command to be retried indefinitely. There are two possibilities: - There is an error returned by the drive that is retried indefinitely by the kernel error recovery code. - There is an error returned by the drive, but the kernel does not retry indefinitely. It returns an error to the client program, which retries indefinitely. > > Do you have the same trouble when you use xmcd? If you don't have motif, > > you can download a precompiled version of xmcd 2.3 from the 3.0 packages > > tree. You can also download a precompiled version of xmcd 2.4 from: > > > > http://metalab.unc.edu/tkan/xmcd/downloads.html > > > > It also includes a command line cd playing utility, cda, that is quite > > nice. > > > I'll try xmcd tonite after work, and see what happens. It may work better than the CD driver + cdcontrol. The reason it may work better is because it uses SCSI passthrough, and does some things in vendor-specific ways. > > I'm not sure why revision 1.7 wouldn't cause any problems, but revision > > 1.9 would. Revision 1.8 mainly concerned probe code fixes, which wouldn't > > affect you. Revision 1.9 moved some spl() protection around in the open > > routine. But it wouldn't have caused the driver to get hung in the cbwait > > state. > > > You're right, 1.7 didn't matter. I tried that last nite. The kernel that ran > fine was from about the beginning of October, if that helps. Hmm. I'd have to look back and see what has changed since then. > > The 'cbwait' state indicates that the kernel is waiting for a transaction > > to complete. So it almost sounds like the request isn't coming back. > > That's why I'd like to see *which* request isn't coming back. The > > debugging printf code will print out the SCSI CDB of the request before it > > is sent to the drive, so we'll be able to see just what is hanging. > > > This would be consistent with the debugging messages it appears. So the > device is never returning a command? I'll try xmcd tonite, let me know if > you need more debugging info. Thanks! Well, it looks like that the command is coming back, but it's getting retried infinitely for some reason. Here's something to try: - go into cdcontrol, and play a track - quit cdcontrol without stopping the CD - type something like this: camcontrol stop -v -n cd -u 0 That should do the same thing as the CD driver's stop ioctl, but the command will not be retried it it fails. The -v switch will cause camcontrol to print out SCSI sense information if the command fails. Hopefully that'll show us what the error is, and we can figure out whether the kernel would retry it indefinitely. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 12:30:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA17672 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 12:30:25 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA17667 for ; Thu, 3 Dec 1998 12:30:23 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id NAA03868; Thu, 3 Dec 1998 13:29:17 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812032029.NAA03868@panzer.plutotech.com> Subject: Re: IBM DCHS woes In-Reply-To: <199812031409.IAA01462@bonkers.taronga.com> from Peter da Silva at "Dec 3, 98 08:09:58 am" To: nick@Taronga.COM Date: Thu, 3 Dec 1998 13:29:17 -0700 (MST) Cc: scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Peter da Silva wrote... > (forwarded from a bounce message for a local user) > > From: nick@Taronga.COM (Nick Danger) > Subject: IBM DCHS woes > Reply-To: nick@Taronga.COM > > > I've got this oemed IBM DCHS 34550 that is being naughty. It refuses > to operate reliably at synchronous transfers rates and does this > regardless of what HBA or OS I'm running it off of. If I instruct > the HBA to not negiotate for synchronous transfers it runs flawlessly > (albeit inefficiently). I'm under the impression it's a firmware > problem. That's probably a good guess. You may want to contact IBM and see if they have any newer firmware for the drive in question. If it won't work with any HBA or OS you've tried, I'm not surprised at all that it doesn't work with FreeBSD. > I'm only concerned with it being functional on a FreeBSD-current > machine (-current as of late last week). These logs are from earlier > but the error is the same. > > > Drive is reported as: > > Nov 19 21:00:56 engylion /kernel: da1 at ahc0 bus 0 target 2 lun 0 > Nov 19 21:00:56 engylion /kernel: da1: Fixed Direct Acce Hmm. An SGI version of the drive. It could be they've got some sort of funky firmware in the drive. > Errors begin about five minutes later as I start doing a bunch of simultaneous > copies to it: > > > /kernel: (da1:ahc0:0:2:0): SCB 0x5 - timed out while id > le, LASTPHASE == 0x1, SCSISIGI == 0x0 > /kernel: SEQADDR == 0x8 > /kernel: SSTAT1 == 0xa > /kernel: (da1:ahc0:0:2:0): Queuing a BDR SCB > /kernel: (da1:ahc0:0:2:0): Bus Device Reset Message Sent > /kernel: (da1:ahc0:0:2:0): no longer in timeout, status = 34b > /kernel: ahc0: Bus Device Reset on A:2. 16 SCBs aborted > /kernel: (da1:ahc0:0:2:0): SCB 0xc - timed out while id le, LASTPHASE > == 0x1, SCSISIGI == 0x0 > /kernel: SSTAT1 == 0xa > /kernel: (da1:ahc0:0:2:0): Queuing a BDR SCB > /kernel: (da1:ahc0:0:2:0): Bus Device Reset Message Sent > /kernel: (da1:ahc0:0:2:0): no longer in timeout, status = 34b > /kernel: ahc0: Bus Device Reset on A:2. 15 SCBs aborted What this means is that the drive went "out to lunch", and we had to whap it over the head with a BDR to get it to wake up. > /kernel: (da1:ahc0:0:2:0): SCB 0x6 - timed out while idle, LASTPHASE == 0x1, SCS > ISIGI == 0x0 > /kernel: SEQADDR == 0xb > /kernel: SSTAT1 == 0xa > /kernel: (da1:ahc0:0:2:0): Queuing a BDR SCB > /kernel: (da1:ahc0:0:2:0): Bus Device Reset Message Sent > /kernel: (da1:ahc0:0:2:0): no longer in timeout, status = 34b > /kernel: ahc0: Bus Device Reset on A:2. 14 SCBs aborted > /kernel: (da1:ahc0:0:2:0): READ(06). CDB: 8 d ca f0 80 0 > /kernel: (da1:ahc0:0:2:0): ABORTED COMMAND asc:1b,0 > /kernel: (da1:ahc0:0:2:0): Synchronous data transfer error > /kernel: (da1:ahc0:0:2:0): READ(06). CDB: 8 d ca f0 60 0 > /kernel: (da1:ahc0:0:2:0): ABORTED COMMAND asc:1b,0 > /kernel: (da1:ahc0:0:2:0): Synchronous data transfer error Hmm. The drive is reporting transfer errors. > Would someone more SCSI-clueful than I mind telling me if this is > something I can try to work around with a quirk entry or if I should > just write it off? I don't think you're going to work around it with a quirk entry. It could be that the drive is messed up and is negotiating at a faster rate than it can actually handle. The "Synchronous data transfer error" above, and the fact that it works fine in async mode indicate that it may be a negotiation problem. Go into the Adaptec bios and try setting the transfer rate to something low (like 5MHz). If the drive works at that speed, gradually increase the speed until it breaks. You may be able to find a synchronous speed lower than 20MHz that it will work at. You'll probably still want to ask IBM about new firmware, though. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 14:51:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08181 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 14:51:23 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08176 for ; Thu, 3 Dec 1998 14:51:20 -0800 (PST) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id QAA20092; Thu, 3 Dec 1998 16:50:56 -0600 (CST) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma020007; Thu, 3 Dec 98 16:50:44 -0600 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with ESMTP id QAA04749; Thu, 3 Dec 1998 16:50:39 -0600 (CST) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Thu, 3 Dec 1998 16:50:39 -0600 (CST) From: Kyle Mestery To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Still errors stopping audio CDs in current In-Reply-To: <199812031819.LAA03245@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 3 Dec 1998, Kenneth D. Merry wrote: > Kyle Mestery wrote... > > On Wed, 2 Dec 1998, Kenneth D. Merry wrote: > Looks fine to me. You don't have a CD in the drive. What happens when you > have a CD in the drive? > hope.winternet.com$ sudo camcontrol tur -v -n cd -u 0 Unit is ready Looks like that completes okay. > That's quite interesting. Something is causing the stop unit command to be > retried indefinitely. There are two possibilities: > > - There is an error returned by the drive that is retried indefinitely by > the kernel error recovery code. > > - There is an error returned by the drive, but the kernel does not retry > indefinitely. It returns an error to the client program, which retries > indefinitely. > It looks like it's the program doing this, because if I run cdcontrol, play a song, exit it without stopping, then stop the cdrom using camcontrol, it stops fine, and prints this error message: hope.winternet.com$ cdcontrol cdcontrol: no CD device name specified, defaulting to /dev/cd0c Compact Disc Control utility, version 2.0 Type `?' for command list cdcontrol> p 6 cdcontrol> ^C hope.winternet.com$ sudo camcontrol stop -v -n cd -u 0 Error received from stop unit command (pass1:bt0:0:4:0): STOP START UNIT. CDB: 1b 0 0 0 0 0 (pass1:bt0:0:4:0): error code 0 hope.winternet.com$ > It may work better than the CD driver + cdcontrol. The reason it may work > better is because it uses SCSI passthrough, and does some things in > vendor-specific ways. > Still downloading xmcd to try it. Looks like I need an elf X11, which I am also doing as we speak.:) > Well, it looks like that the command is coming back, but it's getting > retried infinitely for some reason. > > Here's something to try: > > - go into cdcontrol, and play a track > - quit cdcontrol without stopping the CD > - type something like this: > > camcontrol stop -v -n cd -u 0 > > That should do the same thing as the CD driver's stop ioctl, but the > command will not be retried it it fails. The -v switch will cause > camcontrol to print out SCSI sense information if the command fails. > > Hopefully that'll show us what the error is, and we can figure out whether > the kernel would retry it indefinitely. > See above, it looks like it's the program that isn't handling the error returned, correct? I will try xmcd as soon as XFree builds for me, and xmcd is installed. Until then, I can just use camcontrol to stop the drive, as it lets me get by. Thanks! -- Kyle Mestery StorageTek's Storage Networking Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 14:53:44 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA08453 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 14:53:44 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA08435 for ; Thu, 3 Dec 1998 14:53:38 -0800 (PST) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id QAA20604; Thu, 3 Dec 1998 16:53:17 -0600 (CST) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma020568; Thu, 3 Dec 98 16:53:03 -0600 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with ESMTP id QAA04754; Thu, 3 Dec 1998 16:53:02 -0600 (CST) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Thu, 3 Dec 1998 16:53:02 -0600 (CST) From: Kyle Mestery To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG Subject: Re: Still errors stopping audio CDs in current In-Reply-To: <199812030518.WAA58219@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 2 Dec 1998, Justin T. Gibbs wrote: > I've been too swamped with 'real work' to really look into this, which is > why I haven't commented so far. Sorry about that. > No problem, totally understandable. I just thought I'd keep trying new kernels and new ways to test it until something happened. > I took a quick look at the cd ioctl code and did find at least one > potential problem. When performing a CDIOEJECT, an allow media removal > operation is not performed before issuing the stop unit command. This > may confuse the device. This doesn't explain why we would hang waiting > to get a CCB though. That indicates a resource tracking bug somewhere > in the driver most likely triggered by something cdcontrol or cdplay is > doing before the eject. A ktrace of what these programs do would be > useful. > If you've seen the stuff I've told Ken, is a ktrace still necessary at this point? If so, I can attempt to do that (never done it before). It looks to me at least that cdcontrol isn't handling the error return from the IOCTL. I'm not sure why the drive is returning an error at this point. -- Kyle Mestery StorageTek's Storage Networking Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 15:18:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA10947 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 15:18:16 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA10933 for ; Thu, 3 Dec 1998 15:18:13 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA04738; Thu, 3 Dec 1998 16:17:56 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812032317.QAA04738@panzer.plutotech.com> Subject: Re: Still errors stopping audio CDs in current In-Reply-To: from Kyle Mestery at "Dec 3, 98 04:50:39 pm" To: mestery@winternet.com (Kyle Mestery) Date: Thu, 3 Dec 1998 16:17:55 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: multipart/mixed; boundary=ELM912727075-4685-0_ Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --ELM912727075-4685-0_ Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Kyle Mestery wrote... > On Thu, 3 Dec 1998, Kenneth D. Merry wrote: > > Kyle Mestery wrote... > > > On Wed, 2 Dec 1998, Kenneth D. Merry wrote: > > > Looks fine to me. You don't have a CD in the drive. What happens when you > > have a CD in the drive? > > > hope.winternet.com$ sudo camcontrol tur -v -n cd -u 0 > Unit is ready > > Looks like that completes okay. Yep. > > That's quite interesting. Something is causing the stop unit command to be > > retried indefinitely. There are two possibilities: > > > > - There is an error returned by the drive that is retried indefinitely by > > the kernel error recovery code. > > > > - There is an error returned by the drive, but the kernel does not retry > > indefinitely. It returns an error to the client program, which retries > > indefinitely. > > > It looks like it's the program doing this, because if I run cdcontrol, play > a song, exit it without stopping, then stop the cdrom using camcontrol, it > stops fine, and prints this error message: > > hope.winternet.com$ cdcontrol > cdcontrol: no CD device name specified, defaulting to /dev/cd0c > Compact Disc Control utility, version 2.0 > Type `?' for command list > > cdcontrol> p 6 > cdcontrol> ^C > hope.winternet.com$ sudo camcontrol stop -v -n cd -u 0 > Error received from stop unit command > (pass1:bt0:0:4:0): STOP START UNIT. CDB: 1b 0 0 0 0 0 > (pass1:bt0:0:4:0): error code 0 > hope.winternet.com$ Heh. Well, it isn't what you think. In this case, the kernel is retrying the command over and over again. If I had to guess, I'd say that the drive is returning busy status. In that case, we wouldn't get any sense information. I've attached a patch for camcontrol.c. Can you try the above stop command using this patch? > > It may work better than the CD driver + cdcontrol. The reason it may work > > better is because it uses SCSI passthrough, and does some things in > > vendor-specific ways. > > > Still downloading xmcd to try it. Looks like I need an elf X11, which I am > also doing as we speak.:) Ahh. Well, I could have probably given you an a.out version of it, but I guess you need to upgrade to ELF sometime or another. > > That should do the same thing as the CD driver's stop ioctl, but the > > command will not be retried it it fails. The -v switch will cause > > camcontrol to print out SCSI sense information if the command fails. > > > > Hopefully that'll show us what the error is, and we can figure out whether > > the kernel would retry it indefinitely. > > > See above, it looks like it's the program that isn't handling the error > returned, correct? I will try xmcd as soon as XFree builds for me, and xmcd > is installed. Until then, I can just use camcontrol to stop the drive, as it > lets me get by. Thanks! Good deal. And, as I said above, the problem is that the kernel is retrying the command indefinitely. The patch to camcontrol that I've attached will tell us exactly what error is returned. Once I know that, we can try to decide what to do. Ken -- Kenneth Merry ken@plutotech.com --ELM912727075-4685-0_ Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: attachment; filename=camcontrol.c.startstop.120398 Content-Description: camcontrol.c.startstop.120398 Content-Transfer-Encoding: 7bit ==== //depot/cam/sbin/camcontrol/camcontrol.c#29 - /usr/home/ken/perforce/cam/sbin/camcontrol/camcontrol.c ==== *** /tmp/tmp.7426.0 Thu Dec 3 16:11:59 1998 --- /usr/home/ken/perforce/cam/sbin/camcontrol/camcontrol.c Thu Dec 3 16:10:58 1998 *************** *** 505,524 **** } else { error = 1; ! if (startstop) ! fprintf(stdout, ! "Error received from start unit command\n"); ! else ! fprintf(stdout, ! "Error received from stop unit command\n"); if (arglist & CAM_ARG_VERBOSE) { ! if ((ccb->ccb_h.status & CAM_STATUS_MASK) == CAM_SCSI_STATUS_ERROR) scsi_sense_print(device, &ccb->csio, stderr); else ! fprintf(stderr, "CAM status is %#x\n", ! ccb->ccb_h.status); } } --- 505,523 ---- } else { error = 1; ! fprintf(stdout, ! "Error received from %s unit command\n", ! startstop ? "start" : "stop"); if (arglist & CAM_ARG_VERBOSE) { ! if (((ccb->ccb_h.status & CAM_STATUS_MASK) == CAM_SCSI_STATUS_ERROR) + && (ccb->csio.scsi_status == SCSI_STATUS_CHECK_COND)) scsi_sense_print(device, &ccb->csio, stderr); else ! fprintf(stderr, "CAM status is %#x, SCSI " ! "status is %#x\n", ccb->ccb_h.status, ! ccb->csio.scsi_status); } } --ELM912727075-4685-0_-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 15:23:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA11349 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 15:23:19 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA11344 for ; Thu, 3 Dec 1998 15:23:16 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id QAA04772; Thu, 3 Dec 1998 16:22:59 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812032322.QAA04772@panzer.plutotech.com> Subject: Re: Still errors stopping audio CDs in current In-Reply-To: from Kyle Mestery at "Dec 3, 98 04:53:02 pm" To: mestery@winternet.com (Kyle Mestery) Date: Thu, 3 Dec 1998 16:22:58 -0700 (MST) Cc: scsi@FreeBSD.ORG, gibbs@pluto.plutotech.com X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kyle Mestery wrote... > On Wed, 2 Dec 1998, Justin T. Gibbs wrote: > > > I've been too swamped with 'real work' to really look into this, which is > > why I haven't commented so far. Sorry about that. > > > No problem, totally understandable. I just thought I'd keep trying new kernels > and new ways to test it until something happened. > > > I took a quick look at the cd ioctl code and did find at least one > > potential problem. When performing a CDIOEJECT, an allow media removal > > operation is not performed before issuing the stop unit command. This > > may confuse the device. This doesn't explain why we would hang waiting > > to get a CCB though. That indicates a resource tracking bug somewhere > > in the driver most likely triggered by something cdcontrol or cdplay is > > doing before the eject. A ktrace of what these programs do would be > > useful. > > > If you've seen the stuff I've told Ken, is a ktrace still necessary at this > point? If so, I can attempt to do that (never done it before). It looks to > me at least that cdcontrol isn't handling the error return from the IOCTL. > I'm not sure why the drive is returning an error at this point. ktrace isn't necessary. We're close to finding the problem. Justin confused the 'cbwait' state with the 'cgticb' state. The former means that we're waiting for a CCB to complete, and the latter means that we're waiting to get a CCB. If the cdcontrol program had been stuck in the 'cgticb' state, it would indicate a resource tracking problem of some sort. But, it was stuck in the 'cbwait' state, which is entirely different. And actually, it wasn't stuck, but rather kept entering that state over and over again. :) The problem appears to be that: - a SCSI status other than check condition is being returned - we retry indefinitely That only happens for "busy" and "queue full", and since this isn't a tagged queueing drive, I'd guess that the former is happening. Once you send me the camcontrol output from the patch I sent you in my previous message, we'll know for sure. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 16:33:41 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23078 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 16:33:41 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23052 for ; Thu, 3 Dec 1998 16:33:32 -0800 (PST) (envelope-from gibbs@plutotech.com) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.9.1/8.9.1) with ESMTP id RAA17160; Thu, 3 Dec 1998 17:33:13 -0700 (MST) (envelope-from gibbs@plutotech.com) Message-Id: <199812040033.RAA17160@pluto.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: "Kenneth D. Merry" cc: mestery@winternet.com (Kyle Mestery), scsi@FreeBSD.ORG, gibbs@plutotech.com Subject: Re: Still errors stopping audio CDs in current In-reply-to: Your message of "Thu, 03 Dec 1998 16:22:58 MST." <199812032322.QAA04772@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Dec 1998 17:25:50 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> If you've seen the stuff I've told Ken, is a ktrace still necessary at this >> point? If so, I can attempt to do that (never done it before). It looks to >> me at least that cdcontrol isn't handling the error return from the IOCTL. >> I'm not sure why the drive is returning an error at this point. > >ktrace isn't necessary. We're close to finding the problem. Justin >confused the 'cbwait' state with the 'cgticb' state. The former means that >we're waiting for a CCB to complete, and the latter means that we're >waiting to get a CCB. The ktrace would tell us if it is the program retrying or the kernel. My guess is the kernel, but you never know. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 16:41:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA24452 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 16:41:10 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from mail.intercom.com ([207.51.55.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA24431 for ; Thu, 3 Dec 1998 16:41:08 -0800 (PST) (envelope-from jason@intercom.com) Received: from intercom.com (shagalicious.com [206.98.165.250]) by mail.intercom.com (8.9.0/8.9.0) with ESMTP id TAA13766 for ; Thu, 3 Dec 1998 19:40:46 -0500 (EST) Message-ID: <36672EEB.3BDA8063@intercom.com> Date: Thu, 03 Dec 1998 19:38:19 -0500 From: "Jason J. Horton" X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: 2.2.8-RELEASE and SCSI problem Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, I have been configuring a 2.2.8-RELEASE machine to take the place of my NetBSD 1.3.2 NFS server. The NetBSD machine has an Adaptec 2940-UW controller connected to a disk silo with an Adaptec AEC-4412BS SCSI to SCSI RAID canister with 8 9 gig drives attached, configured as RAID5 with hot spare. To the 2940-UW, the "drive" looks like one large 53 gig disk. NetBSD has not been as stable as we had hoped, and I wanted to put the FreeBSD machine in its place. When I try to mount the array like so: mount /dev/sd0a /mntwhatever I get this error: sd0: Can't deal with 201 bytes logical blocks and obviously the mount doesn't happen. My questions: 1) why is this happening? 2) what are my options (can we tweak some code to get this functional, NetBSD can handle it, why can't we? Am I going to have to backup my array and format it? Can FreeBSD even handle SCSI drives this large?) 3) Are NetBSD filesystems compatible with FreeBSD(all sources report that it is)??? Any information would be greatly appreciated. I do not remember if I am subscribed to this list, so please CC: all responses to jason@intercom.com -J To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 16:50:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA25706 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 16:50:32 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA25701 for ; Thu, 3 Dec 1998 16:50:30 -0800 (PST) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id SAA08638; Thu, 3 Dec 1998 18:50:09 -0600 (CST) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma008615; Thu, 3 Dec 98 18:49:57 -0600 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with ESMTP id SAA07194; Thu, 3 Dec 1998 18:49:56 -0600 (CST) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Thu, 3 Dec 1998 18:49:56 -0600 (CST) From: Kyle Mestery To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Still errors stopping audio CDs in current In-Reply-To: <199812032317.QAA04738@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 3 Dec 1998, Kenneth D. Merry wrote: > Heh. Well, it isn't what you think. In this case, the kernel is retrying > the command over and over again. If I had to guess, I'd say that the drive > is returning busy status. In that case, we wouldn't get any sense > information. > > I've attached a patch for camcontrol.c. Can you try the above stop command > using this patch? > Sure, here is the sequence of commands again, and assosciated output: hope.winternet.com$ cdcontrol cdcontrol: no CD device name specified, defaulting to /dev/cd0c Compact Disc Control utility, version 2.0 Type `?' for command list cdcontrol> p 6 cdcontrol> ^C hope.winternet.com$ sudo camcontrol stop -v -n cd -u 0 Error received from stop unit command CAM status is 0x20c, SCSI status is 0x28 > Good deal. And, as I said above, the problem is that the kernel is > retrying the command indefinitely. The patch to camcontrol that I've > attached will tell us exactly what error is returned. Once I know that, we > can try to decide what to do. > Does that give you enough information to go by? Let me know if there is anything else you need from me to figure this one out. I decided to download XFree86 3.3.3 tomorrow, since at this time I am limited to a 28.8 modem connection.:) Thanks for all the help! -- Kyle Mestery StorageTek's Storage Networking Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 17:18:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA28795 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 17:18:36 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA28787 for ; Thu, 3 Dec 1998 17:18:32 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.1/8.8.5) id SAA05404; Thu, 3 Dec 1998 18:18:15 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199812040118.SAA05404@panzer.plutotech.com> Subject: Re: Still errors stopping audio CDs in current In-Reply-To: from Kyle Mestery at "Dec 3, 98 06:49:56 pm" To: mestery@winternet.com (Kyle Mestery) Date: Thu, 3 Dec 1998 18:18:15 -0700 (MST) Cc: freebsd-scsi@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Kyle Mestery wrote... > On Thu, 3 Dec 1998, Kenneth D. Merry wrote: > > > Heh. Well, it isn't what you think. In this case, the kernel is retrying > > the command over and over again. If I had to guess, I'd say that the drive > > is returning busy status. In that case, we wouldn't get any sense > > information. > > > > I've attached a patch for camcontrol.c. Can you try the above stop command > > using this patch? > > > > Sure, here is the sequence of commands again, and assosciated output: > hope.winternet.com$ cdcontrol > cdcontrol: no CD device name specified, defaulting to /dev/cd0c > Compact Disc Control utility, version 2.0 > Type `?' for command list > > cdcontrol> p 6 > cdcontrol> ^C > hope.winternet.com$ sudo camcontrol stop -v -n cd -u 0 > Error received from stop unit command > CAM status is 0x20c, SCSI status is 0x28 Now that is odd. 0x28 means "queue full". I'm not sure why a non-tagged queueing device would return that status! One question -- when you issue that command, does the CD stop? It is possible that there is a problem in the BusLogic driver somewhere. We may try to reproduce the problem here, if we can find a similar Sony CDROM drive. Justin may ask you to put some printfs in the BusLogic driver to see what we're getting back from the controller. > > Good deal. And, as I said above, the problem is that the kernel is > > retrying the command indefinitely. The patch to camcontrol that I've > > attached will tell us exactly what error is returned. Once I know that, we > > can try to decide what to do. > > > Does that give you enough information to go by? Let me know if there is > anything else you need from me to figure this one out. I decided to download > XFree86 3.3.3 tomorrow, since at this time I am limited to a 28.8 modem > connection.:) Thanks for all the help! That's enough information to go on right now. As far as I can tell, we're not doing anything wrong in terms of the commands we issue to the drive. So, it could be a driver bug, a controller firmware bug, or a drive firmware bug. It'll take a litle more investigation to narrow it down. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 17:50:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA02130 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 17:50:12 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from icicle.winternet.com (icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA02124 for ; Thu, 3 Dec 1998 17:50:10 -0800 (PST) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id TAA16927; Thu, 3 Dec 1998 19:49:52 -0600 (CST) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma016903; Thu, 3 Dec 98 19:49:27 -0600 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with ESMTP id TAA07614; Thu, 3 Dec 1998 19:49:26 -0600 (CST) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Thu, 3 Dec 1998 19:49:25 -0600 (CST) From: Kyle Mestery To: "Kenneth D. Merry" cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Still errors stopping audio CDs in current In-Reply-To: <199812040118.SAA05404@panzer.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 3 Dec 1998, Kenneth D. Merry wrote: > Kyle Mestery wrote... > > > cdcontrol> p 6 > > cdcontrol> ^C > > hope.winternet.com$ sudo camcontrol stop -v -n cd -u 0 > > Error received from stop unit command > > CAM status is 0x20c, SCSI status is 0x28 > > Now that is odd. 0x28 means "queue full". I'm not sure why a non-tagged > queueing device would return that status! > > One question -- when you issue that command, does the CD stop? > Yup, the drive stops playing at this point. > It is possible that there is a problem in the BusLogic driver somewhere. > We may try to reproduce the problem here, if we can find a similar Sony > CDROM drive. Justin may ask you to put some printfs in the BusLogic driver > to see what we're getting back from the controller. > No problem, I can do that. Just tell me where to put 'em, or email me some patches and I'll recompile and run the commands again. > As far as I can tell, we're not doing anything wrong in terms of the > commands we issue to the drive. So, it could be a driver bug, a controller > firmware bug, or a drive firmware bug. It'll take a litle more > investigation to narrow it down. > Okay, thanks Ken! I'll wait to see what Justin has to say at this point. I appreciate the help, thanks! -- Kyle Mestery StorageTek's Storage Networking Group To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 18:33:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA06075 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 18:33:35 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from root.com (root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA06064 for ; Thu, 3 Dec 1998 18:33:32 -0800 (PST) (envelope-from root@root.com) Received: from root.com (localhost [127.0.0.1]) by root.com (8.8.8/8.8.5) with ESMTP id SAA27849 for ; Thu, 3 Dec 1998 18:34:45 -0800 (PST) Message-Id: <199812040234.SAA27849@root.com> To: freebsd-scsi@FreeBSD.ORG Subject: scsi in 2.2.8 From: David Greenman Reply-To: dg@root.com Date: Thu, 03 Dec 1998 18:34:45 -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ------- Forwarded Message Return-Path: owner-freebsd-isp@FreeBSD.ORG Received: from hub.freebsd.org (hub.FreeBSD.ORG [204.216.27.18]) by root.com (8.8.8/8.8.5) with ESMTP id RAA27078 for ; Thu, 3 Dec 1998 17:18:02 -0800 (PST) Received: from localhost (daemon@localhost) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id QAA23623; Thu, 3 Dec 1998 16:35:48 -0800 (PST) (envelope-from owner-freebsd-isp) Received: by hub.freebsd.org (bulk_mailer v1.6); Thu, 3 Dec 1998 16:33:31 -0800 Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA23029 for freebsd-isp-outgoing; Thu, 3 Dec 1998 16:33:30 -0800 (PST) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from mail.intercom.com ([207.51.55.117]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA23004; Thu, 3 Dec 1998 16:33:25 -0800 (PST) (envelope-from jason@intercom.com) Received: from intercom.com (shagalicious.com [206.98.165.250]) by mail.intercom.com (8.9.0/8.9.0) with ESMTP id TAA11287; Thu, 3 Dec 1998 19:32:55 -0500 (EST) Message-ID: <36672D28.3D834BFB@intercom.com> Date: Thu, 03 Dec 1998 19:30:37 -0500 From: "Jason J. Horton" X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-release@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: 2.2.8-RELEASE and SCSI error Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-isp@FreeBSD.ORG X-Loop: FreeBSD.org Hello all, I have been configuring a 2.2.8-RELEASE machine to take the place of my NetBSD 1.3.2 NFS server. The NetBSD machine has an Adaptec 2940-UW controller connected to a disk silo with an Adaptec AEC-4412BS SCSI to SCSI RAID canister with 8 9 gig drives attached, configured as RAID5 with hot spare. To the 2940-UW, the "drive" looks like one large 53 gig disk. NetBSD has not been as stable as we had hoped, and I wanted to put the FreeBSD machine in its place. When I try to mount the array like so: mount /dev/sd0a /mntwhatever I get this error: sd0: Can't deal with 201 bytes logical blocks and obviously the mount doesn't happen. My questions: 1) why is this happening? 2) what are my options (can we tweak some code to get this functional, NetBSD can handle it, why can't we? Am I going to have to backup my array and format it? Can FreeBSD even handle SCSI drives this large?) 3) Are NetBSD filesystems compatible with FreeBSD(all sources report that it is)??? Any information would be greatly appreciated. -J To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message ------- End of Forwarded Message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 18:49:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA07789 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 18:49:20 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from n4hhe.ampr.org (tnt1-19.HiWAAY.net [208.147.147.19]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA07775 for ; Thu, 3 Dec 1998 18:49:12 -0800 (PST) (envelope-from dkelly@n4hhe.ampr.org) Received: from n4hhe.ampr.org (localhost.ampr.org [127.0.0.1]) by n4hhe.ampr.org (8.9.1/8.9.1) with ESMTP id UAA15745 for ; Thu, 3 Dec 1998 20:41:59 -0600 (CST) (envelope-from dkelly@n4hhe.ampr.org) Message-Id: <199812040241.UAA15745@n4hhe.ampr.org> X-Mailer: exmh version 2.0.2 2/24/98 To: scsi@FreeBSD.ORG From: David Kelly Subject: Re: IBM DCHS woes In-reply-to: Message from "Kenneth D. Merry" of "Thu, 03 Dec 1998 13:29:17 MST." <199812032029.NAA03868@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 03 Dec 1998 20:41:59 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Kenneth D. Merry" writes: > > Nov 19 21:00:56 engylion /kernel: da1 at ahc0 bus 0 target 2 lun 0 > > Nov 19 21:00:56 engylion /kernel: da1: Fixed Direct > Acce > > Hmm. An SGI version of the drive. It could be they've got some sort of > funky firmware in the drive. What I've seen of SGI OEM drives (mostly in SGI systems) is that you couldn't ask for better. The DCHS04Y is the standard 4G drive shipped in SGI O2 systems. IMHO there is more than a small chance this HD is sick. Its not often a premium priced SGI HD finds itself on a non-SGI system. If it is sick its possibly new enough the SGI system is still under warranty. If so, you could have a replacement the next day. BTDT. What would really be sweet is to get an SGI OEM firmware'd Archive/ Seagate DDS drive as those are the only DDS drives that can do digital audio over SCSI. They can play/record/copy DAT audio. But then there is the problem of lack of software to make use of such, unless you have an SGI host and Irix. -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Dec 3 19:30:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA12037 for freebsd-scsi-outgoing; Thu, 3 Dec 1998 19:30:55 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from iglou.com (iglou3.iglou.com [192.107.41.6]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA12031 for ; Thu, 3 Dec 1998 19:30:54 -0800 (PST) (envelope-from bertke@iglou.com) Received: from lou-ts4-10.iglou.com ([204.255.239.173] helo=iglou.com) by iglou.com with esmtp (8.9.1/8.9.1) id 0zllww-0004tH-00; Thu, 3 Dec 1998 22:30:35 -0500 Message-ID: <36675951.AA4D9A2D@iglou.com> Date: Thu, 03 Dec 1998 22:38:57 -0500 From: Bert Kellerman X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.34 i586) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: (no subject) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org auth 1b5b2449 unsubscribe freebsd-scsi bertke@iglou.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 5 04:35:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA08219 for freebsd-scsi-outgoing; Sat, 5 Dec 1998 04:35:52 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from ninbox.ml.org (hsv1-57.airnet.net [207.242.81.57]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA08214 for ; Sat, 5 Dec 1998 04:35:49 -0800 (PST) (envelope-from kris@airnet.net) Received: from airnet.net (localhost [127.0.0.1]) by ninbox.ml.org (8.9.1/8.8.5) with ESMTP id GAA00386 for ; Sat, 5 Dec 1998 06:32:30 -0600 (CST) Message-ID: <366927DD.3590DD75@airnet.net> Date: Sat, 05 Dec 1998 06:32:29 -0600 From: Kris Kirby Organization: Absolutely None! X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-RELEASE i386) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: Illegal Request? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org (probe1:adv0:0:1:0): INQUIRY. CDB: 12 1 80 0 ff 0 (probe1:adv0:0:1:0): ILLEGAL REQUEST asc:24,0 (probe1:adv0:0:1:0): Invalid field in CDB sks:c8,1 pass0 at adv0 bus 0 target 1 lun 0 pass0: Fixed Direct Access SCSI1 device pass0: 3.300MB/s transfers First time -v, never showed up before. Something I need to fix? -- Kris Kirby UAH Mail UAH CS Home WWW ------------------------------------------- TGIFreeBSD... 'Nuff said. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 5 09:20:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23460 for freebsd-scsi-outgoing; Sat, 5 Dec 1998 09:20:54 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23454 for ; Sat, 5 Dec 1998 09:20:49 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id SAA01878; Sat, 5 Dec 1998 18:20:45 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id SAA08513; Sat, 5 Dec 1998 18:11:43 +0100 (MET) (envelope-from j) Message-ID: <19981205181141.35063@uriah.heep.sax.de> Date: Sat, 5 Dec 1998 18:11:41 +0100 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Cc: Kris Kirby Subject: Re: Illegal Request? Reply-To: Joerg Wunsch References: <366927DD.3590DD75@airnet.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <366927DD.3590DD75@airnet.net>; from Kris Kirby on Sat, Dec 05, 1998 at 06:32:29AM -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 Kris Kirby wrote: > pass0 at adv0 bus 0 target 1 lun 0 > pass0: Fixed Direct Access SCSI1 device > pass0: 3.300MB/s transfers Boah, eh, such an oldish device... :-) I used to have one of them which i later gave to a friend. He reported me it's now finally dead, after perhaps 8 years of operation. (When i had it, it was so loud i've packaged it up in a cardboard box. Well, it ran a little hot, but this didn't seem to disturb that drive. :) > (probe1:adv0:0:1:0): INQUIRY. CDB: 12 1 80 0 ff 0 > (probe1:adv0:0:1:0): ILLEGAL REQUEST asc:24,0 > (probe1:adv0:0:1:0): Invalid field in CDB sks:c8,1 I guess it doesn't like things like serial number inquiries. Try turning them off by adding a quirk entry in /sys/cam/cam_xpt.c. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- 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 Dec 5 09:21:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23489 for freebsd-scsi-outgoing; Sat, 5 Dec 1998 09:21:04 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA23480 for ; Sat, 5 Dec 1998 09:21:01 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id SAA01880; Sat, 5 Dec 1998 18:20:59 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.9.1/8.9.1) id SAA08525; Sat, 5 Dec 1998 18:15:31 +0100 (MET) (envelope-from j) Message-ID: <19981205181530.47090@uriah.heep.sax.de> Date: Sat, 5 Dec 1998 18:15:30 +0100 From: J Wunsch To: freebsd-scsi@FreeBSD.ORG Cc: "Jason J. Horton" Subject: Re: 2.2.8-RELEASE and SCSI problem Reply-To: Joerg Wunsch References: <36672EEB.3BDA8063@intercom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <36672EEB.3BDA8063@intercom.com>; from Jason J. Horton on Thu, Dec 03, 1998 at 07:38:19PM -0500 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 Jason J. Horton wrote: > mount /dev/sd0a /mntwhatever > I get this error: > sd0: Can't deal with 201 bytes logical blocks > and obviously the mount doesn't happen. This looks odd. While i can imagine why someone has a disk that's formatted to 528 bytes/sector (as recently reported here), i can't imagine what 201 bytes/sector might be good for at all. My guess is that this controller is announcing some value for the block size the FreeBSD SCSI subsystem doesn't get correctly, or something like this. Perhaps you cate to quote the full probe messages (from a boot -v) here? (The part relevant to SCSI is sufficient.) > 3) Are NetBSD filesystems compatible with FreeBSD(all sources report > that it is)??? They should be. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- 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 Dec 5 10:23:04 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA28447 for freebsd-scsi-outgoing; Sat, 5 Dec 1998 10:23:04 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from sumatra.americantv.com (sumatra.americantv.com [207.170.17.37]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA28442 for ; Sat, 5 Dec 1998 10:23:01 -0800 (PST) (envelope-from jlemon@americantv.com) Received: from right.PCS (right.PCS [148.105.10.31]) by sumatra.americantv.com (8.8.5/8.8.5) with ESMTP id MAA08922 for ; Sat, 5 Dec 1998 12:22:58 -0600 (CST) Received: (from jlemon@localhost) by right.PCS (8.6.13/8.6.4) id MAA07804; Sat, 5 Dec 1998 12:22:27 -0600 Message-ID: <19981205122227.25141@right.PCS> Date: Sat, 5 Dec 1998 12:22:27 -0600 From: Jonathan Lemon To: scsi@FreeBSD.ORG Subject: 'timed out while idle' - FBSD 2.2.8 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.61.1 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I just upgraded one of my machines, and am now getting the following pile of errors (while doing a make world, /usr/src and /usr/obj are on sd0/sd1): Dec 5 12:10:13 fish /kernel: sd0(ahc0:0:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x8 Dec 5 12:10:17 fish /kernel: SEQADDR = 0x6 SCSISEQ = 0x12 SSTAT0 = 0x5 SSTAT1 = 0xa Dec 5 12:10:17 fish /kernel: sd0(ahc0:0:0): Queueing an Abort SCB Dec 5 12:10:17 fish /kernel: sd0(ahc0:0:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0x8 Dec 5 12:10:17 fish /kernel: SEQADDR = 0x4 SCSISEQ = 0x5a SSTAT0 = 0x5 SSTAT1 = 0xa Dec 5 12:10:17 fish /kernel: sd0(ahc0:0:0): no longer in timeout Dec 5 12:10:17 fish /kernel: ahc0: Issued Channel A Bus Reset. 2 SCBs aborted Dec 5 12:10:17 fish /kernel: sd0(ahc0:0:0): UNIT ATTENTION asc:29,2 field replaceable unit: 2 Dec 5 12:10:17 fish /kernel: , retries:3 Dec 5 12:10:17 fish /kernel: sd1(ahc0:1:0): UNIT ATTENTION asc:29,2 field replaceable unit: 2 Dec 5 12:10:17 fish /kernel: , retries:4 Dec 5 12:14:28 fish /kernel: sd1(ahc0:1:0): SCB 0x5 - timed out while idle, LAS TPHASE == 0x1, SCSISIGI == 0x8 Dec 5 12:14:32 fish /kernel: SEQADDR = 0x5 SCSISEQ = 0x5a SSTAT0 = 0x5 SSTAT1 = 0xa Dec 5 12:14:32 fish /kernel: sd1(ahc0:1:0): Queueing an Abort SCB Dec 5 12:14:32 fish /kernel: sd1(ahc0:1:0): SCB 0x5 - timed out while idle, LAS TPHASE == 0x1, SCSISIGI == 0x8 Dec 5 12:14:32 fish /kernel: SEQADDR = 0x5 SCSISEQ = 0x5a SSTAT0 = 0x5 SSTAT1 = 0xa Dec 5 12:14:32 fish /kernel: sd1(ahc0:1:0): no longer in timeout Dec 5 12:14:32 fish /kernel: ahc0: Issued Channel A Bus Reset. 4 SCBs aborted Dec 5 12:14:32 fish /kernel: sd0(ahc0:0:0): UNIT ATTENTION asc:29,2 field repl aceable unit: 2 Dec 5 12:14:32 fish /kernel: , retries:3 Dec 5 12:14:32 fish /kernel: sd1(ahc0:1:0): UNIT ATTENTION asc:29,2 field repl aceable unit: 2 Dec 5 12:14:32 fish /kernel: , retries:3 This kernel is currently running the 2.2.8-RELEASE kernel, and has only SCSI devices in it; sd0/sd1 are a pair of Barracudas, and sd2 is a 9G drive. >From the dmesg: ahc0 rev 0 int a irq 11 on pci0:12:0 ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs (ahc0:0:0): "SEAGATE ST34573LW 5960" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 4340MB (8888924 512 byte sectors) (ahc0:1:0): "SEAGATE ST34573LW 5960" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 4340MB (8888924 512 byte sectors) (ahc0:3:0): "SEAGATE ST410800N 0025" type 0 fixed SCSI 2 sd2(ahc0:3:0): Direct-Access 8669MB (17755614 512 byte sectors) (ahc0:4:0): "EXABYTE EXB-85058SQANXR1 07J0" type 1 removable SCSI 2 st0(ahc0:4:0): Sequential-Access density code 0x0, drive empty What could be wrong here? Cabling? The termination is correct. The controller is set for 10.0MB transfers, and has disconnection negotiation enabled. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 5 10:48:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA00818 for freebsd-scsi-outgoing; Sat, 5 Dec 1998 10:48:59 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA00812 for ; Sat, 5 Dec 1998 10:48:57 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id KAA19302; Sat, 5 Dec 1998 10:48:48 -0800 Date: Sat, 5 Dec 1998 10:48:47 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Kris Kirby cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Illegal Request? In-Reply-To: <366927DD.3590DD75@airnet.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 Don't worry about it. Apparently the older 8760 doesn't like to give out VPD info. The probe routine should have been quieter though. On Sat, 5 Dec 1998, Kris Kirby wrote: > (probe1:adv0:0:1:0): INQUIRY. CDB: 12 1 80 0 ff 0 > (probe1:adv0:0:1:0): ILLEGAL REQUEST asc:24,0 > (probe1:adv0:0:1:0): Invalid field in CDB sks:c8,1 > pass0 at adv0 bus 0 target 1 lun 0 > pass0: Fixed Direct Access SCSI1 device > pass0: 3.300MB/s transfers > > First time -v, never showed up before. Something I need to fix? > -- > Kris Kirby > UAH Mail UAH CS > Home WWW > ------------------------------------------- > TGIFreeBSD... 'Nuff said. > > 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 Sat Dec 5 11:10:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA02320 for freebsd-scsi-outgoing; Sat, 5 Dec 1998 11:10:57 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA02315 for ; Sat, 5 Dec 1998 11:10:56 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id MAA84263; Sat, 5 Dec 1998 12:03:31 -0700 (MST) Date: Sat, 5 Dec 1998 12:03:31 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199812051903.MAA84263@narnia.plutotech.com> To: mjacob@feral.com cc: scsi@FreeBSD.ORG Subject: Re: Illegal Request? X-Newsgroups: pluto.freebsd.scsi In-Reply-To: User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article you wrote: > > Don't worry about it. Apparently the older 8760 doesn't like to give out > VPD info. The probe routine should have been quieter though. It is if you don't explicitly boot in verbose mode. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 5 11:22:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA03315 for freebsd-scsi-outgoing; Sat, 5 Dec 1998 11:22:58 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA03310 for ; Sat, 5 Dec 1998 11:22:56 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id LAA19386; Sat, 5 Dec 1998 11:22:46 -0800 Date: Sat, 5 Dec 1998 11:22:46 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG Subject: Re: Illegal Request? In-Reply-To: <199812051903.MAA84263@narnia.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "oh" On Sat, 5 Dec 1998, Justin T. Gibbs wrote: > In article you wrote: > > > > Don't worry about it. Apparently the older 8760 doesn't like to give out > > VPD info. The probe routine should have been quieter though. > > It is if you don't explicitly boot in verbose mode. > > -- > Justin > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 5 13:46:03 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA14872 for freebsd-scsi-outgoing; Sat, 5 Dec 1998 13:46:03 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from silver.gn.iaf.nl (silver.gn.iaf.nl [193.67.144.11]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA14867 for ; Sat, 5 Dec 1998 13:46:01 -0800 (PST) (envelope-from wilko@yedi.iaf.nl) Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by silver.gn.iaf.nl (8.8.8/8.8.8) with SMTP id WAA02945; Sat, 5 Dec 1998 22:45:41 +0100 Received: by uni4nn.gn.iaf.nl with UUCP id AA15482 (5.67b/IDA-1.5); Sat, 5 Dec 1998 22:31:43 +0100 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.8/8.6.12) id VAA23440; Sat, 5 Dec 1998 21:45:17 +0100 (CET) From: Wilko Bulte Message-Id: <199812052045.VAA23440@yedi.iaf.nl> Subject: Re: Illegal Request? In-Reply-To: <19981205181141.35063@uriah.heep.sax.de> from J Wunsch at "Dec 5, 98 06:11:41 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 5 Dec 1998 21:45:17 +0100 (CET) Cc: freebsd-scsi@FreeBSD.ORG, kris@airnet.net X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL38 (25)] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org As J Wunsch wrote... > As Kris Kirby wrote: > > > pass0 at adv0 bus 0 target 1 lun 0 > > pass0: Fixed Direct Access SCSI1 device > > pass0: 3.300MB/s transfers > > Boah, eh, such an oldish device... :-) I used to have one of them > which i later gave to a friend. He reported me it's now finally dead, > after perhaps 8 years of operation. (When i had it, it was so loud > i've packaged it up in a cardboard box. Well, it ran a little hot, > but this didn't seem to disturb that drive. :) This older stuff is built like a tank ;-) > > (probe1:adv0:0:1:0): INQUIRY. CDB: 12 1 80 0 ff 0 > > (probe1:adv0:0:1:0): ILLEGAL REQUEST asc:24,0 > > (probe1:adv0:0:1:0): Invalid field in CDB sks:c8,1 > > I guess it doesn't like things like serial number inquiries. Try > turning them off by adding a quirk entry in /sys/cam/cam_xpt.c. Sounds like the inquiry command tries to get more detailed data. Only newer devices understand what is being asked. Can safely be ignored I'd say. Wilko _ ______________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl |/|/ / / /( (_) Arnhem, The Netherlands WWW : http://www.tcja.nl ______________________________________________ Powered by FreeBSD __________ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 5 16:02:09 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA26678 for freebsd-scsi-outgoing; Sat, 5 Dec 1998 16:02:09 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from jcarter.cais.com (jcarter.cais.com [205.252.8.97]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA26630 for ; Sat, 5 Dec 1998 16:02:04 -0800 (PST) (envelope-from patton@sysnet.net) Received: from [192.168.1.10] (saturn.falcon.com [192.168.1.10]) by jcarter.cais.com (8.9.1a/8.8.5) with ESMTP id SAA05643 for ; Sat, 5 Dec 1998 18:42:39 -0500 (EST) Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sat, 5 Dec 1998 19:08:31 -0500 To: freebsd-scsi@FreeBSD.ORG From: Matthew Patton Subject: CAM vs traditional devices Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I'm lagging -current by a month or so but I have been running with CAM now for a while. I've noticed that the kernel probes the disks as daXX. I therefore converted all of my fstab entries to use daXy where y is the partition letter [a ~ g] except for the entry for root. The kernel still thinks the root device is "sd0s1a". Why is that? Also how come none of the "da" devices have trailing partition letters? eg. there is "da0s1" and "da0a" but no "da0s1a". I am simply too far behind? The /dev/MAKEDEV script doesn't build them. Hmm, I just noticed that the 1st stage boot loader called for (sd0,1,a) Maybe that's why the kernel is confused? I need to install-boot again, right? Again this may be an artifact of not tracking -current closely, but doesn't anybody boot their boxes where say /usr is NFS mounted? /etc/rc doesn't start the network till extremely late in the game - practically when it's done. Other BSD's start the network immediately after / is marked RW. They then explicitly mount /usr and /var in case the automatic method doesn't happen to pick the right order. -------- OpenBSD - Because security matters... (http://www.openbsd.org/) "There is one terrifying word in the world of nuclear physics, Oops." - Tom Servo, Mystery Science Theator 3000 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 5 16:15:37 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29372 for freebsd-scsi-outgoing; Sat, 5 Dec 1998 16:15:37 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29367 for ; Sat, 5 Dec 1998 16:15:35 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id QAA20311; Sat, 5 Dec 1998 16:15:23 -0800 Date: Sat, 5 Dec 1998 16:15:22 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Matthew Patton cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CAM vs traditional devices 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 This isn't a SCSI issue. This is a slice issue. And I sure wish I could figure it out sometimes. You probably need to ask freebsd-current about this. On Sat, 5 Dec 1998, Matthew Patton wrote: > I'm lagging -current by a month or so but I have been running with CAM now > for a while. I've noticed that the kernel probes the disks as daXX. I > therefore converted all of my fstab entries to use daXy where y is the > partition letter [a ~ g] except for the entry for root. > > The kernel still thinks the root device is "sd0s1a". Why is that? Also how > come none of the "da" devices have trailing partition letters? eg. there is > "da0s1" and "da0a" but no "da0s1a". I am simply too far behind? The > /dev/MAKEDEV script doesn't build them. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 5 16:18:36 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA29594 for freebsd-scsi-outgoing; Sat, 5 Dec 1998 16:18:36 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from cogsci.ed.ac.uk (stevenson144.cogsci.ed.ac.uk [129.215.144.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA29586 for ; Sat, 5 Dec 1998 16:18:31 -0800 (PST) (envelope-from richard@cogsci.ed.ac.uk) Received: from doyle.cogsci.ed.ac.uk (richard@doyle [129.215.110.29]) by cogsci.ed.ac.uk (8.8.7/8.8.7) with SMTP id AAA04870 for ; Sun, 6 Dec 1998 00:18:27 GMT Date: Sun, 6 Dec 1998 00:18:26 GMT Message-Id: <23861.199812060018@doyle.cogsci.ed.ac.uk> From: Richard Tobin Subject: AHA 1542 "invalid baseport" To: freebsd-scsi@FreeBSD.ORG Organization: just say no Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [I'm running 3.0-RELEASE] The code that checks for a valid port number in aha_isa.c assumes that the aha_isa_ports array (in dev/aha/aha.c) contains the ports in descending order, but it doesn't. It has 330,334,230,234,130,134. This means that a board at address x34 will report an invalid baseport. -- Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Dec 5 19:30:15 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13027 for freebsd-scsi-outgoing; Sat, 5 Dec 1998 19:30:15 -0800 (PST) (envelope-from owner-freebsd-scsi@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13022 for ; Sat, 5 Dec 1998 19:30:14 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.1/8.7.3) id UAA00453; Sat, 5 Dec 1998 20:22:30 -0700 (MST) Date: Sat, 5 Dec 1998 20:22:30 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <199812060322.UAA00453@narnia.plutotech.com> To: Richard Tobin cc: scsi@FreeBSD.ORG Subject: Re: AHA 1542 "invalid baseport" X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <23861.199812060018@doyle.cogsci.ed.ac.uk> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org In article <23861.199812060018@doyle.cogsci.ed.ac.uk> you wrote: > [I'm running 3.0-RELEASE] This problem was addressed by revision 1.11 of sys/dev/aha.c on 1998/11/10 06:44:42. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message