public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Nick <vincent@systemli.org>
To: "Allen-KH Cheng (程冠勳)" <Allen-KH.Cheng@mediatek.com>,
	"viresh.kumar@linaro.org" <viresh.kumar@linaro.org>,
	"angelogioacchino.delregno@collabora.com"
	<angelogioacchino.delregno@collabora.com>
Cc: "linux-mediatek@lists.infradead.org"
	<linux-mediatek@lists.infradead.org>,
	"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	"regressions@leemhuis.info" <regressions@leemhuis.info>,
	Project_Global_Chrome_Upstream_Group
	<Project_Global_Chrome_Upstream_Group@mediatek.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"matthias.bgg@gmail.com" <matthias.bgg@gmail.com>,
	"daniel@makrotopia.org" <daniel@makrotopia.org>,
	"Rex-BC Chen (陳柏辰)" <Rex-BC.Chen@mediatek.com>,
	"thomas.huehn@hs-nordhausen.de" <thomas.huehn@hs-nordhausen.de>,
	"Jia-wei Chang (張佳偉)" <Jia-wei.Chang@mediatek.com>
Subject: Re: Kernel Kernel bug caused by (cpufreq: mediatek: Refine mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622)
Date: Tue, 20 Dec 2022 15:37:10 +0100	[thread overview]
Message-ID: <3599ec46-20d2-a233-a7c0-d2e363ebdf93@systemli.org> (raw)
In-Reply-To: <5e07eb07de0fea2232c32f58691ffb7cfd2303f8.camel@mediatek.com>

Hey,
thanks for all your help. I guess it's fine now.
If someone wants to reproduce my setup, I published the exact steps here:
https://forum.openwrt.org/t/running-vanilla-kernel-on-banana-pi-r64/145351

I still wonder why my initial try using the OpenWrt build-environment 
together with the 6.1 kernel failed.

Bests
Nick

On 12/19/22 13:21, Allen-KH Cheng (程冠勳) wrote:
> Hi Nick,
>
> This issue doesn't seem to be going to happen.
> Is there anything else we need help confirming?
>
> Thanks,
> Allen
>
> -----Original Message-----
> From: Linux-mediatek <linux-mediatek-bounces@lists.infradead.org> On
> Behalf Of Nick
> Sent: Wednesday, December 7, 2022 11:35 PM
> To: Viresh Kumar <viresh.kumar@linaro.org>; AngeloGioacchino Del Regno
> <angelogioacchino.delregno@collabora.com>
> Cc: Allen-KH Cheng (程冠勳) <Allen-KH.Cheng@mediatek.com>;
> linux-pm@vger.kernel.org; daniel@makrotopia.org;
> Project_Global_Chrome_Upstream_Group <
> Project_Global_Chrome_Upstream_Group@mediatek.com>; Rex-BC Chen (陳柏辰) <
> Rex-BC.Chen@mediatek.com>; Thorsten Leemhuis <regressions@leemhuis.info
>> ; linux-mediatek@lists.infradead.org; matthias.bgg@gmail.com;
> thomas.huehn@hs-nordhausen.de; Jia-wei Chang (張佳偉) <
> Jia-wei.Chang@mediatek.com>; linux-arm-kernel@lists.infradead.org;
> regressions@lists.linux.dev
> Subject: Re: Kernel Kernel bug caused by (cpufreq: mediatek: Refine
> mtk_cpufreq_voltage_tracking()) on Banana Pi R64 (MT7622)
>
> Did something changed on master? I compiled now the image I use on the
> BPI-R64 a bit differently.
> I used the openwrt toolchain "aarch64-openwrt-linux-musl-" to cross-
> compile the original linux repository on current master. Than I
> compiled with OpenWrt-Buildsystem a initramfs, put that together with
> mkimage to a "itb" and booted it. Suddenly it works:
>
> https://urldefense.com/v3/__https://gist.githubusercontent.com/PolynomialDivision/5e49529206ba5d273bf6a416c42c6234/raw/7ecff7be397a6e9a41ef120c3fa61060c488cf5b/mt7622-bpi-vanilla__;!!CTRNKA9wMg0ARbw!glNhziJx8pjvVsVoRm0LO8wshXJL_b2P_jYV5vO_9uhe1EnbMpWRnIEcj_561Ijxurd8C-Fjc7uCbBNIM_E-7YYc$
>   
>
> Bests
> Nick
>
> On 12/2/22 12:01, Viresh Kumar wrote:
>> On 02-12-22, 12:00, AngeloGioacchino Del Regno wrote:
>>> If Viresh can add those while applying the patch, that's fine for
>>> me
>>> - otherwise I can send a v2 adding the two suggested missing tags.
>> Sure, no problem.
>>
>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-12-20 14:39 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
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 [this message]
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=3599ec46-20d2-a233-a7c0-d2e363ebdf93@systemli.org \
    --to=vincent@systemli.org \
    --cc=Allen-KH.Cheng@mediatek.com \
    --cc=Jia-wei.Chang@mediatek.com \
    --cc=Project_Global_Chrome_Upstream_Group@mediatek.com \
    --cc=Rex-BC.Chen@mediatek.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=daniel@makrotopia.org \
    --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=thomas.huehn@hs-nordhausen.de \
    --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