Re: 8265 / 9560 problems
- Reply: Bjoern A. Zeeb: "Re: 8265 / 9560 problems + 7260 + AX200"
- In reply to: Tomoaki AOKI : "Re: 8265 / 9560 problems"
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Tue, 12 Apr 2022 04:45:20 UTC
On 2022-04-08 18:45, Tomoaki AOKI wrote: > On Fri, 8 Apr 2022 11:24:30 +0000 (UTC) > "Bjoern A. Zeeb" <bz@FreeBSD.org> wrote: > >> On Fri, 8 Apr 2022, Bjoern A. Zeeb wrote: >> >> > On Fri, 8 Apr 2022, Eirik 〓verby wrote: >> > >> >> On Fri, 2022-04-08 at 12:48 +0200, J.R. Oldroyd wrote: >> >>> On Thu, 7 Apr 2022 17:14:26 +0000 (UTC) "Bjoern A. Zeeb" <bz@FreeBSD.org> >> >>> wrote: >> >>>> >> >>>> Hi, >> >>>> >> >>>> I have reports from at least three people saying that atfer the March 27 >> >>>> update associating has become hard and they see firmware crashes. >> >>>> >> >>>> These were on 8265 / 9560 chipsets. Some of you tried to gather data >> >>>> for me as well, testing out patches without a positive outcome. >> >>>> I've been able to reproduce this in the lap with a freshly installed >> >>>> 8265. >> >>>> Just wanted to give you that update that I am looking into it. >> >>>> >> >>>> I hope I'll have a further update soon. >> >>>> >> >>>> Bjoern >> >>>> >> >>> >> >>> I was one of those people reporting this. I have an 8265. >> >>> >> >>> For me, applying Bjoern's rssi patch AND also making sure that iwm does >> >>> not load first by using in rc.conf: >> >>> devmatch_blacklist="if_iwm.ko" >> >>> solves the firmware crash and allows iwlwifi to load and associate cleanly >> >>> on boot. >> >>> >> >> >> >> I'll be testing this - can you point me to the patch in question (I >> >> think I missed it..?) >> > >> > It'll be in main in the next hour or so. I'll post a cherry-pick line >> > for people on stable as soon as it is. >> >> If you are on main, you can simply update. If you are on stable/13 >> you want or wait until I'll MFC: >> >> git cherry-pick -x 170acccf1e191ae28571845ad6f0b5a2fbf0effc >> >> And many thanks to JR for his work on this! >> >> >> While this seems to have helped, I can still crash on my 8265 but I >> have probably learnt to twist knobs to do that in the last weeks with >> AX200. >> >> I'll be very happy to hear if this helps you (and others on more >> modern chipsets). >> >> Later, >> Bjoern >> >> -- >> Bjoern A. Zeeb r15:7 > > Thanks. Seems we have advanced! > But unfortunately, it seems to be somehow racy on initialization. > > Tried both > > stable/13 at git 44c69c0a3172b1af1211d7afd72d68deca1099b2 with > cherry-picking git 170acccf1e191ae28571845ad6f0b5a2fbf0effc > > and > > main at git fcaf016796cc0272a8c239850fa87244eebefe13, which is after > git 170acccf1e191ae28571845ad6f0b5a2fbf0effc. > > each of which has devmatch_blacklist="if_iwm.ko" in /etc/rc.conf. > *Maybe devmatch_blacklist="${devmatch_blacklist} if_iwm.ko" > would be safer. > > Sometimes fairly initialized and associated, but sometime not, > regardless cold boot or warm restart. > > Switching to wired (em0) connection and back to wlan0 (iwlwifi0) > sometimes work but sometime not (firmware crash just as before). I can confirm this also happens with a 7260 on 13.1-RC2. I can NOT get it to work on warm or cold boot. I use devmatch_blacklist="if_iwm.ko" However. After login, if I send a service netif restart everything works as intended. I know this is a 7260 and not 8265 / 9560. But thought it still might be useful to know. > > > Thanks in advance! Thanks, Chris