I noticed that when you kill xenstored in xen-unstable.hg 8758, it will
take down all of domain 0. Killing xenstored is probably not the smartest
thing to do, but it shouldn''t take down dom0.
Leendert
Eeek! page_mapcount(page) went negative! (-1)
page->flags = 414
page->count = 1
page->mapping = 00000000
------------[ cut here ]------------
kernel BUG at mm/rmap.c:555!
invalid opcode: 0000 [#1]
Modules linked in: video thermal processor fan button battery ac
CPU: 0
EIP: 0061:[<c014ccc9>] Not tainted VLI
EFLAGS: 00010286 (2.6.16-rc2-xen0)
EIP is at page_remove_rmap+0x99/0xb0
eax: ffffffff ebx: c1011bc0 ecx: 00000000 edx: fbfa8000
esi: f3ef6804 edi: f3b5bcec ebp: f3475d8c esp: f3475d80
ds: 007b es: 007b ss: 0069
Process xenstored (pid: 3015, threadinfo=f3474000 task=f3756a70)
Stack: <0>c0452c25 00000000 c1011bc0 f3475df4 c014682b c1011bc0 b7f3a000
038de06
7
00362ec9 00000001 b7f3a000 00000000 00000001 b7f3b000 ffffffff 00000000
c1011bc0 c059b3b0 c0e3dac0 038de067 b7f3afff c0de3b7c b7f3b000 00000000
Call Trace:
[<c010837d>] show_stack_log_lvl+0xcd/0x120
[<c0108530>] show_registers+0x160/0x200
[<c0108815>] die+0xe5/0x240
[<c0108b98>] do_trap+0x98/0xe0
[<c0108eb1>] do_invalid_op+0xa1/0xb0
[<c0107d87>] error_code+0x2b/0x30
[<c014682b>] unmap_vmas+0x29b/0x610
[<c0149c80>] exit_mmap+0x70/0xf0
[<c0119537>] mmput+0x27/0x80
[<c011c77a>] exit_mm+0x6a/0xe0
[<c011d3d8>] do_exit+0xe8/0x830
[<c011db54>] do_group_exit+0x34/0x90
[<c012772d>] get_signal_to_deliver+0x27d/0x510
[<c01074b4>] do_notify_resume+0x94/0x6ec
[<c0107cab>] work_notifysig+0x13/0x18
Code: c7 04 24 0e 2c 45 c0 40 89 44 24 04 e8 d1 f1 fc ff 8b 43 10 c7 04 24 25 2c
45 c0 89 44 24 04 e8 be f1 fc ff eb 87 8b 53 0c eb d2 <0f> 0b 2b 02 ec 2b
45 c0
e9 7b ff ff ff 8d 76 00 8d bc 27 00 00
<0>Fatal exception: panic in 5 seconds
Kernel panic - not syncing: Fatal exception
(XEN) Domain 0 shutdown: rebooting machine.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
Leendert van Doorn wrote:> I noticed that when you kill xenstored in xen-unstable.hg 8758, it will > take down all of domain 0. Killing xenstored is probably not the smartest > thing to do, but it shouldn''t take down dom0.Killing it manually probably isn''t typical, but it certainly get''s killed and triggers this bug at shutdown/reboot. As of yesterday, changeset 8777:581d4a0ac729, this bug is still there. It''s in bugzilla as bug #520: http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=520 Thanks, Paul Larson _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
* Paul Larson (pl@us.ibm.com) wrote:> Leendert van Doorn wrote: > >I noticed that when you kill xenstored in xen-unstable.hg 8758, it will > >take down all of domain 0. Killing xenstored is probably not the smartest > >thing to do, but it shouldn''t take down dom0. > Killing it manually probably isn''t typical, but it certainly get''s > killed and triggers this bug at shutdown/reboot. > > As of yesterday, changeset 8777:581d4a0ac729, this bug is still there. > It''s in bugzilla as bug #520: > http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=520Should be fixed as of cset 8783:c9edeb3bd652 thanks, -chris _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel