bnx2: kernel panic: killing interrupt handler

Bug #75767 reported by Daniel Topa
6
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-2.6.15-27-amd64-server

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/mapper/vg00-lv_root ro vga=771

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/pci0000:00/0000:00:1c.0/0000:02:00.0/0000:03:00.0
  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)
...

Tags: kernel-oops
Revision history for this message
Daniel Topa (daniel-topa) wrote :
description: updated
description: updated
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

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.

Changed in linux-source-2.6.15:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Timo Aaltonen (tjaalton) wrote :
Timo Aaltonen (tjaalton)
Changed in linux-source-2.6.15:
milestone: none → dapper-updates
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

I compiled the latest driver (1.6.7b), and it has been in use for five days now without any issues.

Changed in linux-source-2.6.15:
status: Confirmed → Triaged
Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

It looks like Hardy has version 1.6.9. Timo or Daniel, care to confirm this is no longer an issue for Hardy at least?

Changed in linux:
status: New → Incomplete
Revision history for this message
Timo Aaltonen (tjaalton) wrote :

It's a production server so I can't test Hardy on it, but I'm sure this issue is fixed at least since Feisty.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Btw, the backported driver has been in use nearly three months now without any issues..

Revision history for this message
Leann Ogasawara (leannogasawara) wrote :

Awesome, thanks.

Changed in linux:
status: Incomplete → Fix Released
Changed in linux-source-2.6.15:
status: Triaged → Won't Fix
dino99 (9d9)
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
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.