Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 17 Jan 2023 22:43:40 +0000
From:      bugzilla-noreply@freebsd.org
To:        bugs@FreeBSD.org
Subject:   [Bug 269019] Serial number of Amazon Kindle is visible via camcotrol but not via geom disk list
Message-ID:  <bug-269019-227-GWAmqQPXYJ@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-269019-227@https.bugs.freebsd.org/bugzilla/>
References:  <bug-269019-227@https.bugs.freebsd.org/bugzilla/>

next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D269019

Oleg Sharoyko <osharoiko@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|Closed                      |New
         Resolution|FIXED                       |---

--- Comment #1 from Oleg Sharoyko <osharoiko@gmail.com> ---
Sorry, hit enter by mistake.

When I connect my old Amazon Kindle it gets detected and block device appea=
rs
in the system which works fine except for one minor issue. The serial numbe=
r of
Kindle can be seen with `camcontrol inquiry da0` but is not visible with `g=
eom
disk list da0`:

```
% sudo camcontrol inquiry da0
pass0: <Kindle Internal Storage 0100> Removable Direct Access SCSI-2 device
pass0: Serial Number B00AD0B11345001S
pass0: 40.000MB/s transfers


% geom disk list da0
Geom name: da0
Providers:
1. Name: da0
   Mediasize: 3282272256 (3.1G)
   Sectorsize: 512
   Mode: r0w0e0
   descr: Kindle Internal Storage
   ident: (null)
   rotationrate: unknown
   fwsectors: 63
   fwheads: 255
```

I'm trying to update Calibre device detection to work under recent versions=
 of
FreeBSD and serial number is needed to associate block device with USB devi=
ce.

Please find verbose kernel messages covering device attachment below (note:
there's something strange that causes "xhci0: Resetting controller", but th=
is
only happens first time after fresh boot and not on subsequent detach/reatt=
ach
of Kindle. It doesn't seem to affect access to block device and
detaching/reattaching Kindle doesn't change situation with the serial numbe=
r in
GEOM). da0 is Kindle, da1 is card reader in the chassis. Please let me know=
 if
any other information is needed.

