From: Philippe Schenker <dev@pschenker.ch>
To: sean.wang@mediatek.com
Cc: deren.wu@mediatek.com, kvalo@kernel.org,
linux-wireless@vger.kernel.org, nbd@nbd.name,
linux@leemhuis.info, davem@davemloft.net, kuba@kernel.org,
lorenzo.bianconi83@gmail.com, matthias.bgg@gmail.com,
pabeni@redhat.com, ryder.lee@mediatek.com,
shayne.chen@mediatek.com, yn.chen@mediatek.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-mediatek@lists.infradead.org, netdev@vger.kernel.org
Subject: Re: [PATCH] Revert "mt76: mt7921: enable aspm by default"
Date: Thu, 02 Jun 2022 10:44:13 +0200 [thread overview]
Message-ID: <2c5a6bb34c67c9c15c393346e89bdb14ae6f3c44.camel@pschenker.ch> (raw)
In-Reply-To: <1654122203-26090-1-git-send-email-sean.wang@mediatek.com>
On Thu, 2022-06-02 at 06:23 +0800, sean.wang@mediatek.com wrote:
> From: Sean Wang <sean.wang@mediatek.com>
>
> > On Tue, 2022-04-12 at 19:06 +0800, Deren Wu wrote:
> > > On Tue, 2022-04-12 at 12:37 +0300, Kalle Valo wrote:
> > > > Philippe Schenker <dev@pschenker.ch> writes:
> > > >
> > > > > This reverts commit bf3747ae2e25dda6a9e6c464a717c66118c588c8.
> > > > >
> > > > > This commit introduces a regression on some systems where the
> > > > > kernel is crashing in different locations after a reboot was
> > > > > issued.
> > > > >
> > > > > This issue was bisected on a Thinkpad P14s Gen2 (AMD) with
> > > > > latest
> > > > > firmware.
> > > > >
> > > > > Link:
> > > > > https://urldefense.com/v3/__https://lore.kernel.org/linux-wireless
> > > > > /5077a953487275837e81bdf1808ded00b9676f9f.camel@pschenker.ch/_
> > > > > _;!!
> > > > > CTRNKA9wMg0ARbw!09tjyaQlMci3fVI3yiNiDJKUW_qwNA_CbVhoAraeIX96B9
> > > > > 9Q14
> > > > > J4iDycWA9cq36Y$
> > > > >
> > > > > Signed-off-by: Philippe Schenker <dev@pschenker.ch>
> > > >
> > > > Can I take this to wireless tree? Felix, ack?
> > > >
> > > > I'll also add:
> > > >
> > > > Fixes: bf3747ae2e25 ("mt76: mt7921: enable aspm by default")
> > > >
> > >
> > > Hi Kalle,
> > >
> > > We have a patch for a similar problem. Can you wait for the
> > > verification by Philippe?
> > > Commit 602cc0c9618a81 ("mt76: mt7921e: fix possible probe failure
> > > after
> > > reboot")
> > > Link:
> > > https://urldefense.com/v3/__https://git.kernel.org/pub/scm/linux/kerne
> > > l/git/torvalds/linux.git/commit/drivers/net/wireless/mediatek/mt76
> > > ?id=
> > > 602cc0c9618a819ab00ea3c9400742a0ca318380__;!!CTRNKA9wMg0ARbw!3N9I3
> > > iKwS
> > > 3XCNAb4LuhbFqt_el1yiOaJzSdUjaJsTaxRCHiWhXnEgbk3bOqYTy6T$
> > >
> > > I can reproduce the problem in my v5.16-rc5 desktop. And the issue
> > > can
> > > be fixed when the patch applied.
> > >
> > >
> > > Hi Philippe,
> > >
> > > Can you please help to check the patch in your platform?
> >
> > Hi Kalle and Deren,
> >
> > I just noticed on my system and mainline v5.18 reboots do now work
> > however Bluetooth is no longer accessible after a reboot.
> >
> > Reverting commit bf3747ae2e25dda6a9e6c464a717c66118c588c8 on top of
> > v5.18 solves this problem for me.
> >
> > @Deren are you aware of this bug?
> > @Kalle Is there a bugtracker somewhere I can submit this?
>
> Hi Philippe,
>
> Could you try the latest firmware to see if it can help with the issue
> you reported here ?
>
> Please check out
> https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/mediatek
> and replace the following three files in /lib/firmware/mediatek on
> your target and reboot
> 1) BT_RAM_CODE_MT7961_1_2_hdr.bin
> 2) WIFI_MT7961_patch_mcu_1_2_hdr.bin
> 3) WIFI_RAM_CODE_MT7961_1.bin
>
> Sean
Hi Sean,
Thanks for your suggestion. I downloaded the firmwares from the link you
indicated and downloaded the three firmwares from main branch. I checked
and the sha256sums of the most recent firmwares match with the one
installed by my distribution. So I already had latest versions on my
tests.
Philippe
>
> >
> > Thanks,
> > Philippe
> >
> > >
> > >
> > > Regards,
> > > Deren
> > >
> >
> >
> >
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-06-02 8:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <e93aef5c9f8a97efe23cfb5892f78f919ce328e7.camel@pschenker.ch--annotate>
2022-06-01 22:23 ` [PATCH] Revert "mt76: mt7921: enable aspm by default" sean.wang
2022-06-02 8:44 ` Philippe Schenker [this message]
2022-04-12 9:04 Philippe Schenker
2022-04-12 9:37 ` Kalle Valo
2022-04-12 9:55 ` Thorsten Leemhuis
2022-04-12 10:33 ` Kalle Valo
2022-04-12 10:36 ` Kalle Valo
2022-04-27 7:32 ` Thorsten Leemhuis
2022-04-12 11:06 ` Deren Wu
2022-04-12 12:30 ` Philippe Schenker
2022-04-12 12:45 ` Kalle Valo
2022-06-01 8:28 ` Philippe Schenker
2022-06-01 8:58 ` Kalle Valo
2022-06-01 16:55 ` Deren Wu
2022-06-02 10:00 ` Philippe Schenker
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=2c5a6bb34c67c9c15c393346e89bdb14ae6f3c44.camel@pschenker.ch \
--to=dev@pschenker.ch \
--cc=davem@davemloft.net \
--cc=deren.wu@mediatek.com \
--cc=kuba@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@leemhuis.info \
--cc=lorenzo.bianconi83@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=ryder.lee@mediatek.com \
--cc=sean.wang@mediatek.com \
--cc=shayne.chen@mediatek.com \
--cc=yn.chen@mediatek.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).