linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Troy Kisky <troy.kisky@boundarydevices.com>
To: Luciano Coelho <coelho@ti.com>
Cc: Gary Thomas <gary@mlbassoc.com>, linux-wireless@vger.kernel.org
Subject: Re: wl1271 watchdog interrupt
Date: Tue, 03 Apr 2012 18:26:36 -0700	[thread overview]
Message-ID: <4F7BA34C.2030001@boundarydevices.com> (raw)
In-Reply-To: <1333355941.16990.23.camel@cumari>

On 4/2/2012 1:39 AM, Luciano Coelho wrote:
> Hi,
>
> On Tue, 2012-03-27 at 08:25 -0600, Gary Thomas wrote:
>> On 2012-03-21 19:26, Troy Kisky wrote:
>>> Hi all
>>>
>>> We have a new board using the wl1271. As long as I keep it busy,
>>> everything is fine. But once it becomes idle I get,
>>> "wl12xx: ERROR watchdog interrupt received! starting recovery."
>>>
>>> Has this been seen by others?
>> I'm getting very similar problems and my messages to this list (and the
>> wl12xx maintainer) are now waiting for nearly two weeks for an answer.
>>
>> Can someone help with these wl12xx issues?
> Sorry for the delay, I've been busy traveling and on vacations in the
> past weeks.
>
>
>>> I'm using compat-wireless-2012-01-26 and my kernel is based on 3.0
>>>
>>> Other relevant log messages:
>>> cfg80211: Calling CRDA to update world regulatory domain
>>> add wake up source irq 108
>>> wl12xx: loaded
>>> wl12xx: firmware booted (Rev 6.3.0.0.77)
>>> wlan0: authenticate with 00:12:17:31:67:e7 (try 1)
>>> wlan0: authenticated
>>> wlan0: associate with 00:12:17:31:67:e7 (try 1)
>>> wlan0: RX AssocResp from 00:12:17:31:67:e7 (capab=0x411 status=0 aid=3)
>>> wlan0: associated
>>> wlan0: moving STA 00:12:17:31:67:e7 to state 1
>>> wlan0: moving STA 00:12:17:31:67:e7 to state 2
>>> wlan0: moving STA 00:12:17:31:67:e7 to state 3
>>> wl12xx: Association completed.
>>>
>>> .......
>>> wl12xx: ERROR watchdog interrupt received! starting recovery.
>>> wl12xx: Reading FW panic log
>>> wl12xx: ERROR command complete timeout
> This is a firmware bug.  Can you please take the contents
> of /sys/bus/platform/drivers/wl12xx_driver/wl12xx/fwlog and send it to
> us so we can take a look at what's going on?
Sorry, it isn't a firmware bug. It was a configuration problem on my 
part. The defconfig
file I was using was enabling a TVOUT driver which this board doesn't 
have. When
the driver wanted to blank the screen, it was turning off my slow clock 
to my WL1271.

When the WL1271 later becomes idle, it goes into a low power state which 
depends upon
slow clock. So please tell your firmware guys, "never mind."
>> wl12xx: Hardware recovery in progress. FW ver: Rev 6.3.0.0.77 pc: 0x23923
> This tells us where the PC was when the crash happened.  I'll ask our
> firmware team to analyze this.
"Never mind...."


Thanks
Troy


  reply	other threads:[~2012-04-04  1:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22  1:26 wl1271 watchdog interrupt Troy Kisky
2012-03-27 14:25 ` Gary Thomas
2012-04-02  8:39   ` Luciano Coelho
2012-04-04  1:26     ` Troy Kisky [this message]
2012-04-04  2:58       ` Luciano Coelho
2012-04-04 11:20         ` Gary Thomas
2012-04-10  6:24           ` Luciano Coelho
2012-04-10 12:05             ` Gary Thomas

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=4F7BA34C.2030001@boundarydevices.com \
    --to=troy.kisky@boundarydevices.com \
    --cc=coelho@ti.com \
    --cc=gary@mlbassoc.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;
as well as URLs for NNTP newsgroup(s).