Re: BCM4313 & brcmsmac & 3.12: only semi-working?

[Arend van Spriel <arend@broadcom.com>]

On 09/23/14 15:44, Seth Forshee wrote:
> On Tue, Sep 23, 2014 at 02:47:45PM +0200, Arend van Spriel wrote:
>> On 09/23/14 12:04, Michael Tokarev wrote:
>>> 21.09.2014 19:30, Michael Tokarev wrote:
>>>> Namely, after resume, the card does not work. ARP works, ping and
>>>> DNS sometimes/somewhat work, inital TCP connection establisment
>>>> works, but eg http download does not work, it stalls almost
>>>> immediately.
>>>
>>> It does not work at all anymore again.  Not only after resume but also
>>> after could power up, it stalls right at start of wget for example.
>>>
>>>> http://www.corpit.ru/mjt/tmp/brcmsmac-4313-trace-20140921.dat.gz -- this
>>>> is a trace collected after resuming from suspend-to-disk
>>>
>>> And here -- http://www.corpit.ru/mjt/tmp/brcmsmac-4313-trace-20140923.dat.gz
>>> is another trace, after insmod brcmutils&   brcmsmac, starting trace-cmd record
>>> (with network-manager running in the background), and running a wget on
>>> http://ip-add-ress-of-the-access-point/somefile (which immediately stalls,
>>> showing minimal progress once in a while only).
>>
>> Well. This log and the one from a few days ago only show me
>> interrupt status changes, which does not tell me a lot. I do see
>> that the hardware signals transmit completions, but it is far less
>> informative then I hoped it would be. Maybe I am missing some debug
>> configuration here?
>>
>> Seth, would you know?
>
> Well, there are a few different trace events defined for brcmsmac. This
> would enable the full set:
>
>   $ trace-cmd record -e brcmsmac -e brcmsmac_tx -e brcmsmac_msg
>
> It's been quite some time since I used them, but I think brcmsmac_tx is
> quite noisy so you may only want to enable that if you already suspect a
> tx problem. I always find it useful to enable the mac80211 and
> mac80211_msg events too when debugging wireless, and I often enable
> cfg80211 events as well (none of these are especially verbose).

Ah, I read back the email from Sep 21 and it says:

trace-cmd record brcmsmac:* &

I am surprised the capture contains something as -e is missing. Good to 
know there are different tracers for the driver.

Regards,
Arend

> Of course all of this depends on having the right config options
> selected. Looks like the relevant options are CONFIG_BRCM_TRACING and
> CONFIG_MAC80211_MESSAGE_TRACING.
>
> Seth
>