netdev - RE: bnx2x crash dump on high network load

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <BD3F7F1EFBA6D54DB056C4FFA451400803A1F8F2F7@SJEXCHCCR01.corp.ad.broadcom.com>
Date:	Fri, 5 Mar 2010 09:31:36 -0800
From:	"Eilon Greenstein" <eilong@...adcom.com>
To:	"Fischer, Anna" <anna.fischer@...com>
cc:	eliezert <eliezert@...adcom.com>,
	"Michael Chan" <mchan@...adcom.com>,
	"netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: RE: bnx2x crash dump on high  network load

Hi Anna,

On this kernel, enabling bridging (like you do on virtualization) does not turn off LRO automatically. Please try to load the bnx2x with disable_tpa=1 (TPA is the HW based LRO feature).

Regards,
Eilon

-----Original Message-----
From: Fischer, Anna [mailto:anna.fischer@...com] 
Sent: Friday, March 05, 2010 7:08 PM
To: netdev@...r.kernel.org
Cc: eliezert; Eilon Greenstein; Michael Chan
Subject: bnx2x crash dump on high network load

I am seeing driver crashes with a bnx2x version 1.50.16. I have attached two crash dumps that I have captured.

I run Linux with the following kernel:

# uname -a
Linux sup-prj-441106 2.6.16.60-0.54.5-debug #1 SMP Fri Sep 4 01:28:03 UTC 2009 x86_64 x86_64 x86_64 GNU/Linux

I am seeing these driver crashes when I run virtual machines (VMware Server) and those VMs do high bandwidth network I/O, so there are a lot of packets going through the NIC. 

Can you give me any hints for what the problem here could be?

Thanks,
Anna

--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html