On Sun, 14 Aug 2005, Pavel Machek wrote: > > Ok perhaps on the resume side instead. When trying to resume can you try > > booting with 'dyntick=disable'. Note this isn't meant to be a long term fix > > but once we figure out where the problem is we should be able to code > > around > > it. > > Can you reproduce it using plain swsusp? > > We probably need more carefull suspend/resume support on timer with dyntick > enabled. > > With vanilla, timer just ticks on constant rate; no state to save. > With dyntick, however...
Why not just set it to a fixed frequency, suspend and then on boot resume to a fixed frequency and let the timer tick code eventually switch back. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
