From: Philipp Psurek <philipp.psurek@gmail.com>
To: Sven Eckelmann <sven@narfation.org>, b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: [B.A.T.M.A.N.] batctl: page allocation failure
Date: Sun, 28 Feb 2016 18:17:27 +0100 [thread overview]
Message-ID: <1456679847.1958.52.camel@gmail.com> (raw)
In-Reply-To: <10118093.UzH4NL7sLW@sven-edge>
Hi Sven,
as already mentioned the failure does not happen any more. I'm sorry
bothering you with this unreproducible issue.
Am Sonntag, den 28.02.2016, 17:23 +0100 schrieb Sven Eckelmann:
> On Sunday 28 February 2016 00:39:08 Philipp Psurek wrote:
> > Hi all,
> >
> > I've got this error with
> [..]
> >
> >
> > ----------------------------------
> [..]
> > [Feb28 00:13] batctl: page allocation failure: order:4, mode:0x40d0
>
> Does this always happen when you use `batctl o` on a system with many
> entries in the originator table?
I never saw this failure before. Executing
# batctl o | wc -l
338
on an 32 MiB RAM router was never a problem. I thought it would be the best reporting this issue.
> When yes, then you could try the attached (very rough) proof-of
> -concept patch. It is based on v2016.0-92-gd7c9a9e
You are a faster coder than me as email writer. I'll implement the
Patch in your 2nd email and report.
Best regards,
Philipp
prev parent reply other threads:[~2016-02-28 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 23:39 [B.A.T.M.A.N.] batctl: page allocation failure Philipp Psurek
2016-02-28 13:27 ` Linus Lüssing
2016-02-28 16:45 ` Matthias Schiffer
2016-02-28 16:55 ` Philipp Psurek
2016-02-28 16:23 ` Sven Eckelmann
2016-02-28 17:06 ` Sven Eckelmann
2016-02-28 17:38 ` Philipp Psurek
2016-02-28 17:42 ` Philipp Psurek
2016-02-28 17:54 ` Sven Eckelmann
2016-02-28 17:17 ` Philipp Psurek [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=1456679847.1958.52.camel@gmail.com \
--to=philipp.psurek@gmail.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=sven@narfation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.