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_0.3 segmentation fault
Date: Wed, 17 Oct 2007 11:09:16 +0200 [thread overview]
Message-ID: <200710171109.17045.axel@open-mesh.net> (raw)
In-Reply-To: <20071016194803.GA8315@apoderado.ometepe.net>
Hi,
since rv 498 the interface initialization and probing for the tun module is
done before the daemon forks into background.
However, the warning for "tun not loaded" has not reflected this. Now it goes
to stderr!
Can you try rv 727 ?
ciao,
/axel
On Dienstag 16 Oktober 2007, Jan Hetges wrote:
> On Tue, Oct 16, 2007 at 12:52:53PM -0600, Jan Hetges wrote:
> > On Tue, Oct 16, 2007 at 11:25:52AM -0600, Jan Hetges wrote:
> > > On Tue, Oct 16, 2007 at 03:13:52PM +0200, Marek Lindner wrote:
> > > > > i just tried both and batmand_0.3-beta-rv674 gives a segmenation
> > > > > fault and
> > > >
> > > > are you sure it segfaults or is it simply not running ? Please
> > >
> > > yes, at least it said "Segmentation fault"
> > >
> > > > > batmand_0.2-rv502 doesn't start (probably segfault as well).
> > >
> > > this one is simply not running
> > >
> > > so i installed
> > > http://downloads.open-mesh.net/batman/development/misc/batmand_0.3-beta
> > >-rv724_mipsel-wr-elf-32-lsb-dynamic-unstripped.tgz md5sum
> > > /tmp/batmand_0.3-beta-rv724_mipsel-wr-elf-32-lsb-dynamic
> > > 955cc1f203c4ad47fea84427b7b7c5c4
> > > /tmp/batmand_0.3-beta-rv724_mipsel-wr-elf-32-lsb-dynamic
> >
> > the safe way to reproduce this:
> > flash openwrt-g-freifunk-1.6.9-es.bin to a wrt54g
> > then put scr lui http;//freifunk.schmudde.com/ipkg into /etc/ipkg.conf
> > ipkg update
> > ipkg install freifunk-batman freifunk-recommended-es
> > install
> > http://downloads.open-mesh.net/batman/development/misc/batmand_0.3-beta-r
> >v724_mipsel-wr-elf-32-lsb-dynamic-unstripped.tgz without rebooting!
> > i insmod /lib/modules/.../tun.o and tried again... still segfaults
> > after rebooting the box no more segfault!
>
> because i'm upgrading some more wrt54g, i can do some more testing :-).
> so i tried some random 0.3 versions and *ALL* of them gave a segmentation
> fault (all the way back including batmand_III_rv405)
> and i veryfied 0.2-rv502 with logread -f , and there was something with
> tun not loaded , can't try again because someone rebooted the box ;-)
> but i have some more :)
>
> --Jan
next prev parent reply other threads:[~2007-10-17 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-16 2:02 [B.A.T.M.A.N.] freifunk 1.6.8/1.6.9 Jan Hetges
2007-10-16 6:23 ` a.anselmi
2007-10-16 7:23 ` Jan Hetges
2007-10-16 8:28 ` Axel Neumann
2007-10-16 13:13 ` Marek Lindner
2007-10-16 17:25 ` [B.A.T.M.A.N.] batmand_0.3-beta-rv724 segmentation fault Jan Hetges
2007-10-16 18:52 ` Jan Hetges
2007-10-16 19:48 ` [B.A.T.M.A.N.] batmand_0.3 " Jan Hetges
2007-10-17 9:09 ` Axel Neumann [this message]
2007-10-17 16:04 ` Jan Hetges
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=200710171109.17045.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox