From nobody Mon Jan 15 15:44:03 2024 X-Original-To: freebsd-wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4TDGfF3J6qz57CSq for ; Mon, 15 Jan 2024 15:44:21 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yw1-x1135.google.com (mail-yw1-x1135.google.com [IPv6:2607:f8b0:4864:20::1135]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4TDGfD6nXZz4wLs; Mon, 15 Jan 2024 15:44:20 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b="jC7y/cKH"; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::1135 as permitted sender) smtp.mailfrom=kob6558@gmail.com Received: by mail-yw1-x1135.google.com with SMTP id 00721157ae682-5f2d4aaa2fdso89371017b3.1; Mon, 15 Jan 2024 07:44:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1705333460; x=1705938260; darn=freebsd.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=mv+jBMjUhBdUxTWi7RYHevUppD6KJbZTzITHFM6qWkc=; b=jC7y/cKHFKpYIdMebutLLPlk0I/iHq43H3fVgHb6QliaHO8dYNVsMXVI9XJmRW9T+K vLXb0hsQNoD8/1Ma2yhcIImXByJIsTpFNcFxYI5JRXf2SMVbcAbmjel6n3AdNk6VxH/H e9qZvRrscymJE2rHil37crxjfNndBwQKN4Qe+R0oADfM2ehm8jdMxYCXA2a16ZCXvuG3 8CuW2+rmdts7X/eA1iwCfwndMPICYQR6LPUMJWEicQZ/gcOBv2wmbdSr4S3I1dFlRLZo Rm5uaCEuqxVKZbBM6Dlax7cDZKq4Tpnc7ZIfXR8n23zJmrsRzG1x9QGHSI48ONkvnFHV 3UKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1705333460; x=1705938260; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=mv+jBMjUhBdUxTWi7RYHevUppD6KJbZTzITHFM6qWkc=; b=DelEqBVYJkTvav+9to+JbiTuGaTUrm/WD6m9HejkjeSlNguDuViTPbJRiyGhRYnvA/ VwxwM6llvtA4m6gMT3nuNtFazDCn992E4ueF0gy5bOn5k2CcrZ1HAF03rYYjUncRFCkx yAuGkFu/XUs0FeitJw94sS3ktZjJsVjcgKPEforrei3yA1JzSZ2nHxBpyJo4Hp8WXZvS 7bPu620y2JsR0hJ6ey3xdKsCvXOR2rOuesriWqq/a/7FtPUFLJ2i/EnkC2YBINMstjW8 2qAN1qAgesLJ/EsW4BNYIh09k+ZqBLc9r5OXXk+5XL6DKJpkBydp51sooRD0mpl6Lbtv /FJA== X-Gm-Message-State: AOJu0YyZeJgZLwkQDonHuBcB+/n3rBqjND3lhtMpLzSozYHcvLH7FDq6 tj2oBKhz/3+789U6dbF5riqpjqovk4GU3Vj3PzQIfIpM X-Google-Smtp-Source: AGHT+IF4EVsHUVfGRdCe+T/mjydB+BpEzM3jOaK79IY1bouahJl9MUx6g9tK2mR/NXLY6cBxLMKYexisO4FyRVN8rUk= X-Received: by 2002:a0d:e602:0:b0:5f6:a0b6:1e11 with SMTP id p2-20020a0de602000000b005f6a0b61e11mr4406961ywe.48.1705333459686; Mon, 15 Jan 2024 07:44:19 -0800 (PST) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org MIME-Version: 1.0 References: <3777q187-4r2q-52s1-1675-8516pnsp5qrq@SerrOFQ.bet> In-Reply-To: From: Kevin Oberman Date: Mon, 15 Jan 2024 07:44:03 -0800 Message-ID: Subject: Re: Interaction between iwlwifi and drm-515-kmod lkpi? To: "Bjoern A. Zeeb" Cc: FreeBSD Wireless Content-Type: multipart/alternative; boundary="000000000000169ae0060efde329" X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.69 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.99)[-0.991]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36:c]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; RCPT_COUNT_TWO(0.00)[2]; ARC_NA(0.00)[]; FROM_HAS_DN(0.00)[]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; FREEMAIL_FROM(0.00)[gmail.com]; TO_DN_ALL(0.00)[]; DKIM_TRACE(0.00)[gmail.com:+]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::1135:from]; MLMMJ_DEST(0.00)[freebsd-wireless@freebsd.org]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; TO_MATCH_ENVRCPT_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; RCVD_COUNT_ONE(0.00)[1]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MISSING_XM_UA(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim] X-Rspamd-Queue-Id: 4TDGfD6nXZz4wLs --000000000000169ae0060efde329 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable After several reboots after updating to drm-61-kmod and the latest lkpi to support it, I am no longer seeing any problems or panics with iwlwifi. I am loading i915kms.ko from kld_list in rc.conf as recommended, which has triggered panics in hte past, but no more problems. (As a bonus, I now have working graphics acceleration.) Note that drm-61-kmod requires a recent 15-CURRENT. My 2023-12-22 kernel was too old. On Sat, Jan 13, 2024 at 6:34=E2=80=AFPM Kevin Oberman = wrote: > Just updated to drm-61-kmod and switched back to loading it from kld_list > in rc.conf. At least for one boot, it did not have any issues. Also fixed > the firmware loading issue on the drm side. > > On Sat, Jan 6, 2024 at 8:58=E2=80=AFPM Kevin Oberman wrote: > >> On Wed, Jan 3, 2024 at 3:47=E2=80=AFAM Bjoern A. Zeeb w= rote: >> >>> On Sat, 30 Dec 2023, Kevin Oberman wrote: >>> >>> > On Fri, Dec 22, 2023 at 9:33=E2=80=AFPM Kevin Oberman >>> wrote: >>> > >>> >> After the ssh vulnerability was announced, I updated my kernel. Afte= r >>> >> 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 t= he >>> >> 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 freez= e >>> 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 =3D 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 ma= ny >>> > 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 cle= an, >> 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: 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=3D0x370, rfid=3D0x2010d000 >> 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=3D0x370 >> 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 =3D 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=3D0x2010d000 >> 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 =3D 4 >> wlan0: Ethernet address: 70:a8:d3:df:3c:de >> Jan 6 20:17:03 ptavv wpa_supplicant[2187]: ioctl[SIOCS80211, op=3D20, >> val=3D0, arg_len=3D7]: 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 >> > > > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 > --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000169ae0060efde329 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
After several reboots after updating to drm-61-k= mod and the latest lkpi to support it, I am no longer seeing any problems o= r panics with iwlwifi. I am loading i915kms.ko from kld_list in rc.conf as = recommended, which has triggered panics in hte past, but no more problems. = (As=C2=A0 a bonus, I now have working graphics acceleration.)

