Why are network interfaces hanging when using the be2net driver in Red Hat Enterprise Linux?

Solution Verified - Updated -

Issue

  • Why are the following errors appearing in dmesg?
be2net 0000:02:00.1: UE Detected!!  
be2net 0000:02:00.1: UE: RDMA; bit set  
be2net 0000:02:00.1: UE: TPRE; bit set  
be2net 0000:02:00.1: Error in Card Detected! Cannot issue commands  
be2net 0000:02:00.1: Error in Card Detected! Cannot issue commands  
be2net 0000:02:00.1: Error in Card Detected! Cannot issue commands  
be2net 0000:02:00.1: Error in Card Detected! Cannot issue commands  
be2net 0000:02:00.1: Error in Card Detected! Cannot issue commands  
be2net 0000:02:00.1: Out of MCCQ wrbs  
be2net 0000:02:00.1: Out of MCCQ wrbs  
be2net 0000:02:00.1: Out of MCCQ wrbs  
be2net 0000:02:00.1: Out of MCCQ wrbs  
be2net 0000:02:00.1: Out of MCCQ wrbs
  • With firmware versions 4.1.442.0 and above dmesg will show:
be2net 0000:16:00.0: FW not responding

Environment

  • Red Hat Enterprise Linux 5.7 and 5.8
  • Red Hat Enterprise Linux 6.2, 6.3 and 6.4
  • be2net driver 4.0.100r [RHEL 5.8]
  • be2net driver 4.0.160r [RHEL 6.2]
  • be2net driver 4.1.450.7 [RHEL 6.4]

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content