From: 王法杰 <wangfajie@longcheer.com>
To: Marc Zyngier <maz@kernel.org>
Cc: "daniel.lezcano@kernel.org" <daniel.lezcano@kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"quic_ylal@quicinc.com" <quic_ylal@quicinc.com>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"will@kernel.org" <will@kernel.org>,
刘仁旺 <liurenwang@longcheer.com>, 张辉 <zhanghui5@longcheer.com>,
"liangke1@xiaomi.com" <liangke1@xiaomi.com>,
沈兵 <ShenBing@longcheer.com>, 刘琦 <liuqi405@icloud.com>
Subject: Re: [PATCH] clocksource/drivers/arm_arch_timer: Update sched_clock when non-boot CPUs need counter workaround
Date: Thu, 19 Jan 2023 13:28:19 +0000 [thread overview]
Message-ID: <86c8b6b630954e63999b58de9d820408@mailboxsrv05.LongCheer.net> (raw)
Hi Marc Zyngier
We found the APPS Crash issue on MTBF test.
Brief crash information, APPS Crash - Kernel BUG at /sched/walt/sched_avg.c:281! in sched_update_nr_prod flow
[Test equipment]
1. Number of phone: 200 pcs
2. CPU info of phone: CPU architecture with Quad Cortex-A73 and Quad Cortex-A53
[Preset conditions]
1. Android 13 with kernel 5.15
2. Install application of top 20
3. Connected to Wi-Fi
4. Connect the adapter to charge the phone
5. Test duration 48 hours
[Expected results]
0 crash happened.
[Test results without [PATCH] clocksource/drivers/arm_arch_timer: Update sched_clock when non-boot CPUs need counter workaround ]
1. First round of test, found 3 phones with APPS Crash issue on /sched/walt/sched_avg.c:281! in sched_update_nr_prod flow
2. Second round of test, found 7 phones with APP Crash issue on /sched/walt/sched_avg.c:281! in sched_update_nr_prod flow
[Test results with [PATCH] clocksource/drivers/arm_arch_timer: Update sched_clock when non-boot CPUs need counter workaround ]
1. First round of test, 0 crash happened.
2. Second round of test, 0 crash happened.
Tested-by: wangfajie <wangfajie@longcheer.com>
Tested-by: liurenwang <liurenwang@longcheer.com>
Tested-by: zhanghui <zhanghui5@longcheer.com>
Tested-by: liangke <liangke1@xiaomi.com>
So we think the PATCH is working and it can fix APPS crash issue. Many thanks your time.
Best regards!
Wangfajie
-----邮件原件-----
发件人: Marc Zyngier [mailto:maz@kernel.org]
发送时间: 2023年1月19日 17:52
收件人: 刘琦 <liuqi405@icloud.com>
抄送: daniel.lezcano@kernel.org; linux-arm-kernel@lists.infradead.org; linux-kernel@vger.kernel.org; mark.rutland@arm.com; quic_ylal@quicinc.com; stable@vger.kernel.org; will@kernel.org; 王法杰 <wangfajie@longcheer.com>; 刘仁旺 <liurenwang@longcheer.com>; 张辉 <zhanghui5@longcheer.com>; liangke1@xiaomi.com
主题: Re: [PATCH] clocksource/drivers/arm_arch_timer: Update sched_clock when non-boot CPUs need counter workaround
On 2023-01-19 07:59, 刘琦 wrote:
> [Test Report]
> Result: Test Pass
>
> A total of two rounds of pending testing
> a. The first round of hanging test
> Number of machines: 200
> Hanging test duration: 48h
> Hanging test results: no walt crash problem
> b. The second round of hanging test
> Number of machines: 200
> Hanging test duration: 72h
> Hanging test results: no walt crash problem
>
> Tested-by: wangfajie <wangfajie@longcheer.com>
> Tested-by: liurenwang <liurenwang@longcheer.com>
> Tested-by: zhanghui <zhanghui5@longcheer.com>
> Tested-by: liangke <liangke1@xiaomi.com>
Thanks for this.
The only issue here is that that you don't explain what you tested, nor how you tested it.
It is also a patch that has known defects (you just have to read the thread for the details)... This makes this testing, no matter how thorough it is, rather ineffective.
M.
--
Jazz is not dead. It just smells funny...
next reply other threads:[~2023-01-19 13:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-19 13:28 王法杰 [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-01-19 7:59 刘琦
2023-01-19 9:52 ` Marc Zyngier
2023-01-13 11:16 Marc Zyngier
2023-01-13 12:45 ` Mark Rutland
2023-03-28 13:59 ` Will Deacon
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=86c8b6b630954e63999b58de9d820408@mailboxsrv05.LongCheer.net \
--to=wangfajie@longcheer.com \
--cc=ShenBing@longcheer.com \
--cc=daniel.lezcano@kernel.org \
--cc=liangke1@xiaomi.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuqi405@icloud.com \
--cc=liurenwang@longcheer.com \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=quic_ylal@quicinc.com \
--cc=stable@vger.kernel.org \
--cc=will@kernel.org \
--cc=zhanghui5@longcheer.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
all inboxes | Powered by JetHome®