pcmcia usb high-speed fails/root on usb device so can't rmmod ehci_hcd

Bug #320314 reported by radsci
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

This is similar to:
  #286575 usb-automount not working - workaround "modprobe -r ehci_hcd"
https://bugs.launchpad.net/token/KkhsfL8NhdQ0L150Xv8d
which became:
http://bugzilla.kernel.org/show_bug.cgi?id=12347

BUT it's on an i386 with root on a usb flash and affects usb ports on an SIIG JU-PCM422-S2 PCMCIA 4 Port USB 2.0 adapter; other pcmcia usb adapters give similar results on this machine, so I tend to suspect the Cardbus Controller.
I got the SIIG to sort of work at high speed on an HP zt3000, but on the machine it's intended for, Compaq V2552US,
there's something about the way it works with the CardBus bridge (Texas Instruments PCIxx21/x515 Cardbus Controller)
that prevents it from working at high speed.

Searches suggested that rmmod ehci_hcd resolves this, but with root on a usb device, it's not an option.
rmmod ohci_hcd followed by reinserting a usb device to the SIIG doesn't let ehci_hcd work, but the device does get
recognized immediately as "full speed" if modprobe ohci_hcd is then given.

I've tried booting with
"pci=assign-busses modprobe=yenta_socket.bios_override=1".
Boot parameters haven't changed anything other than the bus assignment to:
 Bus: primary=00, secondary=01, subordinate=01, sec-latency=64
 Bus: primary=00, secondary=02, subordinate=06, sec-latency=64
 Bus: primary=02, secondary=03, subordinate=06, sec-latency=176
but this didn't fix it.

This is all with the pcmcia adapter plugged in, root on a kingston usb-drive, and another kingston usb-drive plugged in to the SIIG pcmcia USB hub JU-PCM422-S2.

After the attachment was assembled, I tried adding
"options scsi_mod inq_timeout=20"
to /etc/modprobe.d/options
and updating the initrd accordingly, and rebooting with:
 pci=assign-busses module yenta_socket.bios_override=1 scsi_mod.inq_timeout=200

yielding the only apparent difference:
Jan 22 17:29:59 xprime kernel: [ 63.730952] yenta_socket: Unknown symbol pccard_nonstatic_ops
Jan 22 17:29:59 xprime kernel: [ 63.736608] yenta_socket: Unknown symbol pccard_nonstatic_ops

reinserting still yields the usual:
[ 1128.904071] usb 6-4: device descriptor read/64, error -110
[ 1159.448301] usb 6-4: device descriptor read/64, error -110
[ 1159.664066] usb 6-4: reset high speed USB device using ehci_hcd and address 7
[ 1170.072070] usb 6-4: device not accepting address 7, error -110
[ 1170.184080] usb 6-4: reset high speed USB device using ehci_hcd and address 7
[ 1180.592060] usb 6-4: device not accepting address 7, error -110
[ 1180.593818] usb 6-4: USB disconnect, address 7
[ 1180.598271] scsi 5:0:0:0: Device offlined - not ready after error recovery
[ 1180.708053] usb 6-4: new high speed USB device using ehci_hcd and address 8
[...etc...]
and eventual recognition as "full speed"

attached are:
var/log/messages lspci-vvmm lsusb proc/ioports dmidecode lsusb-v lspci-kv proc/version lsb_release-rd

Revision history for this message
radsci (radsci) wrote :
Revision history for this message
radsci (radsci) wrote :

Tried a significantly modified different distribution with a 2.6.27.4 kernel I compiled, (but not
above module parameters)

Same sort of results including "error -110" and "full speed" operation after failure to assign address at high speed.

Revision history for this message
radsci (radsci) wrote :
Download full text (7.0 KiB)

Still not working. Tried some more things.

I may have been using syslinux syntax with GRUB....Booting with

pci=assign-busses modprobe=yenta_socket.bios_override=1,scsi_mod.inq_timeout=20

yields earlier and slightly different detection/config of the CardBus, error -62 during bootup as well as later error -110 like before, but otherwise little difference

dmesg:

[ 5.020060] usb 1-1: new full speed USB device using ohci_hcd and address 3
[ 5.200042] usb 1-1: device descriptor read/64, error -62
[ 5.484041] usb 1-1: device descriptor read/64, error -62
[ 5.764041] usb 1-1: new full speed USB device using ohci_hcd and address 4
[ 5.944040] usb 1-1: device descriptor read/64, error -62

