Bug 49317
| Summary: | After upgrade to kernel 2.4.3-12 usb-controller does not initialize | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | m.oliver |
| Component: | kernel | Assignee: | Pete Zaitcev <zaitcev> |
| Status: | CLOSED ERRATA | QA Contact: | Brock Organ <borgan> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.1 | CC: | alan |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2002-05-28 18:12:55 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
m.oliver
2001-07-17 23:09:15 UTC
"usb-ohci.c: 00:07.4 (Advanced Micro Devices [AMD] AMD-756 [Viper] USB): blacklisted, erratum #4" AMD has released an defectsummar^Werratum that states that your specific chipset has a defective USB chip. It will appear to work but cause LOADS of problems if used. (lost interrupts, infinite interrupts etc etc) I should remark that before the upgrade I was able to do useful work with USB, now I am not. In fact I didn't even notice that there was something wrong with the USB controller. How about a warning like "don't send vital data via USB", rather than blacklisting it altogether? Also, I specifically upgraded the kernel because it fixes those scary mtrr related warnings with the AMD Irongate Chipset. So it would be nice to finally have a flawless kernel for this Chipset. My problem is similar and more basic. I have a sony vaio fx370 laptop. Originaly I installed 7.2 and immediately upgraded the kernel to 2.4.9-13. A appeared to work "except" nothing on the USB port. The USB port was recognized and the basic drivers were loaded. However, when I attached any usb device an error was always reported in the log that the USB device wouldn't accept new address (i.e. it was timing out). The /proc/interrupts count wasn't increasing. To insure it wasn't the laptop I loaded XP, verified the USB ports and reloaded 7.2. I discovered with the default kernel 2.4.7-10, low and behold the USB and sound worked perfectly. I could use my USB based printer and cd-writer. So, I upgrade again to 2.4.9-13 (using up2date) and once again everything broke. However, this time I had kept around the 2.4.7-10 kernel. Once again after booting 2.4.7-10 all worked. There is definitely a problem with the updated kernel with USB. We must not keep bugs NEW for months, assigning to myself. Evidently, 2.4.7-10 used a different table somewhere. I'll work with bug reporters to dump their $PIRQ and MPTABLE as appropritate and see what's up. Well, hopefuly.. :) I would appreciate if both of you guys did this: 1. boot with ok kernel and do "dmesg > /tmp/dmesg.2.4.7-10.ok" 2. boot with broken kernel and do "dmesg > /tmp/dmesg.2.4.9-xx.bad" 3. Attach both dmesg outputs to the bug (please DO NO DROP INTO COMMENTS BOX) If you are on 2.4.9-31 now, that would be helpful too (it does not fix anything AFAIK, but it would be one less diff session for me) Marcel Oliver (requestor) reported success with 2.4.9-21. |