From: Arend van Spriel <arend.vanspriel@broadcom.com>
To: Carl-Erik Kopseng <carlerik@gmail.com>,
brcm80211-dev-list.pdl@broadcom.com
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: Driver crashes on resume after suspend
Date: Tue, 17 Apr 2018 10:28:23 +0200 [thread overview]
Message-ID: <5AD5B027.1030706@broadcom.com> (raw)
In-Reply-To: <CAA05WiZDz1yqHHA-x8bkLSBru_kmwU9wws7gp5NQQEjYEDCaVw@mail.gmail.com>
+ linux-wireless
On 4/17/2018 12:02 AM, Carl-Erik Kopseng wrote:
> I have a BCM4350 on my Ubuntu 18.04 system. Until today, I could never
> suspend my computer, as the driver brcmfmac would crash on resume
> (looking in dmesg) and only a reboot would make the device reappear.
>
> Today, I found a workaround by making the pm-* commands remove and add
> the module before any power management action:
> echo 'SUSPEND_MODULES="brcmfmac"' | sudo tee -a /etc/pm/config.d/config
>
> This worked fine, but it took me quite a lot of digging, including
> trying out the `wl` driver, the `b43` package, and lots of tweaking. But
> even after going full circle and finding a fix, this still doesn't
> address the actual underlying problem: that brcmfmac doesn't survive
> hibernation and standby. Is there any data I can supply to remedy the
> situation? I attached the dump from wifi debugging utility to pinpoint
> my configuration, but it doesn't contain any dmesg output from the
> kernel crashes. You would probably want a more detailed output than what
> is supplied by dmesg anyway ...
Well. dmesg is always a start so let's have it. If you can compile the
driver you could build it with CONFIG_BRCMDBG enabled and load the
driver with parameter 'debug=0x80000'.
Regards,
Arend
parent reply other threads:[~2018-04-17 8:28 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <CAA05WiZDz1yqHHA-x8bkLSBru_kmwU9wws7gp5NQQEjYEDCaVw@mail.gmail.com>]
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=5AD5B027.1030706@broadcom.com \
--to=arend.vanspriel@broadcom.com \
--cc=brcm80211-dev-list.pdl@broadcom.com \
--cc=carlerik@gmail.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).