Ubuntu
linux-source-2.6.20 package

USB problems on IBM T41 laptop

Bug #98608 reported by Perry E. Metzger on 2007-03-29

This bug report is a duplicate of: Bug #88746: ehci_hcd module causes I/O errors in USB 2.0 devices. Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	Incomplete	Undecided	Unassigned
	linux-source-2.6.20 (Ubuntu)	Won't Fix	Undecided	Unassigned

Bug Description

Under Feisty, plugging in a USB high speed flash device (or just about anything else that uses USB high speed) results in the following messages showing up in the log (and a failure to connect the device):

Mar 29 09:28:43 hackworth kernel: [156070.920000] usb 4-4: new high speed USB device using ehci_hcd and address 5
Mar 29 09:28:47 hackworth kernel: [156075.204000] usb 4-4: new high speed USB device using ehci_hcd and address 19
Mar 29 09:28:49 hackworth kernel: [156077.220000] usb 4-4: new high speed USB device using ehci_hcd and address 26
Mar 29 09:28:51 hackworth kernel: [156079.236000] usb 4-4: new high speed USB device using ehci_hcd and address 31
Mar 29 09:28:52 hackworth kernel: [156080.244000] usb 4-4: new high speed USB device using ehci_hcd and address 34
Mar 29 09:29:02 hackworth kernel: [156090.072000] usb 4-4: new high speed USB device using ehci_hcd and address 72
Mar 29 09:29:03 hackworth kernel: [156091.080000] usb 4-4: new high speed USB device using ehci_hcd and address 75
Mar 29 09:29:05 hackworth kernel: [156093.096000] usb 4-4: new high speed USB device using ehci_hcd and address 82

The messages repeat over and over and the device never mounts.

If I do a "rmmod ehci_hcd",

Mar 29 09:30:15 hackworth kernel: [156162.472000] ehci_hcd 0000:00:1d.7: USB bus 4 deregistered
Mar 29 09:30:15 hackworth kernel: [156162.472000] ACPI: PCI interrupt for device 0000:00:1d.7 disabled

the device will then be recognized and mount normally:

Mar 29 09:31:20 hackworth kernel: [156227.792000] usb 2-2: new full speed USB device using uhci_hcd and address 2
Mar 29 09:31:20 hackworth kernel: [156227.960000] usb 2-2: configuration #1 chosen from 1 choice
Mar 29 09:31:20 hackworth kernel: [156228.100000] usbcore: registered new interface driver libusual
Mar 29 09:31:20 hackworth kernel: [156228.112000] Initializing USB Mass Storage driver...
Mar 29 09:31:20 hackworth kernel: [156228.112000] scsi2 : SCSI emulation for USB Mass Storage devices
Mar 29 09:31:20 hackworth kernel: [156228.112000] usbcore: registered new interface driver usb-storage
Mar 29 09:31:20 hackworth kernel: [156228.112000] USB Mass Storage support registered.
Mar 29 09:31:20 hackworth kernel: [156228.112000] usb-storage: device found at 2
Mar 29 09:31:20 hackworth kernel: [156228.112000] usb-storage: waiting for device to settle before scanning
Mar 29 09:31:25 hackworth kernel: [156233.112000] usb-storage: device scan complete
Mar 29 09:31:25 hackworth kernel: [156233.116000] scsi 2:0:0:0: Direct-Access Generic STORAGE DEVICE 0026 PQ: 0 ANSI: 0
Mar 29 09:31:25 hackworth kernel: [156233.120000] SCSI device sdb: 512000 512-byte hdwr sectors (262 MB)
Mar 29 09:31:25 hackworth kernel: [156233.124000] sdb: Write Protect is off
Mar 29 09:31:25 hackworth kernel: [156233.124000] sdb: Mode Sense: 02 00 00 00
Mar 29 09:31:25 hackworth kernel: [156233.124000] sdb: assuming drive cache: write through
Mar 29 09:31:25 hackworth kernel: [156233.136000] SCSI device sdb: 512000 512-byte hdwr sectors (262 MB)
Mar 29 09:31:25 hackworth kernel: [156233.144000] sdb: Write Protect is off
Mar 29 09:31:25 hackworth kernel: [156233.144000] sdb: Mode Sense: 02 00 00 00
Mar 29 09:31:25 hackworth kernel: [156233.144000] sdb: assuming drive cache: write through
Mar 29 09:31:25 hackworth kernel: [156233.144000] sdb: sdb1
Mar 29 09:31:25 hackworth kernel: [156233.148000] sd 2:0:0:0: Attached scsi removable disk sdb
Mar 29 09:31:25 hackworth kernel: [156233.148000] sd 2:0:0:0: Attached scsi generic sg2 type 0

Clearly this is some sort of bug or deficiency in the ehci_hcd module. The ehci device works just fine under other operating systems including Windows and NetBSD.

Tags:

Revision history for this message

Brian Murray (brian-murray) wrote on 2007-03-29:

Thanks for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description doesn't yet have enough information.
Please include the following additional information, if you have not already done so (please pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command 'uname -a' in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command 'dmesg > dmesg.log' and attach the resulting file 'dmesg.log' to this bug report.
3. Please run the command 'sudo lspci -vvnn > lspci-vvnn.log' and attach the resulting file 'lspci-vvnn.log' to this bug report.
For your reference, the full description of procedures for kernel-related bug reports is available at https://wiki.ubuntu.com/KernelTeamBugPolicies . Thanks in advance!

Revision history for this message

Perry E. Metzger (perry-piermont) wrote on 2007-03-30:

dmesg log Edit (121.5 KiB, text/plain)

As requested:

$ uname -a
Linux hackworth 2.6.20-13-generic #2 SMP Sun Mar 25 00:21:25 UTC 2007 i686 GNU/Linux

Attached please find dmesg and lspci output.

Revision history for this message

Perry E. Metzger (perry-piermont) wrote on 2007-03-30:

lspci output Edit (11.1 KiB, text/plain)

lspci output is attached.

Brian Murray (brian-murray) on 2007-03-30

Changed in linux-source-2.6.20:
assignee:	brian-murray → ubuntu-kernel-team
status:	Needs Info → Confirmed

Revision history for this message

Perry E. Metzger (perry-piermont) wrote on 2007-07-07:

Does it really take three months to decide if a bug that prevents users from touching any USB high speed peripheral is important or not?

Revision history for this message

Perry E. Metzger (perry-piermont) wrote on 2007-09-22:

I'm starting to wonder whether anyone actually cares at all. Five months and you can't even assign a priority to the bug?

Revision history for this message

Jukka Laurila (jlaurila) wrote on 2007-11-01:

Gutsy has the same problem and the temporary workaround "rmmod ehci_ucd" works there as well.

Revision history for this message

Perry E. Metzger (perry-piermont) wrote on 2007-11-01: Re: [Bug 98608] Re: USB problems on IBM T41 laptop

Jukka Laurila <email address hidden> writes:
> Gutsy has the same problem and the temporary workaround "rmmod ehci_ucd"
> works there as well.

Wouldn't it be nice if we didn't have to use a workaround.

Perry

Revision history for this message

Perry E. Metzger (perry-piermont) wrote on 2008-05-02:

I can now confirm that Hardy still has the same problem.

Revision history for this message

Leann Ogasawara (leannogasawara) wrote on 2008-05-02:

Hi Perry,

This seems to be a duplicate of bug 88746. Care to take a look. I realize it's a rather long thread of comments to follow, but I'd point you to comment https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/88746/comments/228 which was made by one of kernel developers. Thanks.

Revision history for this message

Perry E. Metzger (perry-piermont) wrote on 2008-05-02:

#10

Leann Ogasawara <email address hidden> writes:
> This seems to be a duplicate of bug 88746. Care to take a look. I
> realize it's a rather long thread of comments to follow, but I'd point
> you to comment
> https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/88746/comments/228
> which was made by one of kernel developers. Thanks.

It does look like a duplicate.

I'll note that under other OSes, it seems possible to autosuspend and
to use USB 2.0 at the same time -- I'm not convinced that both
problems can't be fixed.

Perry

Revision history for this message

Leann Ogasawara (leannogasawara) wrote on 2008-05-02:

#11

I'll go ahead and mark this as a duplicate. You'll want to follow up with any further comments to that bug report. You may also want to take a peek at bug 61235 which might also be related to the issue you are seeing. There were comments there that they see improvements using the 2.6.25 upstream kernel which is what the upcoming Intrepid Ibex 8.10 kernel is currently rebased with. You might want to test it out and see if it helps. Thanks.

Revision history for this message

Launchpad Janitor (janitor) wrote on 2008-08-11: This bug is now reported against the 'linux' package

#12

Beginning with the Hardy Heron 8.04 development cycle, all open Ubuntu kernel bugs need to be reported against the "linux" kernel package. We are automatically migrating this bug to the new "linux" package. However, development has already began for the upcoming Intrepid Ibex 8.10 release. It would be helpful if you could test the upcoming release and verify if this is still an issue - http://www.ubuntu.com/testing . If the issue still exists, please update this report by changing the Status of the "linux" task from "Incomplete" to "New". We appreciate your patience and understanding as we make this transition. Thanks!

Revision history for this message

Launchpad Janitor (janitor) wrote on 2008-12-23: Kernel team bugs

#13

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.