Hi,

On Sat, 29 Jan 2022, at 22:18, Kamil Jonca wrote:
> Package: wpasupplicant
> Version: 2:2.10-1
> Severity: important
> X-Debbugs-Cc: kjo...@poczta.onet.pl
>
> I have upgraded some packages on my laptop with 
>
> 24:00.0 Network controller: Broadcom Inc. and subsidiaries BCM43228 
> 802.11a/b/g/n
>
> controller. After I was not able to up wlan interface and in logs I 
> have entries like:
>
> =============
> 2022-01-29T21:54:57.996370+01:00 bambus wpa_supplicant[22258]: wlan0: 
> CTRL-EVENT-SCAN-FAILED ret=-22 retry=1
> =============
> When I downgrade to 2:2.9.0-22+b1 (and only this package was downgraded)
> everything started to work.

Thanks for your report. I will forward this report to the upstream developers, 
but to help them investigate this issue, could you enable wpa_supplicant debug 
option and provide the logs?

1. Edit /lib/systemd/system/wpa_supplicant.service and add -dddddddddd option:

ExecStart=/sbin/wpa_supplicant -u -s -dddddddddd -O /run/wpa_supplicant

2. Restart wpa_supplicant:
# systemctl daemon-reload
# systemctl restate wpa_supplicant

3. Enable NetworkManager logging:
# nmcli general logging level DEBUG domains ALL

4. Get logs:
$ journalctl -u wpa_supplicant -b
$ journalctl -u NetworkManager -b

Thanks!

-- 
Cheers,
  Andrej

Reply via email to