linux-kernel - io-apic - no timer ticks after resume on IXP200

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20060911003129.GA10600@srcf.ucam.org>
Date:	Mon, 11 Sep 2006 01:31:29 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Pavel Machek <pavel@....cz>
Cc:	linux-kernel@...r.kernel.org, linux-acpi@...r.kernel.org,
	ak@...e.de
Subject: io-apic - no timer ticks after resume on IXP200

(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@...f.ucam.org
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/