From: Tomasz Chmielewski <mangoo@wpkg.org>
To: "Gábor Stefanik" <netrolller.3d@gmail.com>
Cc: linux-wireless@vger.kernel.org, linux-net@vger.kernel.org,
linux-mips@vger.kernel.org, Bob Copeland <me@bobcopeland.com>
Subject: Re: ath5k AP kernel panic when client uses SCP
Date: Fri, 23 Oct 2009 15:24:04 +0200 [thread overview]
Message-ID: <4AE1AE74.4020600@wpkg.org> (raw)
In-Reply-To: <69e28c910910230621j2176813dpe7f77b7dff5b1b44@mail.gmail.com>
Gábor Stefanik wrote:
> On Fri, Oct 23, 2009 at 3:15 PM, Tomasz Chmielewski <mangoo@wpkg.org> wrote:
>> Bob Copeland wrote:
>>> CONFIG_DEBUG_INFO is the basic switch. I don't know if MIPS needs
>>> CONFIG_FRAME_POINTER but that could help too.
>> I don't see CONFIG_FRAME_POINTER available.
>> I compiled with CONFIG_DEBUG_INFO; let me know if I should enable some other
>> DEBUG options as well (see below what's enabled and available).
>>
>> Before it oopses, I see lots of order 0 page allocation failures (there are
>> some extra spaces at the end of each line due to the broken konsole in
>> KDE4):
>>
>> http://www1.wpkg.org/oops2.txt
> Is CONFIG_KALLSYMS set?
Good clue:
# zgrep KALL /proc/config.gz
# CONFIG_KALLSYMS is not set
I'll recompile...
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2009-10-23 13:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-11 17:49 ath5k AP kernel panic when client uses SCP Tomasz Chmielewski
2009-10-11 17:55 ` Tomasz Chmielewski
2009-10-11 22:47 ` Bob Copeland
2009-10-12 8:13 ` Tomasz Chmielewski
2009-10-12 8:13 ` Tomasz Chmielewski
2009-10-23 13:15 ` Tomasz Chmielewski
2009-10-23 13:21 ` Gábor Stefanik
2009-10-23 13:24 ` Tomasz Chmielewski [this message]
2009-10-24 11:59 ` Tomasz Chmielewski
2009-10-24 12:52 ` Bob Copeland
2009-10-24 15:27 ` Tomasz Chmielewski
2009-10-24 16:09 ` Bob Copeland
2009-10-24 18:10 ` Tomasz Chmielewski
2009-10-25 20:19 ` Bob Copeland
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=4AE1AE74.4020600@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=me@bobcopeland.com \
--cc=netrolller.3d@gmail.com \
/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).