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 21:28:21 +0200 [thread overview]
Message-ID: <45352ED5.70505@cosmosbay.com> (raw)
In-Reply-To: <20061017191814.55313.qmail@web57803.mail.re3.yahoo.com>
John Philips a écrit :
>> Hum, given your slow cpu, you might revert tx queue
>> length to 2.4.XX level
>> (100 instead of 1000)
>
> I tried that, it didn't help any.
>
>> Are you sure you cannot post here :
>>
>> tc -s -d qdisc show dev eth6
>
> As I said, there are rules in place for every single
> IP in a /22 subnet. It would be over 12000 lines. I
> tried turning off the traffic shaping, it didn't help.
>
>> You might want to make inet_peer_cache purge faster
>> :
>>
>> echo 1 >/proc/sys/net/ipv4/inet_peer_gc_mintime
>> echo 2 >/proc/sys/net/ipv4/inet_peer_gc_maxtime
>
> I tried that as well, unfortunately it didn't help.
This was just to reduce size of the table (and time of the lookups), not to
solve the nic problem at all :)
>
> It's worth noting that this behavior happens at
> seemingly random times for random amounts of time. It
> also causes the interface to auto-negotiate it's
> settings again. During these periods, ping times to a
> switch plugged directly into eth6 are 4000+ms. When I
> statically set the interface to 100baseT/full duplex
> with mii-tool, ping times to the switch immediately
> return to normal. Unfortunately this fix only lasts a
> few minutes, because the interface hangs up and
> returns to auto-negotiation.
>
> Also, I know this isn't a problem with my hardware
> since it started happening immediately after I
> upgraded the kernel from 2.4.25.
Yes, I supposed that your hardware was running OK with previous kernels.
Which NIC driver is handling eth6 ?
next prev parent reply other threads:[~2006-10-17 19:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 16:43 BUG: warning at kernel/softirq.c:141/local_bh_enable() John Philips
2006-10-17 16:53 ` Eric Dumazet
2006-10-17 19:18 ` John Philips
2006-10-17 19:28 ` Eric Dumazet [this message]
[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
-- 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 13:50 John Philips
2006-10-17 13:56 ` Eric Dumazet
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=45352ED5.70505@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.