All of lore.kernel.org
 help / color / mirror / Atom feed
From: John Garry <john.garry@huawei.com>
To: Bruno Goncalves <bgoncalv@redhat.com>
Cc: Pierre Gondois <pierre.gondois@arm.com>,
	<linux-arm-kernel@lists.infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	CKI Project <cki-project@redhat.com>,
	Ionela Voinescu <Ionela.Voinescu@arm.com>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>
Subject: Re: [aarch64] INFO: rcu_sched detected expedited stalls on CPUs/tasks
Date: Wed, 22 Jun 2022 15:49:02 +0100	[thread overview]
Message-ID: <fbfbb793-78ce-2b5a-307f-c6e78a926db3@huawei.com> (raw)
In-Reply-To: <CA+QYu4r9Z1X3b-PxqcQx3OkdASkon9OvPAVWJcqHLtc2uPkFtA@mail.gmail.com>

On 22/06/2022 15:40, Bruno Goncalves wrote:

Hi Bruno,

> With the config change that does not set
> CONFIG_RCU_EXP_CPU_STALL_TIMEOUT the problem seems to be fixed for us.
> The newer Fedora kernels already have the config fixed.
> 

OK, thanks for the info. Well those debug options I enabled didn't cause 
problems previously. I'll see if it is one in particular and go from there.

> 
>> On v5.19-rc3 I just enabled some debug configs on a vanilla kernel and
>> can easily reproduce a RCU stall on boot, as below.
>>
>> CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=0 for me, that being the default.
>>
>>    Table To iBMC Success.
>> GetVariable Status : Not Found.
>> [    0.000000] Booting Linux on physical CPU 0x0000010000 [0x410fd082]
>> [    0.000000] Linux version 5.19.0-rc3-00001-gd8610c1c16e8
>> (john@debian) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU
>> Binutils for Debian) 2.37) #187 SMP PREEMPT Wed Jun 22 14:08:56 BST 2022
>> [    0.000000] Machine model: Hisilicon PhosphorV660 Development Board
>> [    0.000000] efi: EFI v2.60 by EDK II
>> [    0.000000] efi: SMBIOS=0x3eff0000 SMBIOS 3.0=0x39aa0000
>> ACPI=0x39b70000 ACPI 2.0=0x39b70014 MEMATTR=0x3b8d0018
>> MEMRESERVE=0x3a002d18

Thanks!

WARNING: multiple messages have this Message-ID (diff)
From: John Garry <john.garry@huawei.com>
To: Bruno Goncalves <bgoncalv@redhat.com>
Cc: Pierre Gondois <pierre.gondois@arm.com>,
	<linux-arm-kernel@lists.infradead.org>,
	LKML <linux-kernel@vger.kernel.org>,
	CKI Project <cki-project@redhat.com>,
	Ionela Voinescu <Ionela.Voinescu@arm.com>,
	Dietmar Eggemann <dietmar.eggemann@arm.com>
Subject: Re: [aarch64] INFO: rcu_sched detected expedited stalls on CPUs/tasks
Date: Wed, 22 Jun 2022 15:49:02 +0100	[thread overview]
Message-ID: <fbfbb793-78ce-2b5a-307f-c6e78a926db3@huawei.com> (raw)
In-Reply-To: <CA+QYu4r9Z1X3b-PxqcQx3OkdASkon9OvPAVWJcqHLtc2uPkFtA@mail.gmail.com>

On 22/06/2022 15:40, Bruno Goncalves wrote:

Hi Bruno,

> With the config change that does not set
> CONFIG_RCU_EXP_CPU_STALL_TIMEOUT the problem seems to be fixed for us.
> The newer Fedora kernels already have the config fixed.
> 

OK, thanks for the info. Well those debug options I enabled didn't cause 
problems previously. I'll see if it is one in particular and go from there.

> 
>> On v5.19-rc3 I just enabled some debug configs on a vanilla kernel and
>> can easily reproduce a RCU stall on boot, as below.
>>
>> CONFIG_RCU_EXP_CPU_STALL_TIMEOUT=0 for me, that being the default.
>>
>>    Table To iBMC Success.
>> GetVariable Status : Not Found.
>> [    0.000000] Booting Linux on physical CPU 0x0000010000 [0x410fd082]
>> [    0.000000] Linux version 5.19.0-rc3-00001-gd8610c1c16e8
>> (john@debian) (gcc (Debian 10.2.1-6) 10.2.1 20210110, GNU ld (GNU
>> Binutils for Debian) 2.37) #187 SMP PREEMPT Wed Jun 22 14:08:56 BST 2022
>> [    0.000000] Machine model: Hisilicon PhosphorV660 Development Board
>> [    0.000000] efi: EFI v2.60 by EDK II
>> [    0.000000] efi: SMBIOS=0x3eff0000 SMBIOS 3.0=0x39aa0000
>> ACPI=0x39b70000 ACPI 2.0=0x39b70014 MEMATTR=0x3b8d0018
>> MEMRESERVE=0x3a002d18

Thanks!

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

  reply	other threads:[~2022-06-22 14:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03  9:44 [aarch64] INFO: rcu_sched detected expedited stalls on CPUs/tasks Bruno Goncalves
2022-06-03  9:44 ` Bruno Goncalves
2022-06-03 15:23 ` Pierre Gondois
2022-06-03 15:23   ` Pierre Gondois
2022-06-03 15:32   ` Bruno Goncalves
2022-06-03 15:32     ` Bruno Goncalves
2022-06-08  8:55     ` Pierre Gondois
2022-06-08  8:55       ` Pierre Gondois
2022-06-08 13:26       ` Bruno Goncalves
2022-06-08 13:26         ` Bruno Goncalves
2022-06-22 14:12         ` John Garry
2022-06-22 14:12           ` John Garry
2022-06-22 14:40           ` Bruno Goncalves
2022-06-22 14:40             ` Bruno Goncalves
2022-06-22 14:49             ` John Garry [this message]
2022-06-22 14:49               ` 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=fbfbb793-78ce-2b5a-307f-c6e78a926db3@huawei.com \
    --to=john.garry@huawei.com \
    --cc=Ionela.Voinescu@arm.com \
    --cc=bgoncalv@redhat.com \
    --cc=cki-project@redhat.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pierre.gondois@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.