[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080129210037.GB29300@gateway.home>
Date: Tue, 29 Jan 2008 22:00:37 +0100
From: Erik Mouw <mouw@...linux.org>
To: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>
Cc: netdev@...r.kernel.org
Subject: Re: Lots of "BUG eth1 code -5 qlen 0" messages in 2.6.24
On Tue, Jan 29, 2008 at 11:57:33AM -0800, Waskiewicz Jr, Peter P wrote:
> > I've just started to use 2.6.24 on my home firewall (before
> > it was running 2.6.24-rc2 for about 65 days) and I noticed a
> > couple of error messages I've never seen before:
> >
> > Jan 29 07:50:54 gateway kernel: BUG eth1 code -5 qlen 0 Jan
> > 29 08:28:30 gateway kernel: BUG eth1 code -5 qlen 0 Jan 29
> > 08:57:30 gateway kernel: BUG eth1 code -5 qlen 0 Jan 29
> > 09:44:04 gateway kernel: BUG eth1 code -5 qlen 0 Jan 29
> > 10:01:35 gateway kernel: BUG eth1 code -5 qlen 0 Jan 29
> > 10:01:35 gateway last message repeated 2 times Jan 29
> > 10:16:48 gateway kernel: BUG eth1 code -5 qlen 0 Jan 29
> > 10:16:48 gateway last message repeated 2 times Jan 29
> > 10:45:48 gateway kernel: BUG eth1 code -5 qlen 0 Jan 29
> > 10:45:48 gateway last message repeated 2 times Jan 29
> > 11:10:01 gateway kernel: BUG eth1 code -5 qlen 0 Jan 29
> > 11:10:02 gateway last message repeated 9 times
> >
> > The message seems to be coming from the qdisc_restart() in
> > net/sched/sch_generic.c which was changed with commit
> > 5f1a485d5905aa641f33009019b3699076666a4c .
> >
> > The NIC is an IBM EtherJet cardbus card using the xircom_cb driver:
>
> Are you using any specific qdisc, or just the default pfifo_fast? Have
> you done any specific tuning on your qdisc as well? The default qlen
> seems to have been changed.
I haven't done anything specific at all. Just took the .config from
2.6.24-rc2, ran "make oldconfig", tried to give some sane answers to
new questions and recompile the kernel (been doing that with this
machine since 2.6.16 or so). The machine is an old PII laptop that acts
as my masquerading firewall and mail server. It has a couple of
netfilter rules that reject most of the traffic. I have attached the
config for my kernel and the list of modules, maybe you can find
something wrong.
> Basically your queue is being overrun, and with the current checks in
> the kernel in the stack, it's allowing the skb into the driver. I've
> known about this issue, and I'm hesitant to push a patch to re-add the
> netif_queue_stopped() check into qdisc_restart(). I'd rather push a
> one-time patch to the drivers that interacts with
> netif_stop_subqueue(netdev, 0), so we can completely decouple the single
> queue from the netdev.
>
> I'd say you can somewhat ignore the messages for now. But there is work
> to be done here, and it's obvious I need to do this sooner than later.
> Please let me know about the qdisc parameters though when you get a
> chance.
I'd love to if you tell me how. I'm not really well versed in the
network subsystem...
Erik
--
They're all fools. Don't worry. Darwin may be slow, but he'll
eventually get them. -- Matthew Lammers in alt.sysadmin.recovery
View attachment "config-2.6.24" of type "text/plain" (57875 bytes)
View attachment "modules-2.6.24" of type "text/plain" (3180 bytes)
Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)
Powered by blists - more mailing lists