Received: by 2002:a05:6a10:1a4d:0:0:0:0 with SMTP id nk13csp410703pxb; Tue, 1 Feb 2022 02:37:06 -0800 (PST) X-Google-Smtp-Source: ABdhPJwau6RbyXLWsyu9pF0MKIeetfhPzsudgqdwD5KcChGqYVJjYOFtFm4szd4oTLvdnEF7apBI X-Received: by 2002:a63:474c:: with SMTP id w12mr3043362pgk.147.1643711826154; Tue, 01 Feb 2022 02:37:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1643711826; cv=none; d=google.com; s=arc-20160816; b=wjK6bL/RxSEr8wYanh+poABbo242W2C1Y4Uj3X82F/lPKhsuyj5f8JxzUXITk94D8d uiRJa9Y8BuRQ+tUckyFdbKbY4a9bqPJ20/f4oa25nxBV3EeiK5clxflRd3QHrUby4qQA H/onaAOmJ3maweHq5XJ0/71NH1a0CVaOre0NzfQxwRsZG0AqVbydTgUpbI6bArTYhtMg /7U6qUs3Nx5kLbYhtR/14/3i4aHstqtYDcI+qrVRK8/SHIvSWmbVsxvEXOFi+q/G/uwh /arjstEx2Bjl1gDr0x9c1iIJYwoHPjo3qV3IRwurs1Ob+QhjQU+uWO/NldteA1JbFGCU C0rQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature :dkim-signature; bh=CqNgAQVZzOtSZopuwwTwr1nRliYIINiQLlJfuP6jJh4=; b=pAoJwaLGeJ2sZmYRYv6uZ3FDnmw/01qKm27xuRxOLC1mFTB4bm2zpezcf2ZlWSonLf 6sX7KCGrjdpz+0FqalBHNLg01QiTuu3gA9hlomWjY1l+VRMuD5LTb4mAq337Fy700Wds lEjp5PtASIU8qHM2+xB5x7MpQBj/ClLyGNVZIWNJ77BBEk2EWg2s8BQqN/XZJU3DmnBa +IOGg9yaY/M48VLjcuYfWweoxvNiG1oWOq5qKvQpJ2Ie4eZH5rgcLEqlvB1YhQJsp53a SjEoKKfch4M+vPYe2SK/jyAJyFQ3hFEZ6DbDjXYb0YGUmWDa19bh0t0zPejsx6JPIrnV jVYQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kroah.com header.s=fm3 header.b=n3Tu2W7t; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=MVKeUz4a; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id ga19si1842576pjb.141.2022.02.01.02.36.57; Tue, 01 Feb 2022 02:37:06 -0800 (PST) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kroah.com header.s=fm3 header.b=n3Tu2W7t; dkim=pass header.i=@messagingengine.com header.s=fm1 header.b=MVKeUz4a; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1354791AbiA3M2h (ORCPT + 71 others); Sun, 30 Jan 2022 07:28:37 -0500 Received: from out5-smtp.messagingengine.com ([66.111.4.29]:42067 "EHLO out5-smtp.messagingengine.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1354778AbiA3M2h (ORCPT ); Sun, 30 Jan 2022 07:28:37 -0500 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 4DF925C00D3; Sun, 30 Jan 2022 07:28:36 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Sun, 30 Jan 2022 07:28:36 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kroah.com; h=cc :cc:content-type:date:date:from:from:in-reply-to:in-reply-to :message-id:mime-version:references:reply-to:sender:subject :subject:to:to; s=fm3; bh=CqNgAQVZzOtSZopuwwTwr1nRliYIINiQLlJfuP 6jJh4=; b=n3Tu2W7tZChUun+B1RLi9dStLLdAsEIelsKGUjkPFT2qHmhP6vu0/g Oy/t6JMyeRnNUNRzsWtsM//DgRF+A6/4U4D+zNBako8eAS+yhM/LVjqtH/XsJ637 KYpCwa3derEfqo7cIenPnxxiy7XNmGvWuzZsDm9NJR/HRBTNTO1DCmL2v7eg2/mp LtKYH+HfG4tUOEI0r49r4SS0UunG0MUqmz7O5oU4MdkFxM3a8GN012+3tyxEalF7 VmFjfpJGz/yjqpHFe76D+s6gw/O8K7pXorh3/v+9BW0JzT78QdW2lhAFzXLhEn9R UcLFXGJd9psfikI5qpHbH7tR0i0sDzOA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-type:date:date:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:sender:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=CqNgAQVZzOtSZopuw wTwr1nRliYIINiQLlJfuP6jJh4=; b=MVKeUz4aBFTFwEvZuSauHMreHRnKHH+Sz lK2s2BYgsAGmKvap1dL20k2zEA8+q6gPLiXGuc7bkM7+ATkkERvEfay18EH4n5nR RC33V6r7cZdo4FjWurFEADhRK2o8OdbZm9JwbbGgfReOEbzfQmbn7B6G2HctiKVj JtQzsrsLyhVRknqQTBEjErTidplCCxwDpFeRaJfJsB4oqnWafUN/QZ0jLhKBf1Pe bzSy3Bh/j4hPHk1a9mOXB/qrguSOwQJr4EmvNUX+DFqNd8bAtcHh6nFwZ3LcFy57 AwlsIaan11j4XQif18/JpQC1Ri6IbczvbHUwLJOYCp2OZai9mZeyQ== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvvddrfeelgdegudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvuffkfhggtggujgesthdtredttddtvdenucfhrhhomhepifhrvghgucfm jfcuoehgrhgvgheskhhrohgrhhdrtghomheqnecuggftrfgrthhtvghrnhepveeuheejgf ffgfeivddukedvkedtleelleeghfeljeeiueeggeevueduudekvdetnecuvehluhhsthgv rhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepghhrvghgsehkrhhorghhrd gtohhm X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Sun, 30 Jan 2022 07:28:35 -0500 (EST) Date: Sun, 30 Jan 2022 13:28:33 +0100 From: Greg KH To: Felipe Contreras Cc: Linux stable , Linux wireless Subject: Re: Regression in 5.16.3 with mt7921e Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Sun, Jan 30, 2022 at 02:07:32AM -0600, Felipe Contreras wrote: > On Sun, Jan 30, 2022 at 1:28 AM Greg KH wrote: > > > > On Sat, Jan 29, 2022 at 01:05:50PM -0600, Felipe Contreras wrote: > > > Hello, > > > > > > I've always had trouble with this driver in my Asus Zephyrus laptop, > > > but I was able to use it eventually, that's until 5.16.3 landed. > > > > > > This version completely broke it. I'm unable to bring the interface > > > up, no matter what I try. > > > > > > Before, sometimes I was able to make the chip work by suspending the > > > laptop, but in 5.16.3 the machine doesn't wake up (which is probably > > > another issue). > > > > > > Reverting back to 5.16.2 makes it work. > > > > > > Let me know if you need more information, or if you would like me to > > > bisect the issue. > > > > Using 'git bisect' would be best, so we know what commit exactly causes > > the problems. > > I know, but it has been a while since I've created a decent config > file to build a kernel. > > Either way, I pushed forward and the commit is a38b94c43943. > > Upstream commit 547224024579 introduced a regression that was fixed by > the next commit 680a2ead741a, but the second commit was never merged > to stable. > > I've sent the second commit to fix the regression. Wonderful, thanks for figuring this out and sending the fix. greg k-h