From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: [PATCH] ACPI: reduce log level for message "ACPI: \_PR_.CPU4: failed to get CPU APIC ID" Date: Tue, 28 Jan 2014 01:28:41 +0100 Message-ID: <52E6F9B9.1070900@intel.com> References: <1390804498-30311-1-git-send-email-jiang.liu@linux.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mga02.intel.com ([134.134.136.20]:58637 "EHLO mga02.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752052AbaA1A2q (ORCPT ); Mon, 27 Jan 2014 19:28:46 -0500 In-Reply-To: Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: David Rientjes , Jiang Liu Cc: Jorg Otte , Henrique de Moraes Holschuh , "Rafael J . Wysocki" , Len Brown , linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org On 1/28/2014 1:18 AM, David Rientjes wrote: > On Mon, 27 Jan 2014, Jiang Liu wrote: > >> diff --git a/drivers/acpi/acpi_processor.c b/drivers/acpi/acpi_processor.c >> index c9311be..c29c2c3 100644 >> --- a/drivers/acpi/acpi_processor.c >> +++ b/drivers/acpi/acpi_processor.c >> @@ -261,7 +261,7 @@ static int acpi_processor_get_info(struct acpi_device *device) >> >> apic_id = acpi_get_apicid(pr->handle, device_declaration, pr->acpi_id); >> if (apic_id < 0) { >> - acpi_handle_err(pr->handle, "failed to get CPU APIC ID.\n"); >> + acpi_handle_debug(pr->handle, "failed to get CPU APIC ID.\n"); >> return -ENODEV; >> } > Don't we already leave some artifact in the kernel log at boot about apic > ids that don't get registered? I'm wondering if we should have this > warning at all. It is useful for knowing that there are potentially broken objects in the ACPI tables.