From: Eric Dumazet <dada1@cosmosbay.com>
To: John Philips <johnphilips42@yahoo.com>
Cc: linux-kernel@vger.kernel.org, linux-net@vger.kernel.org
Subject: Re: BUG: warning at kernel/softirq.c:141/local_bh_enable()
Date: Tue, 17 Oct 2006 15:56:37 +0200 [thread overview]
Message-ID: <200610171556.37453.dada1@cosmosbay.com> (raw)
In-Reply-To: <20061017135013.19302.qmail@web57810.mail.re3.yahoo.com>
On Tuesday 17 October 2006 15:50, John Philips wrote:
> 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?
Could you send us, once your machine is handling its typical load :
lspci -v
ethtool -S eth6
tc -s -d qdisc
cat /proc/slabinfo
cat /proc/meminfo
next prev parent reply other threads:[~2006-10-17 13:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 13:50 BUG: warning at kernel/softirq.c:141/local_bh_enable() John Philips
2006-10-17 13:56 ` Eric Dumazet [this message]
-- strict thread matches above, loose matches on Subject: below --
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=200610171556.37453.dada1@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=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