I found that those guests that have not even a login on "virsh console"
still have the timing issue. They just crash early. Dumping and
analyzing those who do not respond to ssh&console at all identified an
early stall detect.
[ 448.448935] INFO: rcu_sched self-detected stall on CPU
[ 448.450095] 0-...: (2 ticks this GP) idle=791/140000000000001/0
softirq=3095/3095 fqs=0
[ 448.450857] (t=104564 jiffies g=102 c=101 q=369)
[ 448.451640] rcu_sched kthread starved for 104564 jiffies! g102 c101 f0x0 s3
->state=0x1
[ 448.452430] Task dump for CPU 0:
[ 448.453201] systemd-udevd R running task 0 440 1 0x00040004
[ 448.453993] Call Trace:
[ 448.454799] [c000000017af79c0] [c0000000000fcac0] sched_show_task+0xe0/0x180
(unreliable)
[ 448.455595] [c000000017af7a30] [c00000000013f9b4]
rcu_dump_cpu_stacks+0xe4/0x150
[ 448.456378] [c000000017af7a80] [c0000000001450e4]
rcu_check_callbacks+0x6b4/0x9b0
[ 448.457131] [c000000017af7bb0] [c00000000014cf48]
update_process_times+0x58/0xa0
[ 448.457870] [c000000017af7be0] [c000000000164638]
tick_sched_handle.isra.6+0x48/0xe0
[ 448.458597] [c000000017af7c20] [c000000000164734] tick_sched_timer+0x64/0xd0
[ 448.459308] [c000000017af7c60] [c00000000014da14]
__hrtimer_run_queues+0x124/0x450
[ 448.460016] [c000000017af7cf0] [c00000000014ea3c]
hrtimer_interrupt+0xec/0x2c0
[ 448.460729] [c000000017af7db0] [c00000000001f5fc]
__timer_interrupt+0x8c/0x290
[ 448.461414] [c000000017af7e00] [c00000000001f9b0] timer_interrupt+0xa0/0xe0
[ 448.462090] [c000000017af7e30] [c000000000002714]
decrementer_common+0x114/0x180
[ 448.463071] NMI watchdog: BUG: soft lockup - CPU#0 stuck for 412s!
[systemd-udevd:440]
[ 448.463755] Modules linked in: ib_iser rdma_cm iw_cm ib_cm ib_sa ib_mad
ib_core ib_addr iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi autofs4
btrfs raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx
xor raid6_pq libcrc32c raid1 raid0 multipath linear hid_generic usbhid hid
[ 448.466967] CPU: 0 PID: 440 Comm: systemd-udevd Not tainted 4.4.0-64-generic
#85-Ubuntu
[ 448.467748] task: c0000000179e9370 ti: c000000017af4000 task.ti:
c000000017af4000
[ 448.468548] NIP: 00003fff9ef23078 LR: 00003fff9ef23060 CTR: 00003fff9ef266ec
[ 448.469343] REGS: c000000017af7ea0 TRAP: 0901 Not tainted
(4.4.0-64-generic)
[ 448.470144] MSR: 800000010280f033 <SF,VEC,VSX,EE,PR,FP,ME,IR,DR,RI,LE> CR:
22042484 XER: 00000000
[ 448.471830] CFAR: 00003fff9ef3dba0 SOFTE: 1
GPR00: 00003fff9ef22e80 00003fffc04f3ff0 00003fff9ef67e00
0000000000000000
GPR04: 0000000051bc1f69 0000000000000000 0000000000000000
fffffffffeff0000
GPR08: 0000000051bc07c0 00003fff9ebb6ff8 0000000000000001
0000000000000007
GPR12: 0000000042024484 00003fff9ef6f9c0
[ 448.476015] NIP [00003fff9ef23078] 0x3fff9ef23078
[ 448.476863] LR [00003fff9ef23060] 0x3fff9ef23060
[ 448.477690] Call Trace:
But I'd still expect this to be a symptom of the broken time.
Please advise how to debug early time init on ppc or - even better - if
you have any thought on what it might be in your opinion?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1668241
Title:
Guests trash time on start, crashing the guest
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1668241/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
