On 2026-06-19, Simon Wollwage <[email protected]> wrote: > I am running 7.9-current (same behavior on 7.8 though) on a Macbook Air > M2 using the bwfm wifi driver. From time to time (more often than I'd > like), the driver seems to just stop working. After a resume but > sometimes also in the middle of working on stuff. Running ifconfig then > hangs for a long time and can't read half the info on the bwfm0 device.
afaik problems on M2 Air are known. (and the slightly different wifi controller on Macbook Pro M2 wifi doesn't work at all). currently for reliable net on the laptop versions of M2 you need a USB adapter of some sort. > dmesg only shows this when it happens: > >> Jun 6 00:14:18 openbsd /bsd: bwfm0: missed beacon threshold set to 30 >> beacons, beacon interval is 100 TU >> Jun 6 00:14:18 openbsd /bsd: bwfm0: received msg 1/4 of the 4-way handshake >> from 7a:22:54:91:03:7e >> Jun 6 00:14:18 openbsd /bsd: bwfm0: sending msg 2/4 of the 4-way handshake >> to 7a:22:54:91:03:7e >> Jun 6 00:14:18 openbsd /bsd: bwfm0: received msg 3/4 of the 4-way handshake >> from 7a:22:54:91:03:7e >> Jun 6 00:14:18 openbsd /bsd: bwfm0: sending msg 4/4 of the 4-way handshake >> to 7a:22:54:91:03:7e >> Jun 6 00:46:31 openbsd /bsd: bwfm0: RUN -> INIT >> Jun 6 00:47:08 openbsd /bsd: bwfm0: flowring not closing >> Jun 6 00:47:10 openbsd /bsd: config_activate_children: device bwfm0 failed 2 >> Jun 6 00:47:10 openbsd /bsd: bwfm0: could not write MAC address I suspect this is something like "the driver does something that the controller doesn't like, so the controller crashes" > Furthermore, on one specific WLAN that I join sometimes at a different > location, the WLAN somehow causes the system to entirely freeze, but the > kernel isn't crashing, so all I can do is a hard reboot. If the reboot > doesn't fsck the "old" hostname.bwfm0 file and continues with that WLAN > added to it, the kernel crashes on boot. I tried to get a dump but was > unsuccessful in doing so. > > If there is anything I need to set to get a successful dump or anything > I can do in the debugger that opens on the boot crash, I can try to get > more info on it. see 5 from https://www.openbsd.org/report.html -- Please keep replies on the mailing list.
