All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: lkp@lists.01.org
Subject: Re: [lkp-robot] [acpi] 2e61bac54f: kmsg.acpi_LNXCPU:#f:Failed_to_get_unique_processor_UID(#)
Date: Wed, 08 Mar 2017 14:48:53 +0800	[thread overview]
Message-ID: <20170308064853.GA22005@yexl-desktop> (raw)
In-Reply-To: <c443f129-0c15-d6b7-1bdd-c16676437a6e@cn.fujitsu.com>

[-- Attachment #1: Type: text/plain, Size: 2557 bytes --]

On 03/08, Dou Liyang wrote:
>Hi Ying,
>
>At 03/08/2017 09:03 AM, kernel test robot wrote:
>>FYI, we noticed the following commit:
>>
>>commit: 2e61bac54fad4c018afd23c118bce2399e504020 ("acpi: Move the verification of duplicate proc_id from booting time to hot-plug time")
>>git://bee.sh.intel.com/git/yexl/linux.git verify-acpi-bug-lkp-hsw-ep2
>>
>>in testcase: boot
>>on test machine: 128 threads 4 Sockets Haswell-EP with 512G memory
>>
>>caused below changes (please refer to attached dmesg/kmsg for entire log/backtrace):
>>
>>
>>kern  :err   : [   11.366678] acpi LNXCPU:20: Failed to get unique processor _UID (0xff)
>>kern  :err   : [   11.373239] acpi LNXCPU:21: Failed to get unique processor _UID (0xff)
>>kern  :err   : [   11.379796] acpi LNXCPU:22: Failed to get unique processor _UID (0xff)
>>kern  :err   : [   11.386349] acpi LNXCPU:23: Failed to get unique processor _UID (0xff)
>>kern  :err   : [   11.394026] acpi LNXCPU:44: Failed to get unique processor _UID (0xff)
>>kern  :err   : [   11.400584] acpi LNXCPU:45: Failed to get unique processor _UID (0xff)
>>kern  :err   : [   11.407141] acpi LNXCPU:46: Failed to get unique processor _UID (0xff)
>>kern  :err   : [   11.413696] acpi LNXCPU:47: Failed to get unique processor _UID (0xff)
>>kern  :err   : [   11.421403] acpi LNXCPU:68: Failed to get unique processor _UID (0xff)
>>kern  :err   : [   11.427963] acpi LNXCPU:69: Failed to get unique processor _UID (0xff)
>>kern  :err   : [   11.434522] acpi LNXCPU:6a: Failed to get unique processor _UID (0xff)
>>kern  :err   : [   11.441082] acpi LNXCPU:6b: Failed to get unique processor _UID (0xff)
>>kern  :err   : [   11.448786] acpi LNXCPU:8c: Failed to get unique processor _UID (0xff)
>>kern  :err   : [   11.455342] acpi LNXCPU:8d: Failed to get unique processor _UID (0xff)
>>kern  :err   : [   11.461900] acpi LNXCPU:8e: Failed to get unique processor _UID (0xff)
>>kern  :err   : [   11.468451] acpi LNXCPU:8f: Failed to get unique processor _UID (0xff)
>>
>
>These logs in dmesg means there are some processors with the same
>acpi_id 0xff in the DSDT.
>
>As we know, the duplicated processors is forbidden for the DSDT.
>
>So I add this check, and print one line log if we found a duplicated
>processors in the DSDT.

So this is intended behavior, right?

Thanks,
Xiaolong
>
>
>Thanks,
>	Liyang.
>>
>>Thanks,
>>Ying Huang
>>
>>
>
>
>_______________________________________________
>LKP mailing list
>LKP(a)lists.01.org
>https://lists.01.org/mailman/listinfo/lkp

  reply	other threads:[~2017-03-08  6:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-08  1:03 [lkp-robot] [acpi] 2e61bac54f: kmsg.acpi_LNXCPU:#f:Failed_to_get_unique_processor_UID(#) kernel test robot
2017-03-08  3:01 ` Dou Liyang
2017-03-08  6:48   ` Ye Xiaolong [this message]
2017-03-08  7:06     ` Dou Liyang

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=20170308064853.GA22005@yexl-desktop \
    --to=xiaolong.ye@intel.com \
    --cc=lkp@lists.01.org \
    /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.