[Xen-ia64-devel] save/restore clean up and related bugs

[Isaku Yamahata <yamahata@xxxxxxxxxxxxx>]

Hi.
I debugged domU save/restore and sent out the patches.
There were some bugs which seemed to occur very rarely.
Please test.

- bug 943
  http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=943
  To be honest I saw a similar issue before and I didn't track it down
  at that time.
  But I'm not able to reproduce it at this time.
  What activity causes it? Does this still happen?

- NULL pointer dereference
  I also observed the following kernel panic when a domain is restored.
  It occured very rarely and I wasn't able to reproduce it reliably.

Unable to handle kernel NULL pointer dereference (address 0000000000000000)
swapper[0]: Oops 11012296146944 [1]
Modules linked in:

Pid: 0, CPU 5, comm:              swapper
psr : 0000121008022010 ifs : 800000000000040b ip  : [<a00000010005f0f1>]    Not 
tainted
ip is at handle_IPI+0xf1/0x360
unat: 0000000000000000 pfs : 800000000000040b rsc : 000000000000000b
rnat: 0000000000000000 bsps: 0000000000000000 pr  : 000000000001e9a5
ldrs: 0000000000000000 ccv : 0000000000200000 fpsr: 0009804c0270033f
csd : 0000000000000000 ssd : 0000000000000000
b0  : a0000001000e54d0 b6  : a00000010005f000 b7  : 0000000000000000
f6  : 000000000000000000000 f7  : 000000000000000000000
f8  : 000000000000000000000 f9  : 000000000000000000000
f10 : 000000000000000000000 f11 : 000000000000000000000
r1  : a000000100ba0dd0 r2  : e00000001fe30f44 r3  : 0000000000000001
r8  : 0000000000000001 r9  : 0000000000000000 r10 : 0000000000000000
r11 : 0000000000000001 r12 : e00000001fe37c30 r13 : e00000001fe30000
r14 : 0000000000000000 r15 : 0000000000000015 r16 : 0000000000000015
r17 : 0000000000000000 r18 : 0000000000000010 r19 : a0000001009bd3f0
r20 : e00000001fd54be0 r21 : 0000000000200000 r22 : 0000000000200000
r23 : 0000000000000000 r24 : 0000000000200000 r25 : a0000001008f64c4
r26 : 0000000000000054 r27 : a0000001008f6470 r28 : a0000001008595a0
r29 : 00000000001fffff r30 : 0000000000010100 r31 : 0000000000200000

Call Trace:
 [<a00000010001b1f0>] show_stack+0x50/0xa0
                                sp=e00000001fe377e0 bsp=e00000001fe31388
 [<a00000010001bac0>] show_regs+0x820/0x840
                                sp=e00000001fe379b0 bsp=e00000001fe31340
 [<a000000100041bb0>] die+0x1d0/0x2a0
                                sp=e00000001fe379b0 bsp=e00000001fe31300
 [<a000000100065cf0>] ia64_do_page_fault+0x7b0/0x8a0
                                sp=e00000001fe379d0 bsp=e00000001fe312a0
 [<a000000100068200>] xen_leave_kernel+0x0/0x3e0
                                sp=e00000001fe37a60 bsp=e00000001fe312a0
 [<a00000010005f0f0>] handle_IPI+0xf0/0x360
                                sp=e00000001fe37c30 bsp=e00000001fe31248
 [<a0000001000e54d0>] handle_IRQ_event+0x150/0x220
                                sp=e00000001fe37c30 bsp=e00000001fe31208
 [<a0000001000e56f0>] __do_IRQ+0x150/0x400
                                sp=e00000001fe37c30 bsp=e00000001fe311a8
 [<a0000001003e6a80>] evtchn_do_upcall+0x1c0/0x300
                                sp=e00000001fe37c30 bsp=e00000001fe31100
 [<a000000100067b00>] xen_event_callback+0x380/0x3c0
                                sp=e00000001fe37c30 bsp=e00000001fe31100
 [<a0000001000e54d0>] handle_IRQ_event+0x150/0x220
                                sp=e00000001fe37c30 bsp=e00000001fe31100
 <3>BUG: sleeping function called from invalid context at 
/src1/yamahata/hg/xen/ia64/my150/compile/test-0/xen-ia64-unstable.hg/linux-2.6.18-xen/kernel/rwsem.c:20
in_atomic():1, irqs_disabled():0

Call Trace:
 [<a00000010001b1f0>] show_stack+0x50/0xa0
                                sp=e00000001fe377c0 bsp=e00000001fe31460
 [<a00000010001b270>] dump_stack+0x30/0x60
                                sp=e00000001fe37990 bsp=e00000001fe31448
 [<a0000001000710a0>] __might_sleep+0x2c0/0x2e0
                                sp=e00000001fe37990 bsp=e00000001fe31420
 [<a0000001000c1980>] down_read+0x20/0x60
                                sp=e00000001fe379a0 bsp=e00000001fe31400
 [<a0000001000a9ba0>] blocking_notifier_call_chain+0x20/0x80
                                sp=e00000001fe379a0 bsp=e00000001fe313c0
 [<a0000001000876f0>] profile_task_exit+0x30/0x60
                                sp=e00000001fe379a0 bsp=e00000001fe313a0
 [<a00000010008b110>] do_exit+0x30/0x1400
                                sp=e00000001fe379a0 bsp=e00000001fe31340
 [<a000000100041c60>] die+0x280/0x2a0
                                sp=e00000001fe379b0 bsp=e00000001fe31300
 [<a000000100065cf0>] ia64_do_page_fault+0x7b0/0x8a0
                                sp=e00000001fe379d0 bsp=e00000001fe312a0
 [<a000000100068200>] xen_leave_kernel+0x0/0x3e0
                                sp=e00000001fe37a60 bsp=e00000001fe312a0
 [<a00000010005f0f0>] handle_IPI+0xf0/0x360
                                sp=e00000001fe37c30 bsp=e00000001fe31248
 [<a0000001000e54d0>] handle_IRQ_event+0x150/0x220
                                sp=e00000001fe37c30 bsp=e00000001fe31208
 [<a0000001000e56f0>] __do_IRQ+0x150/0x400
                                sp=e00000001fe37c30 bsp=e00000001fe311a8
 [<a0000001003e6a80>] evtchn_do_upcall+0x1c0/0x300
                                sp=e00000001fe37c30 bsp=e00000001fe31100
 [<a000000100067b00>] xen_event_callback+0x380/0x3c0
                                sp=e00000001fe37c30 bsp=e00000001fe31100
 [<a0000001000e54d0>] handle_IRQ_event+0x150/0x220
                                sp=e00000001fe37c30 bsp=e00000001fe31100
Kernel panic - not syncing: Aiee, killing interrupt handler!

-- 
yamahata

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