Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753909AbaA1A2s (ORCPT ); Mon, 27 Jan 2014 19:28:48 -0500 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 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.95,732,1384329600"; d="scan'208";a="445527308" Message-ID: <52E6F9B9.1070900@intel.com> Date: Tue, 28 Jan 2014 01:28:41 +0100 From: "Rafael J. Wysocki" Organization: Intel Technology Poland Sp. z o. o., KRS 101882, ul. Slowackiego 173, 80-298 Gdansk User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 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 Subject: Re: [PATCH] ACPI: reduce log level for message "ACPI: \_PR_.CPU4: failed to get CPU APIC ID" References: <1390804498-30311-1-git-send-email-jiang.liu@linux.intel.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: 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. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/