Bug 455563 - 10G NIC modules bnx2x does not work on XEN mode
10G NIC modules bnx2x does not work on XEN mode
Status: CLOSED NEXTRELEASE
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel-xen (Show other bugs)
5.2
i686 Linux
low Severity high
: rc
: ---
Assigned To: Xen Maintainance List
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-07-16 04:31 EDT by huaweisns
Modified: 2008-11-10 16:58 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-11-10 16:58:16 EST
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 huaweisns 2008-07-16 04:31:56 EDT
Description of problem:

The 10G NIC chipset is Boardcom 57710

Rhel 5.2 include the bnx2x module as the chipset 57710 driver module

It works well on the kernel 2.6.18-92-el5,the two netwrok ports works at the 
speed 10G 
bits/s, the data stream transmission is normally.

but when the kernel is 2.6.18-92-el5xen (OS run on XEN mode ),the 10G network 
ports link status is always keep the state of "no-linked"

Version-Release number of selected component (if applicable):

OS Rhel5.2 64bits 

kernel  2.6.18-92.el5Xen

bnx2x ver :1.40.22

CPU : Intel Xeon 5405
 
chipset:  Intel 5000P

NIC Chipset : Boardcom 57710(on board) 

How reproducible:

when the OS is working at XEN mode, the driver module bnx2x does not work !

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Jindrich Novy 2008-08-03 16:04:15 EDT
Are you sure netpbm is a correct component to file this bug against? It looks more like a kernel/userspace problem to me.
Comment 2 huaweisns 2008-08-03 23:51:36 EDT
OK ,add this problem  to  kernel bug is more appropriate,thank you
Comment 3 Andy Gospodarek 2008-11-10 16:58:16 EST
This was a kernel bug, but should be fixed with the latest 5.3 kernel.  Closing out.

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