From nobody Wed Apr 27 18:24:58 2022 X-Original-To: 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 67C4A1AB48BD for ; Wed, 27 Apr 2022 18:24:59 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (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 "mxrelay.nyi.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KpRxQ6pkfz4pgR for ; Wed, 27 Apr 2022 18:24:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (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 did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id C400BF98 for ; Wed, 27 Apr 2022 18:24:58 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 23RIOw2E027542 for ; Wed, 27 Apr 2022 18:24:58 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 23RIOwgc027541 for wireless@FreeBSD.org; Wed, 27 Apr 2022 18:24:58 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: wireless@FreeBSD.org Subject: [Bug 263613] iwlwifi0 on framework laptop crashes when setting IP Date: Wed, 27 Apr 2022 18:24:58 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: wireless X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: jon@xyinn.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: wireless@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated 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 ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1651083899; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding; bh=ckTOqCE6D7QY6W3VR0u7MIHBULh0ti2PUzQl+DO6qhI=; b=NRiPjB/gmo7pGkW0CCAsTo5JpYcTXxTOUN7EzzpjqyugTj2TVtrmItoQcPMYcRdzULcqxQ kluQ48LZgJr/OP4ECY9EWaWAQeigzza5wZE7r4gbaKle6gkDmVNv+IO0RJIpAcfGcUZPyT C6/2K8COJBuWoSRFSdj6zYtIlh0bYh4EVzWDzIrRW9XPgz7CVrltRTG9rI5GZhzxVnH8eo l0k7wx7a2pxfkAPEAB4a0pRz+pdjp+cnQXVPjZUllZTeo8CY8/I3QVJQTnRYY2CHlRVVqo blT7gW9JtHfRZji7rn8QDbubUxQ5EjiFuOLY8P65BTCvKGwBsd848cxaPHJwng== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1651083899; a=rsa-sha256; cv=none; b=imrIorRxwJ9WA3NnLn54av5FVorDIk8sjgoh2hLdUvdvtll2MJ6jbPr6PnLfN7EMwwA58t jgkIMgAdvnTPkSm3cCylTAXMQHDCaW97cCH5bHfRZJ4iZWlFlwXPUXLsgz29XwpgeKH/bt Ep5cshJbW/ghpTrvWE7ZRA1tn0o2rZcZdwCRBLrTVrQg4Ps5U8eM0HPulZAI/zuM/yTgdg zQmKyGNHXwh+6knXZdHQJ9bqalV+bzmZPGECbiufS3w8hY2gN9cNtvb5NURu+N+QFukqup kyNVXr8uz/nCGKrnvb9f2iCFD4U0pLq4AUNPgbwcRYNsypLUkA3ubGrCZ1f94w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D263613 Bug ID: 263613 Summary: iwlwifi0 on framework laptop crashes when setting IP Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: wireless Assignee: wireless@FreeBSD.org Reporter: jon@xyinn.org Created attachment 233540 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D233540&action= =3Dedit dmesg Hey all, I've spent a few days reading _a lot_ of documentation and experimenting wi= th getting FreeBSD running on my Framework Laptop on 13.0-RELEASE, 13.1-RC4, a= nd 14-CURRENT (just to see how far all of the branches are working on it - although originally I wanted to just run 13.1 since that's the next RELEASE= but I was getting too many issues and crashes with it.. and I've been avoiding jumping into STABLE/CURRENT, but c'est la vie haha). I've definitely notice= d a bunch of issues that either already got fixed, or still remain (but I've yet gathered exact repro scenarios). However, for this particular issue (and I'm not sure if it's 100% related but I think it might be), the Intel AX210 car= d on the framework laptop seems to associate with my AP properly, but no DHCPOFF= ERS are received. I think there was only one time a few days ago on an older bu= ild of CURRENT that I was able to get it to get an IP, but I haven't been able = to replicate that working state. Also, this is on the sources for 14-CURRENT (for both world and kernel) as = of today 2022-04-27. I'm motivated to help any of the devs test any code neede= d to get, not only this issue, but really anything regarding the framework lapto= p as an actual desktop productivity machine. I'm not a FreeBSD pro, but have been using it on my home server for the past 2~ years. So apologies if there any particular concepts or things I don't yet know, feel free to point me in the right direction though :). I've attached various parts of my system config and dmesg output to help de= bug this. I've noticed that I sometimes get the following errors as well (I've also looked at what the Linux community said about those errors and it seems they were fixed in 5.13): iwlwifi0: iwl_trans_send_cmd bad_state =3D 0 iwlwifi0: Failed to remove MAC context: -5 repro commands: Given the above situation where the system started up the wlan0 interfaced (parent: iwlwifi0) and was associated to the AP but did not receive any DHCP offers: 1. ifconfig wlan0 down 2. ifconfig wlan0 192.168.1.105/24 netmask 255.255.255.0 > The command will trigger, and a few seconds later it will hard crash. I'v= e attached a camera shot of this. But something relevant may be the followi= ng: iwlwifi0: Failed to send binding (action:1): -5 iwlwifi0: PHY ctxt cmd error. ret=3D-5 iwlwifi0: lkpi_iv_newstate: error -5 during state transition 1 (SCAN) -> 2 (AUTH) iwlwifi0: No queue was found. Dropping TX iwlwifi0: Failed to trigger RX queues sync (-5) ... panic: lkpi_sta_auth_to_scan: lsta 0xfffff8012f0c5800 state not NONE: 0, ns= tate 1 arg 1 --- Overall, this laptop seems to have slowly gotten better support so that's definitely encouraging and I also read the recent news about FreeBSD and the work going on to improve Framework Laptop support. The wifi issues caused h= ard reboots on 13.1-RC4 current (It would just shut off, I believe the "firmware dying in a fire" that Kyle Evans mentioned here: https://lists.freebsd.org/archives/freebsd-wireless/2021-October/000099.html might have been what he meant by that). This may or may not be the same bug that I'm experiencing here, but maybe since I'm running -CURRENT now with t= he default debug configuration, "hard crash reboots" turn into "hard crash - do not reboot" situations?=20 Anyways, let me know if anything and I can further help debug. --=20 You are receiving this mail because: You are the assignee for the bug.=