From mboxrd@z Thu Jan 1 00:00:00 1970
From: bugzilla-daemon@bugzilla.kernel.org
Subject: [Bug 68051] Kernel stack trace when attempt to boot into
3.13.0-0.rc6.git0.1 results in "kernel BUG at mm/page_alloc.c:2788"
Date: Thu, 02 Jan 2014 18:22:37 +0000
Message-ID:
References:
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: QUOTED-PRINTABLE
To: kvm@vger.kernel.org
Return-path:
Received: from mail.kernel.org ([198.145.19.201]:36854 "EHLO mail.kernel.org"
rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
id S1751990AbaABSWk convert rfc822-to-8bit (ORCPT
); Thu, 2 Jan 2014 13:22:40 -0500
Received: from mail.kernel.org (localhost [127.0.0.1])
by mail.kernel.org (Postfix) with ESMTP id 20EBF20165
for ; Thu, 2 Jan 2014 18:22:39 +0000 (UTC)
Received: from bugzilla1.web.kernel.org (bugzilla1.web.kernel.org [172.20.200.51])
by mail.kernel.org (Postfix) with ESMTP id 64EE62015A
for ; Thu, 2 Jan 2014 18:22:37 +0000 (UTC)
In-Reply-To:
Sender: kvm-owner@vger.kernel.org
List-ID:
https://bugzilla.kernel.org/show_bug.cgi?id=3D68051
--- Comment #3 from Kashyap Chamarthy ---
I should add some more context: I noticed this issue when I found an
un-killable defunct qemu process (I ended up with it when I tried to fo=
rce
power-off the guest via `virsh`), and I had to reboot the host.
$ virsh destroy ostack-compute=20
error: Failed to destroy domain 3
error: Failed to terminate process 3152 with SIGKILL: Device or resou=
rce busy
NOTE - The disk image is *not* on NFS mount. It's on local disk:
$ virsh domblklist ostack-compute
Target Source
------------------------------------------------
vda /home/kashyap/vmimages/ostack-compute.qcow2
Try to destroy the guest again, with LIBVIRT_DEBUG enabled, that's what=
I see
in a loop:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
=2E
=2E
=2E
2014-01-02 12:42:54.012+0000: 27462: debug : virKeepAliveCheckMessage:3=
95 : Got
keepalive request from client 0x7f4dfaca75d0
2014-01-02 12:42:54.012+0000: 27462: debug : virNetMessageNew:44 :
msg=3D0x7f4dfaca7770 tracked=3D0
2014-01-02 12:42:54.012+0000: 27462: debug :
virNetMessageEncodePayloadEmpty:479 : Encode length as 28
2014-01-02 12:42:54.012+0000: 27462: debug : virKeepAliveMessage:101 : =
Sending
keepalive response to client 0x7f4dfaca75d0
2014-01-02 12:42:54.012+0000: 27462: debug : virKeepAliveMessage:104 :
RPC_KEEPALIVE_SEND: ka=3D0x7f4dfaca78c0 client=3D0x7f4dfaca75d0 prog=3D=
1801807216
vers=3D1 proc=3D2
2014-01-02 12:42:54.012+0000: 27462: debug : virNetClientQueueNonBlocki=
ng:1926
: RPC_CLIENT_MSG_TX_QUEUE: client=3D0x7f4dfaca75d0 len=3D28 prog=3D1801=
807216 vers=3D1
proc=3D2 type=3D2 status=3D0 serial=3D0
2014-01-02 12:42:54.012+0000: 27462: debug : virNetClientCallNew:1905 :=
New
call 0x7f4dfaca7ae0: msg=3D0x7f4dfaca7770, expectReply=3D0, nonBlock=3D=
1
2014-01-02 12:42:54.012+0000: 27462: debug : virNetMessageClear:55 :
msg=3D0x7f4dfaca7638 nfds=3D0
2014-01-02 12:42:54.012+0000: 27462: debug :
virNetClientIOEventLoopRemoveDone:1379 : Removing completed call 0x7f4d=
faca7ae0
2014-01-02 12:42:59.172+0000: 27462: debug : virNetMessageDecodeLength:=
149 :
Got length, now need 28 total (24 more)
2014-01-02 12:42:59.172+0000: 27462: debug : virNetClientCallDispatch:1=
123 :
RPC_CLIENT_MSG_RX: client=3D0x7f4dfaca75d0 len=3D28 prog=3D1801807216 v=
ers=3D1 proc=3D1
type=3D2 status=3D0 serial=3D0
2014-01-02 12:42:59.172+0000: 27462: debug : virKeepAliveCheckMessage:3=
74 :
ka=3D0x7f4dfaca78c0, client=3D0x7f4dfaca75d0, msg=3D0x7f4dfaca7638
2014-01-02 12:42:59.172+0000: 27462: debug : virKeepAliveCheckMessage:3=
91 :
RPC_KEEPALIVE_RECEIVED: ka=3D0x7f4dfaca78c0 client=3D0x7f4dfaca75d0 pro=
g=3D1801807216
vers=3D1 proc=3D1
=2E
=2E
=2E
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
And:
$ ps -ef | grep qemu
qemu 3152 1 30 2013 ? 13:30:42 [qemu-system-x86]
$ pstree 3152
qemu-system-x86=E2=94=80=E2=94=80=E2=94=80{qemu-system-x86}
Libvirt & QEMU version on the host:
$ rpm -q libvirt-daemon-kvm qemu-system-x86
libvirt-daemon-kvm-1.2.0-1.fc21.x86_64
qemu-system-x86-1.7.0-3.fc21.x86_64
--=20
You are receiving this mail because:
You are watching the assignee of the bug.