From nobody Thu Mar 31 13:34:19 2022 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 C854B1A39FEB for ; Thu, 31 Mar 2022 13:34:32 +0000 (UTC) (envelope-from jbo@insane.engineer) Received: from mail-4323.proton.ch (mail-4323.proton.ch [185.70.43.23]) (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 "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KTkml0S2Tz3Qyg for ; Thu, 31 Mar 2022 13:34:30 +0000 (UTC) (envelope-from jbo@insane.engineer) Date: Thu, 31 Mar 2022 13:34:19 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=insane.engineer; s=protonmail2; t=1648733668; bh=EooChEtiifApA8HUZn+aLdS/Vlb/GSqp8THLHs59DpY=; h=Date:To:From:Reply-To:Subject:Message-ID:In-Reply-To:References: From:To:Cc:Date:Subject:Reply-To:Feedback-ID:Message-ID; b=JasEhranNyNjaZNBBGnAhoQP/idT3MnCRhb8nOqPUZ7miNcY9xnqJ4QRedyPgoFqs 00L8yISfe+aWLFQwv2VtsTzbIPVVNP2TuQDVEPSy24beN6U5+XXcpN3/fE3fGhL4pn xg1Ov95Q7eC/XfQtzBBcdmAUhdn+1Y5ZrdHOGsjol4f0CEOnwImW4qpxJ9+Poh7DE2 0T7kUKmHR5c+L1HWSkpIHwzIW30mHDoHYvLKsA6WzmcyjBbNnU47T67qHa3QsJwPqk 8GlcUOhzYKTr9sfPmZm6N6yG0ppHQaM1ippWUUG64lMC3eMbTg0uOCC32sWnDTXJn3 hf/u8wL7riTyw== To: freebsd-wireless@freebsd.org From: jbo@insane.engineer Reply-To: jbo@insane.engineer Subject: Re: iwlwifi sporadically does not attach Message-ID: In-Reply-To: <511cc8c2-5604-0216-17ac-d64c100712df@spacesurfer.com> References: <511cc8c2-5604-0216-17ac-d64c100712df@spacesurfer.com> 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: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4KTkml0S2Tz3Qyg X-Spamd-Bar: ---- Authentication-Results: mx1.freebsd.org; dkim=pass header.d=insane.engineer header.s=protonmail2 header.b=JasEhran; dmarc=pass (policy=none) header.from=insane.engineer; spf=pass (mx1.freebsd.org: domain of jbo@insane.engineer designates 185.70.43.23 as permitted sender) smtp.mailfrom=jbo@insane.engineer X-Spamd-Result: default: False [-4.00 / 15.00]; HAS_REPLYTO(0.00)[jbo@insane.engineer]; ARC_NA(0.00)[]; R_DKIM_ALLOW(-0.20)[insane.engineer:s=protonmail2]; REPLYTO_EQ_FROM(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.43.0/24]; MIME_GOOD(-0.10)[text/plain]; TO_DN_NONE(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; RCPT_COUNT_ONE(0.00)[1]; RWL_MAILSPIKE_EXCELLENT(0.00)[185.70.43.23:from]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; DKIM_TRACE(0.00)[insane.engineer:+]; DMARC_POLICY_ALLOW(-0.50)[insane.engineer,none]; FROM_NO_DN(0.00)[]; NEURAL_HAM_SHORT(-1.00)[-1.000]; MLMMJ_DEST(0.00)[freebsd-wireless]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N Hi, A day later (the 27th of March), bz pushed a lot of stuff. You might want t= o consider updating to at least 6663718bb49635deac3f5dc55fa6f0f7cba593ba I am rolling with an Intel AX201 as well and had similar problems as you ar= e describing. After updating to that commit these symptoms seem to have (mo= stly?) vanished. Of course, you might want to consider updating just to the latest stable/13= commit rather than that specific one I mentioned. Let us know whether that helped! ~ J ------- Original Message ------- On Thursday, March 31st, 2022 at 11:33, Patrick Mackinlay wrote: > I am using a matebook pro x 2021 (AX201) with FreeBSD 13 stable > > (60338b80693000ed0f9812b90ca54d35fd077cd0 Sat Mar 26 11:04:36 2022 +0100)= . > > Sometimes the iwlwifi driver does not attach, I get the message > > device_attach: iwlwifi0 attach returned 60 > > Even if I unload the module and reload I get the same error. I have > > attached full logs. > > When the driver does attach (most of the time) then the WiFi is pretty > > stable. > > regards, > > Patrick