linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: John Garry <john.garry@huawei.com>
Cc: Mark Rutland <mark.rutland@arm.com>,
	Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Linuxarm <linuxarm@huawei.com>,
	wanghuiqiang <wanghuiqiang@huawei.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: PSCI checker query
Date: Thu, 5 Dec 2019 13:30:20 +0000	[thread overview]
Message-ID: <20191205133020.GA20398@bogus> (raw)
In-Reply-To: <5c3c69bf-cae9-8ad5-9da2-c0af7a5932e7@huawei.com>

On Thu, Dec 05, 2019 at 12:38:25PM +0000, John Garry wrote:
> Hi guys,
>
> I enabled the kernel PSCI checker and it kills my Huawei D05:
>

[...]

> [   18.042122] psci_checker: PSCI checker started using 64 CPUs
> [   18.047774] psci_checker: Starting hotplug tests
> [   18.052387] psci_checker: Trying to turn off and on again all CPUs
> [   18.059082] CPU0: shutdown
> [   18.061777] psci: CPU0 killed.
> [   18.069140] CPU1: shutdown
> [   18.071844] psci: CPU1 killed.
> [   18.078530] CPU2: shutdown
> [   18.081227] psci: CPU2 killed.
> [   18.087874] CPU3: shutdown
> [   18.090605] psci: CPU3 killed.
> [   18.097415] CPU4: shutdown
> [   18.100119] psci: CPU4 killed.
> [   18.105989] usb 1-2: new high-speed USB device number 3 using
> ehci-platform
> [   18.113286] CPU5: shutdown
> [   18.116007] psci: CPU5 killed.
> [   18.122432] CPU6: shutdown
> [   18.125130] psci: CPU6 killed.
> [   18.131525] CPU7: shutdown
> [   18.134243] psci: CPU7 killed.
> [   18.140625] CPU8: shutdown
> [   18.143335] psci: CPU8 killed.
> [   18.149755] CPU9: shutdown
> [   18.152465] psci: CPU9 killed.
> [   18.158867] CPU10: shutdown
>
> [snip]
>
> [   18.521459] CPU52: shutdown
> [   18.524256] psci: CPU52 killed.
> [   18.528634] CPU53: shutdown
> [   18.531461] psci: CPU53 killed.
> [   18.535847] CPU54: shutdown
> [   18.538645] psci: CPU54 killed.
> [   18.542977] CPU55: shutdown
> [   18.545761] psci: CPU55 killed.
> [   18.550050] CPU56: shutdown
> [   18.552836] psci: CPU56 killed.
> [   18.557059] CPU57: shutdown
> [   18.559855] psci: CPU57 killed.
> [   18.564012] CPU58: shutdown
> [   18.566809] psci: CPU58 killed.
> [   18.570941] CPU59: shutdown
> [   18.573725] psci: CPU59 killed.
> [   18.577778] CPU60: shutdown
> [   18.580576] psci: CPU60 killed.
> [   18.584592] CPU61: shutdown
> [   18.587400] psci: CPU61 killed.
> [   18.591351] CPU62: shutdown
> [   18.594148] psci: CPU62 killed.
> [   18.597997] usb 1-2.1: new full-speed USB device number 4 using ehci-platform
>
> The console is unresponsive at this point.
>
> My D06 does not have this issue and the test completes successfully:
>
> D06:
>
> root@(none)$ dmesg | grep -i psci
> [    0.000000] psci: probing for conduit method from ACPI.
> [    0.000000] psci: PSCIv1.1 detected in firmware.
> [    0.000000] psci: Using standard PSCI v0.2 function IDs
> [    0.000000] psci: MIGRATE_INFO_TYPE not supported.
> [    0.000000] psci: SMC Calling Convention v1.1
> [   24.252657] psci_checker: PSCI checker started using 96 CPUs
> [   24.258305] psci_checker: Starting hotplug tests
> [   24.262914] psci_checker: Trying to turn off and on again all CPUs
> [   24.277545] psci: CPU0 killed.
> [   24.298682] psci: CPU1 killed.
> [   24.318704] psci: CPU2 killed.
> [   24.343580] psci: CPU3 killed.
>
> [snip]
>
> [   46.053433] psci_checker: cpuidle not available on CPU 92, ignoring
> [   46.059690] psci_checker: cpuidle not available on CPU 93, ignoring
> [   46.065946] psci_checker: cpuidle not available on CPU 94, ignoring
> [   46.072203] psci_checker: cpuidle not available on CPU 95, ignoring
> [   46.078465] psci_checker: Could not start suspend tests on any CPU
> [   46.084635] psci_checker: PSCI checker completed
> root@(none)$
>
> Is there anything we can check to know what's going wrong?
>

Both use the same firmware(or at-least the baseline) ? Are there any
significant hardware or firmware changes around CPU power-off sequence ?
If you are running same kernel image on both, firmware becomes easy
target to start with. Have you run some tests on PSCI firmware ?

--
Regards,
Sudeep

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

  reply	other threads:[~2019-12-05 13:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-05 12:38 PSCI checker query John Garry
2019-12-05 13:30 ` Sudeep Holla [this message]
2019-12-05 14:22   ` John Garry
2019-12-05 15:48     ` Sudeep Holla
2019-12-05 15:55 ` Marc Zyngier
2019-12-05 16:53   ` Sudeep Holla
2019-12-05 16:59     ` Marc Zyngier
2019-12-05 17:12     ` John Garry

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=20191205133020.GA20398@bogus \
    --to=sudeep.holla@arm.com \
    --cc=john.garry@huawei.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linuxarm@huawei.com \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=mark.rutland@arm.com \
    --cc=wanghuiqiang@huawei.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).