From nobody Wed Jan 03 11:47:43 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 4T4nys0dcQz55gr3 for ; Wed, 3 Jan 2024 11:47:49 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4T4nys08GMz45VX; Wed, 3 Jan 2024 11:47:49 +0000 (UTC) (envelope-from bz@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1704282469; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=hlvPaUw+OFRHu0xoW0F5vKYYQhc2WsRXOnmxJ9HfpmE=; b=Hy895QAzz8lO1xskcrdrQeYbouy2FSx2GJhAgPVle52k2mUkrCR9R1s5VOPkSh54GcaQY1 tbsLHa1V0ZQKydaFZdPSXi5d61SaPQ2b/g0J+nIl/ioX8JOG+lRCAExtoLyDqtBvhB6sI3 XL/y1p27M+cPODV+xFVFJr6YZu3ka/KYpxCe0v9vUl8kSsqnsWxStlsTys7vYbnYlpEx0J AZdsAYiV8JsuYNao7UQL0OIA3Qnuf2lcL8xr9d+uYPrRR0TjWjt7kaeDQ6PekydT1By56g mDBjFoj3Cljv1CG7bDwQHXmFgwehj7i1OGyrgmkyph0Kn2U70HDhJ+sM4kaVlg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1704282469; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=hlvPaUw+OFRHu0xoW0F5vKYYQhc2WsRXOnmxJ9HfpmE=; b=W+2z8TFGoN/0/GTEzfpkQDYflKMJDQeyXM3oe6HE8KRkzKLhqzBZt7aAf7Qa5ideQ57ShF Zs6rDJ4yqvDO8PNvmkiuBNqsIdetvzGA2RY9KP0I5t96NQITwGrQxMoUz/XKcMYTzJYNW0 Vd5yrnOv2pn7zEz29iCifpcvMUUjFFBpidFcAmN+gVu1MtHyKdDL3goDTMZtD+l/1ZvH0F gywryHZ9+9Kcr6RbVQUOK3bTEIxD1REIyOwkJb57JQlLoSTIK0uR5TCg0HttdftOaWDF7n if+wGCxDdHTd8W+tagWJxpmZq7n6M4GMO82BUmpmdL+wFcUhwJScbF5yXl2Unw== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1704282469; a=rsa-sha256; cv=none; b=Ksq2h/0LRPud9wxWcy9TWNDoKcYPnwnmL9HpIBCtlkyKFT8wXOvMzZYk3lltDFIye99gxh 25XKxlI0Yn4C+q2VkB+JGpcG+Uv1WYYa7eRiX4ADWqZeJYx4mhDDmcC0dfwycxB7+BvC86 YdMh9oKW/6P2mmSXl/nxdE7M5rH/c+jzQlOyGEKFLlEOgcm6m7Fe+ZblAIL95eAvWfCXs5 Q3FTReyPWlZr9733+ZUCvQskJSO3/ZPut+hOAKT6I2CJk5HNQYZwHNwlqLnQf847fEuWi4 1A+wcpvRpLazIaFz/5zsP0jFH5mM5qx4AKIuIwBzUDL1wSZDOQmmW/133QNBag== Received: from mx1.sbone.de (mx1.sbone.de [IPv6:2a01:4f8:13b:39f::9f:25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.sbone.de", Issuer "SBone.DE Root Certificate Authority" (not verified)) (Authenticated sender: bz/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4T4nyr4yM5z1094; Wed, 3 Jan 2024 11:47:48 +0000 (UTC) (envelope-from bz@FreeBSD.org) Received: from mail.sbone.de (mail.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.sbone.de (Postfix) with ESMTPS id 53ECB8D4A162; Wed, 3 Jan 2024 11:47:47 +0000 (UTC) Received: from content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPS id 7107C2D029D7; Wed, 3 Jan 2024 11:47:46 +0000 (UTC) X-Virus-Scanned: amavisd-new at sbone.de Received: from mail.sbone.de ([IPv6:fde9:577b:c1a9:4902:0:7404:2:1025]) by content-filter.t4-02.sbone.de (content-filter.t4-02.sbone.de [IPv6:fde9:577b:c1a9:4902:0:7404:2:2742]) (amavisd-new, port 10024) with ESMTP id 6VnieapleIik; Wed, 3 Jan 2024 11:47:45 +0000 (UTC) Received: from strong-aiccu0.sbone.de (strong-aiccu0.sbone.de [IPv6:fde9:577b:c1a9:f491::2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.sbone.de (Postfix) with ESMTPSA id 1AD5A2D029D2; Wed, 3 Jan 2024 11:47:45 +0000 (UTC) Date: Wed, 3 Jan 2024 11:47:43 +0000 (UTC) From: "Bjoern A. Zeeb" To: Kevin Oberman cc: FreeBSD Wireless Subject: Re: Interaction between iwlwifi and drm-515-kmod lkpi? In-Reply-To: Message-ID: <3777q187-4r2q-52s1-1675-8516pnsp5qrq@SerrOFQ.bet> References: X-OpenPGP-Key-Id: 0x14003F198FEFA3E77207EE8D2B58B8F83CCF1842 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 Content-Type: multipart/mixed; boundary="1098556516-1212014823-1704282465=:2837" This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --1098556516-1212014823-1704282465=:2837 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8BIT On Sat, 30 Dec 2023, Kevin Oberman wrote: > On Fri, Dec 22, 2023 at 9:33 PM 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 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 --1098556516-1212014823-1704282465=:2837--