Bug 674273
| Summary: | Flapping errors (and panic) with bonding and arp_interval while using be2net included in 2.6.18-238 [rhel-5.6.z] | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | RHEL Program Management <pm-rhel> |
| Component: | kernel | Assignee: | Jiri Pirko <jpirko> |
| Status: | CLOSED ERRATA | QA Contact: | Hangbin Liu <haliu> |
| Severity: | high | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 5.6 | CC: | agospoda, dhoward, gea, haliu, ivecera, jolsa, jpirko, laurie.barry, nhorman, peter.sjoberg, pm-eus, ptavares, rkhan, subbu.seetharaman, syamazak, tgraf |
| Target Milestone: | rc | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | kernel-2.6.18-238.4.1.el5 | Doc Type: | Bug Fix |
| Doc Text: |
Prior to this update, the be2net driver failed to work with bonding, causing "flapping" errors (the interface switches between states up and down) in the active interface. This was due to the fact that the netdev->trans_start pointer in the be_xmit function was not updated. With this update, the aforementioned pointer has been properly updated and "flapping" errors no longer occur.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-03-01 20:30:51 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: | |||
| Bug Depends On: | 671595 | ||
| Bug Blocks: | |||
|
Description
RHEL Program Management
2011-02-01 09:12:44 UTC
in kernel-2.6.18-238.4.1.el5 linux-2.6-net-be2net-fix-missing-trans_start-update.patch Do you know when this kernel version will be made available ? Thanks in advance. (In reply to comment #5) > Do you know when this kernel version will be made available ? > Thanks in advance. Early March. Is there any test kernel version we could use to start deploying the servers without waiting until march (our customer is in a hurry!). Thanks (In reply to comment #7) > Is there any test kernel version we could use to start deploying the servers > without waiting until march (our customer is in a hurry!). > Thanks I can provide you such test kernel. Which arch are you interested in? I need x86_64 at least, i386 will be nice to have. Thanks (In reply to comment #9) > I need x86_64 at least, i386 will be nice to have. > Thanks http://people.redhat.com/jpirko/test/ Please let me know if you need anything more. Do you have the kernel-devel packages ? (In reply to comment #12) > Do you have the kernel-devel packages ? They are there now. (In reply to comment #13) > (In reply to comment #12) > > Do you have the kernel-devel packages ? > > They are there now. One more thing, what are the chances of getting an updated boot image for 5.6 we could use to kickstart servers without having to reconfigure the network later (since with the original 5.6 kernel it will panic as soon as the bonded interface is brought up). Any news regarding getting the updated boot image ? An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2011-0303.html
Technical note added. If any revisions are required, please edit the "Technical Notes" field
accordingly. All revisions will be proofread by the Engineering Content Services team.
New Contents:
Prior to this update, the be2net driver failed to work with bonding, causing "flapping" errors (the interface switches between states up and down) in the active interface. This was due to the fact that the netdev->trans_start pointer in the be_xmit function was not updated. With this update, the aforementioned pointer has been properly updated and "flapping" errors no longer occur.
|