Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755359AbYLJPxA (ORCPT ); Wed, 10 Dec 2008 10:53:00 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753891AbYLJPwv (ORCPT ); Wed, 10 Dec 2008 10:52:51 -0500 Received: from smtp1.linux-foundation.org ([140.211.169.13]:57072 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753878AbYLJPwu (ORCPT ); Wed, 10 Dec 2008 10:52:50 -0500 Date: Wed, 10 Dec 2008 07:51:35 -0800 (PST) From: Linus Torvalds X-X-Sender: torvalds@localhost.localdomain To: Frans Pop cc: Ingo Molnar , lenb@kernel.org, "Rafael J. Wysocki" , Greg KH , jbarnes@virtuousgeek.org, Linux Kernel Mailing List , tiwai@suse.de, Andrew Morton Subject: Re: "APIC error on CPU1: 00(40)" during resume (was: Regression from 2.6.26: Hibernation (possibly suspend) broken on Toshiba R500) In-Reply-To: <200812101506.45691.elendil@planet.nl> Message-ID: References: <200812020320.31876.rjw@sisk.pl> <200812041900.27514.elendil@planet.nl> <200812101506.45691.elendil@planet.nl> User-Agent: Alpine 2.00 (LFD 1167 2008-08-23) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1129 Lines: 29 On Wed, 10 Dec 2008, Frans Pop wrote: > > Anybody interested in persuing this issue? > > The third thing that worries me is the _very_ early occurrence of > > > > ACPI: Waking up from system sleep state S3 > > APIC error on CPU1: 00(40) > > ACPI: EC: non-query interrupt received, switching to interrupt mode Well, the "too early" part is fixed with the PCI resume changes in -next, and googling for "APIC error on CPU1: 00(40)" shows that it's actually pretty common. Which is sad, but makes it somewhat less scary. The fact that it happens at resume for you (and not randomly) does imply that we perhaps don't have a wonderful APIC wakeup sequence and are doing something slightly wrong. But it likely isn't a big deal. Is that message new? If it is, maybe you can pinpoint roughly when it started happening, and we could try guess which change triggered it. Linus -- 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/