From nobody Sat Dec 30 18:25:46 2023 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 4T2W0H1SFGz55lt7 for ; Sat, 30 Dec 2023 18:26:07 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-yw1-x112e.google.com (mail-yw1-x112e.google.com [IPv6:2607:f8b0:4864:20::112e]) (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 4T2W0G2N1bz4NBp for ; Sat, 30 Dec 2023 18:26:06 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=FiXjiDw0; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::112e as permitted sender) smtp.mailfrom=kob6558@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-yw1-x112e.google.com with SMTP id 00721157ae682-5e86fc3f1e2so52242237b3.0 for ; Sat, 30 Dec 2023 10:26:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1703960763; x=1704565563; darn=freebsd.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=XEp4+/2hmZaku30NEQqBX8FgVVKcIMwnkkkXogjIy9w=; b=FiXjiDw0lfk+pGQVk3vhgucJPamaW1lUR+XXSc5Kf8vIkZV08wJ5XlQU3/17jB2Ubz Fuls5phzpQqzr/SOb5WCrD/VrdHBmAZ0KRi9ZqeARvsj3IzvIfp6aMHDdJgfKmd3V668 Bce/vjd8kKrO+kDzt8INPN9Lw/x15GadMgabUfPIvLDzSjN+GzoJH3DVVs3Jonwjkw0x /3g6JuPL3cGTfz0xftvw7MWX1cttM0fWAs8DYOZq6b+lIAFHBT/3PVe10+cSX3aNwMPX oUWs2AXBjcCgNWtzSCu/pHmJji1LJ0eILva2OBwqUL5U6MNLBQKkYGBXilKsYhKEg+X3 z/EA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703960763; x=1704565563; h=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=XEp4+/2hmZaku30NEQqBX8FgVVKcIMwnkkkXogjIy9w=; b=ngMptRgiHR1L8j5VwYaKCy48yfRXXoynvZIJgKMY9HJN3kmVZNujjvhvBpf/80yLZT /WscMGCgSv4beW4nSQ6WePgoLFcCl4aHcetfnPqTu3CmpmwGV1MQNVeYRRKc4FlRN5Xh oQWUtrXYINdAl64dwDKLuzuMmM39QwckpxlVF3AN4uw8Faf0c0mPny2BMA8Vv6y+6f1x ANouQYk5TyFJ+0sp826CYzZKkjjCLW56qMh0GbCQI0ewa4Ah8LwyOaErq9ucWr1+W7Ms 9QpALdH0Ee2+JTw4Gr7taAjb+MRw6ROyA3XHN6pp3dTA0tRO2O1xis2sGwD9Uu3OC49f kdpg== X-Gm-Message-State: AOJu0YyZr/CCi+SthWCHMsvMNwS8iF+ni88zafQwK41WH48y117YKQgQ qkT0iyoKWStg+NTUr6GjJPwR0rBuTXsnZd/RTa+GsGE4 X-Google-Smtp-Source: AGHT+IFKN2vO+/n09Qj/pIfEn65vspJqMIxG0jNd+UAeRgcXMsK4fWxxpwKVMkKIQ+1kAD9dPt/7XJFu+mVrbxM99tg= X-Received: by 2002:a81:4a45:0:b0:5e7:5545:2f5e with SMTP id x66-20020a814a45000000b005e755452f5emr8167843ywa.37.1703960762979; Sat, 30 Dec 2023 10:26:02 -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: In-Reply-To: From: Kevin Oberman Date: Sat, 30 Dec 2023 10:25:46 -0800 Message-ID: Subject: Re: Interaction between iwlwifi and drm-515-kmod lkpi? To: FreeBSD Wireless Content-Type: multipart/alternative; boundary="000000000000fd1873060dbe472d" X-Spamd-Result: default: False [-2.70 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_SHORT(-1.00)[-0.997]; DMARC_POLICY_ALLOW(-0.50)[gmail.com,none]; FORGED_SENDER(0.30)[rkoberman@gmail.com,kob6558@gmail.com]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; R_SPF_ALLOW(-0.20)[+ip6:2607:f8b0:4000::/36]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; TO_MATCH_ENVRCPT_ALL(0.00)[]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-wireless@freebsd.org]; RCVD_TLS_LAST(0.00)[]; ARC_NA(0.00)[]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::112e:from]; DKIM_TRACE(0.00)[gmail.com:+]; TO_DN_ALL(0.00)[]; MID_RHS_MATCH_FROMTLD(0.00)[]; DWL_DNSWL_NONE(0.00)[gmail.com:dkim]; RCVD_COUNT_ONE(0.00)[1]; FREEMAIL_ENVFROM(0.00)[gmail.com]; MIME_TRACE(0.00)[0:+,1:+,2:~]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-wireless@freebsd.org] X-Rspamd-Queue-Id: 4T2W0G2N1bz4NBp X-Spamd-Bar: -- --000000000000fd1873060dbe472d Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, Dec 22, 2023 at 9:33=E2=80=AFPM Kevin Oberman = 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 ge= t > 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 many WITNESS reports. Do we still keep a list of known ones? --=20 Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --000000000000fd1873060dbe472d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Fri, Dec 22, 2023 at 9:33=E2= =80=AFPM Kevin Oberman <rkoberman@gmail.com> wrote:
<= div style=3D"font-family:tahoma,sans-serif;font-size:small">After the ssh v= ulnerability was announced, I updated my kernel. After completing the upgra= de, it crashed when the system was booted. All stack dumps showed lots of d= rm 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 collis= ion in the lkpi when the drm driver on Alder Lake is present and the wifi s= tarts. While I failed to get much saved during the multiple reboots, all sh= owed the crash after wpa_supplcant started.=C2=A0

Is this remotely possible or just a co= incidence?

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 (i915km= s). There have been no failures or panics while booting. One system freeze = when loading i915kms. No state messages at all.
iwlwifi0: WR= T: Invalid buffer destination
iwlwifi0: WFPM_UMAC_PD_NOTIFICATION: 0x20<= br>iwlwifi0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
iwlwifi0: WFPM_AUTH_KEY_0:= 0x90
iwlwifi0: CNVI_SCU_SEQ_DATA_DW9: 0x0
iwlwifi0: RFIm is deactiva= ted, 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 st= ate changed to UP
=C2=A0got link
DHCPREQUEST on wlan0 to 255.255.255.= 255 port 67
DHCPACK from 192.168.1.1
unknown dhcp option value 0x7dbound 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 ke= ep a list of known ones?
--
Kevin = Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com=
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
--000000000000fd1873060dbe472d--