When plugging in a USB 2 mass-storage device which I've been seeing
problems with, I caught a khubd oops [1]. Kernel is 2.6.22-rc7 on ia32
built with Ubuntu's 2.6.22 .config.

Let me know if you need more details,
  Daniel

--- [1]

[ 4764.112000] usb 5-3: new high speed USB device using ehci_hcd and address 8
[ 4764.244000] PM: Adding info for usb:5-3
[ 4764.244000] PM: Adding info for No Bus:usbdev5.8_ep00
[ 4764.244000] usb 5-3: configuration #1 chosen from 1 choice
[ 4764.244000] PM: Adding info for usb:5-3:1.0
[ 4764.244000] scsi6 : SCSI emulation for USB Mass Storage devices
[ 4764.244000] PM: Adding info for No Bus:host6
[ 4764.244000] PM: Adding info for No Bus:usbdev5.8_ep81
[ 4764.244000] PM: Adding info for No Bus:usbdev5.8_ep02
[ 4764.244000] PM: Adding info for No Bus:usbdev5.8
[ 4764.244000] usb-storage: device found at 8
[ 4764.244000] usb-storage: waiting for device to settle before scanning
[ 4769.244000] usb-storage: device scan complete
[ 4769.244000] PM: Adding info for No Bus:target6:0:0
[ 4769.244000] scsi 6:0:0:0: Direct-Access     Maxtor 6 Y120L0
  0811 PQ: 0 ANSI: 0
[ 4769.244000] PM: Adding info for No Bus:target6:0:1
[ 4769.244000] PM: Removing info for No Bus:target6:0:1
[ 4769.244000] PM: Adding info for No Bus:target6:0:2
[ 4769.244000] PM: Removing info for No Bus:target6:0:2
[ 4769.244000] PM: Adding info for No Bus:target6:0:3
[ 4769.244000] PM: Removing info for No Bus:target6:0:3
[ 4769.244000] PM: Adding info for No Bus:target6:0:4
[ 4769.244000] PM: Removing info for No Bus:target6:0:4
[ 4769.244000] PM: Adding info for No Bus:target6:0:5
[ 4769.244000] PM: Removing info for No Bus:target6:0:5
[ 4769.244000] PM: Adding info for No Bus:target6:0:6
[ 4769.244000] PM: Removing info for No Bus:target6:0:6
[ 4769.244000] PM: Adding info for No Bus:target6:0:7
[ 4769.244000] PM: Removing info for No Bus:target6:0:7
[ 4769.244000] PM: Adding info for scsi:6:0:0:0
[ 4769.248000] sd 6:0:0:0: [sdb] 240121728 512-byte hardware sectors (122942 ...
[ message continues ]

Hi Daniel,




Regards,
Michal

-- 
LOG
http://www.stardust.webpages.pl/log/
-

[ message continues ]

Hi Michal and thanks for your reply,



Attached.

Thanks for your input!
-- 
Daniel J Blueman
[ message continues ]

Although the bug occurred in the context of the khubd process, you can
see from the stack dump that the actual problem appears to lie in the
driver-model core.

Alan Stern

-

[ message continues ]

linux-usb-devel should be CCed on this


-- 
Jiri Kosina
-

[ message continues ]

Then a whole slew of these by-now-familiar messages.

Try disabling CONFIG_USB_SUSPEND.  It makes lots of USB bugs go away:

 - scanners apps work instead of displaying black preview screens
 - printers stop spontaneously disconnecting
 - USB storage devices mysteriously work again
 - Blackberries start charging when plugged in


-

[ message continues ]

I'll give it a shot. For the record, I wasn't trying to perform a
suspend at this time (or since booting).

Thanks for your help,
  Daniel
-- 
Daniel J Blueman
-

[ message continues ]

I doubt that USB suspend has any connection with this problem.  It's
clear that the problem occurs in the driver core when the SCSI core
tries to unregister a device.  It's not directly related to USB at all.

In fact, it looks like the bug is connected with 
CONFIG_SYSFS_DEPRECATED.  You can try to see what happens with that 
switch disabled.

Alan Stern

-

[ message continues ]

On Wed, 11 Jul 2007 17:41:13 -0400 (EDT),

Hm, it seems that the class device's kobject is not set up correctly
(at least, not its name) when make_class_name() is called. Might be
that it is unregistered before it has been added completely (at least,

Turning on verbose driver core messages (CONFIG_DEBUG_DRIVER) while
leaving on CONFIG_SYSFS_DEPRECATED may also be worthwile.
-

[ message continues ]

I have tried to duplicate these two bugs and failed.  On a vanilla
2.6.22 system I set up a USB mass storage device to return an error for
the third and all subsequent reads, so the partition-detection code was
able to learn about the primary partition and the first logical
partition but not the others.  In spite of the error at this point, the
kernel cleaned up properly:

[  550.237869] usb 11-1: new high speed USB device using dummy_hcd and address 7
[  550.401599] usb 11-1: Product: File-backed Storage Gadget
[  550.401603] usb 11-1: Manufacturer: Linux 2.6.22 with dummy_udc
[  550.401606] usb 11-1: SerialNumber: 3238204E6F76
[  550.401866] usb 11-1: configuration #1 chosen from 1 choice
[  550.405661] g_file_storage gadget: high speed config #1
[  550.414507] scsi3 : SCSI emulation for USB Mass Storage devices
[  550.433601] scsi 3:0:0:0: Direct-Access     Linux    File-Stor Gadget 0302 PQ: 0 ANSI: 2
[  550.479009] sd 3:0:0:0: [sda] 64 512-byte hardware sectors (0 MB)
[  550.597318] sd 3:0:0:0: [sda] Write Protect is off
[  550.597385] sd 3:0:0:0: [sda] Assuming drive cache: write through
[  550.620293] sd 3:0:0:0: [sda] 64 512-byte hardware sectors (0 MB)
[  550.737089] sd 3:0:0:0: [sda] Write Protect is off
[  550.737154] sd 3:0:0:0: [sda] Assuming drive cache: write through
[  550.737211]  sda: sda1 sda4 < sda5<7>dummy_udc dummy_udc: disabled ep-a
[  550.884808] usb 11-1: reset high speed USB device using dummy_hcd and address 7
[  551.032553] usb 11-1: can't restore configuration #1 (error=-32)
[  551.032682] usb 11-1: USB disconnect, address 7
[  551.033861] sd 3:0:0:0: [sda] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
[  551.033873] end_request: I/O error, dev sda, sector 40
[  551.033932] Buffer I/O error on device sda, logical block 5
[  551.034228] sd 3:0:0:0: [sda] Result: hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK,SUGGEST_OK
[  551.034236] end_request: I/O error, dev sda, sector 40
[  551.034290] Buffer I/O error on device sda, logical ...
[ message continues ]