From: Dou Liyang <douly.fnst@cn.fujitsu.com>
To: kernel test robot <fengguang.wu@intel.com>
Cc: <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<rjw@rjwysocki.net>, <lenb@kernel.org>, <tglx@linutronix.de>,
<rafael@kernel.org>, <dedekind1@gmail.com>, <ming.lei@redhat.com>,
<lkp@01.org>
Subject: Re: [ACPI / processor] d619c81e24: WARNING:at_include/linux/cpumask.h:#cpumask_test_cpu
Date: Mon, 19 Mar 2018 08:41:11 +0800 [thread overview]
Message-ID: <6212a66a-e301-4f9f-d435-34063da9df4f@cn.fujitsu.com> (raw)
In-Reply-To: <20180316111752.qi3u42mag367vx46@inn>
Hi lkp team
Thank you for testing.
At 03/16/2018 07:17 PM, kernel test robot wrote:
> FYI, we noticed the following commit (built with gcc-7):
>
> commit: d619c81e246424e322f7a902bed6e60b90668d56 ("ACPI / processor: Get accurate possible CPU count")
> url: https://github.com/0day-ci/linux/commits/Dou-Liyang/ACPI-processor-Get-accurate-possible-CPU-count/20180316-140349
>
>
> in testcase: boot
>
> on test machine: qemu-system-x86_64 -enable-kvm -cpu host -smp 2 -m 1G
>
> caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>
>
> +------------------------------------------------------+------------+------------+
> | | 3266b5bd97 | d619c81e24 |
> +------------------------------------------------------+------------+------------+
> | boot_successes | 16 | 2 |
> | boot_failures | 0 | 18 |
> | WARNING:at_include/linux/cpumask.h:#cpumask_test_cpu | 0 | 18 |
> | WARNING:at_include/linux/cpumask.h:#cpumask_check | 0 | 18 |
> | RIP:cpumask_check | 0 | 18 |
> | RIP:cpumask_test_cpu | 0 | 18 |
> | general_protection_fault:#[##] | 0 | 13 |
> | RIP:__lock_acquire | 0 | 13 |
> | Kernel_panic-not_syncing:Fatal_exception | 0 | 13 |
> | BUG:kernel_hang_in_boot_stage | 0 | 5 |
> +------------------------------------------------------+------------+------------+
>
>
>
> [ 0.830741] WARNING: CPU: 1 PID: 1 at include/linux/cpumask.h:122 cpumask_test_cpu+0x32/0x57
> [ 0.830785] WARNING: CPU: 1 PID: 1 at include/linux/cpumask.h:122 cpumask_check+0x2d/0x48
Yes, this patch broke the number of CPUs, we will find out a new way,
please drop the test work of this patch.
Thanks,
dou
prev parent reply other threads:[~2018-03-19 0:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-14 10:28 [RFC PATCH] ACPI / processor: Get accurate possible CPU count Dou Liyang
2018-03-14 17:24 ` Andy Shevchenko
2018-03-15 3:00 ` Dou Liyang
2018-03-16 11:17 ` [ACPI / processor] d619c81e24: WARNING:at_include/linux/cpumask.h:#cpumask_test_cpu kernel test robot
2018-03-16 11:17 ` kernel test robot
2018-03-19 0:41 ` Dou Liyang [this message]
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=6212a66a-e301-4f9f-d435-34063da9df4f@cn.fujitsu.com \
--to=douly.fnst@cn.fujitsu.com \
--cc=dedekind1@gmail.com \
--cc=fengguang.wu@intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
--cc=ming.lei@redhat.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
/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®