[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20091130.001541.134590904.davem@davemloft.net>
Date: Mon, 30 Nov 2009 00:15:41 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: andi@...as.de
Cc: zambrano@...adcom.com, dave@...dillows.org, mb@...sch.de,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] b44.c box lockup fix (netconsole): ratelimit NAPI poll
error message
From: Andreas Mohr <andi@...as.de>
Date: Wed, 25 Nov 2009 22:35:46 +0100
> See
> http://bugzilla.kernel.org/show_bug.cgi?id=14691
> for background information.
The patch below is what I'll check in to fix this, thanks.
As for the r8169 side, that case is much more complicated
to fix. That driver messes with the interrupt masking
before the NAPI schedule check, instead of after it's
sure that NAPI isn't already scheduled like b44 does.
Therefore we might need to undo that programming or move
it into the code block where __napi_schedule() is actually
invoked.
I'll queue this b44 patch up for -stable too.
b44: Fix wedge when using netconsole.
Fixes kernel bugzilla #14691
Due to the way netpoll works, it is perfectly legal to see
NAPI already scheduled when new device events are pending
in b44_interrupt().
So logging a message about it is wrong and in fact harmful.
Based upon a patch by Andreas Mohr.
Signed-off-by: David S. Miller <davem@...emloft.net>
---
drivers/net/b44.c | 3 ---
1 files changed, 0 insertions(+), 3 deletions(-)
diff --git a/drivers/net/b44.c b/drivers/net/b44.c
index e046943..2a91323 100644
--- a/drivers/net/b44.c
+++ b/drivers/net/b44.c
@@ -912,9 +912,6 @@ static irqreturn_t b44_interrupt(int irq, void *dev_id)
bp->istat = istat;
__b44_disable_ints(bp);
__napi_schedule(&bp->napi);
- } else {
- printk(KERN_ERR PFX "%s: Error, poll already scheduled\n",
- dev->name);
}
irq_ack:
--
1.6.5
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists