2.6.26-rc1 regression since 2.6.25
Hello,
as of some high versions of 2.6.25-gitXX and 2.6.26-rc1, USB devices pluged into a dock (minidock for Lenovo ThinkPad T61) are not discoverred until I reload ehci-hcd module with already plugged device.
Also minor omnipresent bug, most of the time, I got garbage message instead of the message "machine restart" when restarting. I think, the message is OK if I boot up and then immediatelly restart. If I restart after some time, only garbage is displayed (ASCII chars with value above 127 mostly).
Signature · 1 line
Lukáš Hejtmánek
Quoted 5 lines · Lukas Hejtmanek
Hello,
as of some high versions of 2.6.25-gitXX and 2.6.26-rc1, USB devices pluged into a dock (minidock for Lenovo ThinkPad T61) are not discoverred until I reload ehci-hcd module with already plugged device.
Can you please post the kernel log file from when this happens?
Added the linux-usb list on the CC: for this as well...
thanks,
greg k-h
Quoted 8 lines · Greg KH
Quoted 5 lines · Lukas Hejtmanek
Hello,
as of some high versions of 2.6.25-gitXX and 2.6.26-rc1, USB devices pluged into a dock (minidock for Lenovo ThinkPad T61) are not discoverred until I reload ehci-hcd module with already plugged device.
Can you please post the kernel log file from when this happens?
I created an attachment to this bug.
http://bugzilla.kernel.org/show_bug.cgi?id=10630
Signature · 1 line
Lukáš Hejtmánek
Quoted 4 lines · Lukas Hejtmanek
Quoted 3 lines · Greg KH
Quoted 2 lines · Lukas Hejtmanek
Hello,
Quoted 8 lines
Quoted 5 lines
Quoted 3 lines
as of some high versions of 2.6.25-gitXX and 2.6.26-rc1, USB devices pluged into a dock (minidock for Lenovo ThinkPad T61) are not discoverred until I reload ehci-hcd module with already plugged device.
Can you please post the kernel log file from when this happens?
I created an attachment to this bug.
http://bugzilla.kernel.org/show_bug.cgi?id=10630
I'd prefer to do this in email, not bugzilla, if you can.
That log file has a lot of suspend/resume cycles (showing some acpi problems as well...)
Can you just boot the box and then plug it into the dock and show the log file for that?
thanks,
greg k-h
Quoted 7 lines · Greg KH
I'd prefer to do this in email, not bugzilla, if you can.
That log file has a lot of suspend/resume cycles (showing some acpi problems as well...)
Can you just boot the box and then plug it into the dock and show the log file for that?
sure, but not till Monday, I do not have the dock at home.
Signature · 1 line
Lukáš Hejtmánek
Quoted 2 lines · Greg KH
Can you just boot the box and then plug it into the dock and show the log file for that?
If you can, use a kernel that has CONFIG_USB_DEBUG turned on.
Alan Stern
Quoted 6 lines · Alan Stern
Quoted 2 lines · Greg KH
Can you just boot the box and then plug it into the dock and show the log file for that?
If you can, use a kernel that has
CONFIG_USB_DEBUGturned on.
I did. The dmesg is attached to the bug:
http://bugzilla.kernel.org/show_bug.cgi?id=10630
Signature · 1 line
Lukáš Hejtmánek
Quoted 10 lines · Lukas Hejtmanek
Quoted 6 lines · Alan Stern
Quoted 2 lines · Greg KH
Can you just boot the box and then plug it into the dock and show the log file for that?
If you can, use a kernel that has
CONFIG_USB_DEBUGturned on.I did. The dmesg is attached to the bug:
http://bugzilla.kernel.org/show_bug.cgi?id=10630
It looks as though the dock's USB hub may not be working right.
Just as a test, can you try applying gregkh-04-usb-2.6.26-rc2.patch (it applies to 2.6.26-rc2, obviously) from
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/
and attaching the dmesg log from that? It contains extra debugging not present in the vanilla kernel -- make sure that you keep CONFIG_USB_DEBUG enabled.
Alan Stern
Quoted 4 lines · Alan Stern
Quoted 2 lines
I did. The dmesg is attached to the bug:
http://bugzilla.kernel.org/show_bug.cgi?id=10630It looks as though the dock's USB hub may not be working right.
Maybe, Lenovo HW is a piece of crap. Anyway, it worked up to 2.6.25 (including).
Quoted 8 lines
Just as a test, can you try applying gregkh-04-usb-2.6.26-rc2.patch (it applies to 2.6.26-rc2, obviously) from
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/
and attaching the dmesg log from that? It contains extra debugging not present in the vanilla kernel -- make sure that you keep
CONFIG_USB_DEBUGenabled.
I did another attachement of the dmesg to the bugzilla.
Signature · 1 line
Lukáš Hejtmánek
Quoted 7 lines · Lukas Hejtmanek
Quoted 4 lines · Alan Stern
Quoted 2 lines
I did. The dmesg is attached to the bug:
http://bugzilla.kernel.org/show_bug.cgi?id=10630It looks as though the dock's USB hub may not be working right.
Maybe, Lenovo HW is a piece of crap.
That's certainly possible.
Quoted 2 lines
Anyway, it worked up to 2.6.25
(including).
Can you attach an equivalent dmesg log for 2.6.25 (with CONFIG_USB_DEBUG enabled, of course)?
Quoted 10 lines
Quoted 8 lines
Just as a test, can you try applying gregkh-04-usb-2.6.26-rc2.patch (it applies to 2.6.26-rc2, obviously) from
http://www.kernel.org/pub/linux/kernel/people/gregkh/gregkh-2.6/
and attaching the dmesg log from that? It contains extra debugging not present in the vanilla kernel -- make sure that you keep
CONFIG_USB_DEBUGenabled.I did another attachement of the dmesg to the bugzilla.
Let me get this straight. You booted without the dock, and then at this line:
Quoted 1 line
[14315425.975807] ACPI: \_SB_.GDCK - docking
you plugged the computer into the dock, right?
Then apparently here:
Quoted 1 line
[14315508.451197] ehci_hcd 0000:00:1a.7: port 4 remote wakeup
you plugged the USB drive into the dock, but it wasn't detected. Or maybe I've got it backward, the drive was already plugged in when you docked the computer, and 14315508.451197 is when you unplugged the drive. Which was it?
AFAICS, the dock never reported the existence of the USB drive.
Okay, let's see some more debugging information on this. Get a usbmon trace (see Documentation/usb/usbmon.txt) for bus 3, starting just before you dock the computer. That will tell us exactly what the dock's USB hub is reporting.
By the way, are you entirely certain that 2.6.25 works correctly in both cases: drive already attached when you dock the computer, and drive plugged in after the computer is docked? I guess it would be good to see equivalent usbmon traces for both 2.6.25 and 2.6.26-rc2.
Alan Stern
Quoted 4 lines · Alan Stern
Quoted 1 line
Quoted 1 line
Quoted 1 line
Can you attach an equivalent dmesg log for 2.6.25 (with
CONFIG_USB_DEBUGenabled, of course)?
attached.
Quoted 6 lines
Let me get this straight. You booted without the dock, and then at this line:
Quoted 1 line
[14315425.975807] ACPI: \_SB_.GDCK - dockingyou plugged the computer into the dock, right?
Yup.
Quoted 9 lines
Then apparently here:
Quoted 1 line
[14315508.451197] ehci_hcd 0000:00:1a.7: port 4 remote wakeupyou plugged the USB drive into the dock, but it wasn't detected. Or maybe I've got it backward, the drive was already plugged in when you docked the computer, and 14315508.451197 is when you unplugged the drive. Which was it?
More precisly, it was already plugged but the external power of the USB drive was switched off and I just switched it on after I had docked.
Quoted 4 lines
Okay, let's see some more debugging information on this. Get a usbmon trace (see
Documentation/usb/usbmon.txt) for bus 3, starting just before you dock the computer. That will tell us exactly what the dock's USB hub is reporting.
Moreover, I discovered that removing ehci module before I put the machine into the dock causes the uhci module to discover the USB device. Dmesg traces are attached.
Do you still need the usbmon traces?
Signature · 1 line
Lukáš Hejtmánek