From: "Arend van Spriel" <arend@broadcom.com>
To: "Frank Kingswood" <frank@kingswood-consulting.co.uk>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: Kernel panic with brcm4313 (kernel 3.2.2)
Date: Tue, 17 Apr 2012 14:52:35 +0200 [thread overview]
Message-ID: <4F8D6793.8090701@broadcom.com> (raw)
In-Reply-To: <4F8D60FC.2090301@kingswood-consulting.co.uk>
On 04/17/2012 02:24 PM, Frank Kingswood wrote:
> Hi Arend,
>> I noticed in some log you sent that your regulatory domain is set to
>> GB, which makes sense. I submitted a patch [1] last week so could you
>> try that and let me know the results.
> [re-sending as plain text]
>
> Thanks for the update. Yes, my AP is on channel 13 so might be affected
> by this.
>
> That line is in brcms_c_wait_for_tx_completion()
>
> main.c,8006 WARN_ON_ONCE(timeout == 0);
>
> Would using another channel be any different for this?
>
I actually did not expect that warning to come up with the patch in
place. So if you can try another channel in 1-11 range and let me know
the result, I might be able to make some sense of it all.
Gr. AvS
next prev parent reply other threads:[~2012-04-17 12:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-04 17:02 Kernel panic with brcm4313 (kernel 3.2.2) Frank A. Kingswood
2012-02-05 11:47 ` Arend van Spriel
2012-02-05 14:46 ` Frank Kingswood
2012-04-17 10:34 ` Arend van Spriel
[not found] ` <4F8D5EFD.8060300@kingswood-consulting.co.uk>
2012-04-17 12:18 ` Frank Kingswood
2012-04-17 12:24 ` Frank Kingswood
2012-04-17 12:52 ` Arend van Spriel [this message]
2012-04-17 13:55 ` Frank Kingswood
2012-02-05 12:39 ` Arend van Spriel
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=4F8D6793.8090701@broadcom.com \
--to=arend@broadcom.com \
--cc=frank@kingswood-consulting.co.uk \
--cc=linux-wireless@vger.kernel.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).