From: Jack Lau <jackelectronics@hotmail.com>
To: <proski@gnu.org>
Cc: <linux-wireless@vger.kernel.org>
Subject: RE: kernel panic ieee80211_agg_splice_packets+0x3d/0xc0 [mac80211]
Date: Thu, 30 Jul 2009 22:48:01 +0000 [thread overview]
Message-ID: <SNT102-W61A452E2BB1C76DD78F435BD130@phx.gbl> (raw)
In-Reply-To: <1248821338.5206.12.camel@mj>
Pavel,
I have downloaded wireless-testing via git, compiled it and installed it which includes the below patch.
The git version was v2.6.31-rc4-29204-g6b3a8c9 (30/07/2009).
Unfortunately, I am still getting this very annoying crash.
Regards,
Jack
----------------------------------------
> Subject: RE: kernel panic ieee80211_agg_splice_packets+0x3d/0xc0 [mac80211]
> From: proski@gnu.org
> To: jackelectronics@hotmail.com
> CC: linux-wireless@vger.kernel.org
> Date: Tue, 28 Jul 2009 18:48:58 -0400
>
> On Tue, 2009-07-28 at 21:21 +0000, Jack Lau wrote:
>
>>> I have enabled debugging in config.mk and installed it.
>
> I didn't suggest that. I think it's irrelevant. Only the setting
> in .config is relevant.
>
> If you are using compat-wireless, I suggest that you try the current
> kernel from wireless-testing. It was quite unstable a few days ago, but
> it should be cleaned up by now. Since you are using the AP mode, you'll
> need this patch, it's still not applied as of now:
>
> http://marc.info/?l=linux-wireless&m=124871936602667&w=2
>
> compat-wireless is great if everything is working, but if something is
> broken, the first suspicion is that compat-wireless doesn't backport
> something correctly.
>
>> The kernel already has debugging enabled as I have examined the
>> source from Ubuntu.
>
> Please be specific what you found and where. I don't have Ubuntu
> around, but others could correct you if you are looking in a wrong
> place.
>
>>> When I load the gdb command, I just get no debugging symbols found
>> and with the l command I just get no symbol file now.
>
> Please don't rephrase tell the error messages, especially if you don't
> understand them fully. I cannot see from your words why there are no
> debugging symbols.
>
> Also please don't top-post, as it makes it harder to quote the
> discussion in a reasonable way.
>
> --
> Regards,
> Pavel Roskin
_________________________________________________________________
Share your memories online with anyone you want.
http://clk.atdmt.com/UKM/go/134665338/direct/01/
next prev parent reply other threads:[~2009-07-30 22:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-26 17:35 kernel panic ieee80211_agg_splice_packets+0x3d/0xc0 [mac80211] Jack Lau
2009-07-26 20:40 ` Pavel Roskin
2009-07-28 21:21 ` Jack Lau
2009-07-28 22:48 ` Pavel Roskin
2009-07-30 22:48 ` Jack Lau [this message]
2009-07-31 14:26 ` Jack Lau
[not found] ` <SNT102-W3823D5AFC70CB052684837BD110@phx.gbl>
2009-08-02 4:18 ` Pavel Roskin
2009-08-02 12:55 ` Jack Lau
2009-08-02 12:57 ` Jack Lau
2009-08-05 19:23 ` Jack Lau
2009-08-02 17:26 ` Jack Lau
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=SNT102-W61A452E2BB1C76DD78F435BD130@phx.gbl \
--to=jackelectronics@hotmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=proski@gnu.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;
as well as URLs for NNTP newsgroup(s).