Can't access USB external disk

[Robert]

Running 13.04 with linux-generic 3.8.0.19.35. USB external disk cannot be accessed.

dmesg output:

[ 4555.788102] usb 1-5: new high-speed USB device number 6 using ehci-pci
[ 4555.921838] usb 1-5: New USB device found, idVendor=14cd, idProduct=6116
[ 4555.921848] usb 1-5: New USB device strings: Mfr=1, Product=3, SerialNumber=2
[ 4555.921855] usb 1-5: Product: USB 2.0 SATA BRIDGE
[ 4555.921861] usb 1-5: Manufacturer: Super Top
[ 4555.921867] usb 1-5: SerialNumber: M6116018VF16
[ 4555.993515] Initializing USB Mass Storage driver...
[ 4555.993646] usbcore: registered new interface driver usb-storage
[ 4555.993649] USB Mass Storage support registered.
[ 4556.037533] scsi2 : usb-storage 1-5:1.0
[ 4556.037724] usbcore: registered new interface driver ums-cypress
[ 4557.037022] scsi 2:0:0:0: Direct-Access WDC WD50 00BEVT-22A0RT0 PQ: 0 ANSI: 0
[ 4557.038772] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 4557.045687] sd 2:0:0:0: [sdb] 976773168 512-byte logical blocks: (500 GB/465 GiB)
[ 4557.046300] sd 2:0:0:0: [sdb] Write Protect is off
[ 4557.046309] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 4557.047053] sd 2:0:0:0: [sdb] No Caching mode page present
[ 4557.047062] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 4557.051810] sd 2:0:0:0: [sdb] No Caching mode page present
[ 4557.051821] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 4557.070000] sdb: sdb1
[ 4557.072555] sd 2:0:0:0: [sdb] No Caching mode page present
[ 4557.072564] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 4557.072571] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 4565.104079] usb 1-5: reset high-speed USB device number 6 using ehci-pci
[ 4632.315329] sd 2:0:0:0: [sdb] Unhandled sense code
[ 4632.315340] sd 2:0:0:0: [sdb]
[ 4632.315345] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 4632.315351] sd 2:0:0:0: [sdb]
[ 4632.315355] Sense Key : Hardware Error [current]
[ 4632.315364] sd 2:0:0:0: [sdb]
[ 4632.315370] Add. Sense: No additional sense information
[ 4632.315376] sd 2:0:0:0: [sdb] CDB:
[ 4632.315379] Read(10): 28 00 3a 38 4c 2f 00 00 08 00
[ 4632.315402] end_request: I/O error, dev sdb, sector 976768047
[ 4632.315411] quiet_error: 42 callbacks suppressed
[ 4632.315418] Buffer I/O error on device sdb1, logical block 488383992
[ 4632.315425] Buffer I/O error on device sdb1, logical block 488383993
[ 4632.315431] Buffer I/O error on device sdb1, logical block 488383994
[ 4632.315436] Buffer I/O error on device sdb1, logical block 488383995
[ 4699.370972] sd 2:0:0:0: [sdb] Unhandled sense code
[ 4699.370980] sd 2:0:0:0: [sdb]
[ 4699.370985] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 4699.370989] sd 2:0:0:0: [sdb]
[ 4699.370992] Sense Key : Hardware Error [current]
[ 4699.370999] sd 2:0:0:0: [sdb]
[ 4699.371003] Add. Sense: No additional sense information
[ 4699.371008] sd 2:0:0:0: [sdb] CDB:
[ 4699.371010] Read(10): 28 00 00 00 00 00 00 00 08 00
[ 4699.371027] end_request: I/O error, dev sdb, sector 0
[ 4699.371034] Buffer I/O error on device sdb, logical block 0

lsusb -v:

Bus 001 Device 006: ID 14cd:6116 Super Top M6116 SATA Bridge
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x14cd Super Top
  idProduct 0x6116 M6116 SATA Bridge
  bcdDevice 1.60
  iManufacturer 1
  iProduct 3
  iSerial 2
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 32
    bNumInterfaces 1
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xc0
      Self Powered
    MaxPower 2mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 8 Mass Storage
      bInterfaceSubClass 6 SCSI
      bInterfaceProtocol 80 Bulk-Only
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0200 1x 512 bytes
        bInterval 0

The hardware worked correctly with 12.04 on the same machine, and still works fine with another machine running 12.04. It obviously fails with 13.04.

USB memory sticks can be used without problems.
---
ApportVersion: 2.9.2-0ubuntu8
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: roseg 1598 F.... pulseaudio
CRDA:
 country DE:
  (2400 - 2483 @ 40), (N/A, 20)
  (5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
  (5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
  (5470 - 5725 @ 40), (N/A, 26), DFS
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=831980a2-7829-431b-a832-9b8c3662d934
InstallationDate: Installed on 2012-06-10 (328 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MachineType: LENOVO 0768B9G
MarkForUpload: True
Package: linux (not installed)
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-19-generic root=UUID=20e9e855-7dd4-40fc-adb8-98fcfec6b8d4 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-19-generic N/A
 linux-backports-modules-3.8.0-19-generic N/A
 linux-firmware 1.106
Tags: raring
Uname: Linux 3.8.0-19-generic i686
UpgradeStatus: Upgraded to raring on 2013-04-26 (8 days ago)
UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
dmi.bios.date: 06/04/07
dmi.bios.vendor: LENOVO
dmi.bios.version: 61ET37WW
dmi.board.name: CAPELL VALLEY(NAPA) CRB
dmi.board.vendor: LENOVO
dmi.board.version: Not Applicable
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnLENOVO:bvr61ET37WW:bd06/04/07:svnLENOVO:pn0768B9G:pvr3000N100:rvnLENOVO:rnCAPELLVALLEY(NAPA)CRB:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.name: 0768B9G
dmi.product.version: 3000 N100
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1176355

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Robert (roseg)]

apport information

[Robert (roseg)]

apport information

[Robert (roseg)]

apport information

[Robert (roseg)]

apport information

[Robert (roseg)]

apport information

[Robert (roseg)]

apport information

[Robert (roseg)]

apport information

[Robert (roseg)]

apport information

[Robert (roseg)]

apport information

[Robert (roseg)]

apport information

[Robert (roseg)]

apport information

[Robert (roseg)]

apport information

[Robert (roseg)]

apport information

[Robert (roseg)]

apport information

[Robert (roseg)]

apport information

[Robert (roseg)]

apport information

[Ming Lei (tom-leiming)]

On Sun, May 5, 2013 at 6:17 AM, Robert <email address hidden> wrote:
> apport information
>
> ** Tags added: apport-collected raring
>
> ** Description changed:
>
> Running 13.04 with linux-generic 3.8.0.19.35. USB external disk cannot
> be accessed.

Could you make sure this USB disk working on previous release or other
OS(such as, windows)?

If it is working on at least one OS, it will be helpful if you can
collect usbmon[1]
trace on the device.

See below link to see how to use usbmon to get the trace(you need to setup
the trace before using the HDD)

http://www.mjmwired.net/kernel/Documentation/usb/usbmon.txt

Thanks,

[Robert (roseg)]

On Son, 2013-05-05 at 13:04 +0000, Ming Lei wrote:
> On Sun, May 5, 2013 at 6:17 AM, Robert <email address hidden> wrote:
> > apport information
> >
> > ** Tags added: apport-collected raring
> >
> > ** Description changed:
> >
> > Running 13.04 with linux-generic 3.8.0.19.35. USB external disk cannot
> > be accessed.
>
> Could you make sure this USB disk working on previous release or other
> OS(such as, windows)?
>
> If it is working on at least one OS, it will be helpful if you can
> collect usbmon[1]
> trace on the device.
>
> See below link to see how to use usbmon to get the trace(you need to setup
> the trace before using the HDD)
>
> http://www.mjmwired.net/kernel/Documentation/usb/usbmon.txt
>
> Thanks,
>

Please have another look at my original report: I clearly said that the
disk worked with 12.04 on the current machine. It stopped working after
the upgrade to 13.04. It still works fine with 12.04 on another machine.

This looks like a simple regression issue - Google shows a few issues
with version 2.20 (rather than 1.60 I have) of the same drive, and it
looks like the driver was incorrectly modified.
--
Robert

[Ming Lei (tom-leiming)]

On Mon, May 6, 2013 at 12:56 AM, Robert <email address hidden> wrote:
>
> Please have another look at my original report: I clearly said that the

Sorry for missing it

> disk worked with 12.04 on the current machine. It stopped working after
> the upgrade to 13.04. It still works fine with 12.04 on another machine.
>
> This looks like a simple regression issue - Google shows a few issues
> with version 2.20 (rather than 1.60 I have) of the same drive, and it
> looks like the driver was incorrectly modified.

Not simple as you imaged, in fact, the fix for 2.20 shouldn't have caused
any regression on 1.60 device3(the fix only excludes 2.20 and above
for cypress subdriver, and not change driver behaviour on 2.19 and below),

Also looks google only shows you have the problem on 1.60 almost.

I think 'dmesg' on 12.04 with the 1.60 device connected should be helpful,
or it is very appreciated that you may test upstream kernel(3.9.0, below link)
and provide usbmon info.

   http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-raring/

Thanks,
--
Ming Lei

[Robert (roseg)]

On Mon, 2013-05-06 at 03:35 +0000, Ming Lei wrote:
> On Mon, May 6, 2013 at 12:56 AM, Robert <email address hidden> wrote:
> >
> > Please have another look at my original report: I clearly said that the
>
> Sorry for missing it
>
> > disk worked with 12.04 on the current machine. It stopped working after
> > the upgrade to 13.04. It still works fine with 12.04 on another machine.
> >
> > This looks like a simple regression issue - Google shows a few issues
> > with version 2.20 (rather than 1.60 I have) of the same drive, and it
> > looks like the driver was incorrectly modified.
>
> Not simple as you imaged, in fact, the fix for 2.20 shouldn't have caused
> any regression on 1.60 device3(the fix only excludes 2.20 and above
> for cypress subdriver, and not change driver behaviour on 2.19 and below),
>
> Also looks google only shows you have the problem on 1.60 almost.
>
> I think 'dmesg' on 12.04 with the 1.60 device connected should be helpful,
> or it is very appreciated that you may test upstream kernel(3.9.0, below link)
> and provide usbmon info.
>
> http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.9-raring/
>
> Thanks,
> --
> Ming Lei
>

dmesg with 3.9 kernel:

[ 100.352128] usb 1-1: new high-speed USB device number 6 using
ehci-pci
[ 100.485872] usb 1-1: New USB device found, idVendor=14cd,
idProduct=6116
[ 100.485882] usb 1-1: New USB device strings: Mfr=1, Product=3,
SerialNumber=2
[ 100.485890] usb 1-1: Product: USB 2.0 SATA BRIDGE
[ 100.485895] usb 1-1: Manufacturer: Super Top
[ 100.485901] usb 1-1: SerialNumber: M6116018VF16
[ 100.559254] Initializing USB Mass Storage driver...
[ 100.559386] usbcore: registered new interface driver usb-storage
[ 100.559389] USB Mass Storage support registered.
[ 100.582754] scsi2 : usb-storage 1-1:1.0
[ 100.582864] usbcore: registered new interface driver ums-cypress
[ 101.580951] scsi 2:0:0:0: Direct-Access WDC WD50 00BEVT-22A0RT0
PQ: 0 ANSI: 0
[ 101.582209] sd 2:0:0:0: [sdb] 976773168 512-byte logical blocks: (500
GB/465 GiB)
[ 101.584097] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 101.585631] sd 2:0:0:0: [sdb] Write Protect is off
[ 101.585642] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 101.586329] sd 2:0:0:0: [sdb] No Caching mode page present
[ 101.586336] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 101.591827] sd 2:0:0:0: [sdb] No Caching mode page present
[ 101.591834] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 101.612764] sdb: sdb1
[ 101.616134] sd 2:0:0:0: [sdb] No Caching mode page present
[ 101.616145] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 101.616153] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 108.944085] usb 1-1: reset high-speed USB device number 6 using
ehci-pci
[ 176.287488] sd 2:0:0:0: [sdb] Unhandled sense code
[ 176.287496] sd 2:0:0:0: [sdb]
[ 176.287500] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 176.287505] sd 2:0:0:0: [sdb]
[ 176.287508] Sense Key : Hardware Error [current]
[ 176.287515] sd 2:0:0:0: [sdb]
[ 176.287520] Add. Sense: No additional sense information
[ 176.287525] sd 2:0:0:0: [sdb] CDB:
[ 176.287528] Read(10): 28 00 3a 38 4c 2f 00 00 08 00
[ 176.2875...

[Ming Lei (tom-leiming)]

Robert,

Thanks for your so quick response.

The usbmon your provided is very helpful, and we can see the problem
happens on the below ATA commands which should be cypress private
protocol:

f6f70d80 1448330528 S Bo:1:010:2 -115 31 = 55534243 80000000 00020000
80001024 2480fe01 00000000 000000ec 000000
f6f70d80 1448330596 C Bo:1:010:2 0 31 >
eff14c00 1448330657 S Bi:1:010:1 -115 512 <
eff14c00 1448333472 C Bi:1:010:1 -121 13 = 55534253 80000000 00000000 00
f6f70d80 1448333517 S Bi:1:010:1 -115 13 <
f6f70d80 1456046737 C Bi:1:010:1 -104 0
f3d04900 1456046808 S Co:1:001:0 s 23 03 0004 0001 0000 0
f3d04900 1456046815 C Co:1:001:0 0 0

Looks the srb->sdb.length isn't matched with ATA's sector count any more
now, and I try to figure out one workaround which is built on raring(see the
images on below link), and could you install the images and feedback the
result? BTW, the patch is still under the link.

         http://kernel.ubuntu.com/~ming/bugs/1176355/v1/

Also could you get the usdmon on 12.04 so that I can compare that what is
the correct ATA command sequences?

Thanks,

[Robert (roseg)]

On Mon, 2013-05-06 at 12:35 +0000, Ming Lei wrote:
> Robert,
>
> Thanks for your so quick response.
>
> The usbmon your provided is very helpful, and we can see the problem
> happens on the below ATA commands which should be cypress private
> protocol:
>
> f6f70d80 1448330528 S Bo:1:010:2 -115 31 = 55534243 80000000 00020000
> 80001024 2480fe01 00000000 000000ec 000000
> f6f70d80 1448330596 C Bo:1:010:2 0 31 >
> eff14c00 1448330657 S Bi:1:010:1 -115 512 <
> eff14c00 1448333472 C Bi:1:010:1 -121 13 = 55534253 80000000 00000000 00
> f6f70d80 1448333517 S Bi:1:010:1 -115 13 <
> f6f70d80 1456046737 C Bi:1:010:1 -104 0
> f3d04900 1456046808 S Co:1:001:0 s 23 03 0004 0001 0000 0
> f3d04900 1456046815 C Co:1:001:0 0 0
>
> Looks the srb->sdb.length isn't matched with ATA's sector count any more
> now, and I try to figure out one workaround which is built on raring(see the
> images on below link), and could you install the images and feedback the
> result? BTW, the patch is still under the link.
>
> http://kernel.ubuntu.com/~ming/bugs/1176355/v1/
>
> Also could you get the usdmon on 12.04 so that I can compare that what is
> the correct ATA command sequences?
>
> Thanks,
>

I installed your patched kernel. dmesg:

[ 104.712099] usb 1-1: new high-speed USB device number 6 using
ehci-pci
[ 104.845857] usb 1-1: New USB device found, idVendor=14cd,
idProduct=6116
[ 104.845868] usb 1-1: New USB device strings: Mfr=1, Product=3,
SerialNumber=2
[ 104.845875] usb 1-1: Product: USB 2.0 SATA BRIDGE
[ 104.845881] usb 1-1: Manufacturer: Super Top
[ 104.845886] usb 1-1: SerialNumber: M6116018VF16
[ 104.908449] Initializing USB Mass Storage driver...
[ 104.908573] usbcore: registered new interface driver usb-storage
[ 104.908576] USB Mass Storage support registered.
[ 104.935146] scsi2 : usb-storage 1-1:1.0
[ 104.935268] usbcore: registered new interface driver ums-cypress
[ 105.932998] scsi 2:0:0:0: Direct-Access WDC WD50 00BEVT-22A0RT0
PQ: 0 ANSI: 0
[ 105.936973] sd 2:0:0:0: Attached scsi generic sg2 type 0
[ 105.939144] sd 2:0:0:0: [sdb] 976773168 512-byte logical blocks: (500
GB/465 GiB)
[ 105.939892] sd 2:0:0:0: [sdb] Write Protect is off
[ 105.939900] sd 2:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 105.940650] sd 2:0:0:0: [sdb] No Caching mode page present
[ 105.940658] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 105.944139] sd 2:0:0:0: [sdb] No Caching mode page present
[ 105.944148] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 105.962181] sdb: sdb1
[ 105.964643] sd 2:0:0:0: [sdb] No Caching mode page present
[ 105.964654] sd 2:0:0:0: [sdb] Assuming drive cache: write through
[ 105.964661] sd 2:0:0:0: [sdb] Attached SCSI disk
[ 107.961517] sd 2:0:0:0: [sdb] Unhandled sense code
[ 107.961527] sd 2:0:0:0: [sdb]
[ 107.961532] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 107.961538] sd 2:0:0:0: [sdb]
[ 107.961542] Sense Key : Hardware Error [current]
[ 107.961551] sd 2:0:0:0: [sdb]
[ 107.961557] Add. Sense: No additional sense information
[ 107.961563] sd 2:0:0:0: [sdb] CDB:
[ 107.961567] ATA command pass through(16): 85 08 2e 00 00 00 00 00 00
00 00 00 00 00 ec 00
[...

[Ming Lei (tom-leiming)]

On Mon, May 6, 2013 at 9:15 PM, Robert <email address hidden> wrote:
>
> I installed your patched kernel. dmesg:

From the 'dmesg' log, we can find the USB reset has been vanished and
current failure might result from protocol error or target. IMO, usbmon on
the patched kernel might be helpful.

>
> I'll try to run a monitor on the older machine later.

With usbmon under the correct case(12.04), we may find what is abnormal
in protocol.

Thanks,
--
Ming Lei

[Robert (roseg)]

On Die, 2013-05-07 at 02:05 +0000, Ming Lei wrote:
> On Mon, May 6, 2013 at 9:15 PM, Robert <email address hidden> wrote:
> >
> > I installed your patched kernel. dmesg:
>
> >From the 'dmesg' log, we can find the USB reset has been vanished and
> current failure might result from protocol error or target. IMO, usbmon on
> the patched kernel might be helpful.
>
> >
> > I'll try to run a monitor on the older machine later.
>
> With usbmon under the correct case(12.04), we may find what is abnormal
> in protocol.
>
>
> Thanks,
> --
> Ming Lei
>

dmesg:

[13440409.632045] usb 1-1: new high speed USB device using ehci_hcd and
address 5
[13440409.765251] usb 1-1: New USB device found, idVendor=14cd,
idProduct=6116
[13440409.765259] usb 1-1: New USB device strings: Mfr=1, Product=3,
SerialNumber=2
[13440409.765266] usb 1-1: Product: USB 2.0 SATA BRIDGE
[13440409.765271] usb 1-1: Manufacturer: Super Top
[13440409.765276] usb 1-1: SerialNumber: M6116018VF16
[13440409.765468] usb 1-1: configuration #1 chosen from 1 choice
[13440409.765932] scsi7 : SCSI emulation for USB Mass Storage devices
[13440409.766161] usb-storage: device found at 5
[13440409.766169] usb-storage: waiting for device to settle before
scanning
[13440414.764771] usb-storage: device scan complete
[13440414.765386] scsi 7:0:0:0: Direct-Access WDC WD50
00BEVT-22A0RT0 PQ: 0 ANSI: 0
[13440414.767031] sd 7:0:0:0: Attached scsi generic sg3 type 0
[13440414.767576] sd 7:0:0:0: [sdc] 976773168 512-byte logical blocks:
(500 GB/465 GiB)
[13440414.768216] sd 7:0:0:0: [sdc] Write Protect is off
[13440414.768227] sd 7:0:0:0: [sdc] Mode Sense: 03 00 00 00
[13440414.768235] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[13440414.769826] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[13440414.769867] sdc: sdc1
[13440414.784198] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[13440414.784247] sd 7:0:0:0: [sdc] Attached SCSI disk

usbmon output attached
--
Robert

[Ming Lei (tom-leiming)]

On Tue, May 7, 2013 at 11:07 PM, Robert <email address hidden> wrote:
> dmesg:
>
> [13440409.632045] usb 1-1: new high speed USB device using ehci_hcd and
> address 5
> [13440409.765251] usb 1-1: New USB device found, idVendor=14cd,
> idProduct=6116
> [13440409.765259] usb 1-1: New USB device strings: Mfr=1, Product=3,
> SerialNumber=2
> [13440409.765266] usb 1-1: Product: USB 2.0 SATA BRIDGE
> [13440409.765271] usb 1-1: Manufacturer: Super Top
> [13440409.765276] usb 1-1: SerialNumber: M6116018VF16
> [13440409.765468] usb 1-1: configuration #1 chosen from 1 choice
> [13440409.765932] scsi7 : SCSI emulation for USB Mass Storage devices
> [13440409.766161] usb-storage: device found at 5
> [13440409.766169] usb-storage: waiting for device to settle before
> scanning
> [13440414.764771] usb-storage: device scan complete
> [13440414.765386] scsi 7:0:0:0: Direct-Access WDC WD50
> 00BEVT-22A0RT0 PQ: 0 ANSI: 0
> [13440414.767031] sd 7:0:0:0: Attached scsi generic sg3 type 0
> [13440414.767576] sd 7:0:0:0: [sdc] 976773168 512-byte logical blocks:
> (500 GB/465 GiB)
> [13440414.768216] sd 7:0:0:0: [sdc] Write Protect is off
> [13440414.768227] sd 7:0:0:0: [sdc] Mode Sense: 03 00 00 00
> [13440414.768235] sd 7:0:0:0: [sdc] Assuming drive cache: write through
> [13440414.769826] sd 7:0:0:0: [sdc] Assuming drive cache: write through
> [13440414.769867] sdc: sdc1
> [13440414.784198] sd 7:0:0:0: [sdc] Assuming drive cache: write through
> [13440414.784247] sd 7:0:0:0: [sdc] Attached SCSI disk
>
> usbmon output attached

One big difference is that precise took 5sec 'delay_use' module parameter
but linus changed it as 1sec in 3.4, could you do a quick test by running
below commands before connecting your USB HDD on 13.04?

            sudo rmmod usb_storage
            sudo modprobe usb_storage delay_use=5

There are still other usbmon differences which I will check later.

Thanks,
--
Ming Lei

[Robert (roseg)]

On Mit, 2013-05-08 at 02:39 +0000, Ming Lei wrote:
> One big difference is that precise took 5sec 'delay_use' module parameter
> but linus changed it as 1sec in 3.4, could you do a quick test by running
> below commands before connecting your USB HDD on 13.04?
>
> sudo rmmod usb_storage
> sudo modprobe usb_storage delay_use=5
>
> There are still other usbmon differences which I will check later.

Done. No change in behaviour, same dmesg errors as before.
--
Robert

[Ming Lei (tom-leiming)]

On Wed, May 8, 2013 at 5:28 PM, Robert <email address hidden> wrote:
> On Mit, 2013-05-08 at 02:39 +0000, Ming Lei wrote:
>> One big difference is that precise took 5sec 'delay_use' module parameter
>> but linus changed it as 1sec in 3.4, could you do a quick test by running
>> below commands before connecting your USB HDD on 13.04?
>>
>> sudo rmmod usb_storage
>> sudo modprobe usb_storage delay_use=5
>>
>> There are still other usbmon differences which I will check later.
>
> Done. No change in behaviour, same dmesg errors as before.

From the usbmon in correct case, there is no any ATA commands
at all. I am not sure where these commands are from(user space
or kernel?) in the failure case.

Could you install the upstream 3.9.0 kernel images on 12.04 to
see if the HDD can work well?

Another difference is that length of the 2nd INQUIRY command becomes
12 instead of 6, which need to check further.

Thanks,

[Robert (roseg)]

On Mit, 2013-05-08 at 12:25 +0000, Ming Lei wrote:
> From the usbmon in correct case, there is no any ATA commands
> at all. I am not sure where these commands are from(user space
> or kernel?) in the failure case.

I suspect it's strictly kernel - I didn't even mount the drive. Mounting
is definitely possible (the drive works fine), but I wanted to show the
minimal difference.

> Could you install the upstream 3.9.0 kernel images on 12.04 to
> see if the HDD can work well?

Sorry, not possible (production machine). I also don't see what would it
bring, as the machine with 13.04 that shows the errors was working fine
with 12.04.

> Another difference is that length of the 2nd INQUIRY command becomes
> 12 instead of 6, which need to check further.

Please do and let me know.
--
Robert

[Ming Lei (tom-leiming)]

On Wed, May 8, 2013 at 10:12 PM, Robert <email address hidden> wrote:
> On Mit, 2013-05-08 at 12:25 +0000, Ming Lei wrote:
>> From the usbmon in correct case, there is no any ATA commands
>> at all. I am not sure where these commands are from(user space
>> or kernel?) in the failure case.
>
> I suspect it's strictly kernel - I didn't even mount the drive. Mounting
> is definitely possible (the drive works fine), but I wanted to show the
> minimal difference.

No, in fact, the scsi layer(sd, kernel) has already read the 4 sectors from
the device successfully, then one inquiry command and some RAW ATA
commands are sent to device, and the disk starts to behave badly. It is
very possible that these commands are sent from userspace when the scsi
disk device shows up and udevd got the notification. And these commands
aren't sent to the device absolutely on precise.

Looks some utilities(smartctl, hdparm) may do that.

>
>> Could you install the upstream 3.9.0 kernel images on 12.04 to
>> see if the HDD can work well?
>
> Sorry, not possible (production machine). I also don't see what would it
> bring, as the machine with 13.04 that shows the errors was working fine
> with 12.04.

Sorry to see that, but you already installed 3.9.0 upstream kernel on
raring(13.04),
right? I am wondering there is any difference to install 3.9.0 kernel on 12.04.

>
>> Another difference is that length of the 2nd INQUIRY command becomes
>> 12 instead of 6, which need to check further.
>
> Please do and let me know.

As I commented above, the 2nd inquiry command might be sent from
user space application.

Thanks,

[Robert (roseg)]

On Mit, 2013-05-08 at 15:40 +0000, Ming Lei wrote:
> On Wed, May 8, 2013 at 10:12 PM, Robert <email address hidden> wrote:
> > On Mit, 2013-05-08 at 12:25 +0000, Ming Lei wrote:
> >> From the usbmon in correct case, there is no any ATA commands
> >> at all. I am not sure where these commands are from(user space
> >> or kernel?) in the failure case.
> >
> > I suspect it's strictly kernel - I didn't even mount the drive. Mounting
> > is definitely possible (the drive works fine), but I wanted to show the
> > minimal difference.
>
> No, in fact, the scsi layer(sd, kernel) has already read the 4 sectors from
> the device successfully, then one inquiry command and some RAW ATA
> commands are sent to device, and the disk starts to behave badly. It is
> very possible that these commands are sent from userspace when the scsi
> disk device shows up and udevd got the notification. And these commands
> aren't sent to the device absolutely on precise.
>
> Looks some utilities(smartctl, hdparm) may do that.

I used no smartctl or hdparm. It is possible that udevd may have sent
something.

> >
> >> Could you install the upstream 3.9.0 kernel images on 12.04 to
> >> see if the HDD can work well?
> >
> > Sorry, not possible (production machine). I also don't see what would it
> > bring, as the machine with 13.04 that shows the errors was working fine
> > with 12.04.
>
> Sorry to see that, but you already installed 3.9.0 upstream kernel on
> raring(13.04),
> right? I am wondering there is any difference to install 3.9.0 kernel on 12.04.

Yes, I sent you the usbmon and dmesg for the patched 3.9.0 on raring.
The 12.04 machine is a production server, so I'd rather not play around
with it. I used it just to make sure the removable disk is working OK.

I still don't understand what information you hope to get from that: I
assure you that the test machine worked OK with precise and stopped
working with raring.
--
Robert

[Ming Lei (tom-leiming)]

On Thu, May 9, 2013 at 12:30 AM, Robert <email address hidden> wrote:
> On Mit, 2013-05-08 at 15:40 +0000, Ming Lei wrote:
>> On Wed, May 8, 2013 at 10:12 PM, Robert <email address hidden> wrote:
>> > On Mit, 2013-05-08 at 12:25 +0000, Ming Lei wrote:
>> >> From the usbmon in correct case, there is no any ATA commands
>> >> at all. I am not sure where these commands are from(user space
>> >> or kernel?) in the failure case.
>> >
>> > I suspect it's strictly kernel - I didn't even mount the drive. Mounting
>> > is definitely possible (the drive works fine), but I wanted to show the
>> > minimal difference.
>>
>> No, in fact, the scsi layer(sd, kernel) has already read the 4 sectors from
>> the device successfully, then one inquiry command and some RAW ATA
>> commands are sent to device, and the disk starts to behave badly. It is
>> very possible that these commands are sent from userspace when the scsi
>> disk device shows up and udevd got the notification. And these commands
>> aren't sent to the device absolutely on precise.
>>
>> Looks some utilities(smartctl, hdparm) may do that.
>
> I used no smartctl or hdparm. It is possible that udevd may have sent
> something.
>
>> >
>> >> Could you install the upstream 3.9.0 kernel images on 12.04 to
>> >> see if the HDD can work well?
>> >
>> > Sorry, not possible (production machine). I also don't see what would it
>> > bring, as the machine with 13.04 that shows the errors was working fine
>> > with 12.04.
>>
>> Sorry to see that, but you already installed 3.9.0 upstream kernel on
>> raring(13.04),
>> right? I am wondering there is any difference to install 3.9.0 kernel on 12.04.
>
> Yes, I sent you the usbmon and dmesg for the patched 3.9.0 on raring.
> The 12.04 machine is a production server, so I'd rather not play around
> with it. I used it just to make sure the removable disk is working OK.
>
> I still don't understand what information you hope to get from that: I
> assure you that the test machine worked OK with precise and stopped
> working with raring.

If the ATA commands are from user-space in raring, 3.9.0 or raring kernel
will work well in precise release. That is what I want to know, :-)

