[DE] Kernel Warning: NO_HZ FULL will not work with unstable sched clock

[ralfi]

Kernel 64 towo 3.14.4 bringt folgende Warnung

Jun 11 10:39:51 kvmtest kernel: [    1.177404] WARNING: CPU: 2 PID: 12 at /tmp/buildd/linux-siduction-3.14/debian/build/source_amd64_none/kernel/time/tick-sched.c:188 can_stop_full_tick+0x84/0x90()
Jun 11 10:39:51 kvmtest kernel: [    1.177946] NO_HZ FULL will not work with unstable sched clock
Jun 11 10:39:51 kvmtest kernel: [    1.177992] Modules linked in:
Jun 11 10:39:51 kvmtest kernel: [    1.178436] CPU: 2 PID: 12 Comm: rcuop/0 Not tainted 3.14-4.towo-siduction-amd64 #1
Jun 11 10:39:51 kvmtest kernel: [    1.178805] Hardware name: FUJITSU CELSIUS R930/D3118-A2, BIOS V4.6.5.4 R1.5.0 for D3118-A2x 10/14/2013
Jun 11 10:39:51 kvmtest kernel: [    1.179176]  0000000000000003 ffffffff8138e643 ffff88185f883f28 ffffffff81043fa5
Jun 11 10:39:51 kvmtest kernel: [    1.179701]  ffffffff8108f457 ffff88185f88eb30 ffff88185f883f78 ffff88185f80e2f0
Jun 11 10:39:51 kvmtest kernel: [    1.180228]  ffff88303a4051d0 ffffffff81044001 ffffffff814fa8f5 ffffffff00000018
Jun 11 10:39:51 kvmtest kernel: [    1.180308] Call Trace:
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  <IRQ>  [<ffffffff8138e643>] ? dump_stack+0x4a/0x75
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff81043fa5>] ? warn_slowpath_common+0x6f/0x84
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff8108f457>] ? can_stop_full_tick+0x84/0x90
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff81044001>] ? warn_slowpath_fmt+0x47/0x49
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff810676f8>] ? account_system_time+0xfc/0x115
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff8108f457>] ? can_stop_full_tick+0x84/0x90
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff8108fd80>] ? tick_nohz_irq_exit+0x5d/0x76
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff81047891>] ? irq_exit+0xb2/0xb8
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff8139495d>] ? irq_work_interrupt+0x6d/0x80
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  <EOI>  [<ffffffff81060953>] ? mmdrop+0xd/0x1c
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff81074b9a>] ? arch_local_irq_restore+0x2/0x8
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff81392a50>] ? _raw_spin_unlock_irqrestore+0xc/0x28
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff81084844>] ? rcu_nocb_kthread+0x138/0x254
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff81071883>] ? finish_wait+0x60/0x60
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff8108470c>] ? rcu_start_future_gp+0xff/0xff
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff8105ada5>] ? kthread+0x9e/0xa6
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff81010a6c>] ? paravirt_read_tsc+0x5/0x8
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff8105ad07>] ? __kthread_parkme+0x55/0x55
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff813937cc>] ? ret_from_fork+0x7c/0xb0
Jun 11 10:39:51 kvmtest kernel: [    1.180308]  [<ffffffff8105ad07>] ? __kthread_parkme+0x55/0x55
Jun 11 10:39:51 kvmtest kernel: [    1.180308] ---[ end trace 079ebe57ec05f63e ]---

Nach kurzem Gucken scheint das nicht so tragisch zu sein und die Kiste funzt auch sehr gut aber es wär halt schön wenns nicht mehr auftreten würde. Was bedeutet diese Warnung?

[towo]

Mal abgesehen davon, daß Du mind. 3.14.6 einsetzen solltest, da alles vorher von CVE-2014-3153 betroffen ist, bei welcher Aktion kommt der Trace?

Außerdem wäre ein inxi -v3 nicht schlecht.