Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 703679

Summary: be2net: interface state flapping after module loading testing
Product: Red Hat Enterprise Linux 6 Reporter: Hushan Jia <hjia>
Component: kernelAssignee: Ivan Vecera <ivecera>
Status: CLOSED CURRENTRELEASE QA Contact: Weibing Zhang <atzhang>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.1CC: arozansk, atzhang, kzhang, nhorman
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-09-19 18:53:30 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 Hushan Jia 2011-05-11 01:17:17 UTC 
Description of problem:
The state of the interface with be2net driver flapping continuously after load/unload the driver module.

Version-Release number of selected component (if applicable):
6.1 RC with 2.6.32-131.0.13.el6.x86_64

How reproducible:


Steps to Reproduce:
1.
i=0
while [ "$i" -lt 100 ]; do
    modprobe -r be2net
    modprobe be2net
    let ++i
done
2. configure address to eth0 or other interface with this driver
3. ping this address
  
Actual results:
interface flapping, and data lost periodically

Expected results:
should be back normally

Additional info:
dmesg log:
be2net 0000:04:00.0: PCI INT A -> GSI 24 (level, low) -> IRQ 24
be2net 0000:04:00.0: setting latency timer to 64
be2net 0000:04:00.0: irq 58 for MSI/MSI-X
be2net 0000:04:00.0: irq 59 for MSI/MSI-X
be2net 0000:04:00.0: irq 60 for MSI/MSI-X
be2net 0000:04:00.0: irq 61 for MSI/MSI-X
be2net 0000:04:00.0: irq 62 for MSI/MSI-X
be2net 0000:04:00.0: irq 63 for MSI/MSI-X
be2net 0000:04:00.0: Emulex OneConnect 10Gbps NIC(be3) port 0
be2net 0000:04:00.1: PCI INT B -> GSI 25 (level, low) -> IRQ 25
be2net 0000:04:00.1: setting latency timer to 64
be2net 0000:04:00.1: irq 64 for MSI/MSI-X
be2net 0000:04:00.1: irq 65 for MSI/MSI-X
be2net 0000:04:00.1: irq 66 for MSI/MSI-X
be2net 0000:04:00.1: irq 67 for MSI/MSI-X
be2net 0000:04:00.1: irq 68 for MSI/MSI-X
be2net 0000:04:00.1: irq 69 for MSI/MSI-X
be2net 0000:04:00.1: Emulex OneConnect 10Gbps NIC(be3) port 1
eth1: Link up
eth0: Link up <== from here, the interface was brought up and address configured
lo: Disabled Privacy Extensions
eth0: Link up
eth0: Link up
eth0: Link up
eth0: Link up
eth0: Link up
eth0: Link up
eth0: Link up
eth0: Link up
eth0: Link up
eth0: Link up
eth0: Link up
eth0: Link up
eth0: Link up
eth0: Link up
......