Thanks,
--
Ming Lei

[Ming Lei (tom-leiming)]

On Thu, May 9, 2013 at 8:47 AM, Ming Lei <email address hidden> wrote:
>> I still don't understand what information you hope to get from that: I
>> assure you that the test machine worked OK with precise and stopped
>> working with raring.
>
> If the ATA commands are from user-space in raring, 3.9.0 or raring kernel
> will work well in precise release. That is what I want to know, :-)

From another report(LP1161985) about the same problem:

        https://bugs.launchpad.net/ubuntu/+source/libatasmart/+bug/1161985

Mar 29 19:19:42 local kernel: [ 47.209120] sd 6:0:0:0: [sdb] Attached SCSI disk
Mar 29 19:19:50 local kernel: [ 54.928067] usb 2-2: reset high-speed
USB device number 5 using ehci-pci
Mar 29 19:19:50 local udisksd[1881]: Error probing device: Error
sending ATA command IDENTIFY DEVICE to /dev/sdb: Unexpected sense data
returned:#0120000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
................#0120010: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 ................#012 (g-io-error-quark, 0)

The ATA command should be from userspace, not kernel.

So you may stop 'udisks' temporarily via below command, then connect the
HDD to your machine and see if you can mount it manually.

                     sudo udisks --inhibit

