Bug 4033 - usb mass storage device isn't recognized anymore
usb mass storage device isn't recognized anymore
Status: REJECTED INSUFFICIENT_DATA
Product: Drivers
Classification: Unclassified
Component: USB
i386 Linux
: P2 normal
Assigned To: Greg Kroah-Hartman
:
Depends on:
Blocks: USB
  Show dependency treegraph
 
Reported: 2005-01-13 03:29 UTC by Arnout Boelens
Modified: 2006-02-13 08:02 UTC (History)
1 user (show)

See Also:
Kernel Version: 2.6.10
Tree: Mainline
Regression: ---


Attachments

Description Arnout Boelens 2005-01-13 03:29:17 UTC
Distribution: Debian unstable 
Hardware Environment: AMD Duron 
Software Environment: 
 
Reading specs from /usr/lib/gcc-lib/i486-linux/3.3.5/specs 
Configured with: ../src/configure -v 
--enable-languages=c,c++,java,f77,pascal,objc,ada,treelang --prefix=/usr 
--mandir=/usr/share/man --infodir=/usr/share/info 
--with-gxx-include-dir=/usr/include/c++/3.3 --enable-shared --with-system-zlib 
--enable-nls --without-included-gettext --enable-__cxa_atexit 
--enable-clocale=gnu --enable-debug --enable-java-gc=boehm 
--enable-java-awt=xlib --enable-objc-gc i486-linux 
Thread model: posix 
gcc version 3.3.5 (Debian 1:3.3.5-6) 
 
coreutils [fileutils]         5.2.1-2 
fileutils                     5.2.1-2 
initrd-tools                  0.1.76 
module-init-tools             3.1-rel-2 
 
Problem Description: 
 
I upgraded my kernel from 2.6.8 (debian-package kernel-image-2.6.8-2-k7) to 
2.6.10 k7 (package kernel-image-2.6.10-1-k7) and as a result my digital camera 
(Konica dimage Z1) isn't recognized anymore. I used to be able to mount it as a 
mass storage device but now nothing happens anymore when plugging it in, 
nothing appears in the kernel log.
Comment 1 Simon Schoar 2005-04-24 08:07:16 UTC
I have the same problem (FinePix S5500) on my debian sarge after upgrading from
vanilla 2.6.10 to vanilla 2.6.11.7 

Apr 24 16:32:32 grasshopper kernel: usb 3-1: new full speed USB device using
uhci_hcd and address 2
Apr 24 16:32:34 grasshopper kernel: Initializing USB Mass Storage driver...
Apr 24 16:32:34 grasshopper kernel: usbcore: registered new driver usb-storage
Apr 24 16:32:34 grasshopper kernel: USB Mass Storage support registered.

Apr 24 16:35:14 grasshopper kernel: usb 3-1: USB disconnect, address 2

grasshopper# lsmod | grep usb
usb_storage            66112  0
scsi_mod               75040  4 usb_storage,sd_mod,sg,sr_mod

No devices (/dev/sda) are created. Would it be helpful if i compile verbose
usb/scsi output in ? Any other tests i could do to help you ?
Comment 2 Simon Schoar 2005-04-24 09:00:21 UTC
ok, dont ask, do it. Here comes the verbose output. I believe that the problem
resides in the usb-storage module (because with .10 the mass storage gets
detected by usb-storage module, no scsi interaction yet, thats the point where
11.7 stops) - reassign bug ??? :

