Hi,
One of our users reported that he had some issues with its Sony Walkman
after switching from 2.6.30_rc7(-git2) to 2.6.30_rc8(-git6).
2.6.30_rc7
-----------------
kernel: [ 108.441141] usb 2-6: new high speed USB device using ehci_hcd and
address 4
kernel: [ 108.556121] usb 2-6: New USB device found, idVendor=054c,
idProduct=036e
kernel: [ 108.556129] usb 2-6: New USB device strings: Mfr=1, Product=2,
SerialNumber=5
kernel: [ 108.556138] usb 2-6: Product: WALKMAN
kernel: [ 108.556143] usb 2-6: Manufacturer: SONY
kernel: [ 108.556149] usb 2-6: SerialNumber: 390100011A5487120002D8F517EBC712
kernel: [ 108.556319] usb 2-6: configuration #1 chosen from 1 choice
kernel: [ 108.683661] Initializing USB Mass Storage driver...
kernel: [ 108.697813] scsi6 : SCSI emulation for USB Mass Storage devices
kernel: [ 108.698127] usbcore: registered new interface driver usb-storage
kernel: [ 108.698130] USB Mass Storage support registered.
kernel: [ 108.699047] usb-storage: device found at 4
kernel: [ 108.699049] usb-storage: waiting for device to settle before
scanning
kernel: [ 109.699338] usb-storage: device scan complete
kernel: [ 109.699951] scsi 6:0:0:0: Direct-Access SONY WALKMAN
1.00 PQ: 0 ANSI: 4
kernel: [ 109.701500] sd 6:0:0:0: Attached scsi generic sg2 type 0
kernel: [ 109.704761] sd 6:0:0:0: [sdb] 956544 2048-byte hardware sectors:
(1.95 GB/1.82 GiB)
kernel: [ 109.705274] sd 6:0:0:0: [sdb] Write Protect is off
kernel: [ 109.705281] sd 6:0:0:0: [sdb] Mode Sense: 3e 00 00 00
kernel: [ 109.705287] sd 6:0:0:0: [sdb] Assuming drive cache: write through
kernel: [ 109.706885] sd 6:0:0:0: [sdb] 956544 2048-byte hardware sectors:
(1.95 GB/1.82 GiB)
kernel: [ 109.738043] sd 6:0:0:0: [sdb] Assuming drive cache: write through
kernel: [ 109.738047] sdb: sdb1
kernel: [ 109.751755] sd 6:0:0:0: [sdb] Attached SCSI removable disk
kernel: [ 115.288030] FAT: utf8 is not a recommended IO charset for FAT
filesystems, filesystem will be case sensitive!
hald: mounted /dev/sdb1 on behalf of uid 1000
2.6.30_rc8
-----------
kernel: [210.259083] usb 2-6: new high speed USB device using ehci_hcd and
address 5
kernel: [210.374010] usb 2-6: New USB device found, idVendor=054c,
idProduct=036e
kernel: [210.374019] usb 2-6: New USB device strings: Mfr=1, Product=2,
SerialNumber=5
kernel: [210.374028] usb 2-6: Product: WALKMAN
kernel: [210.374033] usb 2-6: Manufacturer: SONY
kernel: [210.374038] usb 2-6: SerialNumber: 390100011A5487120002D8F517EBC712
kernel: [210.374216] usb 2-6: configuration #1 chosen from 1 choice
kernel: [210.381558] scsi7 : SCSI emulation for USB Mass Storage devices
kernel: [210.381893] usb-storage: device found at 5
kernel: [210.381899] usb-storage: waiting for device to settle before scanning
I looked a little bit the differences between rc7 and rc8 and the only commit that could be related to that problem seems to be:
d5a877e8dd409d8c702986d06485c374b705d340 async: make sure independent async domains can't accidentally entangle
I'm also attaching the kernel configuration. I'll make him to try again with the stable 2.6.30.
Thanks.
On Fri, 12 Jun 2009, [UTF-8] Ozan Çağlayan wrote:
> Hi,
>
> One of our users reported that he had some issues with its Sony Walkman
> after switching from 2.6.30_rc7(-git2) to 2.6.30_rc8(-git6).
> 2.6.30_rc8
> -----------
>
> kernel: [210.259083] usb 2-6: new high speed USB device using ehci_hcd and
> address 5
> kernel: [210.374010] usb 2-6: New USB device found, idVendor=054c,
> idProduct=036e
> kernel: [210.374019] usb 2-6: New USB device strings: Mfr=1, Product=2,
> SerialNumber=5
> kernel: [210.374028] usb 2-6: Product: WALKMAN
> kernel: [210.374033] usb 2-6: Manufacturer: SONY
> kernel: [210.374038] usb 2-6: SerialNumber: 390100011A5487120002D8F517EBC712
> kernel: [210.374216] usb 2-6: configuration #1 chosen from 1 choice
> kernel: [210.381558] scsi7 : SCSI emulation for USB Mass Storage devices
> kernel: [210.381893] usb-storage: device found at 5
> kernel: [210.381899] usb-storage: waiting for device to settle before scanning
>
>
> I looked a little bit the differences between rc7 and rc8 and the only commit that could be related to that problem seems to be:
>
> d5a877e8dd409d8c702986d06485c374b705d340 async: make sure independent async domains can't accidentally entangle
>
> I'm also attaching the kernel configuration. I'll make him to try
> again with the stable 2.6.30.
If this persists in 2.6.30, report it on the linux-scsi mailing list.
Alan Stern