Date: Sat, 6 Jan 2024 20:58:51 -0800 From: Kevin Oberman <rkoberman@gmail.com> To: "Bjoern A. Zeeb" <bz@freebsd.org> Cc: FreeBSD Wireless <freebsd-wireless@freebsd.org> Subject: Re: Interaction between iwlwifi and drm-515-kmod lkpi? Message-ID: <CAN6yY1vUV59jctfcN-nuOFWrp2XtbAkovwnSkFMYORthNN39TA@mail.gmail.com> In-Reply-To: <3777q187-4r2q-52s1-1675-8516pnsp5qrq@SerrOFQ.bet> References: <CAN6yY1uTFBe8m5ncDVg4QViT0pE38qroSQ5DcvfjwwOZeitkgw@mail.gmail.com> <CAN6yY1udT_uJsEE5kGrvo_Bu3F863Po2HYxH8OhO2j=KRDCgsw@mail.gmail.com> <3777q187-4r2q-52s1-1675-8516pnsp5qrq@SerrOFQ.bet>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Wed, Jan 3, 2024 at 3:47 AM Bjoern A. Zeeb <bz@freebsd.org> wrote: > On Sat, 30 Dec 2023, Kevin Oberman wrote: > > > On Fri, Dec 22, 2023 at 9:33 PM Kevin Oberman <rkoberman@gmail.com> > wrote: > > > >> After the ssh vulnerability was announced, I updated my kernel. After > >> completing the upgrade, it crashed when the system was booted. All stack > >> dumps showed lots of drm points on hte stack. So, I tried removing the > >> i915kms from the kld_list in rc.conf. The system booted and started the > >> wifi without crashing. When I loaded i915kms manually, the system froze. > >> > >> I still am wondering if there is some collision in the lkpi when the drm > >> driver on Alder Lake is present and the wifi starts. While I failed to > get > >> much saved during the multiple reboots, all showed the crash after > >> wpa_supplcant started. > >> > >> Is this remotely possible or just a coincidence? > >> > >> I have rolled my system back to 06c083f79dd7 (Dec. 2) just to get it > >> running with both graphics and wifi. > >> > > > > I have now booted several times with no graphics kmod loaded (i915kms). > > There have been no failures or panics while booting. One system freeze > when > > loading i915kms. No state messages at all. > > iwlwifi0: WRT: Invalid buffer destination > > iwlwifi0: WFPM_UMAC_PD_NOTIFICATION: 0x20 > > iwlwifi0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f > > iwlwifi0: WFPM_AUTH_KEY_0: 0x90 > > iwlwifi0: CNVI_SCU_SEQ_DATA_DW9: 0x0 > > iwlwifi0: RFIm is deactivated, reason = 4 > > wlan0: Ethernet address: 70:a8:d3:df:3c:de > > Created wlan(4) interfaces: wlan0. > > lo0: link state changed to UP > > Starting wpa_supplicant. > > Starting dhclient. > > wlan0: no link .... > > wlan0: link state changed to UP > > got link > > DHCPREQUEST on wlan0 to 255.255.255.255 port 67 > > DHCPACK from 192.168.1.1 > > unknown dhcp option value 0x7d > > bound to 192.168.1.5 -- renewal in 7200 seconds. > > Starting Network: lo0 em0 wlan0. > > > > I should also mention that, when I manually load i915kms, I do see many > > WITNESS reports. Do we still keep a list of known ones? > > > have you at any time tried the other way round: > > load drm-kmod on boot and and NO wireless (possibly blocklist it) and > then try to manually load wireless? > > > While an interaction in LinuxKPI would mean some resources are not > properly save per device most likely (or we get the wrong one), loading > drm-kmod as well probably also changes timing which means you could hit > the net80211/LinuxKPI co-bugs which are triggered by two specifics in > net80211 and then cause assertions in LinuxKPI code (it seems I have > much improvement in a development branch but am still on it after the > New Year to clean things up and track secondary effects of the change). > > /bz > > -- > Bjoern A. Zeeb r15:7 It's taken me a while to get there, but I have done testing. I have now booted three times with the kernel module not loaded. All three were clean, though I did see a bit more verbiage when I loaded it manually. i915kms was loaded via rc.conf. i915kms loaded and worked correctly. I then loaded if_iwlwifi and then started netif and local_unbound. No errors as far as I could tell. Everything works. Here is hte outout of loading and starting: ntel(R) Wireless WiFi based driver for FreeBSD iwlwifi0: <iwlwifi> mem 0x603d1cc000-0x603d1cffff at device 20.3 on pci0 iwlwifi0: Detected crf-id 0x400410, cnv-id 0x80400 wfpm id 0x80000020 iwlwifi0: PCI dev 51f0/0090, rev=0x370, rfid=0x2010d000 iwlwifi0: successfully loaded firmware image 'iwlwifi-so-a0-gf-a0-83.ucode' iwlwifi0: api flags index 2 larger than supported by driver iwlwifi0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.41 iwlwifi0: loaded firmware version 83.e8f84e98.0 so-a0-gf-a0-83.ucode op_mode iwlmvm iwlwifi0: Detected Intel(R) Wi-Fi 6E AX211 160MHz, REV=0x370 iwlwifi0: WRT: Invalid buffer destination Jan 6 20:16:33 ptavv wpa_supplicant[2083]: wlan0: Failed to initialize driver interface iwlwifi0: WFPM_UMAC_PD_NOTIFICATION: 0x20 iwlwifi0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f iwlwifi0: WFPM_AUTH_KEY_0: 0x90 iwlwifi0: CNVI_SCU_SEQ_DATA_DW9: 0x0 iwlwifi0: RFIm is deactivated, reason = 4 iwlwifi0: successfully loaded firmware image 'iwlwifi-so-a0-gf-a0.pnvm' iwlwifi0: loaded PNVM version 181407b3 Jan 6 20:16:33 ptavv dhclient[2104]: wlan0: not found Jan 6 20:16:33 ptavv dhclient[2104]: exiting. iwlwifi0: Detected RF GF, rfid=0x2010d000 iwlwifi0: base HW address: 70:a8:d3:df:3c:de iwlwifi0: WRT: Invalid buffer destination iwlwifi0: WFPM_UMAC_PD_NOTIFICATION: 0x20 iwlwifi0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f iwlwifi0: WFPM_AUTH_KEY_0: 0x90 iwlwifi0: CNVI_SCU_SEQ_DATA_DW9: 0x0 iwlwifi0: RFIm is deactivated, reason = 4 wlan0: Ethernet address: 70:a8:d3:df:3c:de Jan 6 20:17:03 ptavv wpa_supplicant[2187]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Invalid argument wlan0: link state changed to UP Let me know if I can look at anything else. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 [-- Attachment #2 --] <div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif;font-size:small">On Wed, Jan 3, 2024 at 3:47 AM Bjoern A. Zeeb <<a href="mailto:bz@freebsd.org">bz@freebsd.org</a>> wrote:</div></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sat, 30 Dec 2023, Kevin Oberman wrote:<br> <br> > On Fri, Dec 22, 2023 at 9:33 PM Kevin Oberman <<a href="mailto:rkoberman@gmail.com" target="_blank">rkoberman@gmail.com</a>> wrote:<br> ><br> >> After the ssh vulnerability was announced, I updated my kernel. After<br> >> completing the upgrade, it crashed when the system was booted. All stack<br> >> dumps showed lots of drm points on hte stack. So, I tried removing the<br> >> i915kms from the kld_list in rc.conf. The system booted and started the<br> >> wifi without crashing. When I loaded i915kms manually, the system froze.<br> >><br> >> I still am wondering if there is some collision in the lkpi when the drm<br> >> driver on Alder Lake is present and the wifi starts. While I failed to get<br> >> much saved during the multiple reboots, all showed the crash after<br> >> wpa_supplcant started.<br> >><br> >> Is this remotely possible or just a coincidence?<br> >><br> >> I have rolled my system back to 06c083f79dd7 (Dec. 2) just to get it<br> >> running with both graphics and wifi.<br> >><br> ><br> > I have now booted several times with no graphics kmod loaded (i915kms).<br> > There have been no failures or panics while booting. One system freeze when<br> > loading i915kms. No state messages at all.<br> > iwlwifi0: WRT: Invalid buffer destination<br> > iwlwifi0: WFPM_UMAC_PD_NOTIFICATION: 0x20<br> > iwlwifi0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f<br> > iwlwifi0: WFPM_AUTH_KEY_0: 0x90<br> > iwlwifi0: CNVI_SCU_SEQ_DATA_DW9: 0x0<br> > iwlwifi0: RFIm is deactivated, reason = 4<br> > wlan0: Ethernet address: 70:a8:d3:df:3c:de<br> > Created wlan(4) interfaces: wlan0.<br> > lo0: link state changed to UP<br> > Starting wpa_supplicant.<br> > Starting dhclient.<br> > wlan0: no link ....<br> > wlan0: link state changed to UP<br> > got link<br> > DHCPREQUEST on wlan0 to 255.255.255.255 port 67<br> > DHCPACK from 192.168.1.1<br> > unknown dhcp option value 0x7d<br> > bound to 192.168.1.5 -- renewal in 7200 seconds.<br> > Starting Network: lo0 em0 wlan0.<br> ><br> > I should also mention that, when I manually load i915kms, I do see many<br> > WITNESS reports. Do we still keep a list of known ones?<br> <br> <br> have you at any time tried the other way round:<br> <br> load drm-kmod on boot and and NO wireless (possibly blocklist it) and<br> then try to manually load wireless?<br> <br> <br> While an interaction in LinuxKPI would mean some resources are not<br> properly save per device most likely (or we get the wrong one), loading<br> drm-kmod as well probably also changes timing which means you could hit<br> the net80211/LinuxKPI co-bugs which are triggered by two specifics in<br> net80211 and then cause assertions in LinuxKPI code (it seems I have<br> much improvement in a development branch but am still on it after the<br> New Year to clean things up and track secondary effects of the change).<br> <br> /bz<br> <br> -- <br> Bjoern A. Zeeb r15:7</blockquote></div><br clear="all"><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">It's taken me a while to get there, but I have done testing. I have now booted three times with the kernel module not loaded. All three were clean, though I did see a bit more verbiage when I loaded it manually. i915kms was loaded via rc.conf. i915kms loaded and worked correctly. I then loaded if_iwlwifi and then started netif and local_unbound. No errors as far as I could tell. Everything works. Here is hte outout of loading and starting:</div>ntel(R) Wireless WiFi based driver for FreeBSD<br>iwlwifi0: <iwlwifi> mem 0x603d1cc000-0x603d1cffff at device 20.3 on pci0<br>iwlwifi0: Detected crf-id 0x400410, cnv-id 0x80400 wfpm id 0x80000020<br>iwlwifi0: PCI dev 51f0/0090, rev=0x370, rfid=0x2010d000<br>iwlwifi0: successfully loaded firmware image 'iwlwifi-so-a0-gf-a0-83.ucode'<br>iwlwifi0: api flags index 2 larger than supported by driver<br>iwlwifi0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.41<br>iwlwifi0: loaded firmware version 83.e8f84e98.0 so-a0-gf-a0-83.ucode op_mode iwlmvm<br>iwlwifi0: Detected Intel(R) Wi-Fi 6E AX211 160MHz, REV=0x370<br>iwlwifi0: WRT: Invalid buffer destination<br>Jan 6 20:16:33 ptavv wpa_supplicant[2083]: wlan0: Failed to initialize driver interface<br>iwlwifi0: WFPM_UMAC_PD_NOTIFICATION: 0x20<br>iwlwifi0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f<br>iwlwifi0: WFPM_AUTH_KEY_0: 0x90<br>iwlwifi0: CNVI_SCU_SEQ_DATA_DW9: 0x0<br>iwlwifi0: RFIm is deactivated, reason = 4<br>iwlwifi0: successfully loaded firmware image 'iwlwifi-so-a0-gf-a0.pnvm'<br>iwlwifi0: loaded PNVM version 181407b3<br>Jan 6 20:16:33 ptavv dhclient[2104]: wlan0: not found<br>Jan 6 20:16:33 ptavv dhclient[2104]: exiting.<br>iwlwifi0: Detected RF GF, rfid=0x2010d000<br>iwlwifi0: base HW address: 70:a8:d3:df:3c:de<br>iwlwifi0: WRT: Invalid buffer destination<br>iwlwifi0: WFPM_UMAC_PD_NOTIFICATION: 0x20<br>iwlwifi0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f<br>iwlwifi0: WFPM_AUTH_KEY_0: 0x90<br>iwlwifi0: CNVI_SCU_SEQ_DATA_DW9: 0x0<br>iwlwifi0: RFIm is deactivated, reason = 4<br>wlan0: Ethernet address: 70:a8:d3:df:3c:de<br>Jan 6 20:17:03 ptavv wpa_supplicant[2187]: ioctl[SIOCS80211, op=20, val=0, arg_len=7]: Invalid argument<br>wlan0: link state changed to UP<br><div><br></div><div><div style="font-family:tahoma,sans-serif;font-size:small" class="gmail_default">Let me know if I can look at anything else.<br></div></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr">Kevin Oberman, Part time kid herder and retired Network Engineer<br>E-mail: <a href="mailto:rkoberman@gmail.com" target="_blank">rkoberman@gmail.com</a><br></div><div>PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683</div></div></div></div></div></div></div></div></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1vUV59jctfcN-nuOFWrp2XtbAkovwnSkFMYORthNN39TA>