From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752112AbaAYNpP (ORCPT ); Sat, 25 Jan 2014 08:45:15 -0500 Received: from v094114.home.net.pl ([79.96.170.134]:63846 "HELO v094114.home.net.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751433AbaAYNoz convert rfc822-to-8bit (ORCPT ); Sat, 25 Jan 2014 08:44:55 -0500 From: "Rafael J. Wysocki" To: Jiang Liu Cc: =?ISO-8859-1?Q?J=F6rg?= Otte , "Rafael J. Wysocki" , Linus Torvalds , Linux Kernel Mailing List , ACPI Devel Maling List Subject: Re: [kernel 3.13.0-06058-g2d08cd0] Strange ACPI error messages Date: Sat, 25 Jan 2014 14:59:09 +0100 Message-ID: <4387759.ffnsEjDaad@vostro.rjw.lan> User-Agent: KMail/4.11.4 (Linux/3.13.0-rc8+; KDE/4.11.4; x86_64; ; ) In-Reply-To: <9739501.rBu7tJQIYj@vostro.rjw.lan> References: <9739501.rBu7tJQIYj@vostro.rjw.lan> MIME-Version: 1.0 Content-Transfer-Encoding: 8BIT Content-Type: text/plain; charset="utf-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? Rafael