System crash due to be2net driver errors leading to multiple slab corruptions

Solution Verified - Updated -

Issue

  • Server crashed after network link went down
  • be2net and NIC firmware errors
  • slab corruptions leading to list_del corruption
be2net firmware errors:

kernel: be2net 0000:04:00.0: Error in FW/Card             <=                                    
kernel: be2net 0000:04:00.0: eth0: Link down
hp-ams[6018]: CRITICAL: Network Adapter Link Down (Slot 0, Port 1)           

Slab corruption: 

ffff883fe62f1680 biovec-128              2048          0         0      0     4k
ffff883fe62e1640 biovec-64               1024          0         0      0     4k
kmem: biovec-16: full list: slab: ffff882832402040  bad next pointer: 4341434544464446
kmem: biovec-16: full list: slab: ffff882832402040  bad prev pointer: 4341434143414341
kmem: biovec-16: full list: slab: ffff882832402040  bad s_mem pointer: ffff882801002000
ffff883fe62d1600 biovec-16                256          0         0      0     4k
...
...

ffff883fffb60b80 task_struct             2672       1040      1119    373     8k
kmem: cred_jar: partial list: slab: ffff882f0f813000  bad inuse counter: 2298544118
kmem: cred_jar: partial list: slab: ffff882f0f813000  bad s_mem pointer: 7f0a61f67f0af2eb
ffff883fffb50b40 cred_jar                 192        148       320     16     4k
ffff883fffb40b00 anon_vma_chain            48      27166     33803    439     4k

Environment

  • Red Hat Enterprise Linux 6
  • be2net driver
    • Driver version: 11.1.183.21
    • Firmware version: 4.9.416.0

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