Bug 73841
Summary: | usbview causes mca | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 3 | Reporter: | Alex Williamson <alex_williamson> |
Component: | kernel | Assignee: | Anil S Keshavamurthy <akeshava> |
Status: | CLOSED WONTFIX | QA Contact: | David Lawrence <dkl> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.0 | CC: | grgustaf, kaccardi, peterm, petrides, zaitcev |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | ia64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2007-10-19 19:36:30 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alex Williamson
2002-09-11 22:31:41 UTC
Changing to kernel... I can reproduce just by cat'ing /proc/bus/usb/devices Last I knew, Trond wasn't a kernel developer. Re-assigning to Larry Woodman. Here's some more data. If I run the following: touch devices.save while (true) do cat /proc/bus/usb/devices > devices.save2 diff -u devices.save devices.save2 cp devices.save2 devices.save sleep 1 done I seem to reach a steady state of the below output: --- devices.save Thu Sep 12 06:14:31 2002 +++ devices.save2 Thu Sep 12 06:14:32 2002 @@ -47,9 +47,9 @@ D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=047b ProdID=0002 Rev= 1.20 S: Manufacturer=SILITEK -S: Product=USB Keyboard and Mouse C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr= 50mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=hid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=24ms I: If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=hid E: Ad=82(I) Atr=03(Int.) MxPS= 5 Ivl=10ms +I) Atr=03(Int.) MxPS= 5 Ivl=10ms --- devices.save Thu Sep 12 06:14:32 2002 +++ devices.save2 Thu Sep 12 06:14:33 2002 @@ -47,9 +47,9 @@ D: Ver= 1.00 Cls=00(>ifc ) Sub=00 Prot=00 MxPS= 8 #Cfgs= 1 P: Vendor=047b ProdID=0002 Rev= 1.20 S: Manufacturer=SILITEK +S: Product=USB Keyboard and Mouse C:* #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr= 50mA I: If#= 0 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=01 Prot=01 Driver=hid E: Ad=81(I) Atr=03(Int.) MxPS= 8 Ivl=24ms I: If#= 1 Alt= 0 #EPs= 1 Cls=03(HID ) Sub=00 Prot=00 Driver=hid E: Ad=82(I) Atr=03(Int.) MxPS= 5 Ivl=10ms -I) Atr=03(Int.) MxPS= 5 Ivl=10ms The last line "I) Atr=..." looks like a line of the form "E: Ad=...", but for some reason the head of the line was cut-off. I've tried multiple keyboards, and they all will cause an MCA with the original process. I haven't verified that they all cycle in /proc/usb/bus/devices the same as this. Weekly status meeting: Not a showstopper. If RH can look at it would be great. HP isn't pursuing it actively. The MCA often seems to be from the reads in rh_send_irq(). roothub_a() causes the 0x48 offset MCA. If I remove this call (knowing there are 2 ports on the hub), I then get an MCA from reading offset 0x50. This looks to be the call to roothub_status() in the same function. So, it looks like the device is busy and we're timing out on the PCI read. I don't know enough about USB to know if there's a locking issue or if the device has a "go away, I'm busy" register. If I bump up the PCI latency on the USB device, I can greatly reduce the likely hood of hitting to problem, but it doesn't go away entirely. I've also found that the problem is reproducable using a USB NIC. I have a 3com 3c460B 10/100 NIC (these are the ones you can pickup for $5 sometimes). If I hook it up on the same root hub as the keyboard, ssh in trough it, and run usbview, I get an MCA. Also, the variability I was seeing from teh keyboard by itself, doesn't seem to matter. I have another keyboard that doesn't cycle like that and the problem is still there. I've tried to reproduce the problem with a USB mouse, and can't make it fail. FYI, backporting USB updates from 2.4.20-pre7 does _not_ help. normalizing Version in Red Hat Linux Beta product This bug is filed against RHEL 3, which is in maintenance phase. During the maintenance phase, only security errata and select mission critical bug fixes will be released for enterprise products. Since this bug does not meet that criteria, it is now being closed. For more information of the RHEL errata support policy, please visit: http://www.redhat.com/security/updates/errata/ If you feel this bug is indeed mission critical, please contact your support representative. You may be asked to provide detailed information on how this bug is affecting you. |