Thanks,

[Claudio (claudio-fischer)]

I have the same effect with ubuntu raring and a external usb drive:

Bus 001 Device 008: ID 14cd:6116 Super Top M6116 SATA Bridge

[Claudio (claudio-fischer)]

if I boot into Linux Mint 14 cinnamon on the same machine:

Linux mint 3.5.0-27-generic #46-Ubuntu SMP Mon Mar 25 19:58:17 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

the usb drive is working fine

[CassieMoondust (cassie-lx)]

I have the same issue with Raring Ringtail 13.04 and the kernel 3.8.0-19-generic #30-Ubuntu.
Bus 001 Device 005: ID 14cd:6116 Super Top M6116 SATA Bridge

The same drive works well in Precise with kernel 3.5.0-28-generic #48~precise1-Ubuntu.

[CassieMoondust (cassie-lx)]

Maybe related bug, which is fixed: 1082215

[Ming Lei (tom-leiming)]

Anyone can run below command to see if the disk can be mounted manually later?

            sudo udisks --inhibit

[Robert (roseg)]

On Don, 2013-05-09 at 04:51 +0000, Ming Lei wrote:
> So you may stop 'udisks' temporarily via below command, then connect the
> HDD to your machine and see if you can mount it manually.
>
> sudo udisks --inhibit

