From: David Miller <davem@davemloft.net>
To: yanek@ya.bofh.cz
Cc: linux-net@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: PROBLEM: kernel lockup while changing TC rules
Date: Thu, 01 May 2008 14:33:34 -0700 (PDT) [thread overview]
Message-ID: <20080501.143334.10643576.davem@davemloft.net> (raw)
In-Reply-To: <20080501145239.GA20284@atlantis.mitranet.cz>
From: Jan 'yanek' Bortl <yanek@ya.bofh.cz>
Date: Thu, 1 May 2008 16:52:39 +0200
CC:'ing netdev@vger.kernel.org, where such reports belong.
> I have found this problem with today's git (2.6.25-00000-ge4c576b) and 2.6.25:
>
> Network configuration:
>
> +--------+ vlan20 +---------+ vlan80
> | laptop |----------------| router |-----
> +--------+ +---------+
> laptop has address 192.168.243.10
>
> Reproduce HOWTO:
>
> 1. run http://ya.bofh.cz/archive/kernel-2.6-htbcrash/init.sh
> 2. start packet generator on laptop (any traffic targetted to router's vlan80)
> 3. run http://ya.bofh.cz/archive/kernel-2.6-htbcrash/crash.sh
>
> Then machine lockup and afterwhile print these messages:
>
> [ 395.137697] BUG: soft lockup - CPU#0 stuck for 61s! [ksoftirqd/0:4]
> ...
> [ 395.139871] Call Trace:
> [ 395.139940] <IRQ> [<ffffffff8035ea7c>] ? rb_insert_color+0xbc/0xf0
> [ 395.140012] [<ffffffffa01f9cf6>] ? :sch_htb:htb_add_to_wait_tree+0xa6/0xc0
> [ 395.140061] [<ffffffffa01fb46f>] ? :sch_htb:htb_dequeue+0x47f/0x7f0
> [ 395.140111] [<ffffffffa01f9ec2>] ? :sch_htb:htb_activate_prios+0x122/0x140
> [ 395.140160] [<ffffffff804682f6>] ? __qdisc_run+0x216/0x240
> [ 395.140207] [<ffffffff804584e3>] ? dev_queue_xmit+0x2c3/0x390
> [ 395.140253] [<ffffffff8047db07>] ? ip_finish_output+0x117/0x2a0
> [ 395.140300] [<ffffffff8047dfe0>] ? ip_output+0x70/0xb0
> [ 395.140344] [<ffffffff8047ac68>] ? ip_forward_finish+0x38/0x50
>
> and
>
> [ 527.210416] BUG: soft lockup - CPU#1 stuck for 61s! [tc:2848]
> ...
> [ 527.212644] Call Trace:
> [ 527.212715] [<ffffffff803617ff>] ? __delay+0xf/0x30
> [ 527.212759] [<ffffffff80365a4c>] ? _raw_spin_lock+0x10c/0x180
> [ 527.212805] [<ffffffff804d90a6>] ? _spin_lock_bh+0x56/0x70
> [ 527.212849] [<ffffffff80467a3f>] ? qdisc_lock_tree+0x1f/0x30
> [ 527.212895] [<ffffffffa0228bb4>] ? :sch_sfq:sfq_init+0xf4/0x240
> [ 527.212942] [<ffffffff804693e4>] ? qdisc_create+0x154/0x250
> [ 527.212987] [<ffffffff804710d3>] ? nla_parse+0x33/0xf0
> [ 527.213031] [<ffffffff80469fd0>] ? tc_modify_qdisc+0x90/0x420
> [ 527.213079] [<ffffffff804603d9>] ? rtnetlink_rcv_msg+0x1e9/0x230
> [ 527.213125] [<ffffffff804601f0>] ? rtnetlink_rcv_msg+0x0/0x230
>
> (full output here: http://ya.bofh.cz/archive/kernel-2.6-htbcrash/netconsole.txt)
>
> kernel's config here: http://ya.bofh.cz/archive/kernel-2.6-htbcrash/config.txt
> dmesg after boot here: http://ya.bofh.cz/archive/kernel-2.6-htbcrash/dmesg.txt
>
>
> --
> Jan 'yanek' Bortl <yanek [at] ya.bofh. cz>
> http://ya.bofh.cz/ | jab: yanek [at] mitranet. cz
> -----------------------------------------------------------------
> "Maybe one day you will learn that your way is not the only way."
> Opher [StarGate: The Nox]
> --
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next parent reply other threads:[~2008-05-01 21:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080501145239.GA20284@atlantis.mitranet.cz>
2008-05-01 21:33 ` David Miller [this message]
2008-05-03 0:26 ` PROBLEM: kernel lockup while changing TC rules David Miller
2008-05-03 6:16 ` Stephen Hemminger
2008-05-01 15:49 Jan 'yanek' Bortl
2008-05-03 7:16 ` Jarek Poplawski
2008-05-03 9:43 ` Jan 'yanek' Bortl
2008-05-03 12:11 ` Jarek Poplawski
2008-05-03 12:42 ` Jan 'yanek' Bortl
2008-05-03 16:39 ` Jarek Poplawski
2008-05-03 17:26 ` Jan 'yanek' Bortl
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=20080501.143334.10643576.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=linux-net@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=yanek@ya.bofh.cz \
/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).