```
Jan 17 22:19:38 forlond kernel: xhci0: Resetting controller
Jan 17 22:19:38 forlond kernel: usb_alloc_device: set address 3 failed
(USB_ERR_TIMEOUT, ignored)
Jan 17 22:19:43 forlond kernel: usbd_setup_device_desc: getting device
descriptor at addr 3 failed, USB_ERR_IOERROR
Jan 17 22:19:44 forlond kernel: usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set=
 for
USB mass storage device Amazon Amazon Kindle (0x1949:0x0004)
Jan 17 22:19:44 forlond kernel: usb_msc_auto_quirk: UQ_MSC_NO_TEST_UNIT_REA=
DY
set for USB mass storage device Amazon Amazon Kindle (0x1949:0x0004)
Jan 17 22:19:45 forlond kernel: ugen0.3: <Amazon Amazon Kindle> at usbus0
Jan 17 22:19:45 forlond kernel: umass1 on uhub1
Jan 17 22:19:45 forlond kernel: umass1: <Mass Storage> on usbus0
Jan 17 22:19:45 forlond kernel: umass1:  SCSI over Bulk-Only; quirks =3D 0x=
0101
Jan 17 22:19:45 forlond kernel: umass1:5:1: Attached to scbus5
Jan 17 22:19:45 forlond kernel: uhub1: at usbus0, port 1, addr 1 (disconnec=
ted)
Jan 17 22:19:45 forlond kernel: ugen0.3: <Amazon Amazon Kindle> at usbus0
(disconnected)
Jan 17 22:19:45 forlond kernel: umass1: at uhub1, port 5, addr 2 (disconnec=
ted)
Jan 17 22:19:45 forlond kernel: (probe0:umass-sim1:1:0:0): INQUIRY. CDB: 12=
 00
00 00 24 00
Jan 17 22:19:45 forlond kernel: (probe0:umass-sim1:1:0:0): CAM status: CCB
request completed with an error
Jan 17 22:19:45 forlond kernel: (probe0:umass-sim1:1:0:0): Retrying command=
, 3
more tries remain
Jan 17 22:19:45 forlond kernel: umass1: detached
Jan 17 22:19:45 forlond kernel: ugen0.2: <Generic Flash Card Reader/Writer>=
 at
usbus0 (disconnected)
Jan 17 22:19:45 forlond kernel: umass0: at uhub1, port 13, addr 1
(disconnected)
Jan 17 22:19:45 forlond kernel: da0 at umass-sim0 bus 0 scbus4 target 0 lun=
 0
Jan 17 22:19:45 forlond kernel: da0: <Generic- Multiple Reader 1.11>  s/n
058F63666479 detached
Jan 17 22:19:45 forlond kernel: pass0 at umass-sim0 bus 0 scbus4 target 0 l=
un 0
Jan 17 22:19:45 forlond kernel: pass0: <Generic- Multiple Reader 1.11>  s/n
058F63666479 detached
Jan 17 22:19:45 forlond kernel: (pass0:umass-sim0:0:0:0): Periph destroyed
Jan 17 22:19:45 forlond kernel: (da0:umass-sim0:0:0:0): Periph destroyed
Jan 17 22:19:45 forlond kernel: umass0: detached
Jan 17 22:19:45 forlond kernel: uhub1: detached
Jan 17 22:19:45 forlond kernel: uhub1 on usbus0
Jan 17 22:19:45 forlond kernel: uhub1: <AMD XHCI root HUB, class 9/0, rev
3.00/1.00, addr 1> on usbus0
Jan 17 22:19:46 forlond kernel: uhub1: 22 ports with 22 removable, self pow=
ered
Jan 17 22:19:48 forlond kernel: usb_msc_auto_quirk: UQ_MSC_NO_GETMAXLUN set=
 for
USB mass storage device Amazon Amazon Kindle (0x1949:0x0004)
Jan 17 22:19:48 forlond kernel: usb_msc_auto_quirk: UQ_MSC_NO_TEST_UNIT_REA=
DY
set for USB mass storage device Amazon Amazon Kindle (0x1949:0x0004)
Jan 17 22:19:48 forlond kernel: ugen0.2: <Amazon Amazon Kindle> at usbus0
Jan 17 22:19:48 forlond kernel: umass0 on uhub1
Jan 17 22:19:48 forlond kernel: umass0: <Mass Storage> on usbus0
Jan 17 22:19:48 forlond kernel: umass0:  SCSI over Bulk-Only; quirks =3D 0x=
0101
Jan 17 22:19:48 forlond kernel: umass0:4:0: Attached to scbus4
Jan 17 22:19:48 forlond kernel: pass0 at umass-sim0 bus 0 scbus4 target 0 l=
un 0
Jan 17 22:19:48 forlond kernel: pass0: <Kindle Internal Storage 0100> Remov=
able
Direct Access SCSI-2 device
Jan 17 22:19:48 forlond kernel: pass0: 40.000MB/s transfers
Jan 17 22:19:48 forlond kernel: GEOM: new disk da0
Jan 17 22:19:48 forlond kernel: da0 at umass-sim0 bus 0 scbus4 target 0 lun=
 0
Jan 17 22:19:48 forlond kernel: da0: <Kindle Internal Storage 0100> Removab=
le
Direct Access SCSI-2 device
Jan 17 22:19:48 forlond kernel: da0: 40.000MB/s transfers
Jan 17 22:19:48 forlond kernel: da0: 3130MB (6410688 512 byte sectors)
Jan 17 22:19:48 forlond kernel: da0: quirks=3D0x2<NO_6_BYTE>
Jan 17 22:19:48 forlond kernel: da0: Delete methods: <NONE(*),ZERO>
Jan 17 22:19:48 forlond kernel: ugen0.3: <Generic Flash Card Reader/Writer>=
 at
usbus0
Jan 17 22:19:48 forlond kernel: umass1 on uhub1
Jan 17 22:19:48 forlond kernel: umass1: <Generic Flash Card Reader/Writer,
class 0/0, rev 2.00/1.00, addr 2> on usbus0
Jan 17 22:19:48 forlond kernel: umass1:  SCSI over Bulk-Only; quirks =3D 0x=
4001
Jan 17 22:19:48 forlond kernel: umass1:5:1: Attached to scbus5
Jan 17 22:19:48 forlond kernel: pass1 at umass-sim1 bus 1 scbus5 target 0 l=
un 0
Jan 17 22:19:48 forlond kernel: pass1: <Generic- Multiple Reader 1.11>
Removable Direct Access SPC-2 SCSI device
Jan 17 22:19:48 forlond kernel: pass1: Serial Number 058F63666479
Jan 17 22:19:48 forlond kernel: pass1: 40.000MB/s transfers
Jan 17 22:19:48 forlond kernel: da1 at umass-sim1 bus 1 scbus5 target 0 lun=
 0
Jan 17 22:19:48 forlond kernel: da1: <Generic- Multiple Reader 1.11> Remova=
ble
Direct Access SPC-2 SCSI device
Jan 17 22:19:48 forlond kernel: da1: Serial Number 058F63666479
Jan 17 22:19:48 forlond kernel: da1: 40.000MB/s transfers
Jan 17 22:19:48 forlond kernel: da1: Attempt to query device size failed: N=
OT
READY, Medium not present
Jan 17 22:19:48 forlond kernel: da1: quirks=3D0x2<NO_6_BYTE>
Jan 17 22:19:48 forlond kernel: da1: Delete methods: <NONE(*),ZERO>
Jan 17 22:19:49 forlond kernel: GEOM: new disk da1
Jan 17 22:19:49 forlond kernel: (da1:umass-sim1:1:0:0): PREVENT ALLOW MEDIUM
REMOVAL not supported.
```

--=20
You are receiving this mail because:
You are the assignee for the bug.=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-269019-227-GWAmqQPXYJ>