From: Vasanthakumar Thiagarajan <vthiagar@qca.qualcomm.com>
To: Brent Taylor <btaylor1@motorolasolutions.com>
Cc: <linux-wireless@vger.kernel.org>
Subject: Re: ATH6KL lockup during init
Date: Wed, 27 Jul 2011 10:49:50 +0530 [thread overview]
Message-ID: <20110727051949.GA19410@vasanth-laptop> (raw)
In-Reply-To: <loom.20110726T174149-11@post.gmane.org>
On Tue, Jul 26, 2011 at 03:43:02PM +0000, Brent Taylor wrote:
> I’m a developer working with the Atheros AR6003 Wireless LAN chip. I recently
> updated the Linux kernel on my custom board to 3.0.0 and pulled the latest
> snapshot of the ath6kl driver from
> http://git.kernel.org/?p=linux/kernel/git/kvalo/ath6kl-cleanup.git;a=summary (as
> of 2011-07-25). I’m also using the latest firmware images from
> http://www.kernel.org/pub/linux/kernel/people/mcgrof/firmware/ath6k.tar.gz as
> recommended by
> http://wireless.kernel.org/en/users/Drivers/ath6kl?highlight=%28ar6003%29.
>
These are fine.
> After running 'insmod ath6kl.ko', the command line hangs. I’ve narrowed down
> the execution path to the function ath6kl_bmi_get_rx_lkahd (called from
> ath6kl_bmi_exeute after loading the OPT firmware). The parameter value of
> "need_timeout" is set to false. Without this timeout the function never
> returns. The call to ath6kl_hif_read_write_sync always returns 0, and the value
> of rx_word is always 0.
>
> My question is: What would cause the read from address
> RX_LOOKAHEAD_VALID_ADDRESS to always return a value of 0?
Odd, we have never seen this sort of issues. Can you please give
the kernel debug output with BMI debug enabled (debug_mask=0x10).
Vasanth
next prev parent reply other threads:[~2011-07-27 5:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 15:43 ATH6KL lockup during init Brent Taylor
2011-07-27 5:19 ` Vasanthakumar Thiagarajan [this message]
2011-07-27 12:51 ` Brent Taylor
2011-08-02 5:59 ` Kalle Valo
2011-08-04 12:55 ` Brent Taylor
2011-09-13 6:29 ` Kalle Valo
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=20110727051949.GA19410@vasanth-laptop \
--to=vthiagar@qca.qualcomm.com \
--cc=btaylor1@motorolasolutions.com \
--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