* [Bug 68051] Kernel stack trace when attempt to boot "kernel BUG at mm/page_alloc.c:2788"
2014-01-02 14:35 [Bug 68051] New: Kernel stack trace when attempt to boot "kernel BUG at mm/page_alloc.c:2788" bugzilla-daemon
@ 2014-01-02 14:36 ` bugzilla-daemon
2014-01-02 14:37 ` bugzilla-daemon
` (5 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: bugzilla-daemon @ 2014-01-02 14:36 UTC (permalink / raw)
To: kvm
https://bugzilla.kernel.org/show_bug.cgi?id=68051
--- Comment #1 from Kashyap Chamarthy <kashyap.cv@gmail.com> ---
Created attachment 120651
--> https://bugzilla.kernel.org/attachment.cgi?id=120651&action=edit
Complete stdout of dmesg
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 8+ messages in thread* [Bug 68051] Kernel stack trace when attempt to boot "kernel BUG at mm/page_alloc.c:2788"
2014-01-02 14:35 [Bug 68051] New: Kernel stack trace when attempt to boot "kernel BUG at mm/page_alloc.c:2788" bugzilla-daemon
2014-01-02 14:36 ` [Bug 68051] " bugzilla-daemon
@ 2014-01-02 14:37 ` bugzilla-daemon
2014-01-02 14:52 ` [Bug 68051] Kernel stack trace when attempt to boot into 3.13.0-0.rc6.git0.1 results in " bugzilla-daemon
` (4 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: bugzilla-daemon @ 2014-01-02 14:37 UTC (permalink / raw)
To: kvm
https://bugzilla.kernel.org/show_bug.cgi?id=68051
--- Comment #2 from Kashyap Chamarthy <kashyap.cv@gmail.com> ---
Created attachment 120661
--> https://bugzilla.kernel.org/attachment.cgi?id=120661&action=edit
Complete stdout of dmidecode
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 8+ messages in thread* [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"
2014-01-02 14:35 [Bug 68051] New: Kernel stack trace when attempt to boot "kernel BUG at mm/page_alloc.c:2788" bugzilla-daemon
2014-01-02 14:36 ` [Bug 68051] " bugzilla-daemon
2014-01-02 14:37 ` bugzilla-daemon
@ 2014-01-02 14:52 ` bugzilla-daemon
2014-01-02 18:22 ` bugzilla-daemon
` (3 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: bugzilla-daemon @ 2014-01-02 14:52 UTC (permalink / raw)
To: kvm
https://bugzilla.kernel.org/show_bug.cgi?id=68051
Kashyap Chamarthy <kashyap.cv@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Summary|Kernel stack trace when |Kernel stack trace when
|attempt to boot "kernel BUG |attempt to boot into
|at mm/page_alloc.c:2788" |3.13.0-0.rc6.git0.1 results
| |in "kernel BUG at
| |mm/page_alloc.c:2788"
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 8+ messages in thread* [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"
2014-01-02 14:35 [Bug 68051] New: Kernel stack trace when attempt to boot "kernel BUG at mm/page_alloc.c:2788" bugzilla-daemon
` (2 preceding siblings ...)
2014-01-02 14:52 ` [Bug 68051] Kernel stack trace when attempt to boot into 3.13.0-0.rc6.git0.1 results in " bugzilla-daemon
@ 2014-01-02 18:22 ` bugzilla-daemon
2014-01-08 21:13 ` bugzilla-daemon
` (2 subsequent siblings)
6 siblings, 0 replies; 8+ messages in thread
From: bugzilla-daemon @ 2014-01-02 18:22 UTC (permalink / raw)
To: kvm
https://bugzilla.kernel.org/show_bug.cgi?id=68051
--- Comment #3 from Kashyap Chamarthy <kashyap.cv@gmail.com> ---
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 force
power-off the guest via `virsh`), and I had to reboot the host.
$ virsh destroy ostack-compute
error: Failed to destroy domain 3
error: Failed to terminate process 3152 with SIGKILL: Device or resource 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:
=============
.
.
.
2014-01-02 12:42:54.012+0000: 27462: debug : virKeepAliveCheckMessage:395 : Got
keepalive request from client 0x7f4dfaca75d0
2014-01-02 12:42:54.012+0000: 27462: debug : virNetMessageNew:44 :
msg=0x7f4dfaca7770 tracked=0
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=0x7f4dfaca78c0 client=0x7f4dfaca75d0 prog=1801807216
vers=1 proc=2
2014-01-02 12:42:54.012+0000: 27462: debug : virNetClientQueueNonBlocking:1926
: RPC_CLIENT_MSG_TX_QUEUE: client=0x7f4dfaca75d0 len=28 prog=1801807216 vers=1
proc=2 type=2 status=0 serial=0
2014-01-02 12:42:54.012+0000: 27462: debug : virNetClientCallNew:1905 : New
call 0x7f4dfaca7ae0: msg=0x7f4dfaca7770, expectReply=0, nonBlock=1
2014-01-02 12:42:54.012+0000: 27462: debug : virNetMessageClear:55 :
msg=0x7f4dfaca7638 nfds=0
2014-01-02 12:42:54.012+0000: 27462: debug :
virNetClientIOEventLoopRemoveDone:1379 : Removing completed call 0x7f4dfaca7ae0
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:1123 :
RPC_CLIENT_MSG_RX: client=0x7f4dfaca75d0 len=28 prog=1801807216 vers=1 proc=1
type=2 status=0 serial=0
2014-01-02 12:42:59.172+0000: 27462: debug : virKeepAliveCheckMessage:374 :
ka=0x7f4dfaca78c0, client=0x7f4dfaca75d0, msg=0x7f4dfaca7638
2014-01-02 12:42:59.172+0000: 27462: debug : virKeepAliveCheckMessage:391 :
RPC_KEEPALIVE_RECEIVED: ka=0x7f4dfaca78c0 client=0x7f4dfaca75d0 prog=1801807216
vers=1 proc=1
.
.
.
=============
And:
$ ps -ef | grep qemu
qemu 3152 1 30 2013 ? 13:30:42 [qemu-system-x86] <defunct>
$ pstree 3152
qemu-system-x86───{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
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 8+ messages in thread* [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"
2014-01-02 14:35 [Bug 68051] New: Kernel stack trace when attempt to boot "kernel BUG at mm/page_alloc.c:2788" bugzilla-daemon
` (3 preceding siblings ...)
2014-01-02 18:22 ` bugzilla-daemon
@ 2014-01-08 21:13 ` bugzilla-daemon
2014-06-20 4:05 ` bugzilla-daemon
2014-06-20 4:47 ` bugzilla-daemon
6 siblings, 0 replies; 8+ messages in thread
From: bugzilla-daemon @ 2014-01-08 21:13 UTC (permalink / raw)
To: kvm
https://bugzilla.kernel.org/show_bug.cgi?id=68051
Marcelo Tosatti <mtosatti@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mtosatti@redhat.com
--- Comment #4 from Marcelo Tosatti <mtosatti@redhat.com> ---
Fixed by http://comments.gmane.org/gmane.comp.emulators.kvm.devel/117837.
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 8+ messages in thread* [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"
2014-01-02 14:35 [Bug 68051] New: Kernel stack trace when attempt to boot "kernel BUG at mm/page_alloc.c:2788" bugzilla-daemon
` (4 preceding siblings ...)
2014-01-08 21:13 ` bugzilla-daemon
@ 2014-06-20 4:05 ` bugzilla-daemon
2014-06-20 4:47 ` bugzilla-daemon
6 siblings, 0 replies; 8+ messages in thread
From: bugzilla-daemon @ 2014-06-20 4:05 UTC (permalink / raw)
To: kvm
https://bugzilla.kernel.org/show_bug.cgi?id=68051
xerofoify@gmail.com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |xerofoify@gmail.com
--- Comment #5 from xerofoify@gmail.com ---
Seems fixed after reading the comments here. Can you close this
as the bug seems to be close still in June of 2014.
Thanks Nick
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 8+ messages in thread* [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"
2014-01-02 14:35 [Bug 68051] New: Kernel stack trace when attempt to boot "kernel BUG at mm/page_alloc.c:2788" bugzilla-daemon
` (5 preceding siblings ...)
2014-06-20 4:05 ` bugzilla-daemon
@ 2014-06-20 4:47 ` bugzilla-daemon
6 siblings, 0 replies; 8+ messages in thread
From: bugzilla-daemon @ 2014-06-20 4:47 UTC (permalink / raw)
To: kvm
https://bugzilla.kernel.org/show_bug.cgi?id=68051
Kashyap Chamarthy <kashyap.cv@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |CODE_FIX
--- Comment #6 from Kashyap Chamarthy <kashyap.cv@gmail.com> ---
Thanks Marcelo, Xerofoify. I missed to update this. Yes, this can be closed.
With current Fedora Rawhide kernels (3.15.0-0.rc7.git4.2.fc21.x86_64) works in
my current nested environment.
For reference, here's the associated Fedora Kernel bug (that's closed) --
https://bugzilla.redhat.com/show_bug.cgi?id=1047892
--
You are receiving this mail because:
You are watching the assignee of the bug.
^ permalink raw reply [flat|nested] 8+ messages in thread