Sorry, no help there. dmesg while inhibited:

[ 3945.452130] usb 1-1: new high-speed USB device number 8 using
ehci-pci
[ 3945.585537] usb 1-1: New USB device found, idVendor=14cd,
idProduct=6116
[ 3945.585546] usb 1-1: New USB device strings: Mfr=1, Product=3,
SerialNumber=2
[ 3945.585553] usb 1-1: Product: USB 2.0 SATA BRIDGE
[ 3945.585559] usb 1-1: Manufacturer: Super Top
[ 3945.585564] usb 1-1: SerialNumber: M6116018VF16
[ 3945.682966] scsi3 : usb-storage 1-1:1.0
[ 3945.683086] usbcore: registered new interface driver ums-cypress
[ 3946.680993] scsi 3:0:0:0: Direct-Access WDC WD50 00BEVT-22A0RT0
PQ: 0 ANSI: 0
[ 3946.682668] sd 3:0:0:0: Attached scsi generic sg3 type 0
[ 3946.683373] sd 3:0:0:0: [sdc] 976773168 512-byte logical blocks: (500
GB/465 GiB)
[ 3946.684636] sd 3:0:0:0: [sdc] Write Protect is off
[ 3946.684645] sd 3:0:0:0: [sdc] Mode Sense: 03 00 00 00
[ 3946.685744] sd 3:0:0:0: [sdc] No Caching mode page present
[ 3946.685753] sd 3:0:0:0: [sdc] Assuming drive cache: write through
[ 3946.693255] sd 3:0:0:0: [sdc] No Caching mode page present
[ 3946.693265] sd 3:0:0:0: [sdc] Assuming drive cache: write through
[ 3946.701684] sdc: sdc1
[ 3946.704289] sd 3:0:0:0: [sdc] No Caching mode page present
[ 3946.704298] sd 3:0:0:0: [sdc] Assuming drive cache: write through
[ 3946.704306] sd 3:0:0:0: [sdc] Attached SCSI disk
[ 3955.112060] usb 1-1: reset high-speed USB device number 8 using
ehci-pci
[ 4022.442654] sd 3:0:0:0: [sdc] Unhandled sense code
[ 4022.442662] sd 3:0:0:0: [sdc]
[ 4022.442666] Result: hostbyte=DID_ERROR driverbyte=DRIVER_SENSE
[ 4022.442670] sd 3:0:0:0: [sdc]
[ 4022.442673] Sense Key : Hardware Error [current]
[ 4022.442680] sd 3:0:0:0: [sdc]
[ 4022.442684] Add. Sense: No additional sense information
[ 4022.442689] sd 3:0:0:0: [sdc] CDB:
[ 4022.442692] Read(10): 28 00 3a 38 4c 2f 00 00 08 00
[ 4022.442708] end_request: I/O error, dev sdc, sector 976768047
[ 4022.442715] quiet_error: 42 callbacks suppressed
[ 4022.442720] Buffer I/O error on device sdc1, logical block 488383992

What does help is killing udisksd, after which I can mount the disk
manually: It looks like udisks does not do what is expected.
--
Robert

[Ming Lei (tom-leiming)]

On Tue, May 21, 2013 at 8:34 PM, Robert <email address hidden> wrote:
> *** This bug is a duplicate of bug 1161985 ***
> https://bugs.launchpad.net/bugs/1161985
>
> What does help is killing udisksd, after which I can mount the disk
> manually: It looks like udisks does not do what is expected.

Good, so we can confirm that it is same with 1161985, which may be
related with userspace utility.

Thanks
--
Ming Lei

[Robert (roseg)]

On Mit, 2013-05-22 at 10:41 +0000, Ming Lei wrote:
> *** This bug is a duplicate of bug 1161985 ***
> https://bugs.launchpad.net/bugs/1161985
>
> On Tue, May 21, 2013 at 8:34 PM, Robert <email address hidden> wrote:
> > *** This bug is a duplicate of bug 1161985 ***
> > https://bugs.launchpad.net/bugs/1161985
> >
> > What does help is killing udisksd, after which I can mount the disk
> > manually: It looks like udisks does not do what is expected.
>
> Good, so we can confirm that it is same with 1161985, which may be
> related with userspace utility.
>
> Thanks
> --
> Ming Lei
>

