[lkml]   [2006]   [Jul]   [10]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [BUG] APM resume breakage from 2.6.18-rc1 clocksource changes
On Tue, 2006-07-11 at 00:37 +0200, Roman Zippel wrote:
> Hi,
> On Mon, 10 Jul 2006, Pavel Machek wrote:
> > APM can only keep interrupts disabled on non-IBM machines, presumably
> > due to BIOS problems.
> Is it possible to disable the timer interrupt before suspend and just
> reinit the timer afterwards?

The timer interrupt is re-enabled, via the timer_sysclass::resume hook,
while the timekeeping code is re-enabled via the
timekeeping_sysclass::resume hook. The issue being that I'm not sure
there's a defined way to specify the .resume calling order.

The timekeeping_suspended flag is a bit heavy handed, but I think it
might be the safest bet (assuming Mikael finds it works for him).


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-07-11 00:53    [W:0.080 / U:0.196 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site