Thanks Stefan for the quick answer! I have been running with the 7265-17 image for two days and the problem hasn't showed up. I'll keep you posted if it comes back in the next few days.
On Thu, May 30, 2024 at 12:15:26PM +0200, Stefan Sperling wrote: > On Thu, May 30, 2024 at 09:55:00AM +0200, a...@alexis-fouilhe.fr wrote: > > >Synopsis: iwm frequent 'device timeout' error > > >Category: kernel > > >Environment: > > System : OpenBSD 7.5 > > Details : OpenBSD 7.5 (GENERIC.MP) #55: Mon Mar 4 21:59:07 MST 2024 > > > > dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > > > > Architecture: OpenBSD.amd64 > > Machine : amd64 > > >Description: > > Several times a day, wireless networking stops working for a couple of > > minutes. > > Requests time out, browser reports that it can't reach any site, etc. > > After a short time, 'iwm0: device timeout' is added to dmesg and after > > yet > > another short time, wireless networking starts working again. > > iwm0 man page says is should not happen. > > This has happened to me for as long as I can remember. > > > > Below is what the driver says after 'ifconfig iwm0 debug'. > > I trimmed a number of copies of the five lines beginning with > > 'iwm0: begin background scan', both before the timeout and after > > recovery. > > Does it work more reliably if you replace the firmware file as follows? > Not sure if this will help or even work at all, but it might: > > mv /etc/firmware/iwm-7265D-29 /etc/firmware/iwm-7265D-29.orig > cp /etc/firmware/iwm-7265-17 /etc/firmware/iwm-7265D-29 > ifconfig iwm0 down up # force firmware reload > > If this helps then I could change the driver to load 7265-17 firmware > file by default. > > The reason I'm asking is that our driver has issues with 7265D firmware. > We are still using the 7265-17 image on 7265 devices because of this. > The 3165 you have is the same chip, with some capabilities missing.
