On Sat, 2007-04-07 at 10:12 +0200, Ingo Molnar wrote:
> Subject: [patch] high-res timers: UP resume fix
> From: Ingo Molnar <[email protected]>
>
> Soeren Sonnenburg reported that upon resume he is getting
> this backtrace:
>
> [<c0119637>] smp_apic_timer_interrupt+0x57/0x90
> [<c0142d30>] retrigger_next_event+0x0/0xb0
> [<c0104d30>] apic_timer_interrupt+0x28/0x30
> [<c0142d30>] retrigger_next_event+0x0/0xb0
> [<c0140068>] __kfifo_put+0x8/0x90
> [<c0130fe5>] on_each_cpu+0x35/0x60
> [<c0143538>] clock_was_set+0x18/0x20
> [<c0135cdc>] timekeeping_resume+0x7c/0xa0
> [<c02aabe1>] __sysdev_resume+0x11/0x80
> [<c02ab0c7>] sysdev_resume+0x47/0x80
> [<c02b0b05>] device_power_up+0x5/0x10
>
> it turns out that on UP we mistakenly re-enable interrupts,
> so do the timer retrigger only on the current CPU.
>
> Signed-off-by: Ingo Molnar <[email protected]>
Acked-by: Thomas Gleixner <[email protected]>
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
