On Wed, Apr 05, 2023 at 11:55:02AM +0100, Laurence Tratt wrote: > On Mon, Apr 03, 2023 at 09:56:20PM +0200, Stefan Sperling wrote: > > Hello Stefan, > > > This particular sysassert code (0x20002806) is a known issue since > > the -77 firmware update. I don't know what is triggering this error > > and so far I have failed to reproduce it. Apparently something is > > wrong with the scan command but I don't know what is wrong exactly. > > > > As a workaround, does it help to disable background scanning by > > temporarily hard-coding the MAC address of the working 2GHz AP? > > > > ifconfig iwx0 bssid 04:20:84:31:dd:ab > > As you might remember, I've also encountered the same issue with iwx, on two > machines -- I could rack up a few hundred timeouts in an hour if I was > unlucky. > > Since, as you suggested above, forcing the bssid to a specific address, I've > had no timeouts on either machine in a bit over 24 hours, even when I've > been deliberately hammering the network on both machines! So that's a good > short-term fix for me, though whether or not it helps you work out the > underlying cause, I don't know! > > > Laurie >
So I can reliably reproduce "some" hang. I'm not sure it's the same as yours or not. Mine always occurs with network traffic. Forgive me if I already asked, but did we test just letting the machine sit idle in yor env? (Can't recall). I am going to let mine sit overnight just playing videos with mplayer from a local file and see if it hangs. I did (yey) manage to grab a witness error with netlock ; perhaps this is what is causing the "hangs when network is in use". -ml
