From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 93251] qemu-kvm guests randomly hangs after reboot command in
guest
Date: Thu, 19 Mar 2015 20:01:11 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
To: kvm@vger.kernel.org
Return-path:
Received: from mail.kernel.org ([198.145.29.136]:57438 "EHLO mail.kernel.org"
rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
id S1751107AbbCSUBO (ORCPT );
Thu, 19 Mar 2015 16:01:14 -0400
Received: from mail.kernel.org (localhost [127.0.0.1])
by mail.kernel.org (Postfix) with ESMTP id 4279B20532
for ; Thu, 19 Mar 2015 20:01:13 +0000 (UTC)
Received: from bugzilla2.web.kernel.org (bugzilla2.web.kernel.org [172.20.200.52])
by mail.kernel.org (Postfix) with ESMTP id 7C88020523
for ; Thu, 19 Mar 2015 20:01:11 +0000 (UTC)
In-Reply-To:
Sender: kvm-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=93251
Thomas Stein changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |himbeere@meine-oma.de
--- Comment #3 from Thomas Stein ---
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: [] dump_stack+0x45/0x57
Mar 19 20:35:07 hn kernel: [] warn_alloc_failed+0xce/0x120
Mar 19 20:35:07 hn kernel: []
__alloc_pages_nodemask+0x614/0x850
Mar 19 20:35:07 hn kernel: [] ?
megasas_fire_cmd_gen2+0x3f/0x50
Mar 19 20:35:07 hn kernel: [] alloc_pages_current+0x8c/0x100
Mar 19 20:35:07 hn kernel: [] alloc_kmem_pages+0x2c/0xd0
Mar 19 20:35:07 hn kernel: [] kmalloc_order+0x13/0x50
Mar 19 20:35:07 hn kernel: [] kmalloc_order_trace+0x1f/0x90
Mar 19 20:35:07 hn kernel: []
__kmalloc_track_caller+0x159/0x250
Mar 19 20:35:07 hn kernel: [] kmemdup+0x1b/0x40
Mar 19 20:35:07 hn kernel: []
__kvm_set_memory_region+0x1eb/0x950 [kvm]
Mar 19 20:35:07 hn kernel: [] ?
mem_cgroup_uncharge_swap+0x20/0xa0
Mar 19 20:35:07 hn kernel: [] ? swap_entry_free+0x198/0x310
Mar 19 20:35:07 hn kernel: []
kvm_set_memory_region+0x2a/0x50 [kvm]
Mar 19 20:35:07 hn kernel: [] kvm_vm_ioctl+0x51f/0x760 [kvm]
Mar 19 20:35:07 hn kernel: [] do_vfs_ioctl+0x2e0/0x4e0
Mar 19 20:35:07 hn kernel: [] ? vtime_account_user+0x3f/0x60
Mar 19 20:35:07 hn kernel: [] SyS_ioctl+0x81/0xa0
Mar 19 20:35:07 hn kernel: [] 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.