Bug 179327
| Summary: | BONDING: MII monitoring generates a lot of kernel messages | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 4 | Reporter: | Didier Drigues <didier.drigues> |
| Component: | kernel | Assignee: | Chris Lalancette <clalance> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Brian Brock <bbrock> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.0 | CC: | jbaron, linville |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2007-12-07 14:20:14 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
Didier Drigues
2006-01-30 13:54:05 UTC
What hardware you using in the bond? It looks like those messages should only happen if you are using a driver that doesn't have modern ethtool support. (In reply to comment #1) > What hardware you using in the bond? It looks like those messages should only > happen if you are using a driver that doesn't have modern ethtool support. Machine H/W ----------- Product Name: ProLiant DL360 G3 Bonding Configuration (Active Backup with eth1-eth3) --------------------- # cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v2.6.1 (October 29, 2004) Bonding Mode: fault-tolerance (active-backup) Primary Slave: eth1 Currently Active Slave: eth1 MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 Slave Interface: eth1 MII Status: up Link Failure Count: 0 Permanent HW addr: 00:0b:cd:d1:75:b5 Slave Interface: eth3 MII Status: up Link Failure Count: 0 Permanent HW addr: 00:02:a5:89:85:69 Ethernet H/W (extract from hwconf) -------------- class: NETWORK bus: PCI detached: 0 device: eth1 driver: tg3 desc: "Broadcom Corporation NetXtreme BCM5703X Gigabit Ethernet" network.hwaddr: 00:0B:CD:D1:75:B5 vendorId: 14e4 deviceId: 16a7 subVendorId: 0e11 subDeviceId: 00cb pciType: 1 pcidom: 0 pcibus: 4 pcidev: 2 pcifn: 0 class: NETWORK bus: PCI detached: 0 device: eth3 driver: e100 desc: "Intel Corporation 82557/8/9 [Ethernet Pro 100]" network.hwaddr: 00:02:A5:89:85:69 vendorId: 8086 deviceId: 1229 subVendorId: 0e11 subDeviceId: b163 pciType: 1 pcidom: 0 pcibus: 5 pcidev: 5 pcifn: 0 ethtool support --------------- # ethtool eth1 Settings for eth1: Supported ports: [ MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Half 1000baseT/Full Advertised auto-negotiation: Yes Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d Current message level: 0x000000ff (255) Link detected: yes # ethtool eth3 Settings for eth3: Supported ports: [ TP MII ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Supports auto-negotiation: Yes Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full Advertised auto-negotiation: Yes Speed: 100Mb/s Duplex: Full Port: MII PHYAD: 1 Transceiver: internal Auto-negotiation: on Supports Wake-on: g Wake-on: d Current message level: 0x00000007 (7) Link detected: yes Hi all, Responsible of kernel message is e100 driver provided by HP Proliant Support Pack 7.40 rpm -qa | grep e100 e100-3.4.13a-1 Why are you not using the standard RHEL4 e100 driver? Have you tried the beta kernels from RHEL4 U3? Also, try the test kernels available here: http://people.redhat.com/linville/kernels/rhel4/ Please post the results here...thanks! I reccommend downloading and using version 3.5.10, it fixes this issue. You can download it at http://sourceforge.net/projects/e1000. This site is updated by Intel and it includes the e1000 and e100 drivers. I verified your issue and this version fixes it! Mark Closing this bug because of lack of response; if this is still an issue, please re-open. Chris Lalancette |