Date: Sun, 6 Aug 2000 12:40:06 -0700 (PDT) From: "Kenneth D. Merry" <ken@kdm.org> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/20347: YAMAHA CDR100 does not like multiple LUN probing Message-ID: <200008061940.MAA42062@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/20347; it has been noted by GNATS. From: "Kenneth D. Merry" <ken@kdm.org> To: Andre Albsmeier <andre.albsmeier@mchp.siemens.de> Cc: FreeBSD-gnats-submit@FreeBSD.ORG Subject: Re: kern/20347: YAMAHA CDR100 does not like multiple LUN probing Date: Sun, 6 Aug 2000 13:33:42 -0600 On Wed, Aug 02, 2000 at 18:46:31 +0200, Andre Albsmeier wrote: > On Tue, 01-Aug-2000 at 14:03:09 -0600, Kenneth D. Merry wrote: > > On Tue, Aug 01, 2000 at 21:07:32 +0200, Andre Albsmeier wrote: > > > >Environment: > > > > > > probably all FreeBSD versions > > > > > > >Description: > > > > > > The YAMAHA CDR100 doesn't like multiple LUN probing. If you, for example, > > > wire down your devices like this > > > > > > device pass15 at scbus1 target 5 > > > device cd1 at scbus1 target 5 > > > device pass16 at scbus1 target 6 > > > device cd0 at scbus1 target 6 > > > > > > where target 5 is a "YAMAHA CDR100" and target 6 is another cdrom, > > > the following message appears in dmesg > > > > > > (cd0:ahc1:0:5:0): Duplicate Wired Device entry! > > > (cd0:ahc1:0:5:0): Second device will not be wired > > > (cd0:ahc1:0:5:0): lost device > > > (cd0:ahc1:0:5:0): removing device entry > > > > > > and the other cdrom (target 6) becomes cd1. > > > > This isn't a problem with the drive and multiple-lun probing, but rather a > > problem with the hard-wiring code. > > > > The problem is that the hard-wiring code evidently can't deal with multiple > > peripheral drivers wired to the same bus/target/lun. > > > > A work-around here would be to not hard-wire your pass devices, and just > > hard-wire your CDROM devices. > > I tried this already with the following entries: > > #device pass15 at scbus1 target 5 > device cd1 at scbus1 target 5 > #device pass16 at scbus1 target 6 > device cd0 at scbus1 target 6 > > Same result: > > andre@bali:~>dmesg | egrep 'cd|pass0' > (pass0:ahc0:0:0:0): Duplicate Wired Device entry! > (pass0:ahc0:0:0:0): Second device will not be wired > (pass0:ahc0:0:0:0): Duplicate Wired Device entry! > (pass0:ahc0:0:0:0): Second device will not be wired You shouldn't get those messages unless you've got pass0 wired down... In any case, that looks to be a different device than the one that is going away: > (cd0:ahc1:0:5:0): lost device > (cd0:ahc1:0:5:0): removing device entry > cd1 at ahc1 bus 0 target 6 lun 0 > cd1: <PLEXTOR CD-ROM PX-40TS 1.11> Removable CD-ROM SCSI-2 device > cd1: 20.000MB/s transfers (20.000MHz, offset 15) > cd1: Attempt to query device size failed: NOT READY, Medium not present - tray closed > It looks like there is some missing information in there, namely why cd0 went away... > Another try was this: I removed all wiring entries > from the kernel conf (leaving only a "device cd" line): > > device cd > #device pass15 at scbus1 target 5 > #device cd1 at scbus1 target 5 > #device pass16 at scbus1 target 6 > #device cd0 at scbus1 target 6 > > And the result: > > andre@bali:~> dmesg | grep cd > (cd1:ahc1:0:5:0): lost device > (cd1:ahc1:0:5:0): removing device entry > cd0 at ahc1 bus 0 target 6 lun 0 > cd0: <PLEXTOR CD-ROM PX-40TS 1.11> Removable CD-ROM SCSI-2 device > cd0: 20.000MB/s transfers (20.000MHz, offset 15) There weren't any other error messages before the 'lost device' message? > I have three other Yamaha CD-Writers: CD400, CD4260 and a CD6416. > With all of these everything works perfectly. > > Also, the CDR100 is known to be broken with multiple LUN probing. > You can see this if you enable the 'Multiple LUN support' in the > Adaptec BIOS: When booting, you will see 8 CDR100 devices appear > under the assigned SCSI ID when the controller BIOS scans the bus. > All other CD Writers behave normally here... > > > I think, we should consider putting the quirk entry into cam_xpt.c > -- sure the hard-wiring code will still have the problems you wrote > about but the CDR100 is broken for sure :-( > > What do you think? I think you're right, that drive needs a quirk entry, but it still isn't clear to me what's going on with those error messages. But all the problems go away when you add the quirk entry? Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200008061940.MAA42062>