Hi!
> I don't think it's HPET timer, or CONFIG_SMP. It also looks like your
> local APIC timer is working.
>
> If you have a serial console, you can put one letter printks in the
> code. Can you check if you ever get to smp_apic_timer_interrupt()?
> That's where you should get to after the sleep, and that calls the
> PIT timer interrupt to get it going again. I'm thinking that you'll
> get to smp_apic_timer_interrupt(), but once therebut function
> dyn_tick->interrupt(0, NULL, regs) never gets called.
dyn_tick->interrupt *is* being called:
Feb 2 14:53:41 amd last message repeated 36 times
Feb 2 14:53:41 amd postfix/postfix-script: starting the Postfix mail
system
Feb 2 14:53:41 amd kernel: dyn_tick->interrupt
Feb 2 14:53:41 amd kernel: dyn_tick->interrupt
Feb 2 14:53:41 amd postfix/master[1301]: daemon started -- version
2.1.5
Feb 2 14:53:41 amd kernel: dyn_tick->interrupt
Feb 2 14:53:45 amd last message repeated 30 times
Feb 2 14:53:45 amd log1n[1220]: ROOT LOGIN on `tty8'
Feb 2 14:53:45 amd kernel: dyn_tick->interrupt
Feb 2 14:54:16 amd last message repeated 228 times
I'll try turning off CONFIG_PREEMPT...
Pavel
--
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
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/
