-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WiFi firmware brcmfmac crashes when using virtual AP interface #1463
Comments
Add |
@pelwell Here is it:
|
Is that where it ends? I was expecting something more like this:
|
@pelwell That is the complete log from booting the RasPi until some minutes after the crash. There was nothing more. But to be sure I will try again. |
@pelwell Seems I had more luck now. This is what I get with a new try:
|
Any update on this? |
I don't know if this will help. But when I configured wlan0 on RPI3B as ap, I get:
I don't know if this is related, but it seems so. |
I am encountering the same problem even with firmware-brcm80211_20190114-1+rpt4_all.deb. |
I have had the wireless adapter on my Pi4 crash for months. I finally stumbled across this discussion: |
That version is likely to be released early in the new year. |
Thanks, Here is the log from the driver: "surprisingly" doesn't convey confidence :-) |
There is a release candidate firmware available for testing here: https://drive.google.com/file/d/11szy6tlDFL5d7A6JdZLEwr0ZE1yQfNkE/view?usp=sharing All being well it will be released in the next few weeks. |
Thanks, rpi ~$ sudo dpkg --purge firmware-brcm80211 |
No, not like that - this is a simple file substitution:
Once the new firmware is officially released the upgrade process will become:
|
Thanks
wpa_supplicant hangs after that and anything that I try like "ifconfig" or "iw wlan0 info" just sits there. |
My problem was unrelated. |
That "error" message is alarming, but it just shows that we aren't currently using per-device "nvram" files. What the messages don't show is that it then goes on to load |
Hi @pelwell i assume the new firmware is not part in https://downloads.raspberrypi.org/raspios_lite_armhf/images/raspios_lite_armhf-2021-01-12/ ? If not do i get it via [1]?
|
@delijati you can simply: |
Describe the bug
For a WiFi router/repeater I use a Raspberry Pi 4B and created an access point with an uplink client connection to the local internet router using a virtual interface of type
__ap
as created with:The router/repeater works stable with 2020-02-13-raspbian-buster-lite. After an upgrade to 2020-05-27-raspios-buster-lite-armhf I noticed from time to time a crash of the brcmfmac firmware, either silently doesn't reply, or with error message
Disabling power save does not make a difference with:
To reproduce
I have made a stress test that associated and disassociated a laptop with a static ip address to the access point in a loop for example with this script using systemd-networkd:
192.168.50.1 is the internet router of the uplink on the RasPi so routing is also tested. Calling the script with:
I flashed the image (see above) and run it on the RasPi and setup the testing with:
Reboot, then execute:
On the laptop start the stress test.
Expected behaviour
The stress test from the laptop should run without a crash of the brcmfmac firmware as seen with
2020-02-13-raspbian-buster-lite
. There I stopped it after 15 hours without a crash.Actual behaviour
With
2020-05-27-raspios-buster-lite-armhf
the stress test failed after typically 3 to 12 minutes. I haven't seen it running longer than 1 hour.System
2020-02-13-raspbian-buster-lite
comes with firmware-brcm80211_20190114-1+rpt4_all.deb.2020-05-27-raspios-buster-lite-armhf
comes with firmware-brcm80211_20190114-1+rpt6_all.deb.A workaround to fix the crash is to downgrade to the downloaded
firmware-brcm80211_20190114-1+rpt4_all.deb
:This runs stable all the time as before. The crash is 100 % reproducible when installing the downloaded
firmware-brcm80211_20190114-1+rpt6_all
again.Logs
Typical crash:
on the laptop called with
time sudo ./wifistress.sh
on the RasPi from the journal:
The text was updated successfully, but these errors were encountered: