Bug 462373
Summary: | Infamous r8169 (PCI/PCCard) link autoneg issue: Chicken-egg | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 5 | Reporter: | Bryan J Smith <brsmith> |
Component: | kernel | Assignee: | Red Hat Kernel Manager <kernel-mgr> |
Status: | CLOSED DEFERRED | QA Contact: | Martin Jenner <mjenner> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 5.2 | CC: | awaizman, fche, ivecera, james |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
URL: | ftp://66.104.77.130/cn/nic/r8169-6.007.00.tar.bz2 | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-10-29 22:04: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
Bryan J Smith
2008-09-15 18:14:21 UTC
Additional issue, PCCard is unreliable (lost packets). Used different combinations of Speed, Duplex, etc... in driver and ethtool -- none ddress issue. So this card may have other issues altogether. Trying to hunt down a Windows XP notebook to verify if card is defective or not with vendor included drivers. If so, will attempt to procure another card. Please try testing kernel available at: http://people.redhat.com/dzickus/el5/ There is upgraded r8169 driver in version 2.6.18-115 and above. This version practically corresponds with the latest upstream driver. No change with the 5.3 Beta -120.el5 kernel. It seems to still be PHY issue. E.g., the port says "MII" (not "TP") and no lights come on. Various "ethtool -s" settings have no effect. Again, I need to take the time to test the PCCard unit in a Windows system. Just don't seem to have an older CardBus system with Windows on it to test it in. ;) I'm still wondering if this hardware unit is buggy, or has support issues with the PHY with even the RealTek provided/updated r8169 driver. It certainly gets "hot enough" to cause the serial number/barcode ink to be rubbed off. Being that many other fixes and upstream backports have been made in -120.el5, I'm reducing the Priority/Severity to "low" and marking it CLOSED/DEFERRED for now, awaiting confirmation that my unit is not faulty (which I have not been able to verify under Windows with the included drivers as of yet). |