From: Matthias Schiffer <mschiffer@universe-factory.net>
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] Kernel crashes when using more than one interface in bat0
Date: Thu, 20 Aug 2015 13:10:46 +0200 [thread overview]
Message-ID: <55D5B5B6.60002@universe-factory.net> (raw)
In-Reply-To: <78ccce3e5516b2613b09306a586f2584@hilses.de>
[-- Attachment #1: Type: text/plain, Size: 1187 bytes --]
On 08/20/2015 12:08 PM, Hans-Werner Hilse wrote:
> Hi,
>
> Am 2015-08-18 18:35, schrieb Bjoern Franke:
>
>> Thanks for the hint, it did not work on the debian machines, but I got
>> the systems running with crashkernel enabled. Now we got the first
>> crash:
>> https://p.rrbone.net/paste/nnNHrIJI#oHfBMOs2
>
> We've seen these on our Goettingen Freifunk gateways, too. There, too,
> batadv_frag_purge_orig was the smoking gun. However, I didn't report it,
> because:
>
> - first and foremost, we were using the outdated legacy 2013.4 version
> - it was most probably an issue with RCU lists
> - and either disabling SMP or using a much more current kernel fixed it.
>
> So I blamed a buggy RCU implementation in older kernels, plus maybe some
> ill behaviour in the old batman-adv codebase. The crashing kernel was
> the old debian-wheezy one - pretty old, I'd say.
>
> -hwh
This is an independent bug (2013.4 uses a completely different
fragmentation implementation) that has been reported in
https://github.com/freifunk-gluon/batman-adv-legacy/issues/1 . Please
don't bother the upstream BATMAN developers with batman-adv-legacy bugs.
Matthias
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-20 11:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-17 21:47 [B.A.T.M.A.N.] Kernel crashes when using more than one interface in bat0 Bjoern Franke
2015-08-18 8:08 ` Bastian Bittorf
2015-08-18 16:35 ` Bjoern Franke
2015-08-20 10:08 ` Hans-Werner Hilse
2015-08-20 11:10 ` Matthias Schiffer [this message]
2015-08-23 17:59 ` Bjoern Franke
2015-08-20 11:09 ` Simon Wunderlich
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=55D5B5B6.60002@universe-factory.net \
--to=mschiffer@universe-factory.net \
--cc=b.a.t.m.a.n@lists.open-mesh.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