public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiang Liu <jiang.liu@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Henrique de Moraes Holschuh <hmh@hmh.eng.br>,
	jrg.otte@gmail.com
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [kernel 3.13.0-06058-g2d08cd0] Strange ACPI error messages
Date: Sun, 26 Jan 2014 17:31:51 +0800	[thread overview]
Message-ID: <52E4D607.6090509@linux.intel.com> (raw)
In-Reply-To: <2010872.ETICEKhYmO@vostro.rjw.lan>

Hi all,
	I will take care of this issue and send out a patch soon.
Thanks!
Gerry

On 2014/1/26 6:31, Rafael J. Wysocki wrote:
> On Saturday, January 25, 2014 02:18:17 PM Henrique de Moraes Holschuh wrote:
>> On Sat, 25 Jan 2014, Rafael J. Wysocki wrote:
>>> On Saturday, January 25, 2014 02:53:24 PM Rafael J. Wysocki wrote:
>>>> On Saturday, January 25, 2014 11:03:09 AM Jörg Otte wrote:
>>>>> Kernel 3.13.0-06058-g2d08cd0 displays following errors on the console:
>>>>>
>>>>> ACPI: \_PR_.CPU4: failed to get CPU APIC ID.
>>>>> ACPI: \_PR_.CPU5: failed to get CPU APIC ID.
>>>>> ACPI: \_PR_.CPU6: failed to get CPU APIC ID.
>>>>> ACPI: \_PR_.CPU7: failed to get CPU APIC ID.
>>>>>
>>>>> I don't have CPUs 4..7! Error messages regarding not existing
>>>>> CPUs should not be displayed.
>>>>> kernel 3.13.0-05617-g3aacd62 and before did'nt show this messages.
>>>>>
>>>>> This is a regression. I never saw this messages before.
>>>>
>>>> Does your system show any other suspicious symptoms or are you worried about
>>>> those messages only?
>>>
>>> Gerry, this is your commit b981513f806d (ACPI / scan: bail out early if failed
>>> to parse APIC ID for CPU).  Apparently, the BIOS has room for 4 CPUs more than
>>> there actually are in the system.  Maybe we can reduce the log level of those
>>> messages to avoid ringing bells unnecessarily?
>>
>> It is standard practice (at least in SuperMicro boxes, but I've also seen it
>> elsewhere) for the BIOS to have ACPI tables mentioning all cores supported
>> by the biggest core-count CPU topology possible by the motherboard.  The
>> cores you don't have are reported as if they were hotpluggable but absent,
>> even if they will *never* show up at runtime.  Meh.
>>
>> So yes, such warnings will get annoying *very* quickly.
> 
> Well, what about using acpi_handle_debug() in there, then?
> 

  reply	other threads:[~2014-01-26  9:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-25 10:03 [kernel 3.13.0-06058-g2d08cd0] Strange ACPI error messages Jörg Otte
2014-01-25 13:53 ` Rafael J. Wysocki
2014-01-25 13:59   ` Rafael J. Wysocki
2014-01-25 16:18     ` Henrique de Moraes Holschuh
2014-01-25 22:31       ` Rafael J. Wysocki
2014-01-26  9:31         ` Jiang Liu [this message]
2014-01-25 16:32   ` Jörg Otte
2014-01-25 22:29     ` Rafael J. Wysocki
2014-01-27  6:34 ` [PATCH] ACPI: reduce log level for message "ACPI: \_PR_.CPU4: failed to get CPU APIC ID" Jiang Liu
2014-01-27  9:19   ` Jörg Otte
2014-01-28  0:18   ` David Rientjes
2014-01-28  0:28     ` Rafael J. Wysocki
2014-01-28  1:20       ` Jiang Liu

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=52E4D607.6090509@linux.intel.com \
    --to=jiang.liu@linux.intel.com \
    --cc=hmh@hmh.eng.br \
    --cc=jrg.otte@gmail.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@rjwysocki.net \
    /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