From: Denys Fedoryschenko <denys@visp.net.lb>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: Denis Romanenko <ash@sevsky.net>, netdev@vger.kernel.org
Subject: Re: Kernel problem
Date: Thu, 26 Feb 2009 11:38:13 +0200 [thread overview]
Message-ID: <200902261138.13485.denys@visp.net.lb> (raw)
In-Reply-To: <20090226093902.GA12753@gondor.apana.org.au>
I spoke with Denis Romanenko (i know him)
Here is some additional info:
First of all, he booted kernel with extensive debug options. He was not able
to run it for long time, because performance of router degraded too much.
Here is part of script where all things happened
# Disk discipline
echo cfq > /sys/block/sda/queue/scheduler
# Irq for cards
echo 4 >/proc/irq/215/smp_affinity
echo 8 >/proc/irq/214/smp_affinity
echo 1 >/proc/irq/216/smp_affinity
echo 2 >/proc/irq/217/smp_affinity
# Cards setup
/usr/sbin/ethtool -G eth0 rx 1024 tx 1024
/usr/sbin/ethtool -G eth1 rx 1024 tx 1024
/usr/sbin/ethtool -G eth2 rx 1024 tx 1024
/usr/sbin/ethtool -G eth3 rx 1024 tx 1024
/usr/sbin/ethtool -C eth0 rx-usecs 3
/usr/sbin/ethtool -C eth1 rx-usecs 3
/usr/sbin/ethtool -C eth2 rx-usecs 3
/usr/sbin/ethtool -C eth3 rx-usecs 3
/usr/sbin/ethtool -K eth0 tso off
/usr/sbin/ethtool -K eth1 tso off
/usr/sbin/ethtool -K eth2 tso off
/usr/sbin/ethtool -K eth3 tso off
/usr/sbin/ethtool -K eth0 sg off
/usr/sbin/ethtool -K eth1 sg off
/usr/sbin/ethtool -K eth2 sg off
/usr/sbin/ethtool -K eth3 sg off
/usr/sbin/ethtool -K eth0 ufo off
/usr/sbin/ethtool -K eth1 ufo off
/usr/sbin/ethtool -K eth2 ufo off
/usr/sbin/ethtool -K eth3 ufo off
/usr/sbin/ethtool -K eth0 gso off
/usr/sbin/ethtool -K eth1 gso off
/usr/sbin/ethtool -K eth2 gso off
/usr/sbin/ethtool -K eth3 gso off
# interface queue
/sbin/ifconfig eth0 txqueuelen 10000
/sbin/ifconfig eth1 txqueuelen 10000
/sbin/ifconfig eth2 txqueuelen 10000
/sbin/ifconfig eth3 txqueuelen 10000
On Thursday 26 February 2009 11:39:02 Herbert Xu wrote:
> Denis Romanenko <ash@sevsky.net> wrote:
> > I have high loaded router - about 1.2 Gbps
> >
> > after reboot on new kernel - 2.6.27.17 i have messages in dmesg
> >
> > WARNING: at kernel/softirq.c:136 local_bh_enable+0x36/0xab()
>
> So somebody disabled the IRQs on us, the question is who?
>
> Cheers,
next prev parent reply other threads:[~2009-02-26 10:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 11:43 Kernel problem Denis Romanenko
2009-02-26 9:39 ` Herbert Xu
2009-02-26 9:38 ` Denys Fedoryschenko [this message]
2009-02-26 10:56 ` Jarek Poplawski
2009-02-26 11:24 ` Denis Romanenko
2009-02-26 12:00 ` Jarek Poplawski
2009-02-26 12:47 ` Jarek Poplawski
2009-02-26 12:51 ` Denis Romanenko
2009-02-26 13:17 ` Jarek Poplawski
2009-02-26 11:56 ` Herbert Xu
2009-02-26 12:10 ` David Miller
2009-02-26 13:06 ` Herbert Xu
2009-02-26 13:19 ` Jarek Poplawski
2009-02-27 4:11 ` Herbert Xu
2009-02-27 8:03 ` David Miller
2009-02-27 11:45 ` Herbert Xu
2009-02-27 13:24 ` David Miller
2009-02-27 8:41 ` Jarek Poplawski
2009-02-27 8:59 ` David Miller
2009-02-27 9:12 ` Jarek Poplawski
2009-02-27 9:16 ` David Miller
2009-02-27 9:29 ` Jarek Poplawski
2009-03-01 7:38 ` Herbert Xu
2009-03-01 8:12 ` David Miller
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=200902261138.13485.denys@visp.net.lb \
--to=denys@visp.net.lb \
--cc=ash@sevsky.net \
--cc=herbert@gondor.apana.org.au \
--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).