on another host:
ping 10.16.47.244
PING 10.16.47.244 (10.16.47.244) 56(84) bytes of data.
64 bytes from 10.16.47.244: icmp_seq=1 ttl=64 time=1000 ms
64 bytes from 10.16.47.244: icmp_seq=2 ttl=64 time=1.75 ms
64 bytes from 10.16.47.244: icmp_seq=3 ttl=64 time=0.198 ms
64 bytes from 10.16.47.244: icmp_seq=4 ttl=64 time=0.226 ms
64 bytes from 10.16.47.244: icmp_seq=8 ttl=64 time=1.56 ms  <== lost
64 bytes from 10.16.47.244: icmp_seq=9 ttl=64 time=0.214 ms
64 bytes from 10.16.47.244: icmp_seq=12 ttl=64 time=0.871 ms
64 bytes from 10.16.47.244: icmp_seq=13 ttl=64 time=0.219 ms
64 bytes from 10.16.47.244: icmp_seq=17 ttl=64 time=1.05 ms
64 bytes from 10.16.47.244: icmp_seq=18 ttl=64 time=0.217 ms
64 bytes from 10.16.47.244: icmp_seq=21 ttl=64 time=1.50 ms  <==
64 bytes from 10.16.47.244: icmp_seq=22 ttl=64 time=0.234 ms
64 bytes from 10.16.47.244: icmp_seq=26 ttl=64 time=0.852 ms  <==
64 bytes from 10.16.47.244: icmp_seq=27 ttl=64 time=0.211 ms
64 bytes from 10.16.47.244: icmp_seq=30 ttl=64 time=1.17 ms  <==
64 bytes from 10.16.47.244: icmp_seq=31 ttl=64 time=0.227 ms
64 bytes from 10.16.47.244: icmp_seq=36 ttl=64 time=1.50 ms  <==
64 bytes from 10.16.47.244: icmp_seq=37 ttl=64 time=0.202 ms
64 bytes from 10.16.47.244: icmp_seq=43 ttl=64 time=1.81 ms
64 bytes from 10.16.47.244: icmp_seq=44 ttl=64 time=0.213 ms
64 bytes from 10.16.47.244: icmp_seq=46 ttl=64 time=0.980 ms
64 bytes from 10.16.47.244: icmp_seq=47 ttl=64 time=0.208 ms
64 bytes from 10.16.47.244: icmp_seq=49 ttl=64 time=1.16 ms
64 bytes from 10.16.47.244: icmp_seq=50 ttl=64 time=0.228 ms
64 bytes from 10.16.47.244: icmp_seq=55 ttl=64 time=1.28 ms
64 bytes from 10.16.47.244: icmp_seq=56 ttl=64 time=0.218 ms
64 bytes from 10.16.47.244: icmp_seq=61 ttl=64 time=0.780 ms
64 bytes from 10.16.47.244: icmp_seq=62 ttl=64 time=0.221 ms
64 bytes from 10.16.47.244: icmp_seq=65 ttl=64 time=0.916 ms
64 bytes from 10.16.47.244: icmp_seq=66 ttl=64 time=0.227 ms
64 bytes from 10.16.47.244: icmp_seq=69 ttl=64 time=1.24 ms
64 bytes from 10.16.47.244: icmp_seq=70 ttl=64 time=0.222 ms
64 bytes from 10.16.47.244: icmp_seq=72 ttl=64 time=0.424 ms
64 bytes from 10.16.47.244: icmp_seq=73 ttl=64 time=0.225 ms
64 bytes from 10.16.47.244: icmp_seq=77 ttl=64 time=0.894 ms
64 bytes from 10.16.47.244: icmp_seq=78 ttl=64 time=0.220 ms
64 bytes from 10.16.47.244: icmp_seq=81 ttl=64 time=1.22 ms
64 bytes from 10.16.47.244: icmp_seq=82 ttl=64 time=0.218 ms
64 bytes from 10.16.47.244: icmp_seq=84 ttl=64 time=1.42 ms
64 bytes from 10.16.47.244: icmp_seq=85 ttl=64 time=0.214 ms
64 bytes from 10.16.47.244: icmp_seq=89 ttl=64 time=0.677 ms
64 bytes from 10.16.47.244: icmp_seq=90 ttl=64 time=0.211 ms
64 bytes from 10.16.47.244: icmp_seq=92 ttl=64 time=0.996 ms
64 bytes from 10.16.47.244: icmp_seq=93 ttl=64 time=0.212 ms
64 bytes from 10.16.47.244: icmp_seq=96 ttl=64 time=1.31 ms
64 bytes from 10.16.47.244: icmp_seq=97 ttl=64 time=0.213 ms
64 bytes from 10.16.47.244: icmp_seq=100 ttl=64 time=0.807 ms
64 bytes from 10.16.47.244: icmp_seq=101 ttl=64 time=0.224 ms
64 bytes from 10.16.47.244: icmp_seq=103 ttl=64 time=0.855 ms
64 bytes from 10.16.47.244: icmp_seq=104 ttl=64 time=0.231 ms
64 bytes from 10.16.47.244: icmp_seq=106 ttl=64 time=1.31 ms
64 bytes from 10.16.47.244: icmp_seq=107 ttl=64 time=0.216 ms
64 bytes from 10.16.47.244: icmp_seq=111 ttl=64 time=0.618 ms
64 bytes from 10.16.47.244: icmp_seq=112 ttl=64 time=0.232 ms
64 bytes from 10.16.47.244: icmp_seq=117 ttl=64 time=0.791 ms
64 bytes from 10.16.47.244: icmp_seq=118 ttl=64 time=0.235 ms
64 bytes from 10.16.47.244: icmp_seq=120 ttl=64 time=1.06 ms
64 bytes from 10.16.47.244: icmp_seq=121 ttl=64 time=0.231 ms
64 bytes from 10.16.47.244: icmp_seq=126 ttl=64 time=0.425 ms
Comment 2 Hushan Jia 2011-05-17 09:57:09 UTC 
on dell-pec6105-01.lab.bos.redhat.com, I have reserved it, feel free to log into and test.
Comment 3 Ivan Vecera 2011-05-17 15:37:18 UTC 
Hushan,
is it a regression?
Comment 4 Hushan Jia 2011-05-18 06:59:15 UTC 
I didnt see this happens on 6.0 kernel, also this does not happen everytime on 6.1 kernels.
Comment 5 Ivan Vecera 2011-07-22 20:44:19 UTC 
Hushan could you please test kernel packages placed here:
http://people.redhat.com/ivecera/.3737751d985778b5c3ca0fbc49b3cd74/
Comment 7 Weibing Zhang 2011-07-27 09:11:19 UTC 
I tested on dell-pec6105-01.lab.bos.redhat.com with kernel 2.6.32-131.0.13.el6.x86_64 for RHEL 6.1, but with no luck to reproduce it running mod_reload.sh and ping on my own machine for about 20 times. Only one or two packages were lost during the test, but not so many as Hushan described in the bug report.

############## mod_reload.sh ##############

#!/bin/bash
i=0
while [ "$i" -lt 100 ]; do
    modprobe -r be2net
    modprobe be2net
    let ++i
done


pkill dhclient
dhclient eth0
ifconfig eth0 | grep "inet addr" | cut -d':' -f2 | cut -d' ' -f1
echo "now ping"

############## EOF ##############


The bug did not come up on kernel-2.6.32-154.el6.ivtest.1.x86_64.rpm after running mod_reload.sh for 10 times.
Comment 8 Ivan Vecera 2011-08-11 14:02:38 UTC 
Hmm, as per comment #7, could we close this?
Comment 9 Ivan Vecera 2011-09-06 15:38:01 UTC 
Weibing?
Comment 10 Linda Wang 2011-09-19 18:53:30 UTC 
close current release per comment#7
if the issue presist, please feel free to reopen this bug.

thanks.