All of lore.kernel.org
 help / color / mirror / Atom feed
From: Philipp Psurek <philipp.psurek@gmail.com>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] kernel BUG at net/core/skbuff.c:100
Date: Fri, 21 Nov 2014 09:40:43 +0100	[thread overview]
Message-ID: <1416559243.2838.1.camel@gmail.com> (raw)
In-Reply-To: <546DE067.8070807@hundeboll.net>


[-- Attachment #1.1: Type: text/plain, Size: 445 bytes --]

Hi Martin

I've bad news. I ran the VM with crashkernel=32M this wasn't enough. I
couldn't save the vmcore. Now I'll use crashkernel=64M.

I don't think the attached crash report has something to do with our
bug. This is the only information I could retrieve.

I'll report again when dmsg tells something; or with a crash dump.

Best regards

Philipp
________________________
Freifunk Rheinland e. V.
– Funkzelle Wuppertal –

[-- Attachment #1.2: crash_03.png --]
[-- Type: image/png, Size: 16197 bytes --]

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2014-11-21  8:40 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-18 21:58 [B.A.T.M.A.N.] kernel BUG at net/core/skbuff.c:100 Philipp Psurek
2014-11-20  8:32 ` Martin Hundebøll
2014-11-20  9:48   ` Philipp Psurek
2014-11-20 10:27     ` Martin Hundebøll
2014-11-20 12:22       ` Philipp Psurek
2014-11-20 12:36         ` Martin Hundebøll
2014-11-21  8:40           ` Philipp Psurek [this message]
2014-11-22 20:39           ` Philipp Psurek
2014-11-24  8:24             ` Martin Hundebøll
2014-11-24 10:44               ` Philipp Psurek
2014-11-24 12:14                 ` Philipp Psurek
2014-11-24 21:15                   ` Philipp Psurek
2014-11-24 22:26                     ` Philipp Psurek
2014-11-25  0:22                       ` Philipp Psurek
2014-11-25 10:17                         ` Philipp Psurek

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=1416559243.2838.1.camel@gmail.com \
    --to=philipp.psurek@gmail.com \
    --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 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.