[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5421AF5C.6000106@broadcom.com>
Date: Tue, 23 Sep 2014 19:35:24 +0200
From: Arend van Spriel <arend@...adcom.com>
To: Michael Tokarev <mjt@....msk.ru>
CC: Seth Forshee <seth.forshee@...onical.com>,
<brcm80211-dev-list@...adcom.com>,
<linux-wireless@...r.kernel.org>, <netdev@...r.kernel.org>
Subject: Re: BCM4313 & brcmsmac & 3.12: only semi-working?
On 09/23/14 18:02, Michael Tokarev wrote:
> 23.09.2014 18:31, Seth Forshee пишет:
>> On Tue, Sep 23, 2014 at 06:28:54PM +0400, Michael Tokarev wrote:
>>> 23.09.2014 18:25, Michael Tokarev wrote:
>>>> 23.09.2014 17:50, Arend van Spriel wrote:
>>>>> On 09/23/14 15:44, Seth Forshee wrote:
>>> []
>>>>>> 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).
>>>
>>> mac80211_msg does not exist, it looks like. fwiw.
>>
>> Did you check your kernel's config? You need to have
>> CONFIG_MAC80211_MESSAGE_TRACING enabled.
>
> Oh. Indeed. While I enabled it, I recompiled only drivers/net/wireless,
> but not net/. Rebuilt, another trace is here --
>
> http://www.corpit.ru/mjt/tmp/brcmsmac-4313-trace-201409233.dat.gz
>
> Thanks,
Just to confirm. With this trace you also get a stall during wget?
Regards,
Arend
> /mjt
>
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists