From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org, ak@suse.de
Subject: io-apic - no timer ticks after resume on IXP200
Date: Mon, 11 Sep 2006 01:31:29 +0100 [thread overview]
Message-ID: <20060911003129.GA10600@srcf.ucam.org> (raw)
In-Reply-To: <20060910223308.GA1691@elf.ucw.cz>
(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
next prev parent reply other threads:[~2006-09-11 0:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-10 14:15 io-apic breaks suspend unless acpi_skip_timer_override Matthew Garrett
2006-09-10 20:58 ` Pavel Machek
2006-09-10 21:20 ` Matthew Garrett
2006-09-10 22:33 ` Pavel Machek
2006-09-11 0:31 ` Matthew Garrett [this message]
2006-09-11 5:46 ` io-apic - no timer ticks after resume on IXP200 Andi Kleen
2006-09-11 11:05 ` Matthew Garrett
2006-09-11 20:02 ` Andi Kleen
2006-09-11 22:23 ` Matthew Garrett
2006-09-11 23:07 ` [PATCH] - restore i8259A eoi status on resume Matthew Garrett
2006-09-12 9:19 ` Pavel Machek
2006-09-12 12:47 ` Matthew Garrett
2006-09-12 12:11 ` Andi Kleen
2006-09-12 13:40 ` Matthew Garrett
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060911003129.GA10600@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=ak@suse.de \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox