From: Simon Wunderlich <sw@simonwunderlich.de>
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:09:51 +0200 [thread overview]
Message-ID: <1648393.lLZC1ylQqN@prime> (raw)
In-Reply-To: <1439915717.1370.9.camel@nord-west.org>
[-- Attachment #1: Type: text/plain, Size: 1024 bytes --]
Hi Bjoern,
thanks a lot for reporting this issue - it looks like there are some problems
in the cleanup of OGMs when fragmentation is used.
For now, I've created a ticket here:
https://www.open-mesh.org/issues/223
Thanks,
Simon
On Tuesday 18 August 2015 18:35:17 Bjoern Franke wrote:
> Am Dienstag, den 18.08.2015, 10:08 +0200 schrieb Bastian Bittorf:
> > * Bjoern Franke <bjo@nord-west.org> [18.08.2015 09:47]:
> > > Unfornately we have no logs now, because after the crashes no ssh
> > > -access to the servers are possible.
> >
> > try to set
> >
> > /sbin/sysctl -w kernel.panic_on_oops=1
> > /sbin/sysctl -w kernel.panic=10
> > /sbin/sysctl -w vm.panic_on_oom=2
> >
> > if the devices crashed (and reboots now) you have
> > the crash in the file:
> >
> > /sys/kernel/debug/crashlog
>
> 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
>
> Regards
> Bjoern
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2015-08-20 11:09 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
2015-08-23 17:59 ` Bjoern Franke
2015-08-20 11:09 ` Simon Wunderlich [this message]
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=1648393.lLZC1ylQqN@prime \
--to=sw@simonwunderlich.de \
--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