From: Marek Lindner <lindner_marek@yahoo.de>
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.] Problem openWRT "backfire" and "kmod-batman-adv"
Date: Thu, 12 Aug 2010 12:30:46 +0200 [thread overview]
Message-ID: <201008121230.47075.lindner_marek@yahoo.de> (raw)
In-Reply-To: <4C63C96F.8070001@web.de>
On Thursday 12 August 2010 12:14:07 Tim Glaremin wrote:
> Call Trace:[<80a98a5c>] 0x80a98a5c
> [<800430c0>] 0x800430c0
> [<801a2eb0>] 0x801a2eb0
> [<8004325c>] 0x8004325c
> [<801a6e18>] 0x801a6e18
> [<801a7e40>] 0x801a7e40
> [<801a8aa4>] 0x801a8aa4
> [<80190a00>] 0x80190a00
> [<800a2858>] 0x800a2858
> [<800a6270>] 0x800a6270
> [<800a2f90>] 0x800a2f90
> [<80192028>] 0x80192028
> [<80191330>] 0x80191330
> [<800a3034>] 0x800a3034
> [<80192878>] 0x80192878
> [<80003230>] 0x80003230
>
>
> Code: 24c50006 88820003 98820000 <a8a20003> b8a20000 90830004
> a0a30004 90820005 a0a20005
> Disabling lock debugging due to kernel taint"
>
> Hope all this info helps you, for me it's only confusing :)
Yeah, we are getting closer !
Could you please enable the kernel debugging information, repeat the last step
and post the log again. The kernel debugging will replace these numbers by the
actual function names.
At the bottom of this page you will find an step-by-step guide explaining how
to activate the kernel debugging:
http://www.open-mesh.org/wiki/building-batman-adv-with-openwrt
Cheers,
Marek
next prev parent reply other threads:[~2010-08-12 10:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-12 10:14 [B.A.T.M.A.N.] Problem openWRT "backfire" and "kmod-batman-adv" Tim Glaremin
2010-08-12 10:30 ` Marek Lindner [this message]
2010-08-12 10:32 ` Sven Eckelmann
[not found] <mailman.33.1282337388.934.b.a.t.m.a.n@lists.open-mesh.org>
2010-08-21 8:09 ` Tim
2010-08-21 8:15 ` Sven Eckelmann
-- strict thread matches above, loose matches on Subject: below --
2010-08-18 6:42 Tim
[not found] ` <201008201211.51847.sven.eckelmann@gmx.de>
[not found] ` <4C6E8B79.7040801@web.de>
2010-08-20 14:44 ` Sven Eckelmann
2010-08-20 15:38 ` Sven Eckelmann
[not found] ` <4C6F5950.8070204@bb.banban.jp>
2010-08-21 6:19 ` Sven Eckelmann
2010-08-17 9:20 Tim
2010-08-17 9:27 ` Sven Eckelmann
2010-08-17 9:45 ` Tim
2010-08-17 9:51 ` Sven Eckelmann
2010-08-12 18:04 Tim Glaremin
2010-08-13 3:24 ` Sven Eckelmann
2010-08-14 17:26 ` Marek Lindner
2010-08-16 16:51 ` Marek Lindner
[not found] <mailman.1.1281002401.15834.b.a.t.m.a.n@lists.open-mesh.org>
2010-08-11 10:47 ` Tim
2010-08-11 11:14 ` Marek Lindner
2010-08-11 11:20 ` Sven Eckelmann
2010-08-11 14:23 ` Tim
2010-08-11 14:52 ` Sven Eckelmann
2010-08-04 9:21 Tim
2010-08-04 9:34 ` Sven Eckelmann
2010-08-04 22:03 ` 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=201008121230.47075.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.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