From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@kernel.org
Subject: [Bug 191451] Host hangs when hyperv/pvspinlock are disabled
Date: Thu, 23 Feb 2017 22:42:18 +0000 [thread overview]
Message-ID: <bug-191451-28872-v75UOnclVG@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-191451-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=191451
--- Comment #2 from uzytkownik2@gmail.com (uzytkownik2@gmail.com) ---
Debugging unrelated issue I noticed that many processes are in uninterruptable
sleep:
# ps aux | awk '$8 ~ /D/{print $0}'
root 742 0.0 0.0 0 0 ? D Feb20 0:00
[kworker/5:255]
root 913 0.0 0.0 0 0 ? D Feb20 0:15
[kworker/3:173]
root 4875 0.0 0.0 0 0 ? Ds Feb21 0:00
[systemd-logind]
root 4890 0.0 0.0 0 0 ? D Feb21 0:00
[kworker/u24:3]
root 5048 0.0 0.0 0 0 ? D Feb21 0:00 [kworker/6:1]
root 5238 0.0 0.0 62512 3376 ? DNs Feb21 0:00 (coredump)
root 5593 0.0 0.0 62512 3376 ? DNs Feb22 0:00 (coredump)
root 5715 0.0 0.0 62512 3376 ? DNs Feb22 0:00 (coredump)
root 24545 0.0 0.0 0 0 ? DN Feb22 0:00 [scanelf]
root 24556 0.0 0.0 62512 3504 ? DNs Feb22 0:00 (coredump)
root 27852 0.0 0.0 0 0 ? D Feb20 0:02 [kworker/9:4]
root 32672 0.0 0.0 0 0 ? D Feb20 0:20
[kworker/7:232]
# uptime
14:40:15 up 7 days, 15:26, 2 users, load average: 0.00, 0.00, 0.00
The VFIO might be a missed hint which just makes it appear quicker.
In kernel log I have messages such as:
[660318.170055] rcu_sched kthread starved for 6305 jiffies! g933470 c933469
f0x0 RCU_GP_WAIT_FQS(3) ->state=0x1
[660318.170055] rcu_sched S14864 7 2 0x00000000
[660318.170055] ffff970f5bf43500 ffff970f5f5162c0 ffff970b17a16cc0
ffff970f5bef4f80
[660318.170055] ffff970f5f5162c0 ffffa66283197d88 ffffffffa1e673d8
ffffa66283197dd0
[660318.170055] 000000005f50eb00 0000000000000286 ffff970f5bef4f80
ffffa66283197dd0
[660318.170055] Call Trace:
[660318.170055] [<ffffffffa1e673d8>] ? __schedule+0x1f8/0x650
[660318.170055] [<ffffffffa1e67861>] schedule+0x31/0x80
[660318.170055] [<ffffffffa1e6a6d5>] schedule_timeout+0x155/0x2f0
[660318.170055] [<ffffffffa18da01d>] ? rcu_report_qs_rnp+0xed/0x180
[660318.170055] [<ffffffffa18e0580>] ? del_timer_sync+0x50/0x50
[660318.170055] [<ffffffffa18bf2dc>] ? prepare_to_swait+0x5c/0x90
[660318.170055] [<ffffffffa18dc4d3>] rcu_gp_kthread+0x473/0x7f0
[660318.170055] [<ffffffffa18dc060>] ? call_rcu_sched+0x20/0x20
[660318.170055] [<ffffffffa189fe85>] kthread+0xc5/0xe0
[660318.170055] [<ffffffffa189fdc0>] ? kthread_park+0x60/0x60
[660318.170055] [<ffffffffa1e6bc92>] ret_from_fork+0x22/0x30
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2017-02-23 22:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-29 6:06 [Bug 191451] New: Host hangs when hyperv/pvspinlock are disabled bugzilla-daemon
2017-02-13 5:31 ` [Bug 191451] " bugzilla-daemon
2017-02-23 22:42 ` bugzilla-daemon [this message]
2017-03-16 6:44 ` bugzilla-daemon
2017-09-14 1:52 ` bugzilla-daemon
2017-10-07 2:04 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-191451-28872-v75UOnclVG@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.