From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: io-apic - no timer ticks after resume on IXP200 Date: Mon, 11 Sep 2006 01:31:29 +0100 Message-ID: <20060911003129.GA10600@srcf.ucam.org> References: <20060910141533.GA6594@srcf.ucam.org> <20060910205803.GA1966@elf.ucw.cz> <20060910212045.GA9278@srcf.ucam.org> <20060910223308.GA1691@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cavan.codon.org.uk ([217.147.92.49]:19157 "EHLO vavatch.codon.org.uk") by vger.kernel.org with ESMTP id S964839AbWIKAbf (ORCPT ); Sun, 10 Sep 2006 20:31:35 -0400 Content-Disposition: inline In-Reply-To: <20060910223308.GA1691@elf.ucw.cz> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Pavel Machek Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, ak@suse.de (Cc:ing Andi because I seem to remember him reworking the code for this chipset) Got it. After a suspend/resume cycle, I no longer have any timer ticks. Unsurprisingly, this breaks things. This is even true if I stub out the actual suspend code - that is, simply calling the device suspend and resume methods fails to set up the timer again properly. So the situation is the following: without acpi_skip_timer_override, the system works fine until suspend/resume. At that point, I no longer get any timer ticks. With acpi_skip_timer_override, the timer works fine before and after suspend. I suspect that something in the apic suspend/resume code isn't setting things correctly? Is there any useful debug output I can provide? -- Matthew Garrett | mjg59@srcf.ucam.org