This service will be undergoing maintenance at 00:00 UTC, 2017-10-23 It is expected to last about 30 minutes
Bug 452612 - Network Bonding doesn't work with ehea driver
Network Bonding doesn't work with ehea driver
Status: CLOSED CANTFIX
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: kernel (Show other bugs)
4.6
ppc64 Linux
low Severity high
: rc
: ---
Assigned To: Jiri Pirko
Martin Jenner
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-06-23 22:05 EDT by Nate Golnik
Modified: 2012-05-07 16:18 EDT (History)
6 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2012-05-07 14:39:44 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Nate Golnik 2008-06-23 22:05:56 EDT
Description of problem:
Using a P6-570 there is no link monitoring for the ehea network interfaces. 
Which causes issues with bonding.

Version-Release number of selected component (if applicable):
RHEL 4.6, IBM P6-570 

How reproducible:
always

Steps to Reproduce:
1.add the following lines to modprobe.conf:
  alias bond0 bonding
  options bond0 miimon=100 max_bonds=2 mode=1

2. Configure eth0 and eth1 as slaves to bond0
3. Configure bond0
4. load bonding modules and restart networking
  
Actual results:

network: Bringing up interface bond0:  succeeded
ifup: Enslaving eth0 to bond0 
ifup: Enslaving eth1 to bond0 
network: Bringing up interface bond0:  succeeded 
kernel: bonding: MII link monitoring set to 100 ms
kernel: bonding: Warning : no link monitoring support for eth0
kernel: bonding: Warning : no link monitoring support for eth1

no traffic will pass over the interface (kind of expected with no link
monitoring working)

Expected results:
Link monitoring support for eth0 and eth1 and a functioning bonded interface

Additional info:
none
Comment 1 Neil Horman 2010-11-10 11:09:10 EST
Triage assignment.  If you feel this bug doesn't belong to you, or that it cannot be handled in a timely fashion, please contact me for re-assignment
Comment 2 Jiri Pirko 2010-12-07 05:32:58 EST
Interesting. The warning message is printed out in bond_enslave() at the very beginning of this function by following code:

if (!bond->params.use_carrier && slave_dev->ethtool_ops == NULL &&
    slave_dev->do_ioctl == NULL) {
        printk(KERN_WARNING DRV_NAME
               ": Warning : no link monitoring support for %s\n",
               slave_dev->name);
}

But slave_dev->ethtool_ops should not be null, because it is set in drivers/net/ehea/ehea_ethtool.c function ehea_set_ethtool_ops()

Am I missing something?

Are you sure you are experiencing this with ehea driver?
Comment 3 Rashid Khan 2012-05-07 14:39:44 EDT
Due to resource constraints or complexity, this issue could not be resolved in the time frame of this release.
Kindly please try RHEL 6.3 Beta and see if the problem still happens in that release. If it does please start a new bug. 
If you feel you cannot move to that release, please contact your Global Support Specialist for further escalation and prioritization. 
Kind Regards.
Comment 4 Rashid Khan 2012-05-07 16:18:05 EDT
Due to resource constraints or complexity, this issue could not be resolved in
the time frame of this release.
Kindly please try RHEL 6.3 Beta or 5.8 and see if the problem still happens in that
release. If it does please start a new bug. 
If you feel you cannot move to that release, please contact your Global Support
Specialist for further escalation and prioritization. 
Kind Regards.

Note You need to log in before you can comment on or make changes to this bug.