Ubuntu
linux package

Sansa Fuze (via usb-storage) in "auto-detect" mode stopped working in Karmic

Bug #463977 reported by Kees Cook on 2009-10-30

This bug affects 7 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Won't Fix	Low	Unassigned

Bug Description

Jaunty (and earlier Karmic kernels) could detect and communicate with my Sansa Fuze. It seems that something changed sort of recently.

When connecting, I see:
[184289.430019] usb 1-3: new high speed USB device using ehci_hcd and address 6
[184289.581591] usb 1-3: configuration #1 chosen from 1 choice
[184289.587598] scsi10 : SCSI emulation for USB Mass Storage devices
[184289.593124] usb-storage: device found at 6
[184289.593127] usb-storage: waiting for device to settle before scanning
[184294.594090] usb-storage: device scan complete
[184316.073257] usb 1-3: reset high speed USB device using ehci_hcd and address 6
[184316.460028] usb 1-3: reset high speed USB device using ehci_hcd and address 6
[184322.832529] usb 1-3: reset high speed USB device using ehci_hcd and address 6
[184323.210264] usb 1-3: reset high speed USB device using ehci_hcd and address 6
[184323.619320] usb 1-3: reset high speed USB device using ehci_hcd and address 6
[184323.867700] scsi 10:0:0:0: Device offlined - not ready after error recovery

Normally, it would there would be no USB resets, the an sd* device would appear.

ProblemType: Bug
AplayDevices:
**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC268 Analog [ALC268 Analog]
   Subdevices: 0/1
   Subdevice #0: subdevice #0
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: kees 6677 F.... pulseaudio
/dev/snd/pcmC0D0p: kees 6677 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xe0420000 irq 22'
   Mixer name : 'Realtek ALC268'
   Components : 'HDA:10ec0268,80860000,00100003'
   Controls : 18
   Simple ctrls : 12
Date: Thu Oct 29 17:45:04 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=/dev/md1
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-14-generic root=/dev/mapper/systemvg-root2lv ro splash
ProcEnviron:
LANGUAGE=en_US.UTF-8
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
linux-backports-modules-2.6.31-14-generic N/A
linux-firmware 1.24
RfKill:

SourcePackage: linux
Uname: Linux 2.6.31-14-generic x86_64
WpaSupplicantLog:

dmi.bios.date: 09/22/2008
dmi.bios.vendor: Intel Corp.
dmi.bios.version: JOQ3510J.86A.0954.2008.0922.2331
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DQ35JO
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD82085-800
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrJOQ3510J.86A.0954.2008.0922.2331:bd09/22/2008:svn:pn:pvr:rvnIntelCorporation:rnDQ35JO:rvrAAD82085-800:cvn:ct3:cvr:

Tags:

Revision history for this message

Kees Cook (kees) wrote on 2009-10-30:

