Bug 452612
Summary: | Network Bonding doesn't work with ehea driver | ||
---|---|---|---|
Product: | Red Hat Enterprise Linux 4 | Reporter: | Nate Golnik <ngolnik> |
Component: | kernel | Assignee: | Jiri Pirko <jpirko> |
Status: | CLOSED CANTFIX | QA Contact: | Martin Jenner <mjenner> |
Severity: | high | Docs Contact: | |
Priority: | low | ||
Version: | 4.6 | CC: | herbert.xu, jolsa, jpirko, nhorman, rkhan, tgraf |
Target Milestone: | rc | ||
Target Release: | --- | ||
Hardware: | ppc64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-05-07 18:39:44 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
Nate Golnik
2008-06-24 02:05:56 UTC
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 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? 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. 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. |