Bug 154192
| Summary: | [umass] In Garmin Oregon GPS, only the first umass device is visible since upgrade of 9.0-current [regression] | ||
|---|---|---|---|
| Product: | Base System | Reporter: | Thiemo Nordenholz <list+lg3hxa01jll9pdxp> |
| Component: | usb | Assignee: | freebsd-usb (Nobody) <usb> |
| Status: | Open --- | ||
| Severity: | Affects Only Me | ||
| Priority: | Normal | ||
| Version: | Unspecified | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Thiemo Nordenholz
2011-01-21 13:50:07 UTC
FWIW, camcontrol reports two LUNs for the device now, both with ID 0: > camcontrol devlist <HITACHI HTS722020K9SA00 FDE DC4LC75A> at scbus0 target 0 lun 0 (ada0,pass0) <Optiarc DVD RW AD-7910S 1.D0> at scbus1 target 0 lun 0 (cd0,pass1) <Garmin GARMIN Flash 1.00> at scbus2 target 0 lun 0 (pass2,da0) > camcontrol reportluns da0 2 LUNs found 0 0 > -- Query a PGP key server (e.g. http://www.pgp.net/) for my public key 41068629. Strange sender address? Please see http://www.thiemo.net/misc/list-mail.shtml On Friday 21 January 2011 14:48:53 Thiemo Nordenholz wrote:
> >Number: 154192
> >Category: usb
> >Synopsis: In Garmin Oregon GPS, only the first umass device is
> >visible since upgrade of 9.0-current Confidential: no
> >Severity: non-critical
> >Priority: medium
> >Responsible: freebsd-usb
> >State: open
> >Quarter:
> >Keywords:
> >Date-Required:
> >Class: sw-bug
> >Submitter-Id: current-users
> >Arrival-Date: Fri Jan 21 13:50:07 UTC 2011
> >Closed-Date:
> >Last-Modified:
> >Originator: Thiemo Nordenholz
> >Release: 9-current
> >Organization:
>
> >Environment:
> FreeBSD feynman 9.0-CURRENT FreeBSD 9.0-CURRENT #0: Thu Jan 20 16:26:22 CET
> 2011 thiemo@feynman:/usr/obj/usr/src.new/sys/FEYNMAN i386
>
> >Description:
> After upgrading from 9.0-CURRENT as of Jun 08, 2010, to the state csup'ed
> on Sep 29, 2010, I am missing the SD card in my GPS receiver usually
> accessible as USB mass storage. The internal (first) storage in the
> receiver is still visible to fBSD.
>
> Before the upgrade, the "working" output after attaching the GPS looked
> like this:
>
> Sep 20 11:57:13 feynman root: Unknown USB device: vendor 0x091e product
> 0x231b bus uhub0 Sep 20 11:57:13 feynman kernel: ugen0.2: <vendor 0x091e>
> at usbus0 Sep 20 11:57:13 feynman kernel: umass0: <vendor 0x091e product
> 0x231b, class 0/0, rev 1.10/5.09, addr 2> on usbus0 Sep 20 11:57:13
> feynman kernel: umass0: SCSI over Bulk-Only; quirks = 0x0000 Sep 20
> 11:57:14 feynman kernel: umass0:2:0:-1: Attached to scbus2
> Sep 20 11:57:14 feynman kernel: da0 at umass-sim0 bus 0 target 0 lun 0
> Sep 20 11:57:14 feynman kernel: da0: <Garmin GARMIN Flash 1.00> Removable
> Direct Access SCSI-5 device Sep 20 11:57:14 feynman kernel: da0: 1.000MB/s
> transfers
> Sep 20 11:57:14 feynman kernel: da0: 3906MB (7999488 512 byte sectors: 255H
> 63S/T 497C) Sep 20 11:57:14 feynman kernel: da1 at umass-sim0 bus 0 target
> 0 lun 1 Sep 20 11:57:14 feynman kernel: da1: <Garmin GARMIN SD Card 1.00>
> Removable Direct Access SCSI-5 device Sep 20 11:57:14 feynman kernel: da1:
> 1.000MB/s transfers
> Sep 20 11:57:14 feynman kernel: da1: 7580MB (15523840 512 byte sectors:
> 255H 63S/T 966C)
>
> Today (in the meantime upgraded to the fBSD revision as cited above in the
> uname -a output, csup'ed yesterday), the da1 device is missing:
>
> Jan 21 14:27:25 feynman kernel: ugen0.2: <vendor 0x091e> at usbus0
> Jan 21 14:27:25 feynman kernel: umass0: <vendor 0x091e product 0x231b,
> class 0/0, rev 1.10/5.09, addr 2> on usbus0 Jan 21 14:27:25 feynman root:
> Unknown USB device: vendor 0x091e product 0x231b bus uhub0 Jan 21 14:27:26
> feynman kernel: da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 Jan 21
> 14:27:26 feynman kernel: da0: <Garmin GARMIN Flash 1.00> Removable Direct
> Access SCSI-5 device Jan 21 14:27:26 feynman kernel: da0: 1.000MB/s
> transfers
> Jan 21 14:27:26 feynman kernel: da0: 3906MB (7999488 512 byte sectors: 255H
> 63S/T 497C)
>
> When attaching the GPS to a system running Solaris, both mass storage
> devices are visible and working, so I assume the device itself is okay...
>
Try to upgrade USB code to the latest. There I a know issue affecting device
enumeration.
--HPS
> Try to upgrade USB code to the latest. There I a know issue affecting device > enumeration. Just cvsup'ed and tested again with the same result: > uname -a FreeBSD feynman 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Sat Jan 22 12:53:38 CET 2011 thiemo@feynman:/usr/obj/usr/src.new/sys/FEYNMAN i386 Jan 22 13:10:59 feynman root: Unknown USB device: vendor 0x091e product 0x231b bus uhub0 Jan 22 13:10:59 feynman kernel: ugen0.2: <vendor 0x091e> at usbus0 Jan 22 13:10:59 feynman kernel: umass0: <vendor 0x091e product 0x231b, class 0/0, rev 1.10/5.09, addr 2> on usbus0 Jan 22 13:11:00 feynman kernel: da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 Jan 22 13:11:00 feynman kernel: da0: <Garmin GARMIN Flash 1.00> Removable Direct Access SCSI-5 device Jan 22 13:11:00 feynman kernel: da0: 1.000MB/s transfers Jan 22 13:11:00 feynman kernel: da0: 3906MB (7999488 512 byte sectors: 255H 63S/T 497C) [ unplugging device here ] Jan 22 13:11:34 feynman kernel: ugen0.2: <vendor 0x091e> at usbus0 (disconnected) Jan 22 13:11:34 feynman kernel: umass0: at uhub0, port 1, addr 2 (disconnected) Jan 22 13:11:34 feynman kernel: (da0:umass-sim0:0:0:0): lost device Jan 22 13:11:34 feynman kernel: (da0:umass-sim0:0:0:0): removing device entry > camcontrol reportluns da0 2 LUNs found 0 0 Cheers, Thiemo -- Query a PGP key server (e.g. http://www.pgp.net/) for my public key 41068629. Strange sender address? Please see http://www.thiemo.net/misc/list-mail.shtml On Saturday 22 January 2011 13:17:04 Thiemo Nordenholz wrote:
> > Try to upgrade USB code to the latest. There I a know issue affecting
> > device enumeration.
>
> Just cvsup'ed and tested again with the same result:
> > uname -a
>
> FreeBSD feynman 9.0-CURRENT FreeBSD 9.0-CURRENT #1: Sat Jan 22 12:53:38 CET
> 2011 thiemo@feynman:/usr/obj/usr/src.new/sys/FEYNMAN i386
>
> Jan 22 13:10:59 feynman root: Unknown USB device: vendor 0x091e product
> 0x231b bus uhub0 Jan 22 13:10:59 feynman kernel: ugen0.2: <vendor 0x091e>
> at usbus0 Jan 22 13:10:59 feynman kernel: umass0: <vendor 0x091e product
> 0x231b, class 0/0, rev 1.10/5.09, addr 2> on usbus0 Jan 22 13:11:00
> feynman kernel: da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 Jan 22
> 13:11:00 feynman kernel: da0: <Garmin GARMIN Flash 1.00> Removable Direct
> Access SCSI-5 device Jan 22 13:11:00 feynman kernel: da0: 1.000MB/s
> transfers
> Jan 22 13:11:00 feynman kernel: da0: 3906MB (7999488 512 byte sectors: 255H
> 63S/T 497C) [ unplugging device here ]
> Jan 22 13:11:34 feynman kernel: ugen0.2: <vendor 0x091e> at usbus0
> (disconnected) Jan 22 13:11:34 feynman kernel: umass0: at uhub0, port 1,
> addr 2 (disconnected) Jan 22 13:11:34 feynman kernel:
> (da0:umass-sim0:0:0:0): lost device Jan 22 13:11:34 feynman kernel:
> (da0:umass-sim0:0:0:0): removing device entry
>
> > camcontrol reportluns da0
>
Can you build the kernel with "options USB_DEBUG" and post new dmesg? Maybe
your device is quirked while it should not.
--HPS
> Can you build the kernel with "options USB_DEBUG" and post new dmesg? Maybe > your device is quirked while it should not. It says quirks=0: ugen0.2: <vendor 0x091e> at usbus0 umass0: <vendor 0x091e product 0x231b, class 0/0, rev 1.10/5.09, addr 2> on usbus0 umass0: SCSI over Bulk-Only; quirks = 0x0000 umass0:2:0:-1: Attached to scbus2 da0 at umass-sim0 bus 0 scbus2 target 0 lun 0 da0: <Garmin GARMIN Flash 1.00> Removable Direct Access SCSI-5 device da0: 1.000MB/s transfers da0: 3906MB (7999488 512 byte sectors: 255H 63S/T 497C) Regards, Thiemo -- Query a PGP key server (e.g. http://www.pgp.net/) for my public key 41068629. Strange sender address? Please see http://www.thiemo.net/misc/list-mail.shtml Issue still present with 9-CURRENT as of April 11, 2011. -- Query a PGP key server (e.g. http://www.pgp.net/) for my public key 41068629. Strange sender address? Please see http://www.thiemo.net/misc/list-mail.shtml For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped (At least) with 11.2-RELEASE-p2, both storage mediums are accessible when adding the quirk UQ_MSC_NO_INQUIRY for it. |
