All of lore.kernel.org
 help / color / mirror / Atom feed
From: Axel Neumann <axel@open-mesh.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
	<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] batmand crash / core dump
Date: Mon, 12 Nov 2007 18:13:39 +0100	[thread overview]
Message-ID: <200711121813.39609.axel@open-mesh.net> (raw)
In-Reply-To: <840E3F681DF3D043B353C0FDD4A6C353ABFC97@ex9.hostedexchange.local>

Hi,

i've also experienced this problem - on mips and mipsel kamikaze. I also 
remember that it causually worked but not today :-(
If you find any solution to this problem please let me know

thanks,
axel

On Sonntag 11 November 2007, Michael Burmeister-Brown wrote:
> Hi,
>
> We are seeing a crash in batmand (beta, rv767-792) on kamikaze 7.09 /
> atheros 2.6 / mips.
>
> I am trying to get a core dump for Marek, but no file is created despite
> doing ulimit -c 20000.
>
> Does anyone know what must be done to get a core dump on this platform?
>
> Thanks!

  parent reply	other threads:[~2007-11-12 17:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-09 14:23 [B.A.T.M.A.N.] routing problem? Stefano Scipioni
2007-11-10 11:43 ` Axel Neumann
2007-11-11 15:55   ` Stefano Scipioni
2007-11-11 17:16     ` [B.A.T.M.A.N.] routing problem? / Changes in exp rv790 Axel Neumann
2007-11-11 20:41       ` [B.A.T.M.A.N.] batmand crash / core dump Michael Burmeister-Brown
2007-11-11 22:30         ` [B.A.T.M.A.N.] batman gw nodes and routing (rv792) Predrag Balorda
2007-11-12 14:31           ` Axel Neumann
2007-11-11 22:34         ` [B.A.T.M.A.N.] vis and batman-exp (rv780-792) Predrag Balorda
2007-11-12  7:57           ` Stefano Scipioni
2007-11-12 13:53             ` Axel Neumann
2007-11-12 14:00               ` Predrag Balorda
2007-11-12 17:13         ` Axel Neumann [this message]
2007-11-24 13:02           ` [B.A.T.M.A.N.] batmand crash / core dump Marek Lindner

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=200711121813.39609.axel@open-mesh.net \
    --to=axel@open-mesh.net \
    --cc=b.a.t.m.a.n@open-mesh.net \
    /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.