From: "Arend van Spriel" <arend@broadcom.com>
To: "Seth Forshee" <seth.forshee@canonical.com>
Cc: linux-wireless@vger.kernel.org,
"Stefano Brivio" <stefano.brivio@polimi.it>,
"Rafał Miłecki" <zajec5@gmail.com>,
"Hauke Mehrtens" <hauke@hauke-m.de>
Subject: Re: BCM4331 tx failures after S3
Date: Thu, 24 May 2012 11:36:16 +0200 [thread overview]
Message-ID: <4FBE0110.5020209@broadcom.com> (raw)
In-Reply-To: <20120523135506.GB30165@thinkpad-t410>
On 05/23/2012 03:55 PM, Seth Forshee wrote:
> On Wed, May 23, 2012 at 11:30:38AM +0200, Arend van Spriel wrote:
>> On 05/22/2012 06:52 PM, Seth Forshee wrote:
>>> Hi Arend,
>>>
>>> I've inquired about this issue on the list once before, but I thought
>>> I'd try once again to see if Broadcom can offer any suggestions.
>>>
>>> Recent MacBook Pros with BCM4331 wireless have a strange problem. Tx
>>> doesn't work after S3, but only if no external power is applied during
>>> the resume. mac80211 reports mostly timeouts for responses to probe
>>> requests, but analysis with wireshark shows no frames from the BCM4331
>>> on the air. The only way I've found to recover is to reload both b43 and
>>> bcma; reloading b43 alone is not enough.
>>
>> Yikes. I recently did suspend/resume and hibernate testing with BCM43224
>> (so brcmsmac and bcma), but my system was on AC. I will execute them
>> again on battery. I want to make sure it is not a BCM4331 specific issue.
>
> I'm also testing a Macbook Air with BCM43224 using brcmsmac, and it does
> not suffer from the same issue.
Good to know. I will check whether there are any known issues with
BCM4331 that could explain this.
>>> I've checked the values of MACCTL and the DMA TXCTL registers, since
>>> these are the ones used by brcmsmac to mute tx, but those look okay. Any
>>> suggestions of other things to check? My next step would be to start
>>> looking at the state of the phy and radio, but since we don't have much
>>> information about what the registers there actually do some suggestions
>>> would be helpful.
>>
>> When going to S3 the driver is told by mac80211 .stop callback to abort
>> driver operation so I do not expect b43 has a problem. Instead we
>> probably have to look at the host PCI code in bcma, but before going
>> there let me execute my tests.
>>
>> Can you tell me on what kernel version you see this issue. I would also
>> like to have a look at your kernel log.
>
> I'm still seeing it in both 3.4 and wireless-testing. Attached is dmesg
> from wireless-testing.
Nothing really looks wrong in there, but then again there are not much
b43/bcma related messages.
Gr. AvS
next prev parent reply other threads:[~2012-05-24 9:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 16:52 BCM4331 tx failures after S3 Seth Forshee
2012-05-23 9:15 ` Hauke Mehrtens
2012-05-23 13:51 ` Seth Forshee
2012-05-23 9:30 ` Arend van Spriel
2012-05-23 13:55 ` Seth Forshee
2012-05-24 9:36 ` Arend van Spriel [this message]
2012-05-24 21:21 ` Seth Forshee
2012-05-24 21:34 ` Hauke Mehrtens
2012-05-25 10:16 ` Arend van Spriel
2012-05-25 14:13 ` Seth Forshee
2012-05-25 16:47 ` Arend van Spriel
2012-05-25 18:34 ` Seth Forshee
2012-05-25 20:19 ` Arend van Spriel
2012-05-25 20:44 ` Seth Forshee
2012-05-25 20:59 ` Arend van Spriel
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=4FBE0110.5020209@broadcom.com \
--to=arend@broadcom.com \
--cc=hauke@hauke-m.de \
--cc=linux-wireless@vger.kernel.org \
--cc=seth.forshee@canonical.com \
--cc=stefano.brivio@polimi.it \
--cc=zajec5@gmail.com \
/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).