2.6.11.7 (not working):
Apr 24 17:32:57 grasshopper kernel: Initializing USB Mass Storage driver...
Apr 24 17:32:57 grasshopper kernel: usbcore: registered new driver usb-storage
Apr 24 17:32:57 grasshopper kernel: USB Mass Storage support registered.
Apr 24 17:33:02 grasshopper kernel: hub 1-0:1.0: state 5 ports 6 chg 0000 evt 0008
Apr 24 17:33:02 grasshopper kernel: ehci_hcd 0000:00:1d.7: GetStatus port 3
status 001803 POWER sig=j  CSC CONNECT
Apr 24 17:33:02 grasshopper kernel: hub 1-0:1.0: port 3, status 0501, change
0001, 480 Mb/s
Apr 24 17:33:02 grasshopper kernel: hub 1-0:1.0: debounce: port 3: total 100ms
stable 100ms status 0x501
Apr 24 17:33:02 grasshopper kernel: ehci_hcd 0000:00:1d.7: port 3 full speed -->
companion
Apr 24 17:33:02 grasshopper kernel: ehci_hcd 0000:00:1d.7: GetStatus port 3
status 003801 POWER OWNER sig=j  CONNECT
Apr 24 17:33:02 grasshopper kernel: uhci_hcd 0000:00:1d.1: wakeup_hc
Apr 24 17:33:02 grasshopper kernel: hub 3-0:1.0: state 5 ports 2 chg 0000 evt 0002
Apr 24 17:33:02 grasshopper kernel: uhci_hcd 0000:00:1d.1: port 1 portsc 0083,00
Apr 24 17:33:02 grasshopper kernel: hub 3-0:1.0: port 1, status 0101, change
0001, 12 Mb/s
Apr 24 17:33:02 grasshopper kernel: hub 3-0:1.0: debounce: port 1: total 100ms
stable 100ms status 0x101
Apr 24 17:33:03 grasshopper kernel: usb 3-1: new full speed USB device using
uhci_hcd and address 2
Apr 24 17:33:03 grasshopper kernel: usb 3-1: new device strings: Mfr=0,
Product=2, SerialNumber=3
Apr 24 17:33:03 grasshopper kernel: usb 3-1: default language 0x0409
Apr 24 17:33:03 grasshopper kernel: usb 3-1: Product: USB Mass Storage
Apr 24 17:33:03 grasshopper kernel: usb 3-1: SerialNumber:
Y-752^^^^^040915XFPX0003005909
Apr 24 17:33:03 grasshopper kernel: usb 3-1: hotplug
Apr 24 17:33:03 grasshopper kernel: usb 3-1: adding 3-1:1.0 (config #1, interface 0)
Apr 24 17:33:03 grasshopper kernel: usb 3-1:1.0: hotplug
Apr 24 17:33:03 grasshopper kernel: hub 3-0:1.0: state 5 ports 2 chg 0000 evt 0002

2.6.10 (working):
Apr 24 17:49:58 grasshopper kernel: Initializing USB Mass Storage driver...
Apr 24 17:49:58 grasshopper kernel: usbcore: registered new driver usb-storage
Apr 24 17:49:58 grasshopper kernel: USB Mass Storage support registered.
Apr 24 17:50:03 grasshopper kernel: hub 1-0:1.0: state 5 ports 6 chg ffc0 evt 0008
Apr 24 17:50:03 grasshopper kernel: ehci_hcd 0000:00:1d.7: GetStatus port 3
status 001803 POWER sig=j  CSC CONNECT
Apr 24 17:50:03 grasshopper kernel: hub 1-0:1.0: port 3, status 0501, change
0001, 480 Mb/s
Apr 24 17:50:03 grasshopper kernel: hub 1-0:1.0: debounce: port 3: total 100ms
stable 100ms status 0x501
Apr 24 17:50:04 grasshopper kernel: ehci_hcd 0000:00:1d.7: port 3 full speed -->
companion
Apr 24 17:50:04 grasshopper kernel: ehci_hcd 0000:00:1d.7: GetStatus port 3
status 003801 POWER OWNER sig=j  CONNECT
Apr 24 17:50:04 grasshopper kernel: hub 3-0:1.0: state 5 ports 2 chg fffc evt 0002
Apr 24 17:50:04 grasshopper kernel: uhci_hcd 0000:00:1d.1: port 1 portsc 0083,00
Apr 24 17:50:04 grasshopper kernel: hub 3-0:1.0: port 1, status 0101, change
0001, 12 Mb/s
Apr 24 17:50:04 grasshopper kernel: uhci_hcd 0000:00:1d.1: wakeup_hc
Apr 24 17:50:04 grasshopper kernel: hub 3-0:1.0: debounce: port 1: total 100ms
stable 100ms status 0x101
Apr 24 17:50:04 grasshopper kernel: usb 3-1: new full speed USB device using
uhci_hcd and address 2
Apr 24 17:50:04 grasshopper kernel: usb 3-1: new device strings: Mfr=0,
Product=2, SerialNumber=3
Apr 24 17:50:04 grasshopper kernel: usb 3-1: default language 0x0409
Apr 24 17:50:04 grasshopper kernel: usb 3-1: Product: USB Mass Storage
Apr 24 17:50:04 grasshopper kernel: usb 3-1: SerialNumber:
Y-752^^^^^040915XFPX0003005909
Apr 24 17:50:04 grasshopper kernel: usb 3-1: hotplug
Apr 24 17:50:04 grasshopper kernel: usb 3-1: adding 3-1:1.0 (config #1, interface 0)
Apr 24 17:50:04 grasshopper kernel: usb 3-1:1.0: hotplug
Apr 24 17:50:04 grasshopper kernel: usb-storage 3-1:1.0: usb_probe_interface
Apr 24 17:50:04 grasshopper kernel: usb-storage 3-1:1.0: usb_probe_interface -
got id
Apr 24 17:50:04 grasshopper kernel: usb-storage: USB Mass Storage device detected
Apr 24 17:50:04 grasshopper kernel: usb-storage: -- associate_dev
Apr 24 17:50:04 grasshopper kernel: usb-storage: Vendor: 0x04cb, Product:
0x016e, Revision: 0x0100
Apr 24 17:50:04 grasshopper kernel: usb-storage: Interface Subclass: 0x06,
Protocol: 0x50
Apr 24 17:50:04 grasshopper kernel: usb-storage: Vendor: Unknown,  Product: USB
Mass Storage
Apr 24 17:50:04 grasshopper kernel: usb-storage: Transport: Bulk
Apr 24 17:50:04 grasshopper kernel: usb-storage: Protocol: Transparent SCSI
Apr 24 17:50:04 grasshopper kernel: usb-storage: usb_stor_control_msg: rq=fe
rqtype=a1 value=0000 index=00 len=1
Apr 24 17:50:04 grasshopper kernel: usb-storage: GetMaxLUN command result is 1,
data is 0
Apr 24 17:50:04 grasshopper kernel: scsi0 : SCSI emulation for USB Mass Storage
devices
...
Comment 3 Simon Schoar 2005-04-28 19:45:28 UTC
This depends on udev/hotplug stuff.

Remove CONFIG_BLK_DEV_UB (Device Drivers/Block devices/Low Performance USB Block
driver) from your kernel config - works for me!
Comment 4 Adrian Bunk 2005-08-30 07:17:12 UTC
Is this problem still present:
- in kernel 2.6.13 and
- with CONFIG_BLK_DEV_UB=n?
Comment 5 Adrian Bunk 2006-02-13 08:02:10 UTC
I'm assuming this issue is already fixed.

Please reopen this bug if it's still present in recent 2.6 kernels.

Note You need to log in before you can comment on or make changes to this bug.