So what are the next steps?
--
Robert

[Ming Lei (tom-leiming)]

On Thu, May 23, 2013 at 7:40 PM, Robert <email address hidden> wrote:
> So what are the next steps?

It depends on user space packages, which I am not familiar with, so
I am afraid I can't help you further.

Thanks,
--
Ming Lei

[brazz (brazz-ardent)]

Hello,
I think I have this problem:
I have a USB disk enclosure that worked fine until there is very little time (there are a couple of weeks, I transferred 300GB of data ...)
Since there were various progreammes especially kernel upgrade in any case I am unable to access the disk (see below excerpt from dmesg and output of fdisk-l)
In fact the unit is for the disk that is attached is identified, but that does not go away, it does not recognize the partition table, I checked with fdisk (see below)
I'm pretty worried, indeed had my backup market, I checked. It would be weird that right after the drive fails, I would go rather for a driver problem, in fact I had this problem early and after a 13.0 dowgrade to an old version of usisks2 it worked, unfortunately I had not blocked my amendment and subsequent upgrades have invalidated all!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Fin de dmesg:
.......
[ 924.568750] usb 2-1.1: new high-speed USB device number 7 using ehci-pci
[ 924.664941] usb 2-1.1: New USB device found, idVendor=1bcf, idProduct=0c31
[ 924.664947] usb 2-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 924.664952] usb 2-1.1: Product: USB to Serial-ATA bridge
[ 924.664956] usb 2-1.1: Manufacturer: Sunplus Innovation Technology
[ 924.664959] usb 2-1.1: SerialNumber: FF310003330000000000009FE03FF
[ 924.666822] usb-storage 2-1.1:1.0: USB Mass Storage device detected
[ 924.667262] scsi11 : usb-storage 2-1.1:1.0
[ 925.669347] scsi 11:0:0:0: Direct-Access ST310003 33AS 0200 PQ: 0 ANSI: 4
[ 925.672140] sd 11:0:0:0: Attached scsi generic sg5 type 0
[ 925.672958] sd 11:0:0:0: [sde] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[ 925.679802] sd 11:0:0:0: [sde] Write Protect is off
[ 925.679810] sd 11:0:0:0: [sde] Mode Sense: 38 00 00 00
[ 925.686724] sd 11:0:0:0: [sde] No Caching mode page found
[ 925.686732] sd 11:0:0:0: [sde] Assuming drive cache: write through
[ 925.702369] sd 11:0:0:0: [sde] No Caching mode page found
[ 925.702377] sd 11:0:0:0: [sde] Assuming drive cache: write through
[ 932.744863] sde: unknown partition table
[ 932.765634] sd 11:0:0:0: [sde] No Caching mode page found
[ 932.765642] sd 11:0:0:0: [sde] Assuming drive cache: write through
[ 932.765647] sd 11:0:0:0: [sde] Attached SCSI disk

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