Note that drm-61-kmod requires a recent 15-CURRENT. M= y 2023-12-22 kernel was too old.

On Sat, Jan 13, 2024 at 6:34=E2= =80=AFPM Kevin Oberman <rkoberman= @gmail.com> wrote:
Just updated to drm-61-kmod and switc= hed back to loading it from kld_list in rc.conf. At least for one boot, it = did not have any issues. Also fixed the firmware loading issue on the drm s= ide.

On Sat, Jan 6, 2024 at 8:58=E2=80=AFPM Kevin Oberman <rkoberman@gmail.com<= /a>> wrote:
<= div dir=3D"ltr">
On Wed, Jan 3, 2024 at 3:47=E2= =80=AFAM Bjoern A. Zeeb <bz@freebsd.org> wrote:
On Sat, 30 Dec 2023, Kevin = Oberman wrote:

> On Fri, Dec 22, 2023 at 9:33=E2=80=AFPM Kevin Oberman <rkoberman@gmail.com> wr= ote:
>
>> After the ssh vulnerability was announced, I updated my kernel. Af= ter
>> 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 starte= d 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 t= he drm
>> driver on Alder Lake is present and the wifi starts. While I faile= d 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 =3D 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 man= y
> 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=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0r15: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 w= orked 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 ou= tout of loading and starting:
ntel(R) Wireless WiFi based driver for F= reeBSD
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=3D0x370, rfid=3D0x2010d000<= br>iwlwifi0: successfully loaded firmware image 'iwlwifi-so-a0-gf-a0-83= .ucode'
iwlwifi0: api flags index 2 larger than supported by driver<= br>iwlwifi0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.41
iwlwifi0: loade= d firmware version 83.e8f84e98.0 so-a0-gf-a0-83.ucode op_mode iwlmvm
iwl= wifi0: Detected Intel(R) Wi-Fi 6E AX211 160MHz, REV=3D0x370
iwlwifi0: WR= T: Invalid buffer destination
Jan =C2=A06 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
iwlw= ifi0: WFPM_AUTH_KEY_0: 0x90
iwlwifi0: CNVI_SCU_SEQ_DATA_DW9: 0x0
iwlw= ifi0: RFIm is deactivated, reason =3D 4
iwlwifi0: successfully loaded fi= rmware image 'iwlwifi-so-a0-gf-a0.pnvm'
iwlwifi0: loaded PNVM ve= rsion 181407b3
Jan =C2=A06 20:16:33 ptavv dhclient[2104]: wlan0: not fou= nd
Jan =C2=A06 20:16:33 ptavv dhclient[2104]: exiting.
iwlwifi0: Dete= cted RF GF, rfid=3D0x2010d000
iwlwifi0: base HW address: 70:a8:d3:df:3c:= de
iwlwifi0: WRT: Invalid buffer destination
iwlwifi0: WFPM_UMAC_PD_N= OTIFICATION: 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 =3D 4
wlan0: Ethernet address: 70:a8:d3:df= :3c:de
Jan =C2=A06 20:17:03 ptavv wpa_supplicant[2187]: ioctl[SIOCS80211= , op=3D20, val=3D0, arg_len=3D7]: Invalid argument
wlan0: link state cha= nged to UP

Let me know if I can look at an= ything else.
--
Kevin Oberman, Par= t time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


--
Kevin= Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com


--
--000000000000169ae0060efde329--