netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Maciej Rutecki <maciej.rutecki@gmail.com>
To: Doug Nazar <nazard.lkml@gmail.com>
Cc: "linux-kernel" <linux-kernel@vger.kernel.org>, netdev@vger.kernel.org
Subject: Re: WARN with 3c905 boomerang NIC
Date: Thu, 26 Aug 2010 20:32:08 +0200	[thread overview]
Message-ID: <201008262032.08815.maciej.rutecki@gmail.com> (raw)
In-Reply-To: <4C70C516.5020404@gmail.com>

On niedziela, 22 sierpnia 2010 o 08:35:02 Doug Nazar wrote:
>   Since de85d99eb7b595f6751550184b94c1e2f74a828b (netpoll: Fix RCU
> usage) I've been getting the follow warning:
> 
> Aug 20 22:33:26 dryad kernel: [   64.263065] ------------[ cut here
> ]------------
> Aug 20 22:33:26 dryad kernel: [   64.263089] WARNING: at
> /usr/src/linux/kernel/softirq.c:143 local_bh_enable+0x58/0x82()
> Aug 20 22:33:26 dryad kernel: [   64.263095] Hardware name: OptiPlex GX240
> Aug 20 22:33:26 dryad kernel: [   64.263099] Modules linked in:
> rpcsec_gss_krb5 softdog snd_intel8x0 snd_ac97_codec 8250_pnp ac97_bu
> Aug 20 22:33:26 dryad kernel: [   64.263234] Pid: 5892, comm:
> runscript.sh Not tainted 2.6.36-rc1-00133-g47ade1d #43
> Aug 20 22:33:26 dryad kernel: [   64.263238] Call Trace:
> Aug 20 22:33:26 dryad kernel: [   64.263251]  [<c12a492e>] ?
> printk+0x18/0x1a
> Aug 20 22:33:26 dryad kernel: [   64.263263]  [<c102a015>]
> warn_slowpath_common+0x67/0x8e
> Aug 20 22:33:26 dryad kernel: [   64.263271]  [<c102ee76>] ?
> local_bh_enable+0x58/0x82
> Aug 20 22:33:26 dryad kernel: [   64.263277]  [<c102ee76>] ?
> local_bh_enable+0x58/0x82
> Aug 20 22:33:26 dryad kernel: [   64.263285]  [<c102a059>]
> warn_slowpath_null+0x1d/0x1f
> Aug 20 22:33:26 dryad kernel: [   64.263292]  [<c102ee76>]
> local_bh_enable+0x58/0x82
> Aug 20 22:33:26 dryad kernel: [   64.263301]  [<c12399e5>]
> netif_rx+0x14f/0x172
> Aug 20 22:33:26 dryad kernel: [   64.263315]  [<e20e8f0f>]
> boomerang_rx+0x27a/0x42f [3c59x]
> Aug 20 22:33:26 dryad kernel: [   64.263328]  [<c10a369b>] ?
> path_put+0x20/0x23
> Aug 20 22:33:26 dryad kernel: [   64.263342]  [<e20eadfb>]
> boomerang_interrupt+0xd9/0x2b7 [3c59x]
> Aug 20 22:33:26 dryad kernel: [   64.263361]  [<c105651c>]
> handle_IRQ_event+0x3e/0x13e
> Aug 20 22:33:26 dryad kernel: [   64.263369]  [<c1057c6e>]
> handle_fasteoi_irq+0x3c/0x89
> Aug 20 22:33:26 dryad kernel: [   64.263378]  [<c1004e58>]
> handle_irq+0x18/0x30
> Aug 20 22:33:26 dryad kernel: [   64.263385]  [<c10048cb>] do_IRQ+0x34/0x97
> Aug 20 22:33:26 dryad kernel: [   64.263392]  [<c10037a9>]
> common_interrupt+0x29/0x30
> Aug 20 22:33:26 dryad kernel: [   64.263398] ---[ end trace
> 511646352388ce9c ]---
> 
> The card is an:
> 02:0c.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado]
> (rev 78)
> 

I created a Bugzilla entry at 
https://bugzilla.kernel.org/show_bug.cgi?id=17131
for your bug report, please add your address to the CC list in there, thanks!
-- 
Maciej Rutecki
http://www.maciek.unixy.pl

  parent reply	other threads:[~2010-08-26 18:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-22  6:35 WARN with 3c905 boomerang NIC Doug Nazar
2010-08-22  7:46 ` David Miller
2010-08-26 18:32 ` Maciej Rutecki [this message]
2010-08-30 18:48 ` Paul E. McKenney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201008262032.08815.maciej.rutecki@gmail.com \
    --to=maciej.rutecki@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nazard.lkml@gmail.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).