Date: Sun, 16 Jul 2023 00:36:49 +0000 From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 272525] if_iwm: failed to send antennas before calibration with Intel AC 9560 Message-ID: <bug-272525-21060@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D272525 Bug ID: 272525 Summary: if_iwm: failed to send antennas before calibration with Intel AC 9560 Product: Base System Version: 13.2-RELEASE Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: wireless Assignee: wireless@FreeBSD.org Reporter: laurent@nilio.ca Created attachment 243413 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D243413&action= =3Dedit dmesg during a problematic session Hello, Once in a while, when I boot my laptop, the iwm driver is presumably not initialized correctly and I get these messages in the console: iwm0: failed to send antennas before calibration: 35 iwm_run_init_ucode: failed 35 iwm_init_hw failed 35 iwm0: could not initiate scan The last line repeats itself forever. Unloading if_iwm and reloading it does not fix the problem. However, the problem may disappear after a reboot. According to sys/errno.h, 35 is EAGAIN. The device would be busy with somet= hing else during the configuration of the antennas. I can't figure out what it's doing, but it must be actively stuck in a bad mode for a module reload to k= eep failing. Another helpful hint is that line after the reload: iwm0: Could not send NVM_ACCESS command (error=3D35) It didn't do this the first time, but it does it after reloading the module, meaning something caused the device regression the first time it was loaded. Thank you, Laurent --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-272525-21060>