Displaying 2 results from an estimated 2 matches for "coretemp_add_cor".
Did you mean:
coretemp_add_core
2017 Dec 14
1
Xen PV DomU running Kernel 4.14.5-1.el7.elrepo.x86_64: xl -v vcpu-set <domU> <val> triggers domU kernel WARNING, then domU becomes unresponsive
...f R12: 0000000000000000
R13: ffff8800069ea000 R14: ffff88007f60a040 R15: 0000000000000000
FS: 00007f685ca0a700(0000) GS:ffff88007f600000(0000)
knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: 0000000000000010 CR3: 000000000683a000 CR4: 0000000000042660
Call Trace:
? coretemp_add_core+0x50/0x50 [coretemp]
cpuhp_invoke_callback+0xe9/0x700
? put_prev_task_fair+0x26/0x40
? __schedule+0x2d0/0x6e0
? __wake_up_common+0x84/0x130
? __wake_up_common+0x84/0x130
cpuhp_thread_fun+0xee/0x170
smpboot_thread_fn+0x10c/0x160
? smpboot_create_threads+0x80/0x80
kthread+0x10a/0x1...
2017 Dec 12
5
Xen PV DomU running Kernel 4.14.5-1.el7.elrepo.x86_64: xl -v vcpu-set <domU> <val> triggers domU kernel WARNING, then domU becomes unresponsive
Has anyone seen this recently? I couldn't replicate it on:
- CentOS 6 running kernel-2.6.32-696.16.1.el6.x86_64,
kernel-lt-4.4.105-1.el6.elrepo.x86_64
- CentOS 7 running 4.9.67-1.el7.centos.x86_64
But I can replicate it consistently running "xl -v vcpu-set <domU>
<val>" on:
- CentOS 6 running 4.14.5-1.el6.elrepo.x86_64
- CentOS 7 running 4.14.5-1.el7.elrepo.x86_64