From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Viresh Kumar <viresh.kumar@linaro.org>,
Thorsten Leemhuis <regressions@leemhuis.info>
Cc: jia-wei.chang@mediatek.com, Nick <vincent@systemli.org>,
"Matthias Brugger" <matthias.bgg@gmail.com>,
rex-bc.chen@mediatek.com,
"Frank Wunderlich" <frank-w@public-files.de>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
linux-pm@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
Project_Global_Chrome_Upstream_Group@mediatek.com, "Hühn,
Thomas" <thomas.huehn@hs-nordhausen.de>,
"Daniel Golle" <daniel@makrotopia.org>
Subject: Re: Kernel Kernel bug caused by (cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622)
Date: Fri, 2 Dec 2022 10:19:58 +0100 [thread overview]
Message-ID: <c76bd301-0e8d-2d2b-0d3e-a57ece9b496f@collabora.com> (raw)
In-Reply-To: <0ebef1a2-6b5a-04b9-a79b-79eb3349c32b@collabora.com>
Il 02/12/22 09:57, AngeloGioacchino Del Regno ha scritto:
> Il 02/12/22 06:27, Viresh Kumar ha scritto:
>> On 01-12-22, 16:39, Thorsten Leemhuis wrote:
>>> Thx for clarifying. And I noticed I made a mistake: I should have
>>> directed my earlier question wrt to any progress here more into the
>>> direction of Jia-Wei Chang (who authored 6a17b3876b) and Viresh Kumar
>>> (who committed it).
>>
>> I was waiting for the platform maintainers to come up with a fix. I
>> have sent a patch now to revert this, in-reply-to this thread.
>>
>> Please confirm this is working fine. Thanks.
>>
>
> Can you guys try this patch that I've sent a while ago?
>
> https://lore.kernel.org/lkml/20220909093724.40078-1-angelogioacchino.delregno@collabora.com/T/#u
>
> There were comments on it, but if that solves your issue I can push a v2
> to solve what was reported.
>
> Regards,
> Angelo
Wait, sorry, I've re-read the stacktrace and that won't help at all.
MediaTek, can you please look at this issue?
Reverting the proposed commit will make MT8183 unstable.
next prev parent reply other threads:[~2022-12-02 9:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-09 13:35 Kernel Kernel bug caused by (cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622) Nick
2022-11-09 19:40 ` Kernel Kernel bug caused by (cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622) #forregzbot Thorsten Leemhuis
2022-11-10 11:26 ` Kernel Kernel bug caused by (cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622) Matthias Brugger
2022-11-15 19:44 ` Nick
2022-12-01 15:08 ` Thorsten Leemhuis
2022-12-01 15:26 ` Daniel Golle
2022-12-01 15:39 ` Thorsten Leemhuis
2022-12-01 21:40 ` Nick
2022-12-02 5:27 ` Viresh Kumar
2022-12-02 8:57 ` AngeloGioacchino Del Regno
2022-12-02 9:19 ` AngeloGioacchino Del Regno [this message]
2022-12-02 9:43 ` Allen-KH Cheng (程冠勳)
2022-12-02 10:02 ` AngeloGioacchino Del Regno
2022-12-02 10:41 ` Thorsten Leemhuis
2022-12-02 10:47 ` Viresh Kumar
2022-12-02 10:51 ` Thorsten Leemhuis
2022-12-02 11:00 ` AngeloGioacchino Del Regno
2022-12-02 11:01 ` Viresh Kumar
2022-12-07 15:34 ` Nick
2022-12-19 12:21 ` Allen-KH Cheng (程冠勳)
2022-12-20 14:37 ` Nick
2022-12-21 9:24 ` Kernel Kernel bug caused by (cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622) #forregzbot Thorsten Leemhuis
2022-12-02 12:25 ` Kernel Kernel bug caused by (cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622) Nick
2022-12-02 5:26 ` [PATCH] Revert "cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()" Viresh Kumar
2022-12-02 12:17 ` Rafael J. Wysocki
2022-12-02 19:46 ` Rafael J. Wysocki
2022-12-05 4:30 ` Viresh Kumar
2022-12-05 12:08 ` Rafael J. Wysocki
2022-12-05 23:30 ` Viresh Kumar
2022-12-02 12:47 ` Nick
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=c76bd301-0e8d-2d2b-0d3e-a57ece9b496f@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
--cc=daniel@makrotopia.org \
--cc=frank-w@public-files.de \
--cc=jia-wei.chang@mediatek.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=linux-pm@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=rex-bc.chen@mediatek.com \
--cc=thomas.huehn@hs-nordhausen.de \
--cc=vincent@systemli.org \
--cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox