From: Michael Tokarev <mjt@tls.msk.ru>
To: Arend van Spriel <arend@broadcom.com>
Cc: brcm80211-dev-list@broadcom.com, linux-wireless@vger.kernel.org
Subject: Re: BCM4313 & brcmsmac & 3.12: only semi-working?
Date: Sat, 28 Dec 2013 16:24:22 +0400 [thread overview]
Message-ID: <52BEC2F6.7010505@msgid.tls.msk.ru> (raw)
In-Reply-To: <52BE9CF9.7030305@broadcom.com>
[-- Attachment #1: Type: text/plain, Size: 2917 bytes --]
Thank you very much for the reply!
28.12.2013 13:42, Arend van Spriel wrote:
> On 12/27/2013 09:58 PM, Michael Tokarev wrote:
>> Hello.
>>
>> Got a Lenovo Thinkpad notebook with the following wifi card:
>>
>> 03:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller [14e4:4727] (rev 01)
>> Subsystem: Broadcom Corporation Device [14e4:0608]
>> Flags: bus master, fast devsel, latency 0, IRQ 17
>> Memory at f1600000 (64-bit, non-prefetchable) [size=16K]
>> Capabilities: [40] Power Management version 3
>> Capabilities: [58] Vendor Specific Information: Len=78 <?>
>> Capabilities: [48] MSI: Enable- Count=1/1 Maskable- 64bit+
>> Capabilities: [d0] Express Endpoint, MSI 00
>> Capabilities: [100] Advanced Error Reporting
>> Capabilities: [13c] Virtual Channel
>> Capabilities: [160] Device Serial Number 00-00-24-ff-ff-fe-48-d2
>> Capabilities: [16c] Power Budgeting <?>
>> Kernel driver in use: bcma-pci-bridge
[wifi tx stalls after short usage, 3.12 kernel]
>> P.S. I tried to find archives of brcm80211 list, or a way to
>> subscribe to it before posting, but found neither. Are there
>> archives?
>
> Nope. The brcm80211-dev-list is just a (hopefully) convenient way to get
> your message to the brcm80211 driver developer within Broadcom. So it is
> always best to Cc: the linux-wireless list as well.
Ah. So the real archives should be for linux-wireless@ not for brcm..@ :)
Got it, thank you!
> Now about your card. I am not sure where to start, but can you dump
> contents for following debugfs file:
>
> /sys/kernel/debug/brcmsmac/bcma*/hardware
# cat /sys/kernel/debug/brcmsmac/bcma0\:0/hardware
board vendor: 14e4
board type: 608
board revision: 1109
board flags: 402201
board flags2: 884
firmware revision: 262032c
> Also a capture file would be great so if you have wireshark or dumpcap you can add monitor interface and capture 802.11 packets from connect up until the stalls. Commands for adding/enabling monitor interface (ass root/sudo):
>
> # iw dev wlan0 interface add mon0 type monitor
> # ifconfig mon0 up
Capture file made with tcpdump is attached (gzipped). I started the
capture with wlan0 disabled, next I used `nmcli con up id "wifi mjt"'
to connect to the AP (named, obviously, "mjt"), and next I tried to
d/load a file from my website (86.62.121.231). It d/loaded about 27Kb
and stalled. Next I tried to ping the AP (192.168.88.65), which also
didn't work.
That's quite a typical behavour of this whole thing. Sometimes it
lasts a bit longer, but that's rather unusual and it ends up stalling
anyway.
Is it worth the effort to try 3.13-tobe kernel here? I browsed changes
in there made in drivers/net/wireless/brcm80211/ compared with 3.12, but
there aren't many changes related to the softmac version, and most
looks rather cosmetic.
Thank you very much for the help!
/mjt
[-- Attachment #2: bcm4313.dump.gz --]
[-- Type: application/gzip, Size: 45904 bytes --]
next prev parent reply other threads:[~2013-12-28 12:24 UTC|newest]
Thread overview: 64+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-27 20:58 BCM4313 & brcmsmac & 3.12: only semi-working? Michael Tokarev
2013-12-28 9:42 ` Arend van Spriel
2013-12-28 12:24 ` Michael Tokarev [this message]
2014-01-14 8:59 ` Michael Tokarev
2014-01-14 9:30 ` Nikita N.
2014-02-10 19:16 ` Michael Tokarev
2014-04-19 11:42 ` Michael Tokarev
2014-08-26 5:13 ` Michael Tokarev
2014-08-26 14:56 ` Arend van Spriel
2014-08-26 16:15 ` Michael Tokarev
2014-08-26 21:37 ` Arend van Spriel
2014-08-27 10:02 ` Michael Tokarev
2014-08-27 15:27 ` Arend van Spriel
2014-09-15 8:03 ` Arend van Spriel
2014-09-21 15:30 ` Michael Tokarev
2014-09-23 10:04 ` Michael Tokarev
2014-09-23 12:47 ` Arend van Spriel
2014-09-23 13:44 ` Seth Forshee
2014-09-23 13:50 ` Arend van Spriel
2014-09-23 14:25 ` Michael Tokarev
2014-09-23 14:28 ` Michael Tokarev
2014-09-23 14:31 ` Seth Forshee
2014-09-23 16:02 ` Michael Tokarev
2014-09-23 17:35 ` Arend van Spriel
2014-09-23 18:10 ` Michael Tokarev
2014-09-24 13:28 ` Arend van Spriel
2014-09-24 14:51 ` Michael Tokarev
2014-09-26 14:26 ` Michael Tokarev
2014-09-26 14:42 ` Arend van Spriel
2014-09-26 15:20 ` Michael Tokarev
2014-09-29 13:44 ` Arend van Spriel
2014-09-29 19:40 ` Maximilian Engelhardt
2014-09-30 10:06 ` Arend van Spriel
2014-10-08 22:19 ` Maximilian Engelhardt
2014-10-09 7:52 ` Arend van Spriel
2014-10-09 8:21 ` Rafał Miłecki
2014-11-17 22:36 ` Maximilian Engelhardt
2014-11-19 9:04 ` Michael Tokarev
2014-11-19 17:54 ` Arend van Spriel
2014-11-19 19:58 ` Michael Tokarev
2014-11-19 21:00 ` Michael Tokarev
2014-11-23 9:43 ` Arend van Spriel
2014-11-26 9:52 ` Michael Tokarev
2014-11-30 12:04 ` Arend van Spriel
2014-12-02 21:40 ` Michael Tokarev
2014-12-03 12:43 ` Arend van Spriel
2014-12-16 16:51 ` Arend van Spriel
2014-12-21 9:58 ` Michael Tokarev
2014-12-21 10:12 ` Arend van Spriel
2014-12-21 10:27 ` Michael Tokarev
2014-12-21 11:38 ` Arend van Spriel
2014-12-21 14:08 ` Maximilian Engelhardt
2014-12-21 14:13 ` Arend van Spriel
2014-12-21 14:24 ` Maximilian Engelhardt
2014-12-21 15:03 ` Arend van Spriel
2014-12-21 17:34 ` Maximilian Engelhardt
2015-03-09 20:54 ` Daniel Glöckner
2015-03-10 21:27 ` Arend van Spriel
2016-03-14 16:41 ` Daniel Glöckner
[not found] ` <54969A46.8000807@msgid.tls.msk.ru>
2014-12-21 10:17 ` Arend van Spriel
2014-12-01 22:06 ` Maximilian Engelhardt
2014-11-19 13:46 ` Arend van Spriel
2014-11-19 13:49 ` Arend van Spriel
-- strict thread matches above, loose matches on Subject: below --
2020-08-24 3:44 Sébastien Le Preste De Vauban
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=52BEC2F6.7010505@msgid.tls.msk.ru \
--to=mjt@tls.msk.ru \
--cc=arend@broadcom.com \
--cc=brcm80211-dev-list@broadcom.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).