From nobody Sat Dec 23 05:33:10 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 4SxtB13KNgz551RZ for ; Sat, 23 Dec 2023 05:33:29 +0000 (UTC) (envelope-from kob6558@gmail.com) Received: from mail-oi1-x232.google.com (mail-oi1-x232.google.com [IPv6:2607:f8b0:4864:20::232]) (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 4SxtB01pLwz3YSS for ; Sat, 23 Dec 2023 05:33:28 +0000 (UTC) (envelope-from kob6558@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=pass header.d=gmail.com header.s=20230601 header.b=h5h201px; spf=pass (mx1.freebsd.org: domain of kob6558@gmail.com designates 2607:f8b0:4864:20::232 as permitted sender) smtp.mailfrom=kob6558@gmail.com; dmarc=pass (policy=none) header.from=gmail.com Received: by mail-oi1-x232.google.com with SMTP id 5614622812f47-3bb85a20268so1240534b6e.0 for ; Fri, 22 Dec 2023 21:33:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1703309607; x=1703914407; darn=freebsd.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=npZb3/5NC4r8Y9c6wJlH8yTDPPb0jZ/VJhLmtLrje0k=; b=h5h201pxf9EEQbuLugmwRpVQtSP2xXikL155iO5sn3COb/iJ3knzBUzpHd7ky+PRp2 ON1U7anhUT4B7NBk0e7HiTP78WhvZXvCni67EJQmlakrG91AHmbPMQdic70pLaqRt0Qa S85lfqMZ14nJR9c89kTcrJbllrb1LfYIUDvJzRBZ27y40/tV7S9Q+Z9aJIKb8wmbdK9B eT9T9vKiqflptM/bSZkTpPW9tJatQmeIP35WqwN+Ztzr03NTqSWurCk2taI0oZvmOsCY xyPqPOehW/SaBabyxwa+9Ao3cd8y7AA3v5RO2Dfh6AUzKHLNl10KK2WPpEVQE2+go0gf NGXw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1703309607; x=1703914407; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=npZb3/5NC4r8Y9c6wJlH8yTDPPb0jZ/VJhLmtLrje0k=; b=Iw6AO2cQAQKFNAmMlQ1LvLMJ24SDQM1GXy32AsnKlSsdKTyNL8Uw3lp3m3TL9yIxI3 MNZddjUR13GppQ78hQqoCF686mYb0CeXvd8HURW9P3MLmf1s7DgsYvCyXPqUySzKSv0V QrDr7O+Y3k1jhmZ7oObdGAEIuPiKwZUOnrGZoiskk30p/dPZRMrawhq1Q7V38rPeaXFK ikCd1+5SqnnRXrg+BUwIVg6xiR3QX1j28PnP9bZLlS0Kfg8LTZSVNjzqW6HWiyYdUUq2 tNHspGnNBMFjZAfc839oaXBZbCCAHqyFJhSTQpEiPvnGxrf6u/PhDAoZiZWcOU1tMbkj g84w== X-Gm-Message-State: AOJu0YwW3YdluZ6IDQsz08jcFnUpGIc+5hUu052pySWUGf0QO1febBAb IG2+dG5Yjr6drZMBkPIkELqyuzhEh/uguIWcmRIZuTX2rz4= X-Google-Smtp-Source: AGHT+IEYrWVvQtPfLitchAJuiFN4ko9Dm+tPc4vRmXzXOs8WYJvn5BAuCdT2EW/mkV4zkaLQ3YBf1jP1MwDTmuGJ3F0= X-Received: by 2002:a05:6359:669a:b0:172:e402:4243 with SMTP id so26-20020a056359669a00b00172e4024243mr1841078rwb.59.1703309606557; Fri, 22 Dec 2023 21:33:26 -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 From: Kevin Oberman Date: Fri, 22 Dec 2023 21:33:10 -0800 Message-ID: Subject: Interaction between iwlwifi and drm-515-kmod lkpi? To: FreeBSD Wireless Content-Type: multipart/alternative; boundary="0000000000000a9d8d060d26ac05" X-Spamd-Result: default: False [-2.69 / 15.00]; SUBJECT_ENDS_QUESTION(1.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_LONG(-1.00)[-0.996]; NEURAL_HAM_SHORT(-1.00)[-0.995]; 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]; R_DKIM_ALLOW(-0.20)[gmail.com:s=20230601]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; FROM_HAS_DN(0.00)[]; FREEMAIL_FROM(0.00)[gmail.com]; ARC_NA(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; PREVIOUSLY_DELIVERED(0.00)[freebsd-wireless@freebsd.org]; FROM_NEQ_ENVFROM(0.00)[rkoberman@gmail.com,kob6558@gmail.com]; FREEMAIL_ENVFROM(0.00)[gmail.com]; RCVD_IN_DNSWL_NONE(0.00)[2607:f8b0:4864:20::232: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]; MIME_TRACE(0.00)[0:+,1:+,2:~]; RCVD_TLS_LAST(0.00)[]; ASN(0.00)[asn:15169, ipnet:2607:f8b0::/32, country:US]; MLMMJ_DEST(0.00)[freebsd-wireless@freebsd.org] X-Rspamd-Queue-Id: 4SxtB01pLwz3YSS X-Spamd-Bar: -- --0000000000000a9d8d060d26ac05 Content-Type: text/plain; charset="UTF-8" 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. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 --0000000000000a9d8d060d26ac05 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
After the ssh vulnerability was announced, I upd= ated my kernel. After completing the upgrade, it crashed when the system wa= s booted. All stack dumps showed lots of drm points on hte stack. So, I tri= ed 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 sys= tem 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.=C2=A0

Is this remotely possible or just a coincidence?

I have rolled my system back to 06c083f79= dd7 (Dec. 2) just to get it running with both graphics and wifi.
<= span class=3D"gmail_signature_prefix">--
Kevin Oberm= an, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
<= /div>
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
--0000000000000a9d8d060d26ac05--