* Thomas Gleixner ([EMAIL PROTECTED]) wrote: > Hmm, that's even more strange. Can you please provide the output > of /proc/timer_list ?
It's quite normal looking, and a printk in clockevents_set_mode looks normal too. [EMAIL PROTECTED] ~]$ cat /proc/timer_list Timer List Version: v0.3 HRTIMER_MAX_CLOCK_BASES: 2 now at 313565930359 nsecs cpu: 0 clock 0: .index: 0 .resolution: 4000250 nsecs .get_time: ktime_get_real active timers: clock 1: .index: 1 .resolution: 4000250 nsecs .get_time: ktime_get active timers: #0: <ffff810150223e38>, hrtimer_wakeup, S:01 # expires at 313700587872 nsecs [in 134657513 nsecs] #1: <ffff810150223e38>, it_real_fn, S:01 # expires at 332024684987 nsecs [in 18458754628 nsecs] #2: <ffff810150223e38>, hrtimer_wakeup, S:01 # expires at 337032779067 nsecs [in 23466848708 nsecs] #3: <ffff810150223e38>, hrtimer_wakeup, S:01 # expires at 1851212334864 nsecs [in 1537646404505 nsecs] #4: <ffff810150223e38>, it_real_fn, S:01 # expires at 3635317355388 nsecs [in 3321751425029 nsecs] #5: <ffff810150223e38>, it_real_fn, S:01 # expires at 3635630194993 nsecs [in 3322064264634 nsecs] cpu: 1 clock 0: .index: 0 .resolution: 4000250 nsecs .get_time: ktime_get_real active timers: clock 1: .index: 1 .resolution: 4000250 nsecs .get_time: ktime_get active timers: cpu: 2 clock 0: .index: 0 .resolution: 4000250 nsecs .get_time: ktime_get_real active timers: clock 1: .index: 1 .resolution: 4000250 nsecs .get_time: ktime_get active timers: cpu: 3 clock 0: .index: 0 .resolution: 4000250 nsecs .get_time: ktime_get_real active timers: clock 1: .index: 1 .resolution: 4000250 nsecs .get_time: ktime_get active timers: #0: <ffff810150223e38>, it_real_fn, S:01 # expires at 313558625026 nsecs [in -7305333 nsecs] #1: <ffff810150223e38>, hrtimer_wakeup, S:01 # expires at 369334850252 nsecs [in 55768919893 nsecs] #2: <ffff810150223e38>, it_real_fn, S:01 # expires at 3936979059363 nsecs [in 3623413129004 nsecs] Tick Device: mode: 0 Clock Event Device: hpet max_delta_ns: 85899346200 min_delta_ns: 1920 mult: 107374182 shift: 32 mode: 2 next_event: 9223372036854775807 nsecs set_next_event: hpet_next_event set_mode: hpet_set_mode event_handler: tick_handle_periodic_broadcast tick_broadcast_mask: 00000001 Tick Device: mode: 0 Clock Event Device: lapic max_delta_ns: 671088687 min_delta_ns: 1200 mult: 53687081 shift: 32 mode: 1 next_event: 0 nsecs set_next_event: lapic_next_event set_mode: lapic_timer_setup event_handler: tick_handle_periodic Tick Device: mode: 0 Clock Event Device: lapic max_delta_ns: 671088687 min_delta_ns: 1200 mult: 53687081 shift: 32 mode: 2 next_event: 0 nsecs set_next_event: lapic_next_event set_mode: lapic_timer_setup event_handler: tick_handle_periodic Tick Device: mode: 0 Clock Event Device: lapic max_delta_ns: 671088687 min_delta_ns: 1200 mult: 53687081 shift: 32 mode: 2 next_event: 0 nsecs set_next_event: lapic_next_event set_mode: lapic_timer_setup event_handler: tick_handle_periodic Tick Device: mode: 0 Clock Event Device: lapic max_delta_ns: 671088687 min_delta_ns: 1200 mult: 53687081 shift: 32 mode: 2 next_event: 0 nsecs set_next_event: lapic_next_event set_mode: lapic_timer_setup event_handler: tick_handle_periodic [EMAIL PROTECTED] ~]$ grep -e 0: -e LOC: /proc/interrupts 0: 72 2 58 36008 IO-APIC-edge timer LOC: 36655 36772 36725 36683 [EMAIL PROTECTED] ~]$ grep -e 0: -e LOC: /proc/interrupts 0: 72 2 58 36165 IO-APIC-edge timer LOC: 36812 36929 36882 36840 [EMAIL PROTECTED] ~]$ grep -e 0: -e LOC: /proc/interrupts 0: 72 2 58 36297 IO-APIC-edge timer LOC: 36944 37061 37014 36972 [EMAIL PROTECTED] ~]$ grep -e 0: -e LOC: /proc/interrupts 0: 72 2 58 36424 IO-APIC-edge timer LOC: 37071 37188 37141 37099 - 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/
