[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#257526: kernel-image-2.6.7-1-k7: usb mass storage module broken, unlike in 686 precompiled kernel



Andres Salomon <dilinger@voxel.net> writes:

> On Sun, 04 Jul 2004 03:04:16 +0200, Alex Schroeder wrote:
>
>> Package: kernel-image-2.6.7-1-k7
>> Version: 2.6.7-1
>> Severity: normal
>> 
>> 
>> My MP3 player was not recognized under 2.6.6; there was a patch that
>> fixed it.  This patch is now in 2.6.7.  It works when I use
>> kernel-image-2.6.7-1-686.  When I use kernel-image-2.6.7-1-k7,
>> however, it does not work.  The patch affected the file
>
>
> Can you please provide the relevant dmesg output from both kernels?  Does
> the k7 kernel detect it at all, and just fail to initialize/load the
> driver?

Gnah!  I must have been dreaming yesterday night when I thought it
worked in kernel-image-2.6.7-1-686...  :(

I'll try to build a 2.6.7 again, taking into account the
module-init-tools issue from Bug#257469.  The thing is that I cannot
apply the same patch that helped in 2.6.6 to the 2.6.7 sources,
because "it has already been applied".

For the time being, here is the relevant output from the patched
2.6.6, and from both 2.6.7-1-686 and 2.6.7-1-k7, when booting with
the MP3 player connected.  I also have a digital camera.  It's
docking station was connected, but the camera not in the cradle.

2.6.6, patched
==============

...
usbcore: registered new driver usbfs
usbcore: registered new driver hub
ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci_hcd: block sizes: ed 64 td 64
...
ohci_hcd 0000:00:07.4: Advanced Micro Devices [AMD] AMD-756 [Viper] USB
ohci_hcd 0000:00:07.4: irq 5, pci mem c8931000
ohci_hcd 0000:00:07.4: new USB bus registered, assigned bus number 1
ohci_hcd 0000:00:07.4: AMD756 erratum 4 workaround
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
usb 1-2: new full speed USB device using address 2
SCSI subsystem initialized
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
  Vendor:           Model:                   Rev:     
  Type:   Direct-Access                      ANSI SCSI revision: 02
USB Mass Storage device found at 2
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
SCSI device sda: 512000 512-byte hdwr sectors (262 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
 /dev/scsi/host0/bus0/target0/lun0:
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
...

2.6.7-1-686
===========

...
usbcore: registered new driver usbfs
usbcore: registered new driver hub
ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci_hcd: block sizes: ed 64 td 64
...
ohci_hcd 0000:00:07.4: Advanced Micro Devices [AMD] AMD-756 [Viper] USB
ohci_hcd 0000:00:07.4: irq 5, pci mem c8946000
ohci_hcd 0000:00:07.4: new USB bus registered, assigned bus number 1
ohci_hcd 0000:00:07.4: AMD756 erratum 4 workaround
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
usb 1-2: new full speed USB device using address 2
SCSI subsystem initialized
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
  Vendor:           Model:                   Rev:     
  Type:   Direct-Access                      ANSI SCSI revision: 02
USB Mass Storage device found at 2
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
SCSI device sda: 512000 512-byte hdwr sectors (262 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
 /dev/scsi/host0/bus0/target0/lun0:
...
hub 1-0:1.0: port 2 disabled by hub (EMI?), re-enabling...<6>usb 1-2: USB disconnect, address 2
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 0
Buffer I/O error on device sda, logical block 0
scsi0 (0:0): rejecting I/O to device being removed
Buffer I/O error on device sda, logical block 0
 unable to read partition table
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
...
usb 1-2: new full speed USB device using address 3
...
usb 1-2: control timeout on ep0out
...

2.6.7-1-k7
===========

...
usbcore: registered new driver usbfs
usbcore: registered new driver hub
ohci_hcd: 2004 Feb 02 USB 1.1 'Open' Host Controller (OHCI) Driver (PCI)
ohci_hcd: block sizes: ed 64 td 64
...
ohci_hcd 0000:00:07.4: Advanced Micro Devices [AMD] AMD-756 [Viper] USB
ohci_hcd 0000:00:07.4: irq 5, pci mem c8943000
ohci_hcd 0000:00:07.4: new USB bus registered, assigned bus number 1
ohci_hcd 0000:00:07.4: AMD756 erratum 4 workaround
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 4 ports detected
usb 1-2: new full speed USB device using address 2
SCSI subsystem initialized
Initializing USB Mass Storage driver...
scsi0 : SCSI emulation for USB Mass Storage devices
  Vendor:           Model:                   Rev:     
  Type:   Direct-Access                      ANSI SCSI revision: 02
USB Mass Storage device found at 2
usbcore: registered new driver usb-storage
USB Mass Storage support registered.
SCSI device sda: 512000 512-byte hdwr sectors (262 MB)
sda: assuming Write Enabled
sda: assuming drive cache: write through
 /dev/scsi/host0/bus0/target0/lun0:SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 0
Buffer I/O error on device sda, logical block 0
SCSI error : <0 0 0 0> return code = 0x70000
end_request: I/O error, dev sda, sector 0
Buffer I/O error on device sda, logical block 0
 unable to read partition table
Attached scsi removable disk sda at scsi0, channel 0, id 0, lun 0
hub 1-0:1.0: port 2 disabled by hub (EMI?), re-enabling...
...
usb 1-2: USB disconnect, address 2
...
usb 1-2: new full speed USB device using address 3
usb 1-2: control timeout on ep0out
...

I later figured that maybe the digital camera would force other
drivers to load or something like that.  And I found more problems
with USB support.  I think I will need to take this to the
linux-usb-users mailing list.

When I reboot with the camera in the cradle and switched on, the
system hangs after the "usb 1-2: control timeout on ep0out" message.

When I reboot with the camera in the cradle and switched off, then
switch the camera on, and try to mount it, I get an error message
("foo is not a valid block device").  So basically, the USB stuff I'm
using is not working for me in the new kernels.

At the same time, /var/log/syslog reports the following:

Jul  4 14:49:44 confusibombus kernel: ohci_hcd 0000:00:07.4: remote wakeup
Jul  4 14:49:45 confusibombus kernel: usb 1-1: new full speed USB device using address 2
Jul  4 14:49:50 confusibombus kernel: usb 1-1: control timeout on ep0in
Jul  4 14:49:50 confusibombus kernel: SCSI subsystem initialized

Anyway, I'll try to get some 2.6.7 kernel sources I can compile,
switch on USB debugging and all that, and contact linux-usb-users.

Alex.
-- 
.O.  http://www.emacswiki.org/alex/
..O  Schroeder's fourth law:
OOO  None of your friends and coworkers share your taste in music.



Reply to: