Bug 6723
| Summary: | some ohci hardware is broken | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Boris Nicolaev (aein) |
| Component: | USB | Assignee: | David Brownell (dbrownell) |
| Status: | RESOLVED CODE_FIX | ||
| Severity: | normal | CC: | greg |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.17 | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
| Bug Depends on: | |||
| Bug Blocks: | 5089 | ||
| Attachments: |
dmesg 2.6.17
dmesg 2.6.17 with enabled usb-debug dmesg 2.6.17 after rmmod ohci-hcd lspci -vvv patch queued for 2.6.19 dmesg 2.6.18-rc5 kernel with applied patch proposed patch for this board-specific quirk lspci -vvn 2.6.18 kernel with applied patch Patch being submitted |
||
Created attachment 8351 [details]
dmesg 2.6.17
Created attachment 8372 [details]
dmesg 2.6.17 with enabled usb-debug
Created attachment 8373 [details]
dmesg 2.6.17 after rmmod ohci-hcd
Created attachment 8374 [details]
lspci -vvv
Created attachment 8901 [details]
patch queued for 2.6.19
please try current 2.6.18-rc5 with the attached patch, which is
already queued for 2.6.19-early
Created attachment 8947 [details]
dmesg 2.6.18-rc5 kernel with applied patch
Unfortunately, this patch don't resolve trouble.
The problem looks to be your hardware then, since the
root hub is misbehaving.
Probable workaround: as root
# cd /sys/bus/pci/devices/0000:00:02.0
# cd usb1/power
# echo disabled > wakeup
#
That tells the driver that the root hub wakeup mechanism
must not be used.
You'd have to do that on each boot; I have no reason
to think this is generic to every ALI root hub, since
in the past I've used them with no problems.
Since this is clearly a hardware bug and I've included the workaround, I'm reducing its priority and will probably mark it as closed unless there's confirmation that the problem exists in 2.6.18 ... This problem occurs 2.6.18 kernel. Is it possible to add kernel option, which enable workaround for this hardware? Created attachment 9176 [details]
proposed patch for this board-specific quirk
Please see if this patch properly works around the problem on your
board. If it does not, please provide "lspci -vvn" info for the
OHCI controller with this problem.
ping ... any updates on testing? I'm waiting for info about both (a) the /sys/devices/.../wakeup workaround, (b) the patch that knows about this board quirk Comment on attachment 8901 [details]
patch queued for 2.6.19
patch is now merged
Sorry for delay, today I'll provide all information. Created attachment 9241 [details]
lspci -vvn 2.6.18 kernel with applied patch
Workaround works. Patch does not resolve problem.
With 2.6.20 kernel -- all ok. Suppose, now bug can be closed. Created attachment 11221 [details]
Patch being submitted
Previous patches had infrastructure that wasn't validated ... now that the
infrastructure has been merged, this updated patch should be OK. I'm
submitting it (plus a followup patch, verified as making another system work)
for the 2.6.22 kernel.
|
Most recent kernel where this bug did not occur: 2.6.16.20 Distribution: Slackware 10.2 Hardware Environment: Toshiba portege 4000 Problem Description: after loading ohci-hcd module, I get continuous kernel messages: ohci_hcd 0000:00:02.0: wakeup ohci_hcd 0000:00:02.0: wakeup ohci_hcd 0000:00:02.0: wakeup ............................. usb devices are not detecting. But, if I boot system after power off -- all ok. This problem occurs only after system reboot. reboot={b,w,c,h} option is useless. Steps to reproduce: reboot toshiba portege 4000 and load ohci-hcd module.