Re: [ACPI / processor] d619c81e24: WARNING:at_include/linux/cpumask.h:#cpumask_test_cpu

[Dou Liyang]

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