mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Philips <johnphilips42@yahoo.com>
To: linux-kernel@vger.kernel.org
Cc: linux-net@vger.kernel.org
Subject: BUG: warning at kernel/softirq.c:141/local_bh_enable()
Date: Tue, 17 Oct 2006 06:50:12 -0700 (PDT)	[thread overview]
Message-ID: <20061017135013.19302.qmail@web57810.mail.re3.yahoo.com> (raw)

Hi,

I recently upgraded some router/NAT devices from 2.4.25 to 2.6.17.8.  They're using VIA C3 processors and NatSemi DP83815 NICs.

Right after the upgrade I started noticing these error messages on one of the heavier-loaded boxes.  This particular box routes and does NAT for around 400 users, peaking at 6Mb/sec of throughput.

The errors were happening about every 3-5 minutes.  I statically set eth6 to 100baseTX-FD with mii-tool, and now the errors appear every few hours for 10-20 minute stretches.

I searched Google and couldn't find any insight (FYI, I'm NOT using the CIPE patches).

Any ideas?

Oct 16 16:51:32 localhost kernel: NETDEV WATCHDOG: eth6: transmit timed out
Oct 16 16:51:32 localhost kernel: eth6: Transmit timed out, status 0x000000, resetting...
Oct 16 16:51:32 localhost kernel: eth6: DSPCFG accepted after 0 usec.
Oct 16 16:51:32 localhost kernel: eth6: Setting full-duplex based on negotiated link capability.
Oct 16 16:51:36 localhost kernel: NETDEV WATCHDOG: eth6: transmit timed out
Oct 16 16:51:36 localhost kernel: eth6: Transmit timed out, status 0x000000, resetting...
Oct 16 16:51:36 localhost kernel: eth6: DSPCFG accepted after 0 usec.
Oct 16 16:51:36 localhost kernel: eth6: Setting full-duplex based on negotiated link capability.
Oct 16 16:51:43 localhost kernel: eth6: Transmit timed out, status 0x000000, resetting...
Oct 16 16:51:43 localhost kernel: NETDEV WATCHDOG: eth6: transmit timed out
Oct 16 16:51:43 localhost kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
Oct 16 16:51:43 localhost kernel: <c029a975> __kfree_skb+0xa5/0x120  <c0236790> drain_tx+0x20/0x40
Oct 16 16:51:43 localhost kernel: <c011c0fb> local_bh_enable+0x6b/0x70  <c0310bd1> destroy_conntrack+0x31/0xe0
Oct 16 16:51:43 localhost kernel: <c02367bf> reinit_ring+0xf/0x50  <c0237fdf> tx_timeout+0x4f/0xe0
Oct 16 16:51:43 localhost kernel: <c0105d67> timer_interrupt+0x67/0x70  <c02aa500> dev_watchdog+0x0/0xb0
Oct 16 16:51:43 localhost kernel: <c011bf52> __do_softirq+0x42/0x90  <c011bfc6> do_softirq+0x26/0x30
Oct 16 16:51:43 localhost kernel: <c02aa5a0> dev_watchdog+0xa0/0xb0  <c011f3f9> run_timer_softirq+0x129/0x170
Oct 16 16:51:43 localhost kernel: <c0101cab> default_idle+0x2b/0x60  <c0101d1a> cpu_idle+0x3a/0x50
Oct 16 16:51:43 localhost kernel: <c0104a1e> do_IRQ+0x1e/0x30  <c0102d8a> common_interrupt+0x1a/0x20
Oct 16 16:51:43 localhost kernel: <c0408676> start_kernel+0x1e6/0x2b0  <c0408220> unknown_bootoption+0x0/0x270
Oct 16 16:51:43 localhost kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
Oct 16 16:51:43 localhost kernel: <c029a975> __kfree_skb+0xa5/0x120  <c0236790> drain_tx+0x20/0x40
Oct 16 16:51:43 localhost kernel: <c011c0fb> local_bh_enable+0x6b/0x70  <c0310c16> destroy_conntrack+0x76/0xe0
Oct 16 16:51:43 localhost kernel: <c02367bf> reinit_ring+0xf/0x50  <c0237fdf> tx_timeout+0x4f/0xe0
Oct 16 16:51:43 localhost kernel: <c02aa5a0> dev_watchdog+0xa0/0xb0  <c011f3f9> run_timer_softirq+0x129/0x170
Oct 16 16:51:43 localhost kernel: <c0105d67> timer_interrupt+0x67/0x70  <c02aa500> dev_watchdog+0x0/0xb0
Oct 16 16:51:43 localhost kernel: <c011bf52> __do_softirq+0x42/0x90  <c011bfc6> do_softirq+0x26/0x30
Oct 16 16:51:43 localhost kernel: <c0104a1e> do_IRQ+0x1e/0x30  <c0102d8a> common_interrupt+0x1a/0x20
Oct 16 16:51:43 localhost kernel: <c0101cab> default_idle+0x2b/0x60  <c0101d1a> cpu_idle+0x3a/0x50
Oct 16 16:51:43 localhost kernel: <c0408676> start_kernel+0x1e6/0x2b0  <c0408220> unknown_bootoption+0x0/0x270
Oct 16 16:51:43 localhost kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
Oct 16 16:51:43 localhost kernel: <c011c0fb> local_bh_enable+0x6b/0x70  <c0310bd1> destroy_conntrack+0x31/0xe0
Oct 16 16:51:43 localhost kernel: <c029a975> __kfree_skb+0xa5/0x120  <c0236790> drain_tx+0x20/0x40
Oct 16 16:51:43 localhost kernel: <c02aa5a0> dev_watchdog+0xa0/0xb0  <c011f3f9> run_timer_softirq+0x129/0x170
Oct 16 16:51:43 localhost kernel: <c02367bf> reinit_ring+0xf/0x50  <c0237fdf> tx_timeout+0x4f/0xe0
Oct 16 16:51:43 localhost kernel: <c0105d67> timer_interrupt+0x67/0x70  <c02aa500> dev_watchdog+0x0/0xb0
Oct 16 16:51:43 localhost kernel: <c011bf52> __do_softirq+0x42/0x90  <c011bfc6> do_softirq+0x26/0x30
Oct 16 16:51:43 localhost kernel: <c0104a1e> do_IRQ+0x1e/0x30  <c0102d8a> common_interrupt+0x1a/0x20
Oct 16 16:51:43 localhost kernel: <c0101cab> default_idle+0x2b/0x60  <c0101d1a> cpu_idle+0x3a/0x50
Oct 16 16:51:43 localhost kernel: <c0408676> start_kernel+0x1e6/0x2b0  <c0408220> unknown_bootoption+0x0/0x270
Oct 16 16:51:43 localhost kernel: BUG: warning at kernel/softirq.c:141/local_bh_enable()
Oct 16 16:51:43 localhost kernel: <c011c0fb> local_bh_enable+0x6b/0x70  <c0310c16> destroy_conntrack+0x76/0xe0
Oct 16 16:51:43 localhost kernel: <c029a975> __kfree_skb+0xa5/0x120  <c0236790> drain_tx+0x20/0x40
Oct 16 16:51:43 localhost kernel: <c0105d67> timer_interrupt+0x67/0x70  <c02aa500> dev_watchdog+0x0/0xb0
Oct 16 16:51:43 localhost kernel: <c02aa5a0> dev_watchdog+0xa0/0xb0  <c011f3f9> run_timer_softirq+0x129/0x170
Oct 16 16:51:43 localhost kernel: <c02367bf> reinit_ring+0xf/0x50  <c0237fdf> tx_timeout+0x4f/0xe0
Oct 16 16:51:43 localhost kernel: <c0104a1e> do_IRQ+0x1e/0x30  <c0102d8a> common_interrupt+0x1a/0x20
Oct 16 16:51:43 localhost kernel: <c011bf52> __do_softirq+0x42/0x90  <c011bfc6> do_softirq+0x26/0x30
Oct 16 16:51:43 localhost kernel: <c0101cab> default_idle+0x2b/0x60  <c0101d1a> cpu_idle+0x3a/0x50
Oct 16 16:51:43 localhost kernel: <c0408676> start_kernel+0x1e6/0x2b0  <c0408220> unknown_bootoption+0x0/0x270
Oct 16 16:51:43 localhost kernel: eth6: DSPCFG accepted after 0 usec.
Oct 16 16:51:43 localhost kernel: eth6: Setting full-duplex based on negotiated link capability.
Oct 16 16:51:47 localhost kernel: NETDEV WATCHDOG: eth6: transmit timed out
Oct 16 16:51:47 localhost kernel: eth6: Transmit timed out, status 0x000000, resetting...
Oct 16 16:51:47 localhost kernel: eth6: DSPCFG accepted after 0 usec.
Oct 16 16:51:47 localhost kernel: eth6: Setting full-duplex based on negotiated link capability.





             reply	other threads:[~2006-10-17 13:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-17 13:50 John Philips [this message]
2006-10-17 13:56 ` Eric Dumazet
2006-10-17 14:53 John Philips
2006-10-17 16:30 ` Eric Dumazet
2006-10-17 16:43 John Philips
2006-10-17 16:53 ` Eric Dumazet
2006-10-17 19:18   ` John Philips
2006-10-17 19:28     ` Eric Dumazet
     [not found] <20061017201014.51060.qmail@web57802.mail.re3.yahoo.com>
2006-10-17 20:54 ` Eric Dumazet
2006-10-18 15:33   ` John Philips
2006-10-18 18:19   ` John Philips

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=20061017135013.19302.qmail@web57810.mail.re3.yahoo.com \
    --to=johnphilips42@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-net@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

all inboxes | Powered by JetHome®