[Xen-devel] BUG grant_table.c line 939

["King, Steven R" <steven.r.king@xxxxxxxxx>]

Hi Folks,
After trials and tribulations getting my serial ports in order, I'm
finally able to report on a Xen crash I've been seeing.

I have two domUs that share & map grant references with each other, then
both domUs crash.  Shortly thereafter, Xen crashes too.

With dead domUs, the grant references they once held are left orphaned.
Xen isn't provisioned to mop this up, hence the well placed
BUG(rd==NULL).  Make any sense?  I'd be over my head to submit a patch
for this, so I'm hoping for help.

Thanks,
-steve

I did a pull this morning.

(XEN) (file=grant_table.c, line=936) Grant release (0) ref:(605)
flags:(6) dom:(1)
(XEN) BUG at grant_table.c:939
(XEN) CPU:    0
(XEN) EIP:    e008:[<ff10c67e>] gnttab_release_mappings+0x110/0x34d
(XEN) EFLAGS: 00210282   CONTEXT: hypervisor
(XEN) eax: ff1922d8   ebx: ffbe7080   ecx: 00000000   edx: 00000000
(XEN) esi: 00000007   edi: ff1a3fac   ebp: ff1a3dcc   esp: ff1a3d94
(XEN) cr0: 80050033   cr3: ddd58000
(XEN) ds: e010   es: e010   fs: 0000   gs: 0033   ss: e010   cs: e008
(XEN) Xen stack trace from esp=ff1a3d94:
(XEN)    ff180795 ff18087f 000003ab 00000000 0000025d 00000006 00000001
ff12cd4c
(XEN)    ffbae080 00000000 00000000 0000025d ffbac000 ffbad700 ff1a3dec
ff105a74
(XEN)    ffbae080 ffbae318 00000001 ffbae080 ffbae080 00000000 ff1a3f8c
ff104474
(XEN)    ffbae080 ff1a3edc 00000000 ff117a4b ff1a3fb4 ff1a3e68 ff15d931
00000004
(XEN)    00000003 80000004 80000004 00000004 80000003 80000004 fc455838
00000000
(XEN)    ff1a3fb4 ffbae080 ff15ddf0 80000003 ff1fa690 ff1fa480 ff1fa080
00000000
(XEN)    b0000002 80000004 80000004 80000004 80000003 ff1a3ed8 ff139611
ff1fa088
(XEN)    ff1a3ea8 00000008 80000004 fd8c8298 a0000000 00003902 00000000
fec08030
(XEN)    00000008 ff1a3ea8 fec08030 00000000 fc455830 cd604202 08dff21f
80000004
(XEN)    fec08000 00000006 00003902 00003902 ff1fa080 cd60ffff 08dff21f
03902030
(XEN)    00000000 00000000 00000000 ff1a3ee4 00000009 03000000 00000002
08102424
(XEN)    00000000 081fca4c b78fc9fc 080e7f12 b7b44dfc ffffffff b7c70264
08102424
(XEN)    081d5a40 081fc8f4 b78fca8c 080a9ba7 081fc8f4 b7c72b20 b7c6257c
08074694
(XEN)    b7c773e0 b7c76a44 b78fca3c 08074be5 b7c76a44 081fb970 0000001f
00000000
(XEN)    a5dba235 a5dba1ee b7c9a420 b7f4639c b7b2feec b7b3c2ac 00000002
ff1a9d00
(XEN)    ffffffff ff1a3f88 ff144869 ffffffea ffbe7080 ff1a3fac 00e5c037
ff15d31f
(XEN)    b78fc9c4 deadbeef deadbeef deadbeef deadbeef deadbeef c02ccb6e
00000007
(XEN)    b78fc9c4 081fca50 081fca40 08102424 b7b44e18 ec448000 00000007
00070000
(XEN)    c02ccb6e 00000061 00200246 ec449d38 00000069 0000007b 0000007b
00000000
(XEN)    00000033 00000000 ffbe7080
(XEN) Xen call trace:
(XEN)    [<ff10c67e>] gnttab_release_mappings+0x110/0x34d
(XEN)    [<ff105a74>] domain_kill+0x6d/0xa9
(XEN)    [<ff104474>] do_dom0_op+0x73f/0x16d0
(XEN)    [<ff15d31f>] hypercall+0x8f/0xaf
(XEN)
(XEN)
(XEN) ****************************************
(XEN) Panic on CPU 0:
(XEN) CPU0 FATAL TRAP: vector = 6 (invalid operand)
(XEN) [error_code=0000]
(XEN) ****************************************

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel