1
Diagnostic step 1
Capture full dmesg and kernel logs before and after suspend/resume to identify precise error codes and timestamps. Keep logs for vendor/maintainer bug reports.
FULL AI ANALYSIS
Broadcom STA/WL driver drops Wi‑Fi association after suspend on Linux laptop
Generated Oct 3, 2026, 12:35:03 AM
Analysis summary
Driver error messages on resume and the fact that module unload/reload fixes the problem indicate the wl driver fails to reinitialize the device after the kernel hands it back following suspend. This is likely a driver/kernel power-management interaction or PCI power state handling bug rather than a user-space NetworkManager issue. The module reload workaround reinforces a kernel-driver-level root cause.
Possible causes
Proprietary Broadcom wl driver does not properly handle device reset or PCI power state transitions on resume, leaving firmware in an unusable state.
85%PCIe/USB bus power sequencing on this laptop model interacts poorly with the wl driver, causing temporary resource allocation failures after resume.
70%Firmware on the Wi‑Fi chip has a corner-case bug that requires a hard reset (power-cycle) which module reload attempts to emulate partially.
30%Kernel regression between versions (e.g., missing suspend hooks or changed PCI quirk) that affects this specific chipset and driver ABI.
25%Suggested fixes
2
Diagnostic step 2
Create a reproducible minimal test script that suspends and resumes (sleep then wake) while capturing dmesg to demonstrate the failure consistently for maintainers.
3
Diagnostic step 3
Continue using the reversible module-reload workaround via a systemd sleep hook (create /lib/systemd/system-sleep/wl-reload script that rmmods and modprobes the wl module), noting this is a workaround and not a fix.
4
Diagnostic step 4
Try booting a live USB with a newer/mainline kernel to test whether a newer kernel/driver combo fixes resume behavior (non-destructive trial).
5
Diagnostic step 5
If possible, contact Broadcom or distribution maintainers with logs and repro steps; escalate to kernel driver maintainers if a kernel regression is suspected. If hardware replacement is an option and issue persists across kernel versions, test with a USB Wi‑Fi dongle as a definitive hardware bypass.