Re: iwi fatal error

Stefan Sperling <[email protected]> Thu, 18 Jun 2026 15:33:28 +0200
Newsgroups gmane.os.openbsd.bugs
Message-ID <[email protected]>
On Wed, Jun 17, 2026 at 09:00:38PM -0400, [email protected] wrote:
> >Synopsis:	iwi fatal error message repeat regularly
> >Category:	iwi fatal error reported in dmesg
> >Environment:
> 	System      : OpenBSD 7.9
> 	Details     : OpenBSD 7.9 (GENERIC) #329: Wed May  6 14:56:46 MDT 2026
> 			 [email protected]:/usr/src/sys/arch/i386/compile/GENERIC
> 
> 	Architecture: OpenBSD.i386
> 	Machine     : i386
>         Hardware: Thinkpad X40
> >Description:
> many iwi fatal error reported in dmesg
> This has happened as long as I've been using this system, on an off for years,
> through many upgrades.
> System still seems to work O.K., although a bit delayed at time.
> 
> iwi0: flags=808843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,AUTOCONF4> mtu 1500
> 	lladdr 00:13:ce:ae:5b:67
> 	index 2 priority 4 llprio 3
> 	groups: wlan egress
> 	media: IEEE802.11 autoselect
> 	status: active
> 	ieee80211: join OTTERHOLE chan 1 bssid 64:d1:54:34:bf:f2 -39dBm wpakey wpaprotos wpa2 wpaakms psk wpaciphers ccmp wpagroupcipher ccmp
> 	inet 192.168.33.66 netmask 0xffffff00 broadcast 192.168.33.255
> 
> OTTERHOLE AP is Mikrotik 
> 

I would say this is a case of try to fix it yourself, or just live with it.

This driver hasn't been modified in significant ways in more than a decade.
And it is fairly small at only about 2000 lines of code. It is about as simple
as wifi drivers can get. It could be a good starting point to go in and try to
fix something, even for someone with no prior experience.