netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* BNX2X driver: kernel panic when running netperf
@ 2007-10-16 23:34 Max Asbock
  2007-10-16 23:49 ` David Miller
  0 siblings, 1 reply; 3+ messages in thread
From: Max Asbock @ 2007-10-16 23:34 UTC (permalink / raw)
  To: netdev@vger.kernel.org

I tested the bnx2x driver (0001-BNX2X-0.40.10a-net-2.6.24.patch) with
netdev-2.6.24 git tree and found that I can reproducibly panic the
system when running netperf with the TCP_STREAM test.
I copied the following information from the panic message:
RIP: 0xc02fff32
net_rx_action +0x142/0x190
...
do_softirq
...
Kernel panic - not syncing
Fatal exception in interrupt.

Please let me what additional information is useful. 

Max


  



^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: BNX2X driver: kernel panic when running netperf
  2007-10-16 23:34 BNX2X driver: kernel panic when running netperf Max Asbock
@ 2007-10-16 23:49 ` David Miller
  2007-10-17 11:46   ` Eliezer Tamir
  0 siblings, 1 reply; 3+ messages in thread
From: David Miller @ 2007-10-16 23:49 UTC (permalink / raw)
  To: masbock; +Cc: netdev

From: Max Asbock <masbock@us.ibm.com>
Date: Tue, 16 Oct 2007 16:34:40 -0700

> I tested the bnx2x driver (0001-BNX2X-0.40.10a-net-2.6.24.patch) with
> netdev-2.6.24 git tree and found that I can reproducibly panic the
> system when running netperf with the TCP_STREAM test.
> I copied the following information from the panic message:
> RIP: 0xc02fff32
> net_rx_action +0x142/0x190

The driver is doing netif_rx_complete() yet returning a value from
->poll() which is >= budget, which is illegal.

We had to fix a similar bug in the tg3 and bnx2 drivers, the same
logic probably just propagated itself into bnx2x.

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: BNX2X driver: kernel panic when running netperf
  2007-10-16 23:49 ` David Miller
@ 2007-10-17 11:46   ` Eliezer Tamir
  0 siblings, 0 replies; 3+ messages in thread
From: Eliezer Tamir @ 2007-10-17 11:46 UTC (permalink / raw)
  To: masbock, netdev@vger.kernel.org; +Cc: David Miller

On Tue, 2007-10-16 at 16:49 -0700, David Miller wrote:
> From: Max Asbock <masbock@us.ibm.com>
> Date: Tue, 16 Oct 2007 16:34:40 -0700
> 
> > I tested the bnx2x driver (0001-BNX2X-0.40.10a-net-2.6.24.patch)
> with
> > netdev-2.6.24 git tree and found that I can reproducibly panic the
> > system when running netperf with the TCP_STREAM test.
> > I copied the following information from the panic message:
> > RIP: 0xc02fff32
> > net_rx_action +0x142/0x190
> 
> The driver is doing netif_rx_complete() yet returning a value from
> ->poll() which is >= budget, which is illegal.
> 
> We had to fix a similar bug in the tg3 and bnx2 drivers, the same
> logic probably just propagated itself into bnx2x.

I think that this will fix the bug.

This is a diff against 0.40.10a.
I hope to get a new version out soon, once we finish working on Dave's
comments.

Eliezer


---
 drivers/net/bnx2x.c |    5 +++--
 1 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/drivers/net/bnx2x.c b/drivers/net/bnx2x.c
index f462c74..9220bd3 100644
--- a/drivers/net/bnx2x.c
+++ b/drivers/net/bnx2x.c
@@ -8085,9 +8085,10 @@ #endif
 		work_done = bnx2x_rx_int(fp, budget);
 	}
 
-	rmb(); /* TBD check */
+	rmb(); /* bnx2x_has_work() reads the status block */
 
-	if (!bnx2x_has_work(fp)) {
+	/* must not complete if we consumed full budget */
+	if ((work_done < budget) && !bnx2x_has_work(fp)) {
 		netif_rx_complete(bp->dev, napi);
 
 		bnx2x_ack_sb(bp, fp->index, USTORM_ID, fp->fp_u_idx,
-- 
1.4.2




^ permalink raw reply related	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2007-10-17 11:44 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-10-16 23:34 BNX2X driver: kernel panic when running netperf Max Asbock
2007-10-16 23:49 ` David Miller
2007-10-17 11:46   ` Eliezer Tamir

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).