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.
DescriptionSubbu Seetharaman
2010-06-16 15:36:30 UTC
+++ This bug was initially created as a clone of Bug #576172 +++
Bug cloned to attach patch for recent fixes in be2net.
This patch includes the following upstream commits :
3ffd05159815d477f971a3259fc758f0c3c7e640
be2net: convert hdr.timeout in be_cmd_loopback_test() to le32
f25b03a7bd260b939b1a6aa69ca518d9848bb63a
be2net: replace udelay() with schedule_timeout() in mbox polling
889cd4b2e529db4988525b0b3e6fb2c095760848
be2net: cleanup in case of error in be_open()
2892d9c2d925e0d72a7a529852942e2592a970f8
be2net: add unlock on error path
d938a702e5ce8909ea68be97566150507bfea4df
be2net: increase POST timeout for EEH recovery
dd131e76e562fa0c6f9dd53130e8d08d39a0b62c
be2net: Bug fix to avoid disabling bottom half during firmware upgrade
556ae19110f2de5ace4733e0c19e5fa01fad08b3
be2net: Bug fix in init code in probe
b681ee77f8ad248b0fdcec2e5e8c4df6e757eba3
benet: fix the misusage of zero dma address
Additionally, this patch implements a change to return proper PHY information to get_settings ioctl. This change will be submitted to netdev shortly.
Comment 2Andrius Benokraitis
2010-06-17 03:21:10 UTC
I'm assuming this is to apply on *top* of everything so far including SRIOV patches?
Comment 3Subbu Seetharaman
2010-06-17 13:30:47 UTC
Comment 7Andrius Benokraitis
2010-09-13 18:45:48 UTC
*IMPORTANT*
Partners - please test this bugzilla *immediately* and report back with a comment. Delays in test findings could impact future proposed inclusions due to failed partner test commitments. Your results are very important to Red Hat and its mutual customers.
[root@test1238 apic]# modinfo be2net
filename: /lib/modules/2.6.32-71.el6.x86_64/kernel/drivers/net/benet/be2net.ko
license: GPL
author: ServerEngines Corporation
description: ServerEngines BladeEngine 10Gbps NIC Driver 2.102.426r
version: 2.102.426r
srcversion: A37FDC1E50878678DAE1DA5
alias: pci:v000019A2d00000710sv*sd*bc*sc*i*
alias: pci:v000019A2d00000700sv*sd*bc*sc*i*
alias: pci:v000019A2d00000221sv*sd*bc*sc*i*
alias: pci:v000019A2d00000211sv*sd*bc*sc*i*
depends:
vermagic: 2.6.32-71.el6.x86_64 SMP mod_unload modversions
parm: rx_frag_size:Size of a fragment that holds rcvd data. (uint)
parm: num_vfs:Number of PCI VFs to initialize (uint)
Comment 9Subbu Seetharaman
2010-09-14 12:04:55 UTC
All these fixes are verified in RH6, snapshot 12.
Comment 10releng-rhel@redhat.com
2010-11-15 14:07:12 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.