[ 72.789531] yenta_socket: Unknown symbol pccard_nonstatic_ops
[ 72.794825] yenta_socket: Unknown symbol pccard_nonstatic_ops
[ 107.547840] udevd version 124 started
[ 108.523839] pci_hotplug: PCI Hot Plug PCI Core version: 0.5
[ 108.676186] Linux agpgart interface v0.103
[ 108.679461] shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
[ 108.994281] piix4_smbus 0000:00:14.0: SMBus Host Controller at 0x8400, revision 0
[ 109.450400] input: Power Button (FF) as /devices/LNXSYSTM:00/LNXPWRBN:00/input/input2
[ 109.464079] ACPI: Power Button (FF) [PWRF]
[ 109.464303] input: Power Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0C:00/input/input3
[ 109.480045] ACPI: Power Button (CM) [PWRB]
[ 109.480264] input: Sleep Button (CM) as /devices/LNXSYSTM:00/device:00/PNP0C0E:00/input/input4
[ 109.496053] ACPI: Sleep Button (CM) [SLPB]
[ 109.496286] input: Lid Switch as /devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input5
[ 109.496810] ACPI: Lid Switch [LID]
[ 109.612967] ACPI: WMI: Mapper loaded
[ 109.984305] Yenta: CardBus bridge found at 0000:02:09.0 [103c:3091]
[ 109.984386] Yenta: Enabling burst memory read transactions
[ 109.984439] Yenta: Using CSCINT to route CSC interrupts to PCI
[ 109.984485] Yenta: Routing CardBus interrupts to PCI
[ 109.984539] Yenta TI: socket 0000:02:09.0, mfunc 0x01a01b22, devctl 0x66
[ 110.216940] Yenta: ISA IRQ mask 0x0ef8, PCI irq 17
[ 110.216993] Socket status: 30000820
[ 110.217040] pcmcia: parent PCI bridge I/O window: 0xa000 - 0xafff
[ 110.217086] cs: IO port probe 0xa000-0xafff: clean.
[ 110.217402] pcmcia: parent PCI bridge Memory window: 0xc0200000 - 0xc02fffff
[ 110.217448] pcmcia: parent PCI bridge Memory window: 0x40000000 - 0x43ffffff
[ 110.398259] ACPI: AC Adapter [ACAD] (on-line)
[ 110.896052] pccard: CardBus card inserted into slot 0
[ 110.896163] PCI: 0000:03:00.0 reg 10 32bit mmio: [0, fff]
[ 110.896248] pci 0000:03:00.0: supports D1
[ 110.896250] pci 0000:03:00.0: supports D2
[ 110.896254] pci 0000:03:00.0: PME# supported from D0 D1 D2 D3hot
[ 110.896304] pci 0000:03:00.0: PME# disabled
[ 110.896402] PCI: 0000:03:00.1 reg 10 32bit mmio: [0, fff]
[ 110.896484] pci 0000:03:00.1: supports D1
[ 110.896486] pci 0000:03:00.1: supports D2
[ 110.896488] pci 0000:03:00.1: PME# supported from D0 D1 D2 D3hot
[ 110.896538] pci 0000:03:00.1: PME# disabled
[ 110.896638] PCI: 0000:03:00.2 reg 10 32bit mmio: [0, ff]
[ 110.896720] pci 0000:03:00.2: supports D1
[ ...

Read more...

Revision history for this message
radsci (radsci) wrote :
Download full text (3.6 KiB)

new variation seen with last boot parameters:

Plugging in a usb flash disk, then rmmod and modprobe ohci_hcd didn't yield immediate "full speed" recognition but different errors with different hubs (same physical devices) trying at
about the same time.

[46035.084073] usb 1-1: new full speed USB device using ohci_hcd and address 2
[46035.264064] usb 1-1: device descriptor read/64, error -62
[46035.548050] usb 1-1: device descriptor read/64, error -62
[46035.764073] usb 6-4: reset high speed USB device using ehci_hcd and address 7
[46050.876074] usb 6-4: device descriptor read/64, error -110
[46066.092088] usb 6-4: device descriptor read/64, error -110
[46066.372081] usb 1-1: new full speed USB device using ohci_hcd and address 3
[46066.552077] usb 1-1: device descriptor read/64, error -62
[46066.836077] usb 1-1: device descriptor read/64, error -62
[46067.052080] usb 6-4: reset high speed USB device using ehci_hcd and address 7
[46077.460074] usb 6-4: device not accepting address 7, error -110
[46077.636110] usb 1-1: new full speed USB device using ohci_hcd and address 4
[46078.044072] usb 1-1: device not accepting address 4, error -62
[46078.156086] usb 6-4: reset high speed USB device using ehci_hcd and address 7
[46088.564058] usb 6-4: device not accepting address 7, error -110
[46088.565547] scsi 5:0:0:0: Device offlined - not ready after error recovery
[46088.740055] usb 1-1: new full speed USB device using ohci_hcd and address 5
[46089.148062] usb 1-1: device not accepting address 5, error -62
[46089.149466] hub 1-0:1.0: unable to enumerate USB device on port 1
[46089.150807] usb 6-4: USB disconnect, address 7
[46089.264070] usb 6-4: new high speed USB device using ehci_hcd and address 8
[46104.376847] usb 6-4: device descriptor read/64, error -110
[46119.592071] usb 6-4: device descriptor read/64, error -110
[46119.808081] usb 6-4: new high speed USB device using ehci_hcd and address 9
[46134.920054] usb 6-4: device descriptor read/64, error -110
[46150.136071] usb 6-4: device descriptor read/64, error -110
[46150.352083] usb 6-4: new high speed USB device using ehci_hcd and address 10
[46160.760065] usb 6-4: device not accepting address 10, error -110
[46160.872076] usb 6-4: new high speed USB device using ehci_hcd and address 11
[46171.280469] usb 6-4: device not accepting address 11, error -110
[46171.283959] hub 6-0:1.0: unable to enumerate USB device on port 4
[46171.656085] usb 5-2: new full speed USB device using ohci_hcd and address 2
[46171.856968] usb 5-2: not running at top speed; connect to a high speed hub
[46171.926559] usb 5-2: configuration #1 chosen from 1 choice
[46171.954393] scsi6 : SCSI emulation for USB Mass Storage devices
[46171.968230] usb-storage: device found at 2
[46171.968251] usb-storage: waiting for device to settle before scanning
[46176.969430] usb-storage: device scan complete
[46176.976430] scsi 6:0:0:0: Direct-Access Kingston DataTraveler 2.0 PMAP PQ: 0 ANSI: 0 CCS
[46177.637112] sd 6:0:0:0: [sdc] 3903488 512-byte hardware sectors (1999 MB)
[46177.644134] sd 6:0:0:0: [sdc] Write Protect is off
[46177.644144] sd 6:0:0:0: [sdc] Mode Sense: 23 00 00 00
[46177.644148] sd 6:0:0:0: [sdc] Assuming d...

Read more...

Revision history for this message
radsci (radsci) wrote :

moved root (made a livecd)...

apparently, rmmod ehci_hcd / modprobe ehci_hcd DOES NOT FIX THIS.

Revision history for this message
radsci (radsci) wrote :

Tried another PCMCIA card, this one with a VIA 6212 controller which according to various posts works in ubuntu. (Note lspci sees it as VIA 82xxxxx or VIA Technologies, Inc. USB 2.0.) Similar results.

Tried under KNOPPIX 5.3.1. WORKED PERFECTLY AT HIGH SPEED AUTOMATICALLY.

During KNOPPIX boot, messages displayed indicate it's found by cardmgr under udev. Note that this doesn't get reported in dmesg, and /var/log/messages & boot.log aren't enabled by default.

From what I've found, cardmgr is part of pcmcia-cs, depreciated for 2.6 (in favor of pcmciautils), but apparently useful enough for Klaus. Interestingly, ehci_hcd doesn't appear in lsmod, but appears in dmesg, so I surmise it's built-in to the kernel.

Attached is information FROM KNOPPIX.

dd result, uname -a, lsmod, lspci -vvvv, lsusb

cat /proc/cmdline:
ramdisk_size=100000 init=/etc/init lang=de apm=power-off vga=791 initrd=minirt.g
z nomce highres=off loglevel=0 libata.atapi_enabled=1 quiet SELINUX_INIT=NO nmi_
watchdog=0 BOOT_IMAGE=knoppix BOOT_IMAGE=linux lang=us

dmesg wilk follow

Revision history for this message
radsci (radsci) wrote :
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi radsci,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/lucid.

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 320314

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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