bnx2: kernel panic: killing interrupt handler
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (CentOS) |
Fix Released
|
Unknown
|
|||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
linux-source-2.6.15 (Ubuntu) |
Won't Fix
|
High
|
Unassigned |
Bug Description
Binary package hint: linux-image-
Kernel panic on HP BL460c blade server.
The server hangs after high "network" load with bnx2 module (see attachment). No special boot kernel parameters are used.
# cat /proc/cmdline
root=/dev/
Only eth1 is used.
# hwinfo --network
...
49: None 01.0: 10701 Ethernet
[Created at net.114]
Unique ID: L2Ua.ndpeucax6V1
Parent ID: JNkJ.OKRlPBdQgr3
SysFS ID: /class/net/eth1
SysFS Device Link: /devices/
Hardware Class: network interface
Model: "Ethernet network interface"
Driver: "bnx2"
Device File: eth1
HW Address: 00:18:fe:34:19:5c
Link detected: yes
Config Status: cfg=new, avail=yes, need=no, active=unknown
Attached to: #29 (Ethernet controller)
...
description: | updated |
description: | updated |
Changed in linux-source-2.6.15: | |
milestone: | none → dapper-updates |
affects: | centos → ubuntu |
Changed in ubuntu: | |
status: | In Progress → Invalid |
Changed in ubuntu: | |
status: | Invalid → In Progress |
no longer affects: | ubuntu |
Changed in linux (CentOS): | |
status: | Unknown → In Progress |
Changed in linux (CentOS): | |
status: | In Progress → Fix Released |
Confirming, the same happens on our HP DL380G5 and I'm able to reproduce it with ease. The server is our apt mirror, so every time the clients update themselves the server crashes. We worked around it by distributing the load, and it worked fine for a month until this morning.
Although the call trace is not the same, I suspect the bug is. It should be fixed upstream, here is what I found googling around:
http:// bugs.centos. org/view. php?id= 2103
that trace is pretty similar to yours.