All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joakim Tjernlund <Joakim.Tjernlund@infinera.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "sean.wang@mediatek.com" <sean.wang@mediatek.com>,
	"nbd@nbd.name" <nbd@nbd.name>,
	"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Please backport to 5.15.x: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=602cc0c9618a819ab00ea3c9400742a0ca318380
Date: Tue, 17 May 2022 08:28:39 +0000	[thread overview]
Message-ID: <9bd628f13e5ef1f80e3bce8a33d4554627ab4aa4.camel@infinera.com> (raw)
In-Reply-To: <c83379db5202a8f0e2ba4e252c3ae153675f4e58.camel@infinera.com>

Sean and/or Felix, this looks the same error. Please comment.

 Jocke

On Fri, 2022-05-13 at 16:32 +0200, Joakim Tjernlund wrote:
> Still seeing this on 5.15.39 after reboot, I have to power off to regain WiFi
> ~ # dmesg | grep mt
> [    4.621058] mt7921e 0000:03:00.0: enabling device (0000 -> 0002)
> [    4.636344] mt7921e 0000:03:00.0: disabling ASPM  L1
> [    4.637038] mt7921e 0000:03:00.0: can't disable ASPM; OS doesn't have ASPM control
> [    4.643347] mt7921e 0000:03:00.0: ASIC revision: 79610010
> [    5.716687] mt7921e: probe of 0000:03:00.0 failed with error -110
> 
> Sean/Felix ping ?
> 
>  Jocke
> 
> On Tue, 2022-05-10 at 17:06 +0200, Joakim Tjernlund wrote:
> > On Tue, 2022-05-10 at 12:20 +0200, Greg KH wrote:
> > > On Tue, May 10, 2022 at 09:26:31AM +0000, Joakim Tjernlund wrote:
> > > > https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgit.kernel.org%2Fpub%2Fscm%2Flinux%2Fkernel%2Fgit%2Fstable%2Flinux.git%2Fcommit%2F%3Fid%3D602cc0c9618a819ab00ea3c9400742a0ca318380&amp;data=05%7C01%7CJoakim.Tjernlund%40infinera.com%7C59fa126bca0c404c5e1e08da326eaf1e%7C285643de5f5b4b03a1530ae2dc8aaf77%7C1%7C0%7C637877748209285143%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&amp;sdata=CGswwJi11zPnCnULlb6sORh4vllNE80K%2FC7BArf8c7I%3D&amp;reserved=0
> > > > 
> > > > I see this error on ThinkPad T14 Gen 2a
> > > 
> > > But that commit says it fixes commit bf3747ae2e25 ("mt76: mt7921: enable
> > > aspm by default") which is in 5.16, not 5.15.
> > > 
> > > Have you tested this on 5.15.y to verify it will work properly?
> > > 
> > > thanks,
> > > 
> > > greg k-h
> > 
> > I got the same error/symptoms as https://bugzilla.kernel.org/show_bug.cgi?id=214557
> > which I believe "mt76: mt7921e: fix possible probe failure after reboot" addressed.
> > 
> > The patch is not trivial for me to backport so I haven't tested it.
> > 
> > Maybe Sean/Felix can comment?
> > 
> >  Jocke
> 


  reply	other threads:[~2022-05-17  8:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-10  9:26 Please backport to 5.15.x: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=602cc0c9618a819ab00ea3c9400742a0ca318380 Joakim Tjernlund
2022-05-10 10:20 ` Greg KH
2022-05-10 15:06   ` Joakim Tjernlund
2022-05-13 14:32     ` Joakim Tjernlund
2022-05-17  8:28       ` Joakim Tjernlund [this message]
2022-05-22 18:49         ` Joakim Tjernlund
2022-05-23 15:12           ` gregkh

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9bd628f13e5ef1f80e3bce8a33d4554627ab4aa4.camel@infinera.com \
    --to=joakim.tjernlund@infinera.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=nbd@nbd.name \
    --cc=sean.wang@mediatek.com \
    --cc=stable@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.