From: Hannes Frederic Sowa <hannes@stressinduktion.org>
To: Teco Boot <teco@inf-net.nl>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net] ipv6: don't stop backtracking in fib6_lookup_1 if subtree does not match
Date: Fri, 9 Aug 2013 16:57:43 +0200 [thread overview]
Message-ID: <20130809145743.GM14001@order.stressinduktion.org> (raw)
In-Reply-To: <CF3AE072-7B80-4C35-9236-4523EE11629F@inf-net.nl>
On Fri, Aug 09, 2013 at 04:40:03PM +0200, Teco Boot wrote:
>
> Op 9 aug. 2013, om 16:19 heeft Hannes Frederic Sowa <hannes@stressinduktion.org> het volgende geschreven:
>
> > On Fri, Aug 09, 2013 at 04:12:20PM +0200, Teco Boot wrote:
> >> Double checked, it works. Tested with Common Open Research Emulator (CORE, from NRL).
> >>
> >> === But ===
> >>
> >> I had some problems with CORE. Could be me, new kernel version, the patch, CORE using network namespaces, or combination of that. sudo hangs, reboot hangs, ip address show hangs.
> >> With ps -ef, I see some suspected items:
> >> root 4858 4161 0 15:57 ? 00:00:00 /sbin/ip -6 addr flush dev eth0
> >> root 4859 2 0 15:57 ? 00:00:00 [kworker/0:3]
> >> In the emulation I use, there was no IPv6.
> >>
> >> I'll try to figure out if it is CORE & netns in combination with patch. Or just the patch. Or just the new kernel.
> >> Just to speed up, any idea where to look for?
> >
> > echo t > /proc/sysrq-trigger and check dmesg while the system hangs. Maybe you
> > have to use a serial console and send the sysrq over keyboard/break.
>
> System was still running.
> Cleared dmesg, silence.
> Then performed echo t > /proc/sysrq-trigger.
> Quite large dump.
> Afterwards, silence again.
I think you are experience high fib6_gc_lock contention (and while the lock is
held you also hold rtnl_lock, which let's all the other processes hang).
Please test if these patches make things more smooth for you:
https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=2ac3ac8f86f2fe065d746d9a9abaca867adec577
https://git.kernel.org/cgit/linux/kernel/git/davem/net-next.git/commit/?id=49a18d86f66d33a20144ecb5a34bba0d1856b260
Thanks,
Hannes
next prev parent reply other threads:[~2013-08-09 14:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-07 0:34 [PATCH net] ipv6: don't stop backtracking in fib6_lookup_1 if subtree does not match Hannes Frederic Sowa
2013-08-07 19:58 ` Teco Boot
2013-08-07 20:06 ` Hannes Frederic Sowa
2013-08-09 14:12 ` Teco Boot
2013-08-09 14:19 ` Hannes Frederic Sowa
2013-08-09 14:40 ` Teco Boot
2013-08-09 14:57 ` Hannes Frederic Sowa [this message]
2013-08-10 11:39 ` Teco Boot
2013-08-10 12:03 ` Hannes Frederic Sowa
2013-08-13 8:02 ` Teco Boot
2013-08-13 8:15 ` David Miller
2013-08-14 6:40 ` Teco Boot
2013-08-14 7:55 ` David Miller
2013-08-14 7:59 ` Teco Boot
2013-08-14 8:06 ` Teco Boot
2013-08-14 10:06 ` Hannes Frederic Sowa
2013-08-10 12:15 ` Hannes Frederic Sowa
2015-12-02 9:55 ` [PATCH net 1/1] via-rhine: fix VLAN receive handling regression Teco Boot
2015-12-03 20:11 ` David Miller
2013-08-08 0:17 ` [PATCH net] ipv6: don't stop backtracking in fib6_lookup_1 if subtree does not match 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=20130809145743.GM14001@order.stressinduktion.org \
--to=hannes@stressinduktion.org \
--cc=netdev@vger.kernel.org \
--cc=teco@inf-net.nl \
/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