AlsaDevices.txt Edit (461 bytes, text/plain; charset="utf-8")
ArecordDevices.txt Edit (270 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (58.7 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (2.4 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.2.txt Edit (7.3 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (103.2 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.2 KiB, text/plain; charset="utf-8")
IwConfig.txt Edit (138 bytes, text/plain; charset="utf-8")
Lspci.txt Edit (16.2 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (718 bytes, text/plain; charset="utf-8")
PciMultimedia.txt Edit (599 bytes, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (2.9 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (2.2 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (5.4 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (169.3 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (287.5 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (8.9 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (659.8 KiB, text/plain; charset="utf-8")

Revision history for this message

Kees Cook (kees) wrote on 2009-10-30:

I've seen this on two Karmic machines that I've tested the Sansa on.

tags:

added: regression-potential

Leann Ogasawara (leannogasawara) on 2009-10-30

Changed in linux (Ubuntu):
importance:	Undecided → High
status:	New → Triaged

Revision history for this message

Kees Cook (kees) wrote on 2009-10-30:

The device works correctly if it is configured to "MSC" mode (instead of "Auto"). "Auto" used to work, but "MSC" is a good work-around.

Normal connect looks like this:

[ 8379.032069] usb 1-1: new high speed USB device using ehci_hcd and address 8
[ 8379.166161] usb 1-1: configuration #1 chosen from 1 choice
[ 8379.174374] scsi4 : SCSI emulation for USB Mass Storage devices
[ 8379.174665] usb-storage: device found at 8
[ 8379.174671] usb-storage: waiting for device to settle before scanning
[ 8384.172443] usb-storage: device scan complete
[ 8384.173186] scsi 4:0:0:0: Direct-Access SanDisk Sansa Fuze 4GB v02. PQ: 0 ANSI: 0
[ 8384.173800] scsi 4:0:0:1: Direct-Access SanDisk Sansa Fuze 4GB v02. PQ: 0 ANSI: 0
[ 8384.174861] sd 4:0:0:0: Attached scsi generic sg2 type 0
[ 8384.175142] sd 4:0:0:1: Attached scsi generic sg3 type 0
[ 8384.207342] sd 4:0:0:0: [sdb] 7683072 512-byte logical blocks: (3.93 GB/3.66 GiB)
[ 8384.207980] sd 4:0:0:0: [sdb] Write Protect is off
[ 8384.207984] sd 4:0:0:0: [sdb] Mode Sense: 04 00 00 00
[ 8384.207987] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 8384.210072] sd 4:0:0:1: [sdc] 15523840 512-byte logical blocks: (7.94 GB/7.40 GiB)
[ 8384.214947] sd 4:0:0:1: [sdc] Write Protect is off
[ 8384.214952] sd 4:0:0:1: [sdc] Mode Sense: 04 00 00 00
[ 8384.214955] sd 4:0:0:1: [sdc] Assuming drive cache: write through
[ 8384.220527] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 8384.220534] sdb:
[ 8384.233438] sd 4:0:0:1: [sdc] Assuming drive cache: write through
[ 8384.233445] sdc: sdc1
[ 8384.239152] sd 4:0:0:0: [sdb] Assuming drive cache: write through
[ 8384.239159] sd 4:0:0:0: [sdb] Attached SCSI removable disk
[ 8384.240302] sd 4:0:0:1: [sdc] Assuming drive cache: write through
[ 8384.240306] sd 4:0:0:1: [sdc] Attached SCSI removable disk

Leann Ogasawara (leannogasawara) on 2009-10-30

Changed in linux (Ubuntu):
importance:	High → Medium

Revision history for this message

Stefan Bader (smb) wrote on 2009-11-02:

Kees, where/how do you enable that MSC mode and is there any explanation what this would/should do? What does MSC even mean in that context? Also, could you try to capture usb debug data for bus 1 (if you use the same port/hub) as described in https://wiki.ubuntu.com/KernelTeam/Debugging/USB? Thanks.

Revision history for this message

Kees Cook (kees) wrote on 2009-11-04:

"The Sansa Fuze supports MTP (Media Transfer Protocol) and MSC (Mass Storage device Class) for the transfer of media."

And it has (by default) an "auto-detect" mode (which is what this report is about). I may not have time to capture USB details for a bit -- I want to provide both Jaunty and Karmic logs so it'll be meaningful.

Changed in linux (Ubuntu):
importance:	Medium → Low
summary:	- Sansa Fuze (via usb-storage) stopped working in Karmic + Sansa Fuze (via usb-storage) in "auto-detect" mode stopped working in + Karmic

Revision history for this message

brian mcgee (justinisnt) wrote on 2009-11-13:

Changing to MSC mode was a successful workaround for my Sansa Clip. To change to MSC, on your device, go to Settings -> USB Mode -> MSC. HTH

Leann Ogasawara (leannogasawara) on 2009-11-29

tags:

added: regression-release
removed: regression-potential

Leann Ogasawara (leannogasawara) on 2009-12-08

tags:

added: karmic

Revision history for this message

Brad Figg (brad-figg) wrote on 2011-07-14: Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

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

Changed in linux (Ubuntu):
status:	Triaged → Won't Fix

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Bug attachments

Add attachment

Remote bug watches

Bug watches keep track of this bug in other bug trackers.

Ubuntulinux package

Sansa Fuze (via usb-storage) in "auto-detect" mode stopped working in Karmic

Bug Description

Other bug subscribers

Bug attachments

Remote bug watches

Ubuntu
linux package