"Cannot issue commands" messages and hang when initialising be2net NIC

Solution Verified - Updated -

Issue

  • When network interfaces are brought online during boot, the system hangs while bringing up eth0/em1 or similar. The following messages are printed to the console:
    be2net 0000:04:00.0: Error in Card Detected! Cannot issue commands
    be2net 0000:04:00.0: Error in Card Detected! Cannot issue commands
  • The console may then show a hung task, blocked for more than 120 seconds. The call trace is:
    __mutex_lock_slowpath
    linkwatch_event
    mutex_lock
    rtnl_lock
    linkwatch_event
    worker_thread
    autoremove_wake_function
    worker_thread
    kthread
    child_rip
    kthread
    child_rep

Environment

  • Red Hat Enterprise Linux 6.2
  • HP ProLiant BL460c Gen8
  • HP FlexFabric 10Gb 2-port 554FLB FlexLOM (Emulex, be2net)
  • HP LPe1205A-HP 8Gb FC HBA (Emulex, lpfc)

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