Re: iwi(4) fatal firmware error
On Thu, Apr 5, 2018 at 3:37 AM, Stefan Sperling wrote: > > Is this a purely cosmetic issue or does it actually prevent your > wifi connection from working? > > These looks like potentially harmless errors which happen during > association. > Does the driver recover from these errors automatically? It should be able > to. > > As to why the firmware reports such errors: We have no idea. It's a black > box. > As far as I can tell, it recovers. Lately, it's been doing it at odd hours when I'm not actually using it, but I've never come back to it being disconnected or anything like that. I had it next to me streaming music with Pianobar for a few hours yesterday without any hiccups. I'll just ignore these. Thanks, stsp!
Re: iwi(4) fatal firmware error
On Wed, Apr 04, 2018 at 12:20:03PM -0500, Ax0n wrote: > I have a Motorola ML900 which seems to be running OpenBSD with X and > WindowMaker just fine. Every few hours it gets a group of errors within the > span of a few seconds (about 1 second between them in /var/log/messages) > > Apr 4 04:30:01 luggy /bsd: iwi0: fatal firmware error > Apr 4 05:17:37 luggy /bsd: iwi0: fatal firmware error > Apr 4 05:17:39 luggy /bsd: iwi0: unknown authentication state 1 > Apr 4 05:17:40 luggy /bsd: iwi0: reused group key update received from > 60:38:e0:89:9b:dc > Apr 4 06:51:05 luggy /bsd: iwi0: fatal firmware error > Apr 4 06:51:06 luggy /bsd: iwi0: unknown authentication state 1 > Apr 4 06:51:07 luggy /bsd: iwi0: reused group key update received from > 60:38:e0:89:9b:dc > Apr 4 10:11:48 luggy /bsd: iwi0: fatal firmware error > Apr 4 10:11:51 luggy /bsd: iwi0: unknown authentication state 1 > Apr 4 10:11:52 luggy /bsd: iwi0: reused group key update received from > 60:38:e0:89:9b:dc > > I was seeing this same behavior with 6.2-STABLE, which I just installed a > few weeks ago. > > Full dmesg (before any of the above errors) is below. Is this a purely cosmetic issue or does it actually prevent your wifi connection from working? These looks like potentially harmless errors which happen during association. Does the driver recover from these errors automatically? It should be able to. As to why the firmware reports such errors: We have no idea. It's a black box.