pierre@bamboo:~$ sudo fdisk -l
[sudo] password for pierre:

Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 têtes, 63 secteurs/piste, 60801 cylindres, total 976773168 secteurs
Unités = secteurs de 1 * 512 = 512 octets
Taille de secteur (logique / physique) : 512 octets / 512 octets
taille d'E/S (minimale / optimale) : 512 octets / 512 octets
Identifiant de disque : 0x0000b867

Périphérique Amorçage Début Fin Blocs Id. Système
/dev/sda1 * 2048 575557631 287777792 83 Linux
/dev/sda2 960006142 976773167 8383513 5 Étendue
/dev/sda3 575557632 960002047 192222208 83 Linux
/dev/sda5 960006144 976771071 8382464 82 partition d'échange Linux / Solaris

Les entrées de la table de partitions ne sont pas ...

[Rowan Potgieter (rowan-potgieter)]

Hi, I have the same issue but it seems to affect ALL USB disks.

I unfortunately only have 1 on me right now but this disk does work on Windows and I'm fairly certain that I had no USB issues in November 2013, I suspect an update in December messed things up. I have also tried with 2 other USB disks which did work previously and they also are not working.

DMESG Ouptput:
[33712.381565] usb 1-1.2: new high-speed USB device number 4 using ehci_hcd
[33712.553269] usb 1-1.2: New USB device found, idVendor=0011, idProduct=7788
[33712.553273] usb 1-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[33712.553276] usb 1-1.2: Product: Mass Storage
[33712.553278] usb 1-1.2: Manufacturer: Generic
[33712.553280] usb 1-1.2: SerialNumber: 29F9C21B
[33712.553948] scsi5 : usb-storage 1-1.2:1.0
[33713.552907] scsi 5:0:0:0: Direct-Access Generic Flash Disk 8.00 PQ: 0 ANSI: 2
[33713.553945] sd 5:0:0:0: Attached scsi generic sg2 type 0
[33713.555480] sd 5:0:0:0: [sdb] 16691200 512-byte logical blocks: (8.54 GB/7.95 GiB)
[33713.556071] sd 5:0:0:0: [sdb] Write Protect is off
[33713.556074] sd 5:0:0:0: [sdb] Mode Sense: 03 00 00 00
[33713.556572] sd 5:0:0:0: [sdb] No Caching mode page present
[33713.556576] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[33713.559217] sd 5:0:0:0: [sdb] No Caching mode page present
[33713.559222] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[33713.609029] sdb: sdb1
[33713.611489] sd 5:0:0:0: [sdb] No Caching mode page present
[33713.611494] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[33713.611497] sd 5:0:0:0: [sdb] Attached SCSI removable disk
[33744.352957] usb 1-1.2: reset high-speed USB device number 4 using ehci_hcd
[33775.322639] usb 1-1.2: reset high-speed USB device number 4 using ehci_hcd
[33806.228316] usb 1-1.2: reset high-speed USB device number 4 using ehci_hcd
[33837.134160] usb 1-1.2: reset high-speed USB device number 4 using ehci_hcd
[33868.167673] usb 1-1.2: reset high-speed USB device number 4 using ehci_hcd
[33899.073388] usb 1-1.2: reset high-speed USB device number 4 using ehci_hcd
[33899.241280] sd 5:0:0:0: [sdb] Media Changed
[33899.241285] sd 5:0:0:0: [sdb]
[33899.241287] Result: hostbyte=DID_ABORT driverbyte=DRIVER_SENSE
[33899.241289] sd 5:0:0:0: [sdb]
[33899.241290] Sense Key : Unit Attention [current]
[33899.241294] Info fld=0x0
[33899.241296] sd 5:0:0:0: [sdb]
[33899.241299] Add. Sense: Not ready to ready change, medium may have changed
[33899.241301] sd 5:0:0:0: [sdb] CDB:
[33899.241303] Read(10): 28 00 00 fe af f8 00 00 01 00
[33899.241311] end_request: I/O error, dev sdb, sector 16691192
[33899.241315] Buffer I/O error on device sdb, logical block 2086399
[33899.245484] sd 5:0:0:0: [sdb] No Caching mode page present
[33899.245489] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[33899.247723] sd 5:0:0:0: [sdb] No Caching mode page present
[33899.247728] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[33899.297542] sdb: sdb1
[33929.979207] usb 1-1.2: reset high-speed USB device number 4 using ehci_hcd

lsusb -v:

Bus 001 Device 004: ID 0011:7788
Couldn't open device, some information will be missing
Device Descriptor:
  bLength...

[Phillip Susi (psusi)]

Papamatti, please don't mark bugs as duplicates at random. This has nothing at all to do with #1161985.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]