From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 93251] qemu-kvm guests randomly hangs after reboot command in guest
Date: Thu, 19 Mar 2015 20:01:11 +0000 [thread overview]
Message-ID: <bug-93251-28872-QejR9HRbcb@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-93251-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=93251
Thomas Stein <himbeere@meine-oma.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |himbeere@meine-oma.de
--- Comment #3 from Thomas Stein <himbeere@meine-oma.de> ---
Hello.
I have the very same error on my kvm machines.
Mar 19 20:35:07 hn kernel: qemu-system-x86: page allocation failure: order:4,
mode:0x40d0
Mar 19 20:35:07 hn kernel: CPU: 0 PID: 7029 Comm: qemu-system-x86 Not tainted
3.19.2 #1
Mar 19 20:35:07 hn kernel: Hardware name: System manufacturer System Product
Name/P8B WS, BIOS 0802 08/29/
2011
Mar 19 20:35:07 hn kernel: 0000000000000000 ffff88038857f9d8 ffffffff81711fce
0000000000000001
Mar 19 20:35:07 hn kernel: 00000000000040d0 ffff88038857fa68 ffffffff81108d4e
ffff88042fded838
Mar 19 20:35:07 hn kernel: 0000000000000380 00000000000003c0 0000000000000286
fffffff00000000f
Mar 19 20:35:07 hn kernel: Call Trace:
Mar 19 20:35:07 hn kernel: [<ffffffff81711fce>] dump_stack+0x45/0x57
Mar 19 20:35:07 hn kernel: [<ffffffff81108d4e>] warn_alloc_failed+0xce/0x120
Mar 19 20:35:07 hn kernel: [<ffffffff8110bc24>]
__alloc_pages_nodemask+0x614/0x850
Mar 19 20:35:07 hn kernel: [<ffffffff8140da5f>] ?
megasas_fire_cmd_gen2+0x3f/0x50
Mar 19 20:35:07 hn kernel: [<ffffffff8114783c>] alloc_pages_current+0x8c/0x100
Mar 19 20:35:07 hn kernel: [<ffffffff81108eac>] alloc_kmem_pages+0x2c/0xd0
Mar 19 20:35:07 hn kernel: [<ffffffff811227f3>] kmalloc_order+0x13/0x50
Mar 19 20:35:07 hn kernel: [<ffffffff8112284f>] kmalloc_order_trace+0x1f/0x90
Mar 19 20:35:07 hn kernel: [<ffffffff811511b9>]
__kmalloc_track_caller+0x159/0x250
Mar 19 20:35:07 hn kernel: [<ffffffff8111ce1b>] kmemdup+0x1b/0x40
Mar 19 20:35:07 hn kernel: [<ffffffffa0004aab>]
__kvm_set_memory_region+0x1eb/0x950 [kvm]
Mar 19 20:35:07 hn kernel: [<ffffffff8115aca0>] ?
mem_cgroup_uncharge_swap+0x20/0xa0
Mar 19 20:35:07 hn kernel: [<ffffffff8113e3a8>] ? swap_entry_free+0x198/0x310
Mar 19 20:35:07 hn kernel: [<ffffffffa000523a>]
kvm_set_memory_region+0x2a/0x50 [kvm]
Mar 19 20:35:07 hn kernel: [<ffffffffa000577f>] kvm_vm_ioctl+0x51f/0x760 [kvm]
Mar 19 20:35:07 hn kernel: [<ffffffff81170d30>] do_vfs_ioctl+0x2e0/0x4e0
Mar 19 20:35:07 hn kernel: [<ffffffff8107666f>] ? vtime_account_user+0x3f/0x60
Mar 19 20:35:07 hn kernel: [<ffffffff81170fb1>] SyS_ioctl+0x81/0xa0
Mar 19 20:35:07 hn kernel: [<ffffffff81719ff2>] system_call_fastpath+0x12/0x17
Is anyone working on this?
thanks and best regards
t.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2015-03-19 20:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-14 12:46 [Bug 93251] New: qemu-kvm guests randomly hangs after reboot command in guest bugzilla-daemon
2015-02-14 12:52 ` [Bug 93251] " bugzilla-daemon
2015-02-25 22:49 ` bugzilla-daemon
2015-03-19 20:01 ` bugzilla-daemon [this message]
2015-03-19 21:31 ` bugzilla-daemon
2015-03-19 22:25 ` bugzilla-daemon
2015-03-20 9:16 ` bugzilla-daemon
2015-03-20 9:28 ` bugzilla-daemon
2015-03-20 10:04 ` bugzilla-daemon
2015-03-20 10:30 ` bugzilla-daemon
2015-03-26 14:51 ` bugzilla-daemon
2015-03-26 15:13 ` bugzilla-daemon
2015-03-27 10:00 ` bugzilla-daemon
2015-03-27 15:08 ` bugzilla-daemon
2015-03-27 15:25 ` bugzilla-daemon
2015-04-14 13:57 ` 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-93251-28872-QejR9HRbcb@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.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.