From owner-freebsd-scsi Mon Feb 11 7:46:47 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from Mail6.nc.rr.com (fe6.southeast.rr.com [24.93.67.53]) by hub.freebsd.org (Postfix) with ESMTP id B639637B402; Mon, 11 Feb 2002 07:46:28 -0800 (PST) Received: from i8k.babbleon.org ([66.57.85.154]) by Mail6.nc.rr.com with Microsoft SMTPSVC(5.5.1877.687.68); Mon, 11 Feb 2002 09:41:55 -0500 Received: by i8k.babbleon.org (Postfix, from userid 111) id 22A834074; Mon, 11 Feb 2002 09:37:07 -0500 (EST) From: Brian T.Schellenberger To: Subject: Re: USB drive -- problems Date: Mon, 11 Feb 2002 09:37:06 -0500 X-Mailer: KMail [version 1.3] References: <000901c1b2d9$89cac820$fe02010a@twoflower.liebende.de> In-Reply-To: <000901c1b2d9$89cac820$fe02010a@twoflower.liebende.de> Cc: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org MIME-Version: 1.0 Content-Type: Multipart/Mixed; boundary="------------Boundary-00=_UXHD66TKBLBXGT3KDOZ6" Message-Id: <20020211143707.22A834074@i8k.babbleon.org> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --------------Boundary-00=_UXHD66TKBLBXGT3KDOZ6 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit Bingo! That was it! It's working beautifully now. ThankyouThankyouThankyouThankyou. I'll submit the patches to a committer so I don't have to re-patch every time I upgrade the source. PS: Did you submit your patch so it can be integrated into the offiical source? PPS: Anyway know of any particular reason why DA_Q_NO_6_BYTE isn't just the default? Looking at the scsi file it sure seems like a large number of devices need this . . . at any rate it seems like it might be cool if i/o errors of this nature could be recognized and the feature dynamically turned off . . . PS: Just in case there's somebody on the scsi list who'd like to commit my change, my patch is attached. On Monday 11 February 2002 03:53 am, Jan Stocker wrote: > Excuse me for the late reply... > > src/sys/cam/scsi/scsi_da.c contains quirks for each da device... > > ive added one for my digicam: > > { > /* MINOLTA DIMAGE 2330 */ > {T_DIRECT, SIP_MEDIA_REMOVABLE, "MINOLTA", "DIMAGE 2330*","*"}, > /*quirks*/ DA_Q_NO_6_BYTE > }, > > so no 6-byte commands will be send to the device... search for a device > entry similar to your disc controller, add an entry and recompile... > > Jan > > P.S: Your surname looks quite german.... > > > -----Original Message----- > > From: Brian T.Schellenberger [mailto:bts@babbleon.org] > > Sent: Saturday, February 09, 2002 12:31 AM > > To: jstocker@tzi.de > > Subject: Re: USB drive -- problems > > > > On Monday 04 February 2002 08:00 am, you wrote: > > > A maybe better discussion group will be freebsd-scsi. > > > > > > Maybe you need to turn off 6-byte commands with a quirk... > > > > Hmm . . . perhaps. But I'm afraid I don't even know what that means. > > Can you clarify, or tell me what I should be reading that I'm not? > > > > > Jan > > > > > > > PPS: Why, oh why is there a /dev/ad0 and a /dev/da0? What do > > > > they stand for? > > > > > > Okay... da is for the DirectAccess drives on USB/SCSI > > > ad represent the ATA-Drives. So ad0 is the primary-master ATA-IDE > > > drive. > > > > > > > -----Original Message----- > > > > From: owner-freebsd-hardware@FreeBSD.ORG > > > > [mailto:owner-freebsd-hardware@FreeBSD.ORG]On Behalf Of Brian > > > > T.Schellenberger > > > > Sent: Sunday, February 03, 2002 3:20 PM > > > > To: freebsd-question@FreeBSD.ORG; freebsd-hardware@FreeBSD.ORG > > > > Subject: USB drive -- problems > > > > > > > > > > > > > > > > Ok, with little confidence it would work, since I could find > > > > no very good > > > > > > info on USB & FreeBSD, and there was no response to my query on > > > > the subject, > > > > I decided in a "what the hell" moment to get a USB drive and see what > > > > happened. > > > > > > > > I have a LaCie 80G drive. It was $250 for 80, USB 2, and if > > > > it works it > > > > > > should be pretty darn cool. > > > > > > > > It is recognized by the kernel, so I thought I was doing > > > > pretty well, but > > > > > > when I try to actually do anything with it, I run into > > > > trouble. Here are > > > > > > some messages from /var/log messages, first hte successful > > > > boot stuff and > > > > > > then the failure messages: > > > > > > > > Feb 3 04:31:21 i8k /kernel: uhci0: > > > controller > > > > USB-A> port 0xbce0-0xbcff irq 11 at device 31.2 on pci0 > > > > Feb 3 04:31:21 i8k /kernel: usb0: > > > controller > > > > USB-A> on uhci0 > > > > Feb 3 04:31:21 i8k /kernel: usb0: USB revision 1.0 > > > > Feb 3 04:31:21 i8k /kernel: uhub0: Intel UHCI root hub, > > > > class 9/0, rev > > > > > > 1.00/1.00, addr 1 > > > > Feb 3 04:31:21 i8k /kernel: uhub0: 2 ports with 2 removable, self > > > > powered Feb 3 04:31:21 i8k /kernel: umass0: LaCie LaCie > > > > StudioDrive USB2 > > > > > > , > > > > rev 2.00/10.06, addr 2 > > > > > > > > > > > > Feb 3 04:31:21 i8k /kernel: da0 at umass-sim0 bus 0 target 0 lun 0 > > > > Feb 3 04:31:22 i8k /kernel: da0: Fixed > > > > Direct Access > > > > SCSI-0 device > > > > Feb 3 04:31:22 i8k /kernel: da0: 650KB/s transfers > > > > Feb 3 04:31:22 i8k /kernel: da0: 78167MB (160086528 512 byte > > > > sectors: 64H > > > > 32S/T 12631C) > > > > > > > > > > > > Feb 3 05:08:48 i8k /kernel: (da0:umass-sim0:0:0:0): READ(06). > > > > CDB: 8 0 0 0 1 > > > > 0 > > > > Feb 3 05:08:48 i8k /kernel: (da0:umass-sim0:0:0:0): ILLEGAL > > > > REQUEST asc:21,0 > > > > Feb 3 05:08:48 i8k /kernel: (da0:umass-sim0:0:0:0): Logical > > > > block address > > > > out of range > > > > Feb 3 05:08:57 i8k /kernel: (da0:umass-sim0:0:0:0): READ(06). > > > > CDB: 8 0 0 0 1 > > > > 0 > > > > Feb 3 05:08:57 i8k /kernel: (da0:umass-sim0:0:0:0): ILLEGAL > > > > REQUEST asc:21,0 > > > > Feb 3 05:08:57 i8k /kernel: (da0:umass-sim0:0:0:0): Logical > > > > block address > > > > out of range > > > > > > > > The set of error messages above were returned when I did a simple > > > > > > > > dd if=/dev/da0 > > > > > > > > > > > > PS: I might not recieve mail for a couple days so don't be > > > > surprised if > > > > > > responses are a little slow. Based on previous response to USB > > > > queries on > > > > the questions list I doubt that excessive responses will be a big > > > > problem. > > > > I'm including the questions list here more as an "FYI" sort of thing. > > > > > > > > It's darn confusing and it makes me nervous as heck doing > > > > "dangerous" operations where I am one swapped letter pair away from > > > > wiping out my primary > > > > drive! > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > Brian T. Schellenberger . . . . . . . bts@wnt.sas.com (work) > > > > Brian, the man from Babble-On . . . . bts@babbleon.org (personal) > > > > ME --> http://www.babbleon.org > > > > http://www.eff.org <-- GOOD GUYS --> > > > > http://www.programming-freedom.org > > > > > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > > > with "unsubscribe freebsd-hardware" in the body of the message > > > > -- > > Brian T. Schellenberger . . . . . . . bts@wnt.sas.com (work) > > Brian, the man from Babble-On . . . . bts@babbleon.org (personal) > > ME --> http://www.babbleon.org > > http://www.eff.org <-- GOOD GUYS --> > > http://www.programming-freedom.org -- Brian T. Schellenberger . . . . . . . bts@wnt.sas.com (work) Brian, the man from Babble-On . . . . bts@babbleon.org (personal) ME --> http://www.babbleon.org http://www.eff.org <-- GOOD GUYS --> http://www.programming-freedom.org --------------Boundary-00=_UXHD66TKBLBXGT3KDOZ6 Content-Type: text/x-diff; charset="iso-8859-1"; name="sys_cam_scsi_scsi_da.c.patch" Content-Transfer-Encoding: 8bit Content-Disposition: attachment; filename="sys_cam_scsi_scsi_da.c.patch" *** scsi_da.c.org Mon Feb 11 07:18:39 2002 --- scsi_da.c Mon Feb 11 07:23:18 2002 *************** *** 255,265 **** {T_DIRECT, SIP_MEDIA_REMOVABLE, "Sony", "Sony DSC", "*"}, /*quirks*/ DA_Q_NO_6_BYTE|DA_Q_NO_SYNC_CACHE }, ! { /* * Maxtor 3000LE USB Drive */ {T_DIRECT, SIP_MEDIA_FIXED, "MAXTOR*", "K040H2*", "*"}, /*quirks*/ DA_Q_NO_6_BYTE }, { --- 255,272 ---- {T_DIRECT, SIP_MEDIA_REMOVABLE, "Sony", "Sony DSC", "*"}, /*quirks*/ DA_Q_NO_6_BYTE|DA_Q_NO_SYNC_CACHE }, ! { /* * Maxtor 3000LE USB Drive */ {T_DIRECT, SIP_MEDIA_FIXED, "MAXTOR*", "K040H2*", "*"}, + /*quirks*/ DA_Q_NO_6_BYTE + }, + { + /* + * LaCie USB drive, among others + */ + {T_DIRECT, SIP_MEDIA_FIXED, "Maxtor*", "D080H4*", "*"}, /*quirks*/ DA_Q_NO_6_BYTE }, { --------------Boundary-00=_UXHD66TKBLBXGT3KDOZ6-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 11 8: 6:53 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from murphy.dachbu.de (murphy.dachbu.de [195.180.4.161]) by hub.freebsd.org (Postfix) with ESMTP id 5A72A37B402 for ; Mon, 11 Feb 2002 08:06:48 -0800 (PST) Received: (from freddy@localhost) by murphy.dachbu.de (8.11.6/8.11.4) id g1BG6fL01156; Mon, 11 Feb 2002 17:06:41 +0100 (CET) (envelope-from frank@altpeter.de) X-Authentication-Warning: murphy.dachbu.de: freddy set sender to frank@altpeter.de using -f Date: Mon, 11 Feb 2002 17:06:40 +0100 From: Frank Altpeter To: freebsd-scsi@freebsd.org Cc: frank@altpeter.de Subject: SCSI parity error detected Message-ID: <20020211170640.C245@ision.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i X-Mozilla-HTML: FALSE Organization: ISION Internet AG, Hamburg, Germany X-ICQ-UIN: 6133423 X-IRCNICK: Freddy X-PGP-KeyID: 0xF128ADF3 X-PGP-Fingerprint: 97 A1 A6 3C 2F 61 84 B0 A6 39 C0 A2 53 F0 D4 0B X-PGP-Download: hkp://wwwkeys.de.pgp.net/0xF128ADF3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org hello! After many hours of testing with a good friend we didn't work out any solution for my problem - he recommended asking you, because you are the cracks that wrote the driver :-)) Well... something about my hardware first... i'm running an x86 system, powered with a gigabyte (GA-7VTXE+) board and an Athlon XP 1500+ CPU. There are four SCSI devices connected via a Dawicontrol DC-2945U hostadapter (symbios 53C875 chipset). The device list is as follows: murphy# camcontrol devlist -v scbus0 on sym0 bus 0: at scbus0 target 0 lun 0 (pass0,da0) at scbus0 target 1 lun 0 (pass1) at scbus0 target 2 lun 0 (pass2) at scbus0 target 4 lun 0 (pass3,cd0) < > at scbus0 target -1 lun -1 () scbus-1 on xpt0 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) Target 0 is an SCSI-2 harddisk, and the targets 1 and 2 are SCA disks, plugged in with some SCA-SCSI-2 adapter. The main disk (target 0) is working: da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) But the two other disks show up these errors: sym0: SCSI parity error detected: SCR1=1 DBC=11000000 SBCL=29 sym0: SCSI parity error detected: SCR1=3 DBC=11000000 SBCL=29 sym0: SCSI parity error detected: SCR1=1 DBC=11000000 SBCL=29 sym0: SCSI parity error detected: SCR1=3 DBC=11000000 SBCL=29 sym0: SCSI parity error detected: SCR1=1 DBC=11000000 SBCL=29 sym0: SCSI parity error detected: SCR1=3 DBC=11000000 SBCL=29 sym0: SCSI parity error detected: SCR1=1 DBC=11000000 SBCL=29 (da1:sym0:0:1:0): got CAM status 0x50 (da1:sym0:0:1:0): fatal error, failed to attach to device (da1:sym0:0:1:0): lost device (da1:sym0:0:1:0): removing device entry (da2:sym0:0:2:0): got CAM status 0x50 (da2:sym0:0:2:0): fatal error, failed to attach to device (da2:sym0:0:2:0): lost device (da2:sym0:0:2:0): removing device entry Since i used to have an adaptec 1542cf before, i'm quite sure that the disks and the SCA adapters are ok, because the system was running fine with the old card (yes, i know it's a shame to run fast SCA disks with this setting, but i got them really cheap :). After switching to the new motherboard, the old adaptec was unusable because it was an ISA card (new board only supports PCI). The CDROM was the last device in the chain and was terminating. I have changed this now, and have terminated the chain with an active terminator at the end of the SCSI cable. But, the errors keep showing up and the devices are not useable. Can you perhaps give me any hints on that problem? -- Fachbegriffe der Informatik einfach erklaert, Teil 6: "Globale Variable" == "Parameteruebergabemechanismus in 4GLs" (Marit Koehntopp) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 11 8:37:53 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from web13404.mail.yahoo.com (web13404.mail.yahoo.com [216.136.175.62]) by hub.freebsd.org (Postfix) with SMTP id 346AB37B419 for ; Mon, 11 Feb 2002 08:37:21 -0800 (PST) Message-ID: <20020211163721.18370.qmail@web13404.mail.yahoo.com> Received: from [4.18.79.232] by web13404.mail.yahoo.com via HTTP; Mon, 11 Feb 2002 08:37:21 PST Date: Mon, 11 Feb 2002 08:37:21 -0800 (PST) From: Andrew Gould Subject: Re: USB drive -- problems To: "Brian T.Schellenberger" , jstocker@tzi.de Cc: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org In-Reply-To: <20020211143707.22A834074@i8k.babbleon.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I understand neither scsi nor usb issues; but am considering getting a usb drive for my KDS minibook pc ( a cool little device, except for the winmodem). Is the problem below related to any use of usb hard drives? Is it isolated to the use of pci usb controllers? Am I way off base on both questions? Thanks, Andrew Gould --- "Brian T.Schellenberger" wrote: > > Bingo! > > That was it! It's working beautifully now. > > ThankyouThankyouThankyouThankyou. > > I'll submit the patches to a committer so I don't > have to re-patch every time > I upgrade the source. > > PS: Did you submit your patch so it can be > integrated into the offiical > source? > > PPS: Anyway know of any particular reason why > DA_Q_NO_6_BYTE isn't just the > default? Looking at the scsi file it sure seems > like a large number of > devices need this . . . at any rate it seems like it > might be cool if i/o > errors of this nature could be recognized and the > feature dynamically turned > off . . . > > > PS: Just in case there's somebody on the scsi list > who'd like to commit my > change, my patch is attached. > > > On Monday 11 February 2002 03:53 am, Jan Stocker > wrote: > > Excuse me for the late reply... > > > > src/sys/cam/scsi/scsi_da.c contains quirks for > each da device... > > > > ive added one for my digicam: > > > > { > > /* MINOLTA DIMAGE 2330 */ > > {T_DIRECT, SIP_MEDIA_REMOVABLE, "MINOLTA", > "DIMAGE 2330*","*"}, > > /*quirks*/ DA_Q_NO_6_BYTE > > }, > > > > so no 6-byte commands will be send to the > device... search for a device > > entry similar to your disc controller, add an > entry and recompile... > > > > Jan > > > > P.S: Your surname looks quite german.... > > > > > -----Original Message----- > > > From: Brian T.Schellenberger > [mailto:bts@babbleon.org] > > > Sent: Saturday, February 09, 2002 12:31 AM > > > To: jstocker@tzi.de > > > Subject: Re: USB drive -- problems > > > > > > On Monday 04 February 2002 08:00 am, you wrote: > > > > A maybe better discussion group will be > freebsd-scsi. > > > > > > > > Maybe you need to turn off 6-byte commands > with a quirk... > > > > > > Hmm . . . perhaps. But I'm afraid I don't even > know what that means. > > > Can you clarify, or tell me what I should be > reading that I'm not? > > > > > > > Jan > > > > > > > > > PPS: Why, oh why is there a /dev/ad0 and a > /dev/da0? What do > > > > > they stand for? > > > > > > > > Okay... da is for the DirectAccess drives on > USB/SCSI > > > > ad represent the ATA-Drives. So ad0 is the > primary-master ATA-IDE > > > > drive. > > > > > > > > > -----Original Message----- > > > > > From: owner-freebsd-hardware@FreeBSD.ORG > > > > > > [mailto:owner-freebsd-hardware@FreeBSD.ORG]On Behalf > Of Brian > > > > > T.Schellenberger > > > > > Sent: Sunday, February 03, 2002 3:20 PM > > > > > To: freebsd-question@FreeBSD.ORG; > freebsd-hardware@FreeBSD.ORG > > > > > Subject: USB drive -- problems > > > > > > > > > > > > > > > > > > > > Ok, with little confidence it would work, > since I could find > > > > > > no very good > > > > > > > > info on USB & FreeBSD, and there was no > response to my query on > > > > > the subject, > > > > > I decided in a "what the hell" moment to get > a USB drive and see what > > > > > happened. > > > > > > > > > > I have a LaCie 80G drive. It was $250 for > 80, USB 2, and if > > > > > > it works it > > > > > > > > should be pretty darn cool. > > > > > > > > > > It is recognized by the kernel, so I thought > I was doing > > > > > > pretty well, but > > > > > > > > when I try to actually do anything with it, > I run into > > > > > > trouble. Here are > > > > > > > > some messages from /var/log messages, first > hte successful > > > > > > boot stuff and > > > > > > > > then the failure messages: > > > > > > > > > > Feb 3 04:31:21 i8k /kernel: uhci0: 82801BA/BAM (ICH2) USB > > > > > controller > > > > > USB-A> port 0xbce0-0xbcff irq 11 at device > 31.2 on pci0 > > > > > Feb 3 04:31:21 i8k /kernel: usb0: 82801BA/BAM (ICH2) USB > > > > > controller > > > > > USB-A> on uhci0 > > > > > Feb 3 04:31:21 i8k /kernel: usb0: USB > revision 1.0 > > > > > Feb 3 04:31:21 i8k /kernel: uhub0: Intel > UHCI root hub, > > > > > > class 9/0, rev > > > > > > > > 1.00/1.00, addr 1 > > > > > Feb 3 04:31:21 i8k /kernel: uhub0: 2 ports > with 2 removable, self > > > > > powered Feb 3 04:31:21 i8k /kernel: umass0: > LaCie LaCie > > > > > > StudioDrive USB2 > > > > > > > > , > > > > > rev 2.00/10.06, addr 2 > > > > > > > > > > > > > > > Feb 3 04:31:21 i8k /kernel: da0 at > umass-sim0 bus 0 target 0 lun 0 > > > > > Feb 3 04:31:22 i8k /kernel: da0: D080H4 DAH0> Fixed > > > > > Direct Access > > > > > SCSI-0 device > > > > > Feb 3 04:31:22 i8k /kernel: da0: 650KB/s > transfers > > > > > Feb 3 04:31:22 i8k /kernel: da0: 78167MB > (160086528 512 byte > > > > > sectors: 64H > > > > > 32S/T 12631C) > > > > > > > > > > > > > > > Feb 3 05:08:48 i8k /kernel: > (da0:umass-sim0:0:0:0): READ(06). > > > > > CDB: 8 0 0 0 1 > > > > > 0 > > > > > Feb 3 05:08:48 i8k /kernel: > (da0:umass-sim0:0:0:0): ILLEGAL > > > > > REQUEST asc:21,0 > > > > > Feb 3 05:08:48 i8k /kernel: > (da0:umass-sim0:0:0:0): Logical > > > > > block address > > > > > out of range > > > > > Feb 3 05:08:57 i8k /kernel: > (da0:umass-sim0:0:0:0): READ(06). > > > > > CDB: 8 0 0 0 1 > > > > > 0 > > > > > Feb 3 05:08:57 i8k /kernel: > (da0:umass-sim0:0:0:0): ILLEGAL > > > > > REQUEST asc:21,0 > > > > > Feb 3 05:08:57 i8k /kernel: > (da0:umass-sim0:0:0:0): Logical > > > > > block address > > > > > out of range > > > > > > > > > > The set of error messages above were > returned when I did a simple > > > > > > > > > > dd if=/dev/da0 > > > > > > > > > > > > > > > PS: I might not recieve mail for a couple > days so don't be > > > > > > surprised if > > > > > > > > responses are a little slow. Based on > previous response to USB > > > > > queries on > > > > > the questions list I doubt that excessive > responses will be a big > > > > > problem. > > > > > I'm including the questions list here more > as an "FYI" sort of thing. > > > > > > > > > > It's darn confusing and it makes me nervous > as heck doing > > > > > "dangerous" operations where I am one > swapped letter pair away from > > > > > wiping out my primary > > > > > drive! > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Brian T. Schellenberger . . . . . . . > bts@wnt.sas.com (work) > > > > > Brian, the man from Babble-On . . . . > bts@babbleon.org (personal) > > > > > ME --> > http://www.babbleon.org > > > > > http://www.eff.org <-- GOOD GUYS --> > > > > > http://www.programming-freedom.org > > > > > > > > > > > > > > > To Unsubscribe: send mail to > majordomo@FreeBSD.org > > > > > with "unsubscribe freebsd-hardware" in the > body of the message > > > > > > -- > > > Brian T. Schellenberger . . . . . . . > bts@wnt.sas.com (work) > > > Brian, the man from Babble-On . . . . > bts@babbleon.org (personal) > > > ME --> > http://www.babbleon.org > > > http://www.eff.org <-- GOOD GUYS --> > > > > http://www.programming-freedom.org > > -- > Brian T. Schellenberger . . . . . . . > bts@wnt.sas.com (work) > Brian, the man from Babble-On . . . . > bts@babbleon.org (personal) > ME --> > http://www.babbleon.org > http://www.eff.org <-- GOOD GUYS --> > http://www.programming-freedom.org > > *** scsi_da.c.org Mon Feb 11 07:18:39 2002 > --- scsi_da.c Mon Feb 11 07:23:18 2002 > *************** > *** 255,265 **** > {T_DIRECT, SIP_MEDIA_REMOVABLE, "Sony", "Sony > DSC", "*"}, > /*quirks*/ DA_Q_NO_6_BYTE|DA_Q_NO_SYNC_CACHE > }, > ! { > /* > * Maxtor 3000LE USB Drive > */ > {T_DIRECT, SIP_MEDIA_FIXED, "MAXTOR*", > "K040H2*", "*"}, > /*quirks*/ DA_Q_NO_6_BYTE > }, > { > --- 255,272 ---- > {T_DIRECT, SIP_MEDIA_REMOVABLE, "Sony", "Sony > DSC", "*"}, > /*quirks*/ DA_Q_NO_6_BYTE|DA_Q_NO_SYNC_CACHE > }, > ! { > /* > * Maxtor 3000LE USB Drive > */ > {T_DIRECT, SIP_MEDIA_FIXED, "MAXTOR*", > "K040H2*", "*"}, > + /*quirks*/ DA_Q_NO_6_BYTE > + }, > + { > + /* > + * LaCie USB drive, among others > + */ > + {T_DIRECT, SIP_MEDIA_FIXED, "Maxtor*", > "D080H4*", "*"}, > /*quirks*/ DA_Q_NO_6_BYTE > }, > { > __________________________________________________ Do You Yahoo!? Send FREE Valentine eCards with Yahoo! Greetings! http://greetings.yahoo.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 11 12:16:22 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by hub.freebsd.org (Postfix) with ESMTP id 47B2C37B402 for ; Mon, 11 Feb 2002 12:16:17 -0800 (PST) Received: from [192.168.1.129] (212.129.9.146) by mail.libertysurf.net (5.1.053) id 3C633FD4000B9298; Mon, 11 Feb 2002 21:12:29 +0100 Date: Sun, 10 Feb 2002 22:12:31 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: To: Frank Altpeter Cc: Subject: Re: SCSI parity error detected In-Reply-To: <20020211170640.C245@ision.net> Message-ID: <20020210215543.P1982-100000@gerard> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 11 Feb 2002, Frank Altpeter wrote: > hello! > > After many hours of testing with a good friend we didn't work out any > solution for my problem - he recommended asking you, because you are the > cracks that wrote the driver :-)) > > Well... something about my hardware first... i'm running an x86 system, > powered with a gigabyte (GA-7VTXE+) board and an Athlon XP 1500+ CPU. > There are four SCSI devices connected via a Dawicontrol DC-2945U > hostadapter (symbios 53C875 chipset). > > The device list is as follows: > > murphy# camcontrol devlist -v > scbus0 on sym0 bus 0: > at scbus0 target 0 lun 0 (pass0,da0) > at scbus0 target 1 lun 0 (pass1) > at scbus0 target 2 lun 0 (pass2) > at scbus0 target 4 lun 0 (pass3,cd0) > < > at scbus0 target -1 lun -1 () > scbus-1 on xpt0 bus 0: > < > at scbus-1 target -1 lun -1 (xpt0) > > > Target 0 is an SCSI-2 harddisk, and the targets 1 and 2 are SCA disks, > plugged in with some SCA-SCSI-2 adapter. > > The main disk (target 0) is working: > > da0 at sym0 bus 0 target 0 lun 0 > da0: Fixed Direct Access SCSI-2 device > da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled > da0: 4357MB (8925000 512 byte sectors: 255H 63S/T 555C) > > But the two other disks show up these errors: > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D11000000 SBCL=3D29 > sym0: SCSI parity error detected: SCR1=3D3 DBC=3D11000000 SBCL=3D29 > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D11000000 SBCL=3D29 > sym0: SCSI parity error detected: SCR1=3D3 DBC=3D11000000 SBCL=3D29 > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D11000000 SBCL=3D29 > sym0: SCSI parity error detected: SCR1=3D3 DBC=3D11000000 SBCL=3D29 > sym0: SCSI parity error detected: SCR1=3D1 DBC=3D11000000 SBCL=3D29 The PCI SCSI chip is reporting SCSI PARITY ERROR in DATA IN phase. > (da1:sym0:0:1:0): got CAM status 0x50 > (da1:sym0:0:1:0): fatal error, failed to attach to device > (da1:sym0:0:1:0): lost device > (da1:sym0:0:1:0): removing device entry > (da2:sym0:0:2:0): got CAM status 0x50 > (da2:sym0:0:2:0): fatal error, failed to attach to device > (da2:sym0:0:2:0): lost device > (da2:sym0:0:2:0): removing device entry > > Since i used to have an adaptec 1542cf before, i'm quite sure that the > disks and the SCA adapters are ok, because the system was running fine > with the old card (yes, i know it's a shame to run fast SCA disks with > this setting, but i got them really cheap :). The hardware combination was probably ok for the 1542, but it doesn't seem so for the 53c875. As you should|do know, there are major differences between the 2 controllers: - 1542 is 8 bit SCSI, 53c875 is 16 bit SCSI - 1542 is FAST-10, 53c875 is FAST-20. OTOH, the offending devices exhibit some *SUN* proprietary firmware. Given that SUN guys are known to be great reinventors of the wheel, we may suspect these devices to have some questionnable behaviour. Anyway, without a clear description of your SCSI BUS, I cannot really help you a lot. If we suppose that SUN guys didn't break SCSI too much here (??), the problem may be due to your SCA-to-SCSI2 tinking machines not connecting and/or terminating all signals as needed for WIDE SCSI. Another possibility could be that you are using a 8 bit SCSI BUS, but that your devices are claiming and accepting a wide negotiation. Etc..., etc... > After switching to the new motherboard, the old adaptec was unusable > because it was an ISA card (new board only supports PCI). > The CDROM was the last device in the chain and was terminating. I have > changed this now, and have terminated the chain with an active terminator > at the end of the SCSI cable. > > But, the errors keep showing up and the devices are not useable. > > Can you perhaps give me any hints on that problem? You may first check that, on paper, all SCSI BUS signals are properly, either connected, or terminated when they have to be, as expected by the 53c875 chip. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 11 13:30:19 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id C6CA837B419 for ; Mon, 11 Feb 2002 13:30:09 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id WAA24600; Mon, 11 Feb 2002 22:30:08 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g1BLPQN61061; Mon, 11 Feb 2002 22:25:26 +0100 (MET) (envelope-from j) Date: Mon, 11 Feb 2002 22:25:26 +0100 (MET) Message-Id: <200202112125.g1BLPQN61061@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <20020211170640.C245@ision.net> <20020210215543.P1982-100000@gerard> In-Reply-To: <20020210215543.P1982-100000@gerard> From: j@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: SCSI parity error detected X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Cc: Frank Altpeter Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Gérard Roudier wrote: > OTOH, the offending devices exhibit some *SUN* proprietary > firmware. Given that SUN guys are known to be great reinventors of > the wheel, we may suspect these devices to have some questionnable > behaviour. Ah no. AFAICT, all that Sun's doing here is addings their "SUNxxG" to the vendor string so their tools can quickly identify and categorize their disks. I'm using a at scbus0 target 0 lun 0 (pass0,da0) (also SCA, but sitting behind a Tekram 53c895 40 MHz LVD bus) here, and it works just great. > If we suppose that SUN guys didn't break SCSI too much here (??), > the problem may be due to your SCA-to-SCSI2 tinking machines not > connecting and/or terminating all signals as needed for WIDE SCSI. Since i was the guy advising him to ask here, i'm now already familiar with Frank's setup. ;-) He originally used a plain 8-bit configuration, his "SCA-to-SCSI2" should rather read as "SCA to 8-bit 50-pin" adapter. So there's no wide negotiation involved at all. Certainly those adapters don't terminate anything, but the disks should never enter wide mode anyway. Following my advise he changed the old configuration from using the CD-ROM's internal (passive) termination to an active plug-in terminator, which didn't help. This Dawicontrol is 8-bit only btw., despite of using an 53c875. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 11 14:43:43 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by hub.freebsd.org (Postfix) with ESMTP id B0A0537B405 for ; Mon, 11 Feb 2002 14:43:38 -0800 (PST) Received: from [192.168.1.129] (212.129.44.23) by mail.libertysurf.net (5.1.053) id 3C633E9A000BA9C4; Mon, 11 Feb 2002 23:43:28 +0100 Date: Mon, 11 Feb 2002 00:43:30 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: To: Joerg Wunsch Cc: , Frank Altpeter Subject: Re: SCSI parity error detected In-Reply-To: <200202112125.g1BLPQN61061@uriah.heep.sax.de> Message-ID: <20020211002602.I2420-100000@gerard> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 11 Feb 2002, Joerg Wunsch wrote: > G=E9rard Roudier wrote: > > > OTOH, the offending devices exhibit some *SUN* proprietary > > firmware. Given that SUN guys are known to be great reinventors of > > the wheel, we may suspect these devices to have some questionnable > > behaviour. > > Ah no. AFAICT, all that Sun's doing here is addings their "SUNxxG" to > the vendor string so their tools can quickly identify and categorize > their disks. Very probably. But it just makes their firmware suspicious. What a questionnable value-added. > I'm using a > > at scbus0 target 0 lun 0 (pass0,da0) > > (also SCA, but sitting behind a Tekram 53c895 40 MHz LVD bus) here, > and it works just great. May-be the driver understands the NVRAM setup here. I donnot know all hard disks in existence. Is this one wide capable? > > If we suppose that SUN guys didn't break SCSI too much here (??), > > the problem may be due to your SCA-to-SCSI2 tinking machines not > > connecting and/or terminating all signals as needed for WIDE SCSI. > > Since i was the guy advising him to ask here, i'm now already familiar > with Frank's setup. ;-) He originally used a plain 8-bit > configuration, his "SCA-to-SCSI2" should rather read as "SCA to 8-bit > 50-pin" adapter. So there's no wide negotiation involved at all. > Certainly those adapters don't terminate anything, but the disks > should never enter wide mode anyway. > > Following my advise he changed the old configuration from using the > CD-ROM's internal (passive) termination to an active plug-in > terminator, which didn't help. > > This Dawicontrol is 8-bit only btw., despite of using an 53c875. But the driver cannot guess it. And it doesn't understand the Dawicontrol settings from NVRAM (if some exists). Note that when the driver negotiates Wide, it negotiates also Sync immediately without any DATA phase occurring and reports the new parameters to CAM. As a result, the new transfer settings should be printed to the syslog prior to any further DATA phase. If there is no such message in the log, then the Wide+Sync negotiation should not have taken place. This point should be checked. OTOH, if there is no such message in the log, it could well be the initial INQUIRY response that got a SCSI PARITY error. The problem might then be the/a SCSI PARITY signal not being properly driven/connected. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 11 15: 0:54 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id B02C337B421 for ; Mon, 11 Feb 2002 15:00:34 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id AAA25568; Tue, 12 Feb 2002 00:00:18 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g1BMtYQ62815; Mon, 11 Feb 2002 23:55:34 +0100 (MET) (envelope-from j) Date: Mon, 11 Feb 2002 23:55:34 +0100 From: Joerg Wunsch To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: freebsd-scsi@FreeBSD.ORG, Frank Altpeter Subject: Re: SCSI parity error detected Message-ID: <20020211235534.G57760@uriah.heep.sax.de> Reply-To: Joerg Wunsch Mail-Followup-To: Joerg Wunsch , =?iso-8859-1?Q?G=E9rard_Roudier?= , freebsd-scsi@FreeBSD.ORG, Frank Altpeter References: <200202112125.g1BLPQN61061@uriah.heep.sax.de> <20020211002602.I2420-100000@gerard> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20020211002602.I2420-100000@gerard>; from groudier@free.fr on Mon, Feb 11, 2002 at 12:43:30AM +0100 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org As Gérard Roudier wrote: > > Ah no. AFAICT, all that Sun's doing here is addings their "SUNxxG" to > > the vendor string so their tools can quickly identify and categorize > > their disks. > > Very probably. But it just makes their firmware suspicious. > What a questionnable value-added. Well, from your point of view it might be questionable. From their point of view (in particular from format(1m)'s point of view) it has some value, since regardless of which vendor their "SUN9G" drive is from, they use all those drives with the same settings, so they are interchangeable in the field. They might lose a few sectors for some drive, depending on the actual model used, but that doesn't hurt much. > I donnot know all hard disks in existence. Is this one wide capable? Yep, all the Sun SCA disks are wide-capable. > But the driver cannot guess it. And it doesn't understand the > Dawicontrol settings from NVRAM (if some exists). Don't know about the NVRAM in Dawicontrol. According to Frank, it at least doesn't have much BIOS knobs. If there is NVRAM, it should never attempt to negotiate wide, since the entire controller is narrow only. > Note that when the driver negotiates Wide, it negotiates also Sync > immediately without any DATA phase occurring and reports the new > parameters to CAM. As a result, the new transfer settings should be > printed to the syslog prior to any further DATA phase. I think Frank posted all relevant messages in his initial mail. > OTOH, if there is no such message in the log, it could well be the > initial INQUIRY response that got a SCSI PARITY error. The problem > might then be the/a SCSI PARITY signal not being properly > driven/connected. Hmm, but it used to be connected with the AHA1542. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 11 18:17:40 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from newman2.bestweb.net (newman2.bestweb.net [209.94.102.67]) by hub.freebsd.org (Postfix) with ESMTP id CE3E837B43E; Mon, 11 Feb 2002 18:16:49 -0800 (PST) Received: from okeeffe.bestweb.net (okeefe.bestweb.net [209.94.100.110]) by newman2.bestweb.net (Postfix) with ESMTP id 38E5A23099; Mon, 11 Feb 2002 21:16:42 -0500 (EST) Received: by okeeffe.bestweb.net (Postfix, from userid 0) id 592F99EE45; Mon, 11 Feb 2002 21:11:44 -0500 (EST) Date: Tue, 5 Feb 2002 20:14:22 +0100 From: Thomas Quinot To: Garrett Wollman Cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG, Subject: Re: Support for atapi cdrw as scsi in -current? Reply-To: thomas@cuivre.fr.eu.org Message-Id: <20020212021144.592F99EE45@okeeffe.bestweb.net> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Is there a place where I can find this updated patch which will work for > me in the current -current? Thanks. I put up updated patches at http://www.cuivre.fr.eu.org/~thomas/atapicam/ For -CURRENT, you should be using the latest one (of today) which fixes a silly line inversion. I'd be very interested in success/failuire reports on this patch, especially with ATAPI tape or floppy drives. Thomas. -- Thomas.Quinot@Cuivre.FR.EU.ORG To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 11 18:17:51 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from newman2.bestweb.net (newman2.bestweb.net [209.94.102.67]) by hub.freebsd.org (Postfix) with ESMTP id 7DD8F37B48C; Mon, 11 Feb 2002 18:17:05 -0800 (PST) Received: from okeeffe.bestweb.net (okeefe.bestweb.net [209.94.100.110]) by newman2.bestweb.net (Postfix) with ESMTP id BAAB423185; Mon, 11 Feb 2002 21:16:48 -0500 (EST) Received: by okeeffe.bestweb.net (Postfix, from userid 0) id 043E29F29C; Mon, 11 Feb 2002 21:11:53 -0500 (EST) Date: Tue, 05 Feb 2002 12:49:06 -0600 From: Jordan Breeding To: Garrett Wollman Cc: freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Support for atapi cdrw as scsi in -current? Message-Id: <20020212021153.043E29F29C@okeeffe.bestweb.net> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Garrett Wollman wrote: > < > >>I noticed a patch on freebsd-scsi a while back that >>added a not very complete form of atapi as scsi support >>to the freebsd kernel. Are there plans to complete >>this and add it to -current sometime before -current >>turns into 5.0-RELEASE? Thanks for any information. >> > > I've been using it somewhat actively in the past week or so in > -current. The patch as it exists needs a few changes to fit in > current -current. > > $ camcontrol devlist > at scbus0 target 0 lun 0 (cd0,pass0) > at scbus0 target 1 lun 0 (cd1,pass1) > > I don't think that ATAPICAM works well enough to use it entirely in > place of the atapi-cd driver; for example, I get the following errors: > > atapicam0: READ_DISK_INFO - ILLEGAL REQUEST asc=0x20 ascq=0x00 error=0x04 > atapicam0: READ_TOC - ILLEGAL REQUEST asc=0x24 ascq=0x00 error=0x04 > > However, it works well-enough to run cdrdao, which is what mattered to > me, for both reading and writing on both of the afore-mentioned ATAPI > devices. > > -GAWollman > > > Is there a place where I can find this updated patch which will work for me in the current -current? Thanks. Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 11 20:45:54 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from 196.mudb.snfc.snfccafj.dsl.att.net (196.mudb.snfc.snfccafj.dsl.att.net [12.99.91.196]) by hub.freebsd.org (Postfix) with SMTP id 229C237B4CC for ; Mon, 11 Feb 2002 20:39:39 -0800 (PST) Received: (qmail 24297 invoked by uid 1000); 12 Feb 2002 04:38:36 -0000 Date: Mon, 11 Feb 2002 20:38:36 -0800 From: Christopher Nielsen To: Thomas Quinot Cc: Garrett Wollman , freebsd-current@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Support for atapi cdrw as scsi in -current? Message-ID: <20020212043836.GB22145@cassie.foobarbaz.net> References: <20020212021144.592F99EE45@okeeffe.bestweb.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20020212021144.592F99EE45@okeeffe.bestweb.net> User-Agent: Mutt/1.3.27i Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, Feb 05, 2002 at 08:14:22PM +0100, Thomas Quinot wrote: > > Is there a place where I can find this updated patch which will work for > > me in the current -current? Thanks. > > I put up updated patches at > http://www.cuivre.fr.eu.org/~thomas/atapicam/ > > For -CURRENT, you should be using the latest one (of today) > which fixes a silly line inversion. > > I'd be very interested in success/failuire reports on this patch, > especially with ATAPI tape or floppy drives. FYI, I applied the patch to -stable and tested it using cdrdao with my plextor 1610A. Worked like a charm. -- Christopher Nielsen - Metal-wielding pyro techie madhatter@teaparty.org "Those who are willing to trade freedom for security deserve neither freedom nor security." --Benjamin Franklin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 11 20:52:38 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail4.nc.rr.com (fe4.southeast.rr.com [24.93.67.51]) by hub.freebsd.org (Postfix) with ESMTP id 36B0837B728; Mon, 11 Feb 2002 20:46:35 -0800 (PST) Received: from i8k.babbleon.org ([66.57.85.154]) by mail4.nc.rr.com with Microsoft SMTPSVC(5.5.1877.687.68); Mon, 11 Feb 2002 22:15:55 -0500 Received: by i8k.babbleon.org (Postfix, from userid 111) id 2B772408D; Mon, 11 Feb 2002 22:10:53 -0500 (EST) Content-Type: text/plain; charset="iso-8859-1" From: Brian T.Schellenberger To: Andrew Gould , jstocker@tzi.de Subject: Re: USB drive -- problems Date: Mon, 11 Feb 2002 22:10:53 -0500 X-Mailer: KMail [version 1.3] Cc: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org References: <20020211163721.18370.qmail@web13404.mail.yahoo.com> In-Reply-To: <20020211163721.18370.qmail@web13404.mail.yahoo.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020212031053.2B772408D@i8k.babbleon.org> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Monday 11 February 2002 11:37 am, Andrew Gould wrote: > I understand neither scsi nor usb issues; but am > considering getting a usb drive for my KDS minibook pc > ( a cool little device, except for the winmodem). > > Is the problem below related to any use of usb hard > drives? Is it isolated to the use of pci usb > controllers? Am I way off base on both questions? Actually, I am no expert, but I believe that the problem below has nothing to do with USB or PCI -- that part of the equation in fact worked flawlessly without any difficulty. (I *did* build a kernel with all the proper USB support before I even bought the drive.) It's just the inside of the 80G LaCie USB drive there happens to reside a SCSI drive, and *that* had a problem. This problem, was however, very easily fixed once somebody could tell me how. > > Thanks, > > Andrew Gould > > --- "Brian T.Schellenberger" wrote: > > Bingo! > > > > That was it! It's working beautifully now. > > > > ThankyouThankyouThankyouThankyou. > > > > I'll submit the patches to a committer so I don't > > have to re-patch every time > > I upgrade the source. > > > > PS: Did you submit your patch so it can be > > integrated into the offiical > > source? > > > > PPS: Anyway know of any particular reason why > > DA_Q_NO_6_BYTE isn't just the > > default? Looking at the scsi file it sure seems > > like a large number of > > devices need this . . . at any rate it seems like it > > might be cool if i/o > > errors of this nature could be recognized and the > > feature dynamically turned > > off . . . > > > > > > PS: Just in case there's somebody on the scsi list > > who'd like to commit my > > change, my patch is attached. > > > > > > On Monday 11 February 2002 03:53 am, Jan Stocker > > > > wrote: > > > Excuse me for the late reply... > > > > > > src/sys/cam/scsi/scsi_da.c contains quirks for > > > > each da device... > > > > > ive added one for my digicam: > > > > > > { > > > /* MINOLTA DIMAGE 2330 */ > > > {T_DIRECT, SIP_MEDIA_REMOVABLE, "MINOLTA", > > > > "DIMAGE 2330*","*"}, > > > > > /*quirks*/ DA_Q_NO_6_BYTE > > > }, > > > > > > so no 6-byte commands will be send to the > > > > device... search for a device > > > > > entry similar to your disc controller, add an > > > > entry and recompile... > > > > > Jan > > > > > > P.S: Your surname looks quite german.... > > > > > > > -----Original Message----- > > > > From: Brian T.Schellenberger > > > > [mailto:bts@babbleon.org] > > > > > > Sent: Saturday, February 09, 2002 12:31 AM > > > > To: jstocker@tzi.de > > > > Subject: Re: USB drive -- problems > > > > > > > > On Monday 04 February 2002 08:00 am, you wrote: > > > > > A maybe better discussion group will be > > > > freebsd-scsi. > > > > > > > Maybe you need to turn off 6-byte commands > > > > with a quirk... > > > > > > Hmm . . . perhaps. But I'm afraid I don't even > > > > know what that means. > > > > > > Can you clarify, or tell me what I should be > > > > reading that I'm not? > > > > > > > Jan > > > > > > > > > > > PPS: Why, oh why is there a /dev/ad0 and a > > > > /dev/da0? What do > > > > > > > > they stand for? > > > > > > > > > > Okay... da is for the DirectAccess drives on > > > > USB/SCSI > > > > > > > ad represent the ATA-Drives. So ad0 is the > > > > primary-master ATA-IDE > > > > > > > drive. > > > > > > > > > > > -----Original Message----- > > > > > > From: owner-freebsd-hardware@FreeBSD.ORG > > > > [mailto:owner-freebsd-hardware@FreeBSD.ORG]On Behalf > > Of Brian > > > > > > > > T.Schellenberger > > > > > > Sent: Sunday, February 03, 2002 3:20 PM > > > > > > To: freebsd-question@FreeBSD.ORG; > > > > freebsd-hardware@FreeBSD.ORG > > > > > > > > Subject: USB drive -- problems > > > > > > > > > > > > > > > > > > > > > > > > Ok, with little confidence it would work, > > > > since I could find > > > > > > no very good > > > > > > > > > > info on USB & FreeBSD, and there was no > > > > response to my query on > > > > > > > > the subject, > > > > > > I decided in a "what the hell" moment to get > > > > a USB drive and see what > > > > > > > > happened. > > > > > > > > > > > > I have a LaCie 80G drive. It was $250 for > > > > 80, USB 2, and if > > > > > > it works it > > > > > > > > > > should be pretty darn cool. > > > > > > > > > > > > It is recognized by the kernel, so I thought > > > > I was doing > > > > > > pretty well, but > > > > > > > > > > when I try to actually do anything with it, > > > > I run into > > > > > > trouble. Here are > > > > > > > > > > some messages from /var/log messages, first > > > > hte successful > > > > > > boot stuff and > > > > > > > > > > then the failure messages: > > > > > > > > > > > > Feb 3 04:31:21 i8k /kernel: uhci0: > > > 82801BA/BAM (ICH2) USB > > > > > > > > controller > > > > > > USB-A> port 0xbce0-0xbcff irq 11 at device > > > > 31.2 on pci0 > > > > > > > > Feb 3 04:31:21 i8k /kernel: usb0: > > > 82801BA/BAM (ICH2) USB > > > > > > > > controller > > > > > > USB-A> on uhci0 > > > > > > Feb 3 04:31:21 i8k /kernel: usb0: USB > > > > revision 1.0 > > > > > > > > Feb 3 04:31:21 i8k /kernel: uhub0: Intel > > > > UHCI root hub, > > > > > > class 9/0, rev > > > > > > > > > > 1.00/1.00, addr 1 > > > > > > Feb 3 04:31:21 i8k /kernel: uhub0: 2 ports > > > > with 2 removable, self > > > > > > > > powered Feb 3 04:31:21 i8k /kernel: umass0: > > > > LaCie LaCie > > > > > > StudioDrive USB2 > > > > > > > > > > , > > > > > > rev 2.00/10.06, addr 2 > > > > > > > > > > > > > > > > > > Feb 3 04:31:21 i8k /kernel: da0 at > > > > umass-sim0 bus 0 target 0 lun 0 > > > > > > > > Feb 3 04:31:22 i8k /kernel: da0: > > > D080H4 DAH0> Fixed > > > > > > > > Direct Access > > > > > > SCSI-0 device > > > > > > Feb 3 04:31:22 i8k /kernel: da0: 650KB/s > > > > transfers > > > > > > > > Feb 3 04:31:22 i8k /kernel: da0: 78167MB > > > > (160086528 512 byte > > > > > > > > sectors: 64H > > > > > > 32S/T 12631C) > > > > > > > > > > > > > > > > > > Feb 3 05:08:48 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): READ(06). > > > > > > > > CDB: 8 0 0 0 1 > > > > > > 0 > > > > > > Feb 3 05:08:48 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): ILLEGAL > > > > > > > > REQUEST asc:21,0 > > > > > > Feb 3 05:08:48 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): Logical > > > > > > > > block address > > > > > > out of range > > > > > > Feb 3 05:08:57 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): READ(06). > > > > > > > > CDB: 8 0 0 0 1 > > > > > > 0 > > > > > > Feb 3 05:08:57 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): ILLEGAL > > > > > > > > REQUEST asc:21,0 > > > > > > Feb 3 05:08:57 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): Logical > > > > > > > > block address > > > > > > out of range > > > > > > > > > > > > The set of error messages above were > > > > returned when I did a simple > > > > > > > > dd if=/dev/da0 > > > > > > > > > > > > > > > > > > PS: I might not recieve mail for a couple > > > > days so don't be > > > > > > surprised if > > > > > > > > > > responses are a little slow. Based on > > > > previous response to USB > > > > > > > > queries on > > > > > > the questions list I doubt that excessive > > > > responses will be a big > > > > > > > > problem. > > > > > > I'm including the questions list here more > > > > as an "FYI" sort of thing. > > > > > > > > It's darn confusing and it makes me nervous > > > > as heck doing > > > > > > > > "dangerous" operations where I am one > > > > swapped letter pair away from > > > > > > > > wiping out my primary > > > > > > drive! > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Brian T. Schellenberger . . . . . . . > > > > bts@wnt.sas.com (work) > > > > > > > > Brian, the man from Babble-On . . . . > > > > bts@babbleon.org (personal) > > > > > > > > ME --> > > > > http://www.babbleon.org > > > > > > > > http://www.eff.org <-- GOOD GUYS --> > > > > > > http://www.programming-freedom.org > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to > > > > majordomo@FreeBSD.org > > > > > > > > with "unsubscribe freebsd-hardware" in the > > > > body of the message > > > > > > -- > > > > Brian T. Schellenberger . . . . . . . > > > > bts@wnt.sas.com (work) > > > > > > Brian, the man from Babble-On . . . . > > > > bts@babbleon.org (personal) > > > > > > ME --> > > > > http://www.babbleon.org > > > > > > http://www.eff.org <-- GOOD GUYS --> > > > > > > http://www.programming-freedom.org > > > > -- > > Brian T. Schellenberger . . . . . . . > > bts@wnt.sas.com (work) > > Brian, the man from Babble-On . . . . > > bts@babbleon.org (personal) > > ME --> > > http://www.babbleon.org > > http://www.eff.org <-- GOOD GUYS --> > > http://www.programming-freedom.org > > > > > *** scsi_da.c.org Mon Feb 11 07:18:39 2002 > > > > --- scsi_da.c Mon Feb 11 07:23:18 2002 > > *************** > > *** 255,265 **** > > {T_DIRECT, SIP_MEDIA_REMOVABLE, "Sony", "Sony > > DSC", "*"}, > > /*quirks*/ DA_Q_NO_6_BYTE|DA_Q_NO_SYNC_CACHE > > }, > > ! { > > /* > > * Maxtor 3000LE USB Drive > > */ > > {T_DIRECT, SIP_MEDIA_FIXED, "MAXTOR*", > > "K040H2*", "*"}, > > /*quirks*/ DA_Q_NO_6_BYTE > > }, > > { > > --- 255,272 ---- > > {T_DIRECT, SIP_MEDIA_REMOVABLE, "Sony", "Sony > > DSC", "*"}, > > /*quirks*/ DA_Q_NO_6_BYTE|DA_Q_NO_SYNC_CACHE > > }, > > ! { > > /* > > * Maxtor 3000LE USB Drive > > */ > > {T_DIRECT, SIP_MEDIA_FIXED, "MAXTOR*", > > "K040H2*", "*"}, > > + /*quirks*/ DA_Q_NO_6_BYTE > > + }, > > + { > > + /* > > + * LaCie USB drive, among others > > + */ > > + {T_DIRECT, SIP_MEDIA_FIXED, "Maxtor*", > > "D080H4*", "*"}, > > /*quirks*/ DA_Q_NO_6_BYTE > > }, > > { > > __________________________________________________ > Do You Yahoo!? > Send FREE Valentine eCards with Yahoo! Greetings! > http://greetings.yahoo.com -- Brian T. Schellenberger . . . . . . . bts@wnt.sas.com (work) Brian, the man from Babble-On . . . . bts@babbleon.org (personal) ME --> http://www.babbleon.org http://www.eff.org <-- GOOD GUYS --> http://www.programming-freedom.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 11 20:55:42 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail4.nc.rr.com (fe4.southeast.rr.com [24.93.67.51]) by hub.freebsd.org (Postfix) with ESMTP id 36B0837B728; Mon, 11 Feb 2002 20:46:35 -0800 (PST) Received: from i8k.babbleon.org ([66.57.85.154]) by mail4.nc.rr.com with Microsoft SMTPSVC(5.5.1877.687.68); Mon, 11 Feb 2002 22:15:55 -0500 Received: by i8k.babbleon.org (Postfix, from userid 111) id 2B772408D; Mon, 11 Feb 2002 22:10:53 -0500 (EST) Content-Type: text/plain; charset="iso-8859-1" From: Brian T.Schellenberger To: Andrew Gould , jstocker@tzi.de Subject: Re: USB drive -- problems Date: Mon, 11 Feb 2002 22:10:53 -0500 X-Mailer: KMail [version 1.3] Cc: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org References: <20020211163721.18370.qmail@web13404.mail.yahoo.com> In-Reply-To: <20020211163721.18370.qmail@web13404.mail.yahoo.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020212031053.2B772408D@i8k.babbleon.org> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Monday 11 February 2002 11:37 am, Andrew Gould wrote: > I understand neither scsi nor usb issues; but am > considering getting a usb drive for my KDS minibook pc > ( a cool little device, except for the winmodem). > > Is the problem below related to any use of usb hard > drives? Is it isolated to the use of pci usb > controllers? Am I way off base on both questions? Actually, I am no expert, but I believe that the problem below has nothing to do with USB or PCI -- that part of the equation in fact worked flawlessly without any difficulty. (I *did* build a kernel with all the proper USB support before I even bought the drive.) It's just the inside of the 80G LaCie USB drive there happens to reside a SCSI drive, and *that* had a problem. This problem, was however, very easily fixed once somebody could tell me how. > > Thanks, > > Andrew Gould > > --- "Brian T.Schellenberger" wrote: > > Bingo! > > > > That was it! It's working beautifully now. > > > > ThankyouThankyouThankyouThankyou. > > > > I'll submit the patches to a committer so I don't > > have to re-patch every time > > I upgrade the source. > > > > PS: Did you submit your patch so it can be > > integrated into the offiical > > source? > > > > PPS: Anyway know of any particular reason why > > DA_Q_NO_6_BYTE isn't just the > > default? Looking at the scsi file it sure seems > > like a large number of > > devices need this . . . at any rate it seems like it > > might be cool if i/o > > errors of this nature could be recognized and the > > feature dynamically turned > > off . . . > > > > > > PS: Just in case there's somebody on the scsi list > > who'd like to commit my > > change, my patch is attached. > > > > > > On Monday 11 February 2002 03:53 am, Jan Stocker > > > > wrote: > > > Excuse me for the late reply... > > > > > > src/sys/cam/scsi/scsi_da.c contains quirks for > > > > each da device... > > > > > ive added one for my digicam: > > > > > > { > > > /* MINOLTA DIMAGE 2330 */ > > > {T_DIRECT, SIP_MEDIA_REMOVABLE, "MINOLTA", > > > > "DIMAGE 2330*","*"}, > > > > > /*quirks*/ DA_Q_NO_6_BYTE > > > }, > > > > > > so no 6-byte commands will be send to the > > > > device... search for a device > > > > > entry similar to your disc controller, add an > > > > entry and recompile... > > > > > Jan > > > > > > P.S: Your surname looks quite german.... > > > > > > > -----Original Message----- > > > > From: Brian T.Schellenberger > > > > [mailto:bts@babbleon.org] > > > > > > Sent: Saturday, February 09, 2002 12:31 AM > > > > To: jstocker@tzi.de > > > > Subject: Re: USB drive -- problems > > > > > > > > On Monday 04 February 2002 08:00 am, you wrote: > > > > > A maybe better discussion group will be > > > > freebsd-scsi. > > > > > > > Maybe you need to turn off 6-byte commands > > > > with a quirk... > > > > > > Hmm . . . perhaps. But I'm afraid I don't even > > > > know what that means. > > > > > > Can you clarify, or tell me what I should be > > > > reading that I'm not? > > > > > > > Jan > > > > > > > > > > > PPS: Why, oh why is there a /dev/ad0 and a > > > > /dev/da0? What do > > > > > > > > they stand for? > > > > > > > > > > Okay... da is for the DirectAccess drives on > > > > USB/SCSI > > > > > > > ad represent the ATA-Drives. So ad0 is the > > > > primary-master ATA-IDE > > > > > > > drive. > > > > > > > > > > > -----Original Message----- > > > > > > From: owner-freebsd-hardware@FreeBSD.ORG > > > > [mailto:owner-freebsd-hardware@FreeBSD.ORG]On Behalf > > Of Brian > > > > > > > > T.Schellenberger > > > > > > Sent: Sunday, February 03, 2002 3:20 PM > > > > > > To: freebsd-question@FreeBSD.ORG; > > > > freebsd-hardware@FreeBSD.ORG > > > > > > > > Subject: USB drive -- problems > > > > > > > > > > > > > > > > > > > > > > > > Ok, with little confidence it would work, > > > > since I could find > > > > > > no very good > > > > > > > > > > info on USB & FreeBSD, and there was no > > > > response to my query on > > > > > > > > the subject, > > > > > > I decided in a "what the hell" moment to get > > > > a USB drive and see what > > > > > > > > happened. > > > > > > > > > > > > I have a LaCie 80G drive. It was $250 for > > > > 80, USB 2, and if > > > > > > it works it > > > > > > > > > > should be pretty darn cool. > > > > > > > > > > > > It is recognized by the kernel, so I thought > > > > I was doing > > > > > > pretty well, but > > > > > > > > > > when I try to actually do anything with it, > > > > I run into > > > > > > trouble. Here are > > > > > > > > > > some messages from /var/log messages, first > > > > hte successful > > > > > > boot stuff and > > > > > > > > > > then the failure messages: > > > > > > > > > > > > Feb 3 04:31:21 i8k /kernel: uhci0: > > > 82801BA/BAM (ICH2) USB > > > > > > > > controller > > > > > > USB-A> port 0xbce0-0xbcff irq 11 at device > > > > 31.2 on pci0 > > > > > > > > Feb 3 04:31:21 i8k /kernel: usb0: > > > 82801BA/BAM (ICH2) USB > > > > > > > > controller > > > > > > USB-A> on uhci0 > > > > > > Feb 3 04:31:21 i8k /kernel: usb0: USB > > > > revision 1.0 > > > > > > > > Feb 3 04:31:21 i8k /kernel: uhub0: Intel > > > > UHCI root hub, > > > > > > class 9/0, rev > > > > > > > > > > 1.00/1.00, addr 1 > > > > > > Feb 3 04:31:21 i8k /kernel: uhub0: 2 ports > > > > with 2 removable, self > > > > > > > > powered Feb 3 04:31:21 i8k /kernel: umass0: > > > > LaCie LaCie > > > > > > StudioDrive USB2 > > > > > > > > > > , > > > > > > rev 2.00/10.06, addr 2 > > > > > > > > > > > > > > > > > > Feb 3 04:31:21 i8k /kernel: da0 at > > > > umass-sim0 bus 0 target 0 lun 0 > > > > > > > > Feb 3 04:31:22 i8k /kernel: da0: > > > D080H4 DAH0> Fixed > > > > > > > > Direct Access > > > > > > SCSI-0 device > > > > > > Feb 3 04:31:22 i8k /kernel: da0: 650KB/s > > > > transfers > > > > > > > > Feb 3 04:31:22 i8k /kernel: da0: 78167MB > > > > (160086528 512 byte > > > > > > > > sectors: 64H > > > > > > 32S/T 12631C) > > > > > > > > > > > > > > > > > > Feb 3 05:08:48 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): READ(06). > > > > > > > > CDB: 8 0 0 0 1 > > > > > > 0 > > > > > > Feb 3 05:08:48 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): ILLEGAL > > > > > > > > REQUEST asc:21,0 > > > > > > Feb 3 05:08:48 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): Logical > > > > > > > > block address > > > > > > out of range > > > > > > Feb 3 05:08:57 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): READ(06). > > > > > > > > CDB: 8 0 0 0 1 > > > > > > 0 > > > > > > Feb 3 05:08:57 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): ILLEGAL > > > > > > > > REQUEST asc:21,0 > > > > > > Feb 3 05:08:57 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): Logical > > > > > > > > block address > > > > > > out of range > > > > > > > > > > > > The set of error messages above were > > > > returned when I did a simple > > > > > > > > dd if=/dev/da0 > > > > > > > > > > > > > > > > > > PS: I might not recieve mail for a couple > > > > days so don't be > > > > > > surprised if > > > > > > > > > > responses are a little slow. Based on > > > > previous response to USB > > > > > > > > queries on > > > > > > the questions list I doubt that excessive > > > > responses will be a big > > > > > > > > problem. > > > > > > I'm including the questions list here more > > > > as an "FYI" sort of thing. > > > > > > > > It's darn confusing and it makes me nervous > > > > as heck doing > > > > > > > > "dangerous" operations where I am one > > > > swapped letter pair away from > > > > > > > > wiping out my primary > > > > > > drive! > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Brian T. Schellenberger . . . . . . . > > > > bts@wnt.sas.com (work) > > > > > > > > Brian, the man from Babble-On . . . . > > > > bts@babbleon.org (personal) > > > > > > > > ME --> > > > > http://www.babbleon.org > > > > > > > > http://www.eff.org <-- GOOD GUYS --> > > > > > > http://www.programming-freedom.org > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to > > > > majordomo@FreeBSD.org > > > > > > > > with "unsubscribe freebsd-hardware" in the > > > > body of the message > > > > > > -- > > > > Brian T. Schellenberger . . . . . . . > > > > bts@wnt.sas.com (work) > > > > > > Brian, the man from Babble-On . . . . > > > > bts@babbleon.org (personal) > > > > > > ME --> > > > > http://www.babbleon.org > > > > > > http://www.eff.org <-- GOOD GUYS --> > > > > > > http://www.programming-freedom.org > > > > -- > > Brian T. Schellenberger . . . . . . . > > bts@wnt.sas.com (work) > > Brian, the man from Babble-On . . . . > > bts@babbleon.org (personal) > > ME --> > > http://www.babbleon.org > > http://www.eff.org <-- GOOD GUYS --> > > http://www.programming-freedom.org > > > > > *** scsi_da.c.org Mon Feb 11 07:18:39 2002 > > > > --- scsi_da.c Mon Feb 11 07:23:18 2002 > > *************** > > *** 255,265 **** > > {T_DIRECT, SIP_MEDIA_REMOVABLE, "Sony", "Sony > > DSC", "*"}, > > /*quirks*/ DA_Q_NO_6_BYTE|DA_Q_NO_SYNC_CACHE > > }, > > ! { > > /* > > * Maxtor 3000LE USB Drive > > */ > > {T_DIRECT, SIP_MEDIA_FIXED, "MAXTOR*", > > "K040H2*", "*"}, > > /*quirks*/ DA_Q_NO_6_BYTE > > }, > > { > > --- 255,272 ---- > > {T_DIRECT, SIP_MEDIA_REMOVABLE, "Sony", "Sony > > DSC", "*"}, > > /*quirks*/ DA_Q_NO_6_BYTE|DA_Q_NO_SYNC_CACHE > > }, > > ! { > > /* > > * Maxtor 3000LE USB Drive > > */ > > {T_DIRECT, SIP_MEDIA_FIXED, "MAXTOR*", > > "K040H2*", "*"}, > > + /*quirks*/ DA_Q_NO_6_BYTE > > + }, > > + { > > + /* > > + * LaCie USB drive, among others > > + */ > > + {T_DIRECT, SIP_MEDIA_FIXED, "Maxtor*", > > "D080H4*", "*"}, > > /*quirks*/ DA_Q_NO_6_BYTE > > }, > > { > > __________________________________________________ > Do You Yahoo!? > Send FREE Valentine eCards with Yahoo! Greetings! > http://greetings.yahoo.com -- Brian T. Schellenberger . . . . . . . bts@wnt.sas.com (work) Brian, the man from Babble-On . . . . bts@babbleon.org (personal) ME --> http://www.babbleon.org http://www.eff.org <-- GOOD GUYS --> http://www.programming-freedom.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 11 20:59:12 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail4.nc.rr.com (fe4.southeast.rr.com [24.93.67.51]) by hub.freebsd.org (Postfix) with ESMTP id 36B0837B728; Mon, 11 Feb 2002 20:46:35 -0800 (PST) Received: from i8k.babbleon.org ([66.57.85.154]) by mail4.nc.rr.com with Microsoft SMTPSVC(5.5.1877.687.68); Mon, 11 Feb 2002 22:15:55 -0500 Received: by i8k.babbleon.org (Postfix, from userid 111) id 2B772408D; Mon, 11 Feb 2002 22:10:53 -0500 (EST) Content-Type: text/plain; charset="iso-8859-1" From: Brian T.Schellenberger To: Andrew Gould , jstocker@tzi.de Subject: Re: USB drive -- problems Date: Mon, 11 Feb 2002 22:10:53 -0500 X-Mailer: KMail [version 1.3] Cc: freebsd-questions@freebsd.org, freebsd-scsi@freebsd.org References: <20020211163721.18370.qmail@web13404.mail.yahoo.com> In-Reply-To: <20020211163721.18370.qmail@web13404.mail.yahoo.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Message-Id: <20020212031053.2B772408D@i8k.babbleon.org> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Monday 11 February 2002 11:37 am, Andrew Gould wrote: > I understand neither scsi nor usb issues; but am > considering getting a usb drive for my KDS minibook pc > ( a cool little device, except for the winmodem). > > Is the problem below related to any use of usb hard > drives? Is it isolated to the use of pci usb > controllers? Am I way off base on both questions? Actually, I am no expert, but I believe that the problem below has nothing to do with USB or PCI -- that part of the equation in fact worked flawlessly without any difficulty. (I *did* build a kernel with all the proper USB support before I even bought the drive.) It's just the inside of the 80G LaCie USB drive there happens to reside a SCSI drive, and *that* had a problem. This problem, was however, very easily fixed once somebody could tell me how. > > Thanks, > > Andrew Gould > > --- "Brian T.Schellenberger" wrote: > > Bingo! > > > > That was it! It's working beautifully now. > > > > ThankyouThankyouThankyouThankyou. > > > > I'll submit the patches to a committer so I don't > > have to re-patch every time > > I upgrade the source. > > > > PS: Did you submit your patch so it can be > > integrated into the offiical > > source? > > > > PPS: Anyway know of any particular reason why > > DA_Q_NO_6_BYTE isn't just the > > default? Looking at the scsi file it sure seems > > like a large number of > > devices need this . . . at any rate it seems like it > > might be cool if i/o > > errors of this nature could be recognized and the > > feature dynamically turned > > off . . . > > > > > > PS: Just in case there's somebody on the scsi list > > who'd like to commit my > > change, my patch is attached. > > > > > > On Monday 11 February 2002 03:53 am, Jan Stocker > > > > wrote: > > > Excuse me for the late reply... > > > > > > src/sys/cam/scsi/scsi_da.c contains quirks for > > > > each da device... > > > > > ive added one for my digicam: > > > > > > { > > > /* MINOLTA DIMAGE 2330 */ > > > {T_DIRECT, SIP_MEDIA_REMOVABLE, "MINOLTA", > > > > "DIMAGE 2330*","*"}, > > > > > /*quirks*/ DA_Q_NO_6_BYTE > > > }, > > > > > > so no 6-byte commands will be send to the > > > > device... search for a device > > > > > entry similar to your disc controller, add an > > > > entry and recompile... > > > > > Jan > > > > > > P.S: Your surname looks quite german.... > > > > > > > -----Original Message----- > > > > From: Brian T.Schellenberger > > > > [mailto:bts@babbleon.org] > > > > > > Sent: Saturday, February 09, 2002 12:31 AM > > > > To: jstocker@tzi.de > > > > Subject: Re: USB drive -- problems > > > > > > > > On Monday 04 February 2002 08:00 am, you wrote: > > > > > A maybe better discussion group will be > > > > freebsd-scsi. > > > > > > > Maybe you need to turn off 6-byte commands > > > > with a quirk... > > > > > > Hmm . . . perhaps. But I'm afraid I don't even > > > > know what that means. > > > > > > Can you clarify, or tell me what I should be > > > > reading that I'm not? > > > > > > > Jan > > > > > > > > > > > PPS: Why, oh why is there a /dev/ad0 and a > > > > /dev/da0? What do > > > > > > > > they stand for? > > > > > > > > > > Okay... da is for the DirectAccess drives on > > > > USB/SCSI > > > > > > > ad represent the ATA-Drives. So ad0 is the > > > > primary-master ATA-IDE > > > > > > > drive. > > > > > > > > > > > -----Original Message----- > > > > > > From: owner-freebsd-hardware@FreeBSD.ORG > > > > [mailto:owner-freebsd-hardware@FreeBSD.ORG]On Behalf > > Of Brian > > > > > > > > T.Schellenberger > > > > > > Sent: Sunday, February 03, 2002 3:20 PM > > > > > > To: freebsd-question@FreeBSD.ORG; > > > > freebsd-hardware@FreeBSD.ORG > > > > > > > > Subject: USB drive -- problems > > > > > > > > > > > > > > > > > > > > > > > > Ok, with little confidence it would work, > > > > since I could find > > > > > > no very good > > > > > > > > > > info on USB & FreeBSD, and there was no > > > > response to my query on > > > > > > > > the subject, > > > > > > I decided in a "what the hell" moment to get > > > > a USB drive and see what > > > > > > > > happened. > > > > > > > > > > > > I have a LaCie 80G drive. It was $250 for > > > > 80, USB 2, and if > > > > > > it works it > > > > > > > > > > should be pretty darn cool. > > > > > > > > > > > > It is recognized by the kernel, so I thought > > > > I was doing > > > > > > pretty well, but > > > > > > > > > > when I try to actually do anything with it, > > > > I run into > > > > > > trouble. Here are > > > > > > > > > > some messages from /var/log messages, first > > > > hte successful > > > > > > boot stuff and > > > > > > > > > > then the failure messages: > > > > > > > > > > > > Feb 3 04:31:21 i8k /kernel: uhci0: > > > 82801BA/BAM (ICH2) USB > > > > > > > > controller > > > > > > USB-A> port 0xbce0-0xbcff irq 11 at device > > > > 31.2 on pci0 > > > > > > > > Feb 3 04:31:21 i8k /kernel: usb0: > > > 82801BA/BAM (ICH2) USB > > > > > > > > controller > > > > > > USB-A> on uhci0 > > > > > > Feb 3 04:31:21 i8k /kernel: usb0: USB > > > > revision 1.0 > > > > > > > > Feb 3 04:31:21 i8k /kernel: uhub0: Intel > > > > UHCI root hub, > > > > > > class 9/0, rev > > > > > > > > > > 1.00/1.00, addr 1 > > > > > > Feb 3 04:31:21 i8k /kernel: uhub0: 2 ports > > > > with 2 removable, self > > > > > > > > powered Feb 3 04:31:21 i8k /kernel: umass0: > > > > LaCie LaCie > > > > > > StudioDrive USB2 > > > > > > > > > > , > > > > > > rev 2.00/10.06, addr 2 > > > > > > > > > > > > > > > > > > Feb 3 04:31:21 i8k /kernel: da0 at > > > > umass-sim0 bus 0 target 0 lun 0 > > > > > > > > Feb 3 04:31:22 i8k /kernel: da0: > > > D080H4 DAH0> Fixed > > > > > > > > Direct Access > > > > > > SCSI-0 device > > > > > > Feb 3 04:31:22 i8k /kernel: da0: 650KB/s > > > > transfers > > > > > > > > Feb 3 04:31:22 i8k /kernel: da0: 78167MB > > > > (160086528 512 byte > > > > > > > > sectors: 64H > > > > > > 32S/T 12631C) > > > > > > > > > > > > > > > > > > Feb 3 05:08:48 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): READ(06). > > > > > > > > CDB: 8 0 0 0 1 > > > > > > 0 > > > > > > Feb 3 05:08:48 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): ILLEGAL > > > > > > > > REQUEST asc:21,0 > > > > > > Feb 3 05:08:48 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): Logical > > > > > > > > block address > > > > > > out of range > > > > > > Feb 3 05:08:57 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): READ(06). > > > > > > > > CDB: 8 0 0 0 1 > > > > > > 0 > > > > > > Feb 3 05:08:57 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): ILLEGAL > > > > > > > > REQUEST asc:21,0 > > > > > > Feb 3 05:08:57 i8k /kernel: > > > > (da0:umass-sim0:0:0:0): Logical > > > > > > > > block address > > > > > > out of range > > > > > > > > > > > > The set of error messages above were > > > > returned when I did a simple > > > > > > > > dd if=/dev/da0 > > > > > > > > > > > > > > > > > > PS: I might not recieve mail for a couple > > > > days so don't be > > > > > > surprised if > > > > > > > > > > responses are a little slow. Based on > > > > previous response to USB > > > > > > > > queries on > > > > > > the questions list I doubt that excessive > > > > responses will be a big > > > > > > > > problem. > > > > > > I'm including the questions list here more > > > > as an "FYI" sort of thing. > > > > > > > > It's darn confusing and it makes me nervous > > > > as heck doing > > > > > > > > "dangerous" operations where I am one > > > > swapped letter pair away from > > > > > > > > wiping out my primary > > > > > > drive! > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > Brian T. Schellenberger . . . . . . . > > > > bts@wnt.sas.com (work) > > > > > > > > Brian, the man from Babble-On . . . . > > > > bts@babbleon.org (personal) > > > > > > > > ME --> > > > > http://www.babbleon.org > > > > > > > > http://www.eff.org <-- GOOD GUYS --> > > > > > > http://www.programming-freedom.org > > > > > > > > > > > > > > > > > > To Unsubscribe: send mail to > > > > majordomo@FreeBSD.org > > > > > > > > with "unsubscribe freebsd-hardware" in the > > > > body of the message > > > > > > -- > > > > Brian T. Schellenberger . . . . . . . > > > > bts@wnt.sas.com (work) > > > > > > Brian, the man from Babble-On . . . . > > > > bts@babbleon.org (personal) > > > > > > ME --> > > > > http://www.babbleon.org > > > > > > http://www.eff.org <-- GOOD GUYS --> > > > > > > http://www.programming-freedom.org > > > > -- > > Brian T. Schellenberger . . . . . . . > > bts@wnt.sas.com (work) > > Brian, the man from Babble-On . . . . > > bts@babbleon.org (personal) > > ME --> > > http://www.babbleon.org > > http://www.eff.org <-- GOOD GUYS --> > > http://www.programming-freedom.org > > > > > *** scsi_da.c.org Mon Feb 11 07:18:39 2002 > > > > --- scsi_da.c Mon Feb 11 07:23:18 2002 > > *************** > > *** 255,265 **** > > {T_DIRECT, SIP_MEDIA_REMOVABLE, "Sony", "Sony > > DSC", "*"}, > > /*quirks*/ DA_Q_NO_6_BYTE|DA_Q_NO_SYNC_CACHE > > }, > > ! { > > /* > > * Maxtor 3000LE USB Drive > > */ > > {T_DIRECT, SIP_MEDIA_FIXED, "MAXTOR*", > > "K040H2*", "*"}, > > /*quirks*/ DA_Q_NO_6_BYTE > > }, > > { > > --- 255,272 ---- > > {T_DIRECT, SIP_MEDIA_REMOVABLE, "Sony", "Sony > > DSC", "*"}, > > /*quirks*/ DA_Q_NO_6_BYTE|DA_Q_NO_SYNC_CACHE > > }, > > ! { > > /* > > * Maxtor 3000LE USB Drive > > */ > > {T_DIRECT, SIP_MEDIA_FIXED, "MAXTOR*", > > "K040H2*", "*"}, > > + /*quirks*/ DA_Q_NO_6_BYTE > > + }, > > + { > > + /* > > + * LaCie USB drive, among others > > + */ > > + {T_DIRECT, SIP_MEDIA_FIXED, "Maxtor*", > > "D080H4*", "*"}, > > /*quirks*/ DA_Q_NO_6_BYTE > > }, > > { > > __________________________________________________ > Do You Yahoo!? > Send FREE Valentine eCards with Yahoo! Greetings! > http://greetings.yahoo.com -- Brian T. Schellenberger . . . . . . . bts@wnt.sas.com (work) Brian, the man from Babble-On . . . . bts@babbleon.org (personal) ME --> http://www.babbleon.org http://www.eff.org <-- GOOD GUYS --> http://www.programming-freedom.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 12 1:37:17 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from gatesrv.RZ.UniBw-Muenchen.de (gatesrv.RZ.UniBw-Muenchen.de [137.193.11.27]) by hub.freebsd.org (Postfix) with ESMTP id B3A8C37B427 for ; Tue, 12 Feb 2002 01:37:13 -0800 (PST) Received: from medusa.informatik.unibw-muenchen.de (medusa.Informatik.UniBw-Muenchen.de [137.193.60.34]) by gatesrv.RZ.UniBw-Muenchen.de (8.11.2/8.11.2) with SMTP id g1C9T3E15167 for ; Tue, 12 Feb 2002 10:29:04 +0100 (MET) Received: (qmail 509 invoked by uid 216); 12 Feb 2002 09:28:51 -0000 To: thomas@cuivre.fr.eu.org Cc: freebsd-current@freebsd.org, freebsd-scsi@freebsd.org Subject: Re: Support for atapi cdrw as scsi in -current? References: <20020212021144.592F99EE45@okeeffe.bestweb.net> From: Lutz Bichler In-Reply-To: <20020212021144.592F99EE45@okeeffe.bestweb.net> Date: 12 Feb 2002 10:28:51 +0100 Message-ID: Lines: 18 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hi, i tested your patch onn 4.5-stable with TOSHIBA SD-M1502 (master) and PIONEER DVR-103 (slave). Unfortunately the system hangs at boot time after (noperiph:atapi1:0:-1:-1): Registered SIM for ata1 Any ideas? Lutz -- Lutz Bichler Institute for Software Technology, Department of Computer Science University of the Federal Armed Forces Munich, D-85577 Neubiberg, Germany TEL/FAX: +49(0)89 6004-2261/-4447, NET: lutz@informatik.unibw-muenchen.de To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 12 6:15:12 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from ct980320-b.blmngtn1.in.home.com (ct980320-b.blmngtn1.in.home.com [65.8.207.32]) by hub.freebsd.org (Postfix) with ESMTP id 1E2A337B41A for ; Tue, 12 Feb 2002 06:15:05 -0800 (PST) Received: (from mikes@localhost) by ct980320-b.blmngtn1.in.home.com (8.11.6/8.11.4) id g1CECYT40262; Tue, 12 Feb 2002 09:12:34 -0500 (EST) (envelope-from mikes) From: Mike Squires Message-Id: <200202121412.g1CECYT40262@ct980320-b.blmngtn1.in.home.com> Subject: Re: SCSI parity error detected In-Reply-To: <20020211170640.C245@ision.net> "from Frank Altpeter at Feb 11, 2002 05:06:40 pm" To: Frank Altpeter Date: Tue, 12 Feb 2002 09:12:34 -0500 (EST) Cc: FreeBSD SCSI X-Mailer: ELM [version 2.4ME+ PL88 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Frank Altpeter > > Since i used to have an adaptec 1542cf before, i'm quite sure that the > disks and the SCA adapters are ok, because the system was running fine This really sounds like hardware to me. I have seen comments that the SCA adaptors are problematic, especially if the bus is set to high speed; the 154X series defaulted to something like 5MB/sec unless you changed BIOS defaults, since most motherboards had lousy DMA implementations. Sometimes the solutions don't make any sense; I used at one time the Archive 458xNP DAT autoloaders with FreeBSD and Win NT and I never could get them to work properly with their internal terminators, but they worked perfectly when terminated with an old NEC SCSI CD-ROM (controllers were always Adaptec 2940UW's). If this system were mine I would replace the SCSI controller with one of the Symbios/LSI/NCR PCI controllers with both 68 and 50 pin connectors; in the U.S. they run about $30. I would also replace both SCA adaptors with 68-pin variants. Again, in the US, I've seen these for about $20. I'm currently running 4.5-STABLE with 4 ST410800WD's (Sun surplus) off a DPT SmartRAID IV controller and an NEC CD-ROM and ADIC VLS DLT tape changer off an Adaptec 2940UW; motherboard is SM P6DLH. System has been running under various 4.x versions for more than a year, absolutely rock solid. MLS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 12 11:42:29 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id 2FAF037B419 for ; Tue, 12 Feb 2002 11:42:23 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id UAA13674 for freebsd-scsi@freebsd.org; Tue, 12 Feb 2002 20:40:04 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g1CJXCF87301; Tue, 12 Feb 2002 20:33:12 +0100 (MET) (envelope-from j) Date: Tue, 12 Feb 2002 20:33:12 +0100 (MET) Message-Id: <200202121933.g1CJXCF87301@uriah.heep.sax.de> Mime-Version: 1.0 X-Newsreader: knews 1.0b.1 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) Organization: Private BSD site, Dresden X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E References: <200202112125.g1BLPQN61061@uriah.heep.sax.de> <20020211002602.I2420-100000@gerard> From: j@uriah.heep.sax.de (Joerg Wunsch) Subject: Re: SCSI parity error detected X-Original-Newsgroups: local.freebsd.scsi To: freebsd-scsi@freebsd.org Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Gérard Roudier wrote: >> This Dawicontrol is 8-bit only btw., despite of using an 53c875. > But the driver cannot guess it. And it doesn't understand the > Dawicontrol settings from NVRAM (if some exists). But don't we have a problem here then? The controller uses a chip that could do 16 bit, but has only an 8-bit bus attached. Since there's no NVRAM on it, there's no chance for the driver to tell this. As soon as another 16-bit capable device appears, this device would also try to negotiate 16-bit when asked for (since it doesn't know about the 8-bitness of its bus adapter), and there's no chance for user intervention to tell the controller to restrict everything to 8 bit. > OTOH, if there is no such message in the log, it could well be the > initial INQUIRY response that got a SCSI PARITY error. The problem > might then be the/a SCSI PARITY signal not being properly > driven/connected. What happens if the upper 8 bit are just terminated only on the controller? Would this generate a parity error? Sure, that controller looks fairly crappy by design to me (Frank meanwhile replaced it by a better one), but since we claim we support the entire Symbios Logic line, we IMHO should offer a method to fallback to safe defaults. (For -current, could perhaps be done in the device hints, but that'd cause a chicken-and-egg problem when installing.) -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 12 12:12: 6 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by hub.freebsd.org (Postfix) with ESMTP id AA61137B405 for ; Tue, 12 Feb 2002 12:12:00 -0800 (PST) Received: from [192.168.1.129] (212.129.8.3) by mail.libertysurf.net (5.1.053) id 3C633F88000ED2C3; Tue, 12 Feb 2002 20:53:57 +0100 Date: Mon, 11 Feb 2002 21:53:55 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: To: Joerg Wunsch Cc: , Frank Altpeter Subject: Re: SCSI parity error detected In-Reply-To: <20020211235534.G57760@uriah.heep.sax.de> Message-ID: <20020211213743.N1867-100000@gerard> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 11 Feb 2002, Joerg Wunsch wrote: > As G=E9rard Roudier wrote: > > > > Ah no. AFAICT, all that Sun's doing here is addings their "SUNxxG" t= o > > > the vendor string so their tools can quickly identify and categorize > > > their disks. > > > > Very probably. But it just makes their firmware suspicious. > > What a questionnable value-added. > > Well, from your point of view it might be questionable. From their > point of view (in particular from format(1m)'s point of view) it has > some value, since regardless of which vendor their "SUN9G" drive is > from, they use all those drives with the same settings, so they are > interchangeable in the field. They might lose a few sectors for some > drive, depending on the actual model used, but that doesn't hurt much. If your explanation is true, then this looks to me not only questionnable, but highly stupid. :-) > > I donnot know all hard disks in existence. Is this one wide capable? > > Yep, all the Sun SCA disks are wide-capable. > > > But the driver cannot guess it. And it doesn't understand the > > Dawicontrol settings from NVRAM (if some exists). > > Don't know about the NVRAM in Dawicontrol. According to Frank, it at > least doesn't have much BIOS knobs. If there is NVRAM, it should > never attempt to negotiate wide, since the entire controller is narrow > only. Dawicontrol uses proprietary BIOS and setup area not supported by the driver. Their BIOS very probably knows that the upper lines of the 53c875 that is _wide_ are not connected to the SCSI BUS. But the sym driver does not detect this. This could be achieved, for example, by providing a specific sub-vendor id. But for now, I donnot know if their controller provides such information. As a result, the sym driver does consider your 53c875 as wide-capable and will negotiate Wide for devices that say they support wide in their INQUIRY response. (In fact, it is CAM that tells the driver to negotiate Wide for device that report Wide capability, providing that the driver reported such a user setting for the device) > > Note that when the driver negotiates Wide, it negotiates also Sync > > immediately without any DATA phase occurring and reports the new > > parameters to CAM. As a result, the new transfer settings should be > > printed to the syslog prior to any further DATA phase. > > I think Frank posted all relevant messages in his initial mail. > > > OTOH, if there is no such message in the log, it could well be the > > initial INQUIRY response that got a SCSI PARITY error. The problem > > might then be the/a SCSI PARITY signal not being properly > > driven/connected. > > Hmm, but it used to be connected with the AHA1542. The AHA1542 will never negotiate Wide for the simple reason it is only Narrow-capable. In order to check the possible Wide nego. issue, the driver source can be hacked, for example, as follows: --- sym_conf.h.orig=09Sun Dec 2 16:21:07 2001 +++ sym_conf.h=09Mon Feb 11 21:49:46 2002 @@ -146,7 +146,7 @@ /* * Max wide order. */ -#define SYM_SETUP_MAX_WIDE=09(1) +#define SYM_SETUP_MAX_WIDE=09(0) /* * Max SCSI offset. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 12 12:25: 4 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id C59C137B41C for ; Tue, 12 Feb 2002 12:24:44 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id VAA14166; Tue, 12 Feb 2002 21:20:12 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g1CKGbF88226; Tue, 12 Feb 2002 21:16:37 +0100 (MET) (envelope-from j) Date: Tue, 12 Feb 2002 21:16:37 +0100 From: Joerg Wunsch To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: freebsd-scsi@FreeBSD.ORG, Frank Altpeter Subject: Re: SCSI parity error detected Message-ID: <20020212211637.L74623@uriah.heep.sax.de> Reply-To: Joerg Wunsch Mail-Followup-To: Joerg Wunsch , =?iso-8859-1?Q?G=E9rard_Roudier?= , freebsd-scsi@FreeBSD.ORG, Frank Altpeter References: <20020211235534.G57760@uriah.heep.sax.de> <20020211213743.N1867-100000@gerard> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20020211213743.N1867-100000@gerard>; from groudier@free.fr on Mon, Feb 11, 2002 at 09:53:55PM +0100 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org As Gérard Roudier wrote: > Dawicontrol uses proprietary BIOS and setup area not supported by > the driver. Their BIOS very probably knows that the upper lines of > the 53c875 that is _wide_ are not connected to the SCSI BUS. That would be my guess, too. > But the sym driver does not detect this. This could be achieved, for > example, by providing a specific sub-vendor id. But for now, I > donnot know if their controller provides such information. Hmm, maybe Frank still has the output of a verbose boot that includes the PCI registers... > In order to check the possible Wide nego. issue, the driver source can be > hacked, for example, as follows: > > --- sym_conf.h.orig Sun Dec 2 16:21:07 2001 > +++ sym_conf.h Mon Feb 11 21:49:46 2002 > @@ -146,7 +146,7 @@ > /* > * Max wide order. > */ > -#define SYM_SETUP_MAX_WIDE (1) > +#define SYM_SETUP_MAX_WIDE (0) Ah, so see my other mail, that would be the required tunable e. g. for the device hints... -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 12 15: 2:52 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mail.libertysurf.net (mail.libertysurf.net [213.36.80.91]) by hub.freebsd.org (Postfix) with ESMTP id D6C9637B48B for ; Tue, 12 Feb 2002 15:02:41 -0800 (PST) Received: from [192.168.1.129] (212.129.8.3) by mail.libertysurf.net (5.1.053) id 3C6959160000DE37; Wed, 13 Feb 2002 00:02:36 +0100 Date: Tue, 12 Feb 2002 01:02:35 +0100 (CET) From: =?ISO-8859-1?Q?G=E9rard_Roudier?= X-X-Sender: To: Joerg Wunsch Cc: Subject: Re: SCSI parity error detected In-Reply-To: <200202121933.g1CJXCF87301@uriah.heep.sax.de> Message-ID: <20020212004513.X2315-100000@gerard> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Tue, 12 Feb 2002, Joerg Wunsch wrote: > G=E9rard Roudier wrote: > > >> This Dawicontrol is 8-bit only btw., despite of using an 53c875. > > > But the driver cannot guess it. And it doesn't understand the > > Dawicontrol settings from NVRAM (if some exists). > > But don't we have a problem here then? May-be. If you can get the NVRAM layout and some data sheet about a possible NVRAM type, let me know. ;) Btw, if Dawicontrol uses PCI sub-vendor ids or some GPIO specific wiring to identify their controller, I can let the driver probe such kind of stuff. But unfortunately, I have exactly no info about those controllers. > The controller uses a chip that could do 16 bit, but has only an 8-bit > bus attached. Since there's no NVRAM on it, there's no chance for the > driver to tell this. As soon as another 16-bit capable device > appears, this device would also try to negotiate 16-bit when asked for > (since it doesn't know about the 8-bitness of its bus adapter), and > there's no chance for user intervention to tell the controller to > restrict everything to 8 bit. Btw, under Linux, this can be achieved using boot command parameters. Under FreeBSD, such facility didn't exist at the time I worked on that. Note that this can be achieved from the kernel config file using appropriate SYM_* defines and building a custom driver. (user can look into sym_conf.h file. There are tons of options) > > OTOH, if there is no such message in the log, it could well be the > > initial INQUIRY response that got a SCSI PARITY error. The problem > > might then be the/a SCSI PARITY signal not being properly > > driven/connected. > > What happens if the upper 8 bit are just terminated only on the > controller? Would this generate a parity error? There is no risk as long as no device accepts a Wide Negotiation. If one does, boom!! > Sure, that controller looks fairly crappy by design to me (Frank > meanwhile replaced it by a better one), but since we claim we > support the entire Symbios Logic line, we IMHO should offer a > method to fallback to safe defaults. (For -current, could perhaps > be done in the device hints, but that'd cause a chicken-and-egg > problem when installing.) The crappyness is to use undocumented stuff, in my opinion. Will look into device hints again. Last time I did, this didn't fit. The safe default it to use hardware correctly. A SCA adapter that shrinks 16 bits BUS to 8 bit BUS, device being connected on the 16 bit side and a Wide controller castrated to 8 bit connected to the 8 bit is an horror that fails as expected. G=E9rard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 13 3:40:10 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (Postfix) with ESMTP id B3D2537B400 for ; Wed, 13 Feb 2002 03:40:05 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.9.3/8.9.3) with UUCP id MAA18243; Wed, 13 Feb 2002 12:40:02 +0100 (CET) Received: (from j@localhost) by uriah.heep.sax.de (8.11.6/8.11.6) id g1DBY9N08738; Wed, 13 Feb 2002 12:34:09 +0100 (MET) (envelope-from j) Date: Wed, 13 Feb 2002 12:34:09 +0100 From: Joerg Wunsch To: =?iso-8859-1?Q?G=E9rard_Roudier?= Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: SCSI parity error detected Message-ID: <20020213123409.C7110@uriah.heep.sax.de> Reply-To: Joerg Wunsch Mail-Followup-To: Joerg Wunsch , =?iso-8859-1?Q?G=E9rard_Roudier?= , freebsd-scsi@FreeBSD.ORG References: <200202121933.g1CJXCF87301@uriah.heep.sax.de> <20020212004513.X2315-100000@gerard> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit User-Agent: Mutt/1.2.5i In-Reply-To: <20020212004513.X2315-100000@gerard>; from groudier@free.fr on Tue, Feb 12, 2002 at 01:02:35AM +0100 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 List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org As Gérard Roudier wrote: > Btw, if Dawicontrol uses PCI sub-vendor ids or some GPIO specific wiring > to identify their controller, I can let the driver probe such kind of > stuff. But unfortunately, I have exactly no info about those controllers. Since Frank has already replaced his controller by an 53c895-based one, our only chance is to look in his old boot -v log (which he fortunately still has). > A SCA adapter that shrinks 16 bits BUS to 8 bit BUS, device being > connected on the 16 bit side and a Wide controller castrated to 8 bit > connected to the 8 bit is an horror that fails as expected. Sure. -- cheers, J"org .-.-. --... ...-- -.. . DL8DTL http://www.sax.de/~joerg/ NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 16 13:27:29 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from olorin.homeip.net (pool-141-153-200-232.mad.east.verizon.net [141.153.200.232]) by hub.freebsd.org (Postfix) with ESMTP id E050C37B400 for ; Sat, 16 Feb 2002 13:27:24 -0800 (PST) Received: from athlon.olorin.homeip.net (athlon.olorin.homeip.net [192.168.1.2]) by mmx.olorin.homeip.net (Postfix) with SMTP id CB2F41E879 for ; Sat, 16 Feb 2002 15:59:33 -0500 (EST) Date: Sat, 16 Feb 2002 16:00:43 -0500 From: Ben Neuman To: freebsd-scsi@freebsd.org Subject: Issues with ATAPICAM and 4.5-STABLE Message-Id: <20020216160043.69a1d4a0.olorin@olorin.homeip.net> Organization: La X-Mailer: Sylpheed version 0.7.0 (GTK+ 1.2.10; i386--freebsd4.5) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I've been trying out the ATAPICAM patch(20020205), and not having much luck with it. After applying the patch, I enabled scbus, da, and ATAPICAM in the kernel. It compiled and installed fine, but I had issues on boot. Here is the output from dmesg: acd0: DVD-ROM at ata1-master using UDMA66 acd1: CD-RW at ata1-slave using WDMA2 (noperiph:atapi1:0:-1:-1): Registered SIM for ata1 atapicam1m: read data overrun 96/95 atapicam1s: unknown CMD (0x12) - ILLEGAL REQUEST asc=24 ascq=00 error=04 atapicam1m: unknown CMD (0x12) - ILLEGAL REQUEST asc=24 ascq=00 error=00 Mounting root from ufs:/dev/ad0s1a cd0 at atapi1 bus 0 target 0 lun 0 cd0: Removable CD-ROM SCSI-0 device cd0: 844.800MB/s transfers (2048bit) cd0: Attempt to query device size failed: NOT READY, Medium not present cd1 at atapi1 bus 0 target 1 lun 0 cd1: Removable CD-ROM SCSI-0 device cd1: 844.800MB/s transfers (2048bit) cd1: Attempt to query device size failed: NOT READY, Medium not present It didn't hang, but running cdrecord -scanbus gave me a "No SCSI devices found". To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message