BNX2/Network breaks at normal output on SSH client (eg. 'top', 'ps faxww')

Bug #86965 reported by JaccoH
4
Affects Status Importance Assigned to Milestone
linux-source-2.6.20 (Ubuntu)
Invalid
Undecided
Kyle McMartin

Bug Description

Binary package hint: linux-image-2.6.20-8-server

Install Ubuntu Edgy on Dell PowerEdge 2950 with BNX2 NICs. Install SSH and access it. Use a command like TOP or PS FAXWW.
In my case this will crash the network operations of this server.

Work around:
Edit rc.local and add the line:
rmmod bnx2 && /etc/init.d/networking stop && modprobe bnx2 && /etc/init.d/networking start && /etc/init.d/ssh restart

This solves the issue. With out this line it will break BNX2/Network.

-- System Information:
Debian Release: testing/unstable
  APT prefers edgy
  APT policy: (700, 'edgy'), (650, 'feisty'), (500, 'edgy-updates'), (500, 'edgy-security'), (500, 'edgy-backports')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/dash
Kernel: Linux 2.6.20-8-server
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)

JaccoH (jacco)
description: updated
Revision history for this message
Chuck Short (zulcss) wrote :

Can you attach the output of lspci -vnn > dmesg.txt.

Thanks
chuck

Changed in linux-source-2.6.20:
assignee: nobody → zulcss
status: Unconfirmed → Needs Info
Revision history for this message
JaccoH (jacco) wrote :

There you go.

JaccoH (jacco)
description: updated
Revision history for this message
JaccoH (jacco) wrote :

Some extra info:

Ive tried using bonding on this set of NICs (2 BNX2) and this is even worse. Ping get DUPs and then like 50% packet loss etc. Or crashes.. etc.

Revision history for this message
JaccoH (jacco) wrote :

per request... lspci -vvv

Revision history for this message
Kyle McMartin (kyle) wrote :

Hi, I think Chuck meant to ask you to do lspci >lspci.txt and dmesg >dmesg.txt but just mashed his thoughts together. Can you please reproduce this crash (by running top or ps, etc.) and run "dmesg >dmesg.txt" after the problem has occured. Could you please then attach this dmesg.txt to the bug which should help us track where or why the error is occuring. Additionally could you attach the output of "sudo ethtool -k eth0" where "eth0" is whichever the problematic network device is.

Thanks!
  Kyle

Changed in linux-source-2.6.20:
assignee: zulcss → kyle
Revision history for this message
Brian Murray (brian-murray) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

Changed in linux-source-2.6.20:
status: Incomplete → Invalid
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.