From nobody Tue Jan 11 20:30:02 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 63A7D194EF99 for ; Tue, 11 Jan 2022 20:30:14 +0000 (UTC) (envelope-from kevans@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 4JYMkt1Ddrz4q8b; Tue, 11 Jan 2022 20:30:14 +0000 (UTC) (envelope-from kevans@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1641933014; 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=/nUeCrpnpetTMxhlJSITtJ/UqKf5R1Aq90JHLvRR8Mk=; b=K+hqv2dEQi4vRPQr7jv05nlyqv1Fe3O2cNDMxkWbEIUGozcjfNU3ASysPZSrTOzQSOORsM sPpHYVqfocggKzLgr9MFLIIBI/06replazUOMcuiQqre2TISr6R81f+syeWQNmuca907vT TA4S44en+WQMqwT9vqX5430XefzofIQ9k04F+2Nyl2KKU+kxmAqB+tytgOjeh5UluaS7Cf nnEtbPrPhkmcDYMfHhdYPyahPgKZ6c4jb3ZmlvL8RarKlqk+fgCWaa9boiTbKtB/iV+CAU LORgssg/HREReRbYmGewjNm+QfYSB2DvZYg4kOM3yUSZ6r6T3an7GC7bcNlSSQ== Received: from mail-qv1-f45.google.com (mail-qv1-f45.google.com [209.85.219.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) (Authenticated sender: kevans) by smtp.freebsd.org (Postfix) with ESMTPSA id B03258554; Tue, 11 Jan 2022 20:30:13 +0000 (UTC) (envelope-from kevans@freebsd.org) Received: by mail-qv1-f45.google.com with SMTP id q4so547660qvh.9; Tue, 11 Jan 2022 12:30:13 -0800 (PST) X-Gm-Message-State: AOAM531r8cuvbnfLuPDmzK1s/jPeaiLO8roizshWJTd2Pk+AL6rvKLUR i5itu2s0lEWMZW+j8Y5ZiTVMq0LGkUxXEBJnBdo= X-Google-Smtp-Source: ABdhPJy0iTk/qtcNQZzUq5cxXuWYcVvpzyB1Mu7vaNnoPuShHRMGjObYJ3VxqX0EYUVo3DAI2PBIOKgQ2/Sz72FBce0= X-Received: by 2002:a05:6214:2386:: with SMTP id fw6mr5686143qvb.79.1641933013243; Tue, 11 Jan 2022 12:30:13 -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: Kyle Evans Date: Tue, 11 Jan 2022 14:30:02 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: iwlwifi auth->scan error/panic To: "Bjoern A. Zeeb" Cc: wireless@freebsd.org Content-Type: text/plain; charset="UTF-8" ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1641933014; 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=/nUeCrpnpetTMxhlJSITtJ/UqKf5R1Aq90JHLvRR8Mk=; b=xuuZ6DhoJ/6DdfpiSmzj2PAYa2A3wmISPLzXAAHWtUn3C+jyi+zTgFQHllZn9UNyFc/Dfg x1l0Ai1KLHEoQ+5vuPtUX1znQ7nxr3x/QKAnDKifzIinmQrgB1svUURz4Qd22ghqgoQhyC YyKDqQXYoIauNxCCVr4wlgIR2IQGoDqcnE4PVH+/cgoBfa15Etn8DyxZkQViOJbjFW8V+m hdAfje5JjCquxtVHHq7kDrt8tRE4SohArvz/ogyv+79lvgJmU/p8dtmlT71DvJNPCZikyB YGnIcsxy+0OZHwHLMstBepejgI6o7JyUiBRshjBoS1cMO3vosfbIbvCR/wuX8Q== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1641933014; a=rsa-sha256; cv=none; b=Zsl+jVJcs0TEzXnjrPl9a5qw6HhEUBboRUda4KybVzLMWLy3KRiZjDsVcKJSxCLpWd3ZZO GshHsZDLRE6fxVp06ZbnZYarFjbKwVNOPHDCGL2kqRKi3iISADScd/xJ1nYqKNccOUEVMb +yNIAfMoJ3D8NJLZo95QOY/hYgRDFs9FWl/vpj1agvAGlqFx+5TKP6TQvud4brG7ubKBD1 +6ZvtDpiH3tJH1iLBaAgCUdzWuj6GKgnetm058oNFr0aZve/dNAuj3gsMXDDJ6YdKyV46j J5fZwn4kVb9BP82gZPpjEdsBsN7zEmVHpKxSMLXdD6V1PrpWMcQnTvR8oxbDfA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On Fri, Dec 31, 2021 at 6:03 PM Bjoern A. Zeeb wrote: > > Hi, > > I got two reports in the last three days from people who have traces > showing the driver attaching, scanning and starting to authenticate/associate > and (in one case) apparently having succeeded but then bounce back to > scanning. > > The two cases are different but essentially mean net80211 or > iwlwifi/firmware didn't see some frames it expected (or there is also > a possibility of a logic bug between mac80211/iwlwifi still; I had > cherry-picked some fixes for that already). > > Long story short: in the follow-up of the auth_to_scan change people > are seeing firmware crashes or in a follow-up even a panic. > > I'll be looking into those the first days in the New Year. > If you have such a case please make sure to turn on wlandebug with > "+auth +scan +state +node" at least (see wiki for how to do this in > rc.conf [1]) and drop me a private email with the log. > I'm seeing something that goes a little like (transcribed from a picture, swap partition too small): wlan0: no link ... WARNING mva_sta->dup_data == ((void *0)) failed at /usr/src/sys/contrib/dev/iwlwifi/mvm/rxmq.c:509 wlan0: ieee80211_new_state_locked: pending ASSOC -> RUN transition lost wlan0: link state changed to UP wlan0: link state changed to DOWN WARNING mva_sta->dup_data == ((void *0)) failed at /usr/src/sys/contrib/dev/iwlwifi/mvm/rxmq.c:509 (repeated at least a dozen times) panic: lkpi_sta_assoc_to_auth: lsta ... state not AUTH: 0 ... Related? This is with main at bec766282f242aab3a4bfba402ea74cb0ccf96fb ("LinuxKPi: 802.11 fix locking ..."). I'm seeing this on maybe 70-80% of boots now, while the last snapshot before it entered the tree was relatively-ish stable. Thanks, Kyle Evans