* (XEN) domain_crash_sync called from entry.S (ff158e99)
@ 2006-04-11 19:43 Christopher S. Aker
2006-04-20 2:29 ` Christopher S. Aker
0 siblings, 1 reply; 5+ messages in thread
From: Christopher S. Aker @ 2006-04-11 19:43 UTC (permalink / raw)
To: xen-devel
Xen/xen0 as of Sun Apr 9 18:23:16 2006 +0100 9591:81bc9e9fb40d. The
domU kernel is a few days previous to that -- after all of Keir's xvf
kthread updates.
(XEN) domain_crash_sync called from entry.S (ff158e99)
(XEN) Domain 51 (vcpu#1) crashed on cpu#0:
(XEN) ----[ Xen-3.0-unstable Not tainted ]----
(XEN) CPU: 0
(XEN) EIP: 0061:[<c0111df0>]
(XEN) EFLAGS: 00010292 CONTEXT: guest
(XEN) eax: 00000000 ebx: 01649000 ecx: 7ffdf061 edx: 80000000
(XEN) esi: 00000001 edi: c6087030 ebp: c0867fb4 esp: c0867f24
(XEN) cr0: 8005003b cr3: 7fc81000
(XEN) ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0069 cs: 0061
(XEN) Guest stack trace from esp=c0867f24:
(XEN) c0866000 c69dd900 c0111e80 c69dd900 c0468438 c69dd900 c01051fa
00000001
(XEN) c0866000 012193bf 00000000 c0866000 c0866000 00476385 00000000
c011fd55
(XEN) c253267c c2532550 c110a240 f88990d7 00005409 c0866000 f8528476
00005409
(XEN) c69dd580 c0867f9c b7ec2ff4 bfe21920 00000000 c0866000 c0102e47
00000011
(XEN) bfe218fc b7ec2ff4 f578d040 00000000 c0866000 c01051fa b7ec2ff4
00000000
(XEN) 00000000 bfe21920 00000000 bfe21908 000016c2 0000007b 0000007b
00000002
(XEN) b7e366d8 00000073 00000246 bfe218fc 0000007b 2507f000 b7d2115d
...then, very shortly after, in dom0...
Unable to handle kernel NULL pointer dereference at virtual address 00000004
printing eip:
c0161655
07fb5000 -> *pde = 00000001:e33ff001
077ba000 -> *pme = 00000000:00000000
Oops: 0002 [#1]
SMP
Modules linked in:
CPU: 0
EIP: 0061:[<c0161655>] Not tainted VLI
EFLAGS: 00010046 (2.6.16-xen0 #1)
EIP is at cache_alloc_refill+0x185/0x560
eax: c065ed80 ebx: ffffffff ecx: 00000010 edx: 00000000
esi: c7ac5040 edi: 00000002 ebp: c067ee80 esp: c7a75e94
ds: 007b es: 007b ss: 0069
Process li-statusd.pl (pid: 24459, threadinfo=c7a74000 task=cdc9e030)
Stack: <0>c011bfe2 c0673d40 000000d0 000000d0 00000001 000000d0 c0673dc0
c0672c00
c065ed80 00000020 c95f6240 c7a74000 c95f6240 c7ac505c 00000001
fffffff4
00000000 ceb0ea84 c696d030 c01614c7 fffffff4 ca164a84 c011d5cc
c0673dc0
Call Trace:
[<c011bfe2>] dup_fd+0xc2/0x3b0
[<c01614c7>] kmem_cache_alloc+0x77/0x80
[<c011d5cc>] copy_process+0xa5c/0x1220
[<c0164a9c>] fd_install+0x2c/0x60
[<c011de00>] do_fork+0x70/0x200
[<c0102e47>] sys_fork+0x37/0x40
[<c0105121>] syscall_call+0x7/0xb
Code: 56 0c 8b 3c b8 89 7e 14 89 54 8d 14 41 89 4d 00 8b 44 24 18 8b 7e
10 3b 78 38 0f 83 3a ff ff ff 4b 83 fb ff 75 c0 8b 16 8b 46 04 <89> 42
04 89 10 83 7e 14 ff c7 06 00 01 10 00 c7 46 04 00 02 20
-Chris
^ permalink raw reply [flat|nested] 5+ messages in thread
* RE: (XEN) domain_crash_sync called from entry.S (ff158e99)
@ 2006-04-13 0:43 Ian Pratt
2006-04-13 1:31 ` Nivedita Singhvi
0 siblings, 1 reply; 5+ messages in thread
From: Ian Pratt @ 2006-04-13 0:43 UTC (permalink / raw)
To: Christopher S. Aker, xen-devel
Have you a recipe for reproducing? We haven't seen this.
Thanks,
Ian
> -----Original Message-----
> From: xen-devel-bounces@lists.xensource.com
> [mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of
> Christopher S. Aker
> Sent: 11 April 2006 20:43
> To: xen-devel
> Subject: [Xen-devel] (XEN) domain_crash_sync called from
> entry.S (ff158e99)
>
> Xen/xen0 as of Sun Apr 9 18:23:16 2006 +0100
> 9591:81bc9e9fb40d. The domU kernel is a few days previous to
> that -- after all of Keir's xvf kthread updates.
>
> (XEN) domain_crash_sync called from entry.S (ff158e99)
> (XEN) Domain 51 (vcpu#1) crashed on cpu#0:
> (XEN) ----[ Xen-3.0-unstable Not tainted ]----
> (XEN) CPU: 0
> (XEN) EIP: 0061:[<c0111df0>]
> (XEN) EFLAGS: 00010292 CONTEXT: guest
> (XEN) eax: 00000000 ebx: 01649000 ecx: 7ffdf061 edx: 80000000
> (XEN) esi: 00000001 edi: c6087030 ebp: c0867fb4 esp: c0867f24
> (XEN) cr0: 8005003b cr3: 7fc81000
> (XEN) ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0069 cs: 0061
> (XEN) Guest stack trace from esp=c0867f24:
> (XEN) c0866000 c69dd900 c0111e80 c69dd900 c0468438
> c69dd900 c01051fa
> 00000001
> (XEN) c0866000 012193bf 00000000 c0866000 c0866000
> 00476385 00000000
> c011fd55
> (XEN) c253267c c2532550 c110a240 f88990d7 00005409
> c0866000 f8528476
> 00005409
> (XEN) c69dd580 c0867f9c b7ec2ff4 bfe21920 00000000
> c0866000 c0102e47
> 00000011
> (XEN) bfe218fc b7ec2ff4 f578d040 00000000 c0866000
> c01051fa b7ec2ff4
> 00000000
> (XEN) 00000000 bfe21920 00000000 bfe21908 000016c2
> 0000007b 0000007b
> 00000002
> (XEN) b7e366d8 00000073 00000246 bfe218fc 0000007b
> 2507f000 b7d2115d
>
> ...then, very shortly after, in dom0...
>
> Unable to handle kernel NULL pointer dereference at virtual
> address 00000004
> printing eip:
> c0161655
> 07fb5000 -> *pde = 00000001:e33ff001
> 077ba000 -> *pme = 00000000:00000000
> Oops: 0002 [#1]
> SMP
> Modules linked in:
> CPU: 0
> EIP: 0061:[<c0161655>] Not tainted VLI
> EFLAGS: 00010046 (2.6.16-xen0 #1)
> EIP is at cache_alloc_refill+0x185/0x560
> eax: c065ed80 ebx: ffffffff ecx: 00000010 edx: 00000000
> esi: c7ac5040 edi: 00000002 ebp: c067ee80 esp: c7a75e94
> ds: 007b es: 007b ss: 0069
> Process li-statusd.pl (pid: 24459, threadinfo=c7a74000 task=cdc9e030)
> Stack: <0>c011bfe2 c0673d40 000000d0 000000d0 00000001
> 000000d0 c0673dc0 c0672c00
> c065ed80 00000020 c95f6240 c7a74000 c95f6240 c7ac505c 00000001
> fffffff4
> 00000000 ceb0ea84 c696d030 c01614c7 fffffff4 ca164a84
> c011d5cc c0673dc0 Call Trace:
> [<c011bfe2>] dup_fd+0xc2/0x3b0
> [<c01614c7>] kmem_cache_alloc+0x77/0x80
> [<c011d5cc>] copy_process+0xa5c/0x1220
> [<c0164a9c>] fd_install+0x2c/0x60
> [<c011de00>] do_fork+0x70/0x200
> [<c0102e47>] sys_fork+0x37/0x40
> [<c0105121>] syscall_call+0x7/0xb
> Code: 56 0c 8b 3c b8 89 7e 14 89 54 8d 14 41 89 4d 00 8b 44
> 24 18 8b 7e 10 3b 78 38 0f 83 3a ff ff ff 4b 83 fb ff 75 c0
> 8b 16 8b 46 04 <89> 42
> 04 89 10 83 7e 14 ff c7 06 00 01 10 00 c7 46 04 00 02 20
>
> -Chris
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: (XEN) domain_crash_sync called from entry.S (ff158e99)
2006-04-13 0:43 (XEN) domain_crash_sync called from entry.S (ff158e99) Ian Pratt
@ 2006-04-13 1:31 ` Nivedita Singhvi
0 siblings, 0 replies; 5+ messages in thread
From: Nivedita Singhvi @ 2006-04-13 1:31 UTC (permalink / raw)
To: Ian Pratt; +Cc: xen-devel
Ian Pratt wrote:
> Have you a recipe for reproducing? We haven't seen this.
>
> Thanks,
> Ian
Ian, we had also seen this running xm-test on a SMP box,
01_migrate_localhost_pos in particular. I think this has
been fixed in tree, though (4/6). Haven't confirmed.
Christopher, you might want to upgrade the domU kernel, too.
thanks,
Nivedita
>>-----Original Message-----
>>From: xen-devel-bounces@lists.xensource.com
>>[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of
>>Christopher S. Aker
>>Sent: 11 April 2006 20:43
>>To: xen-devel
>>Subject: [Xen-devel] (XEN) domain_crash_sync called from
>>entry.S (ff158e99)
>>
>>Xen/xen0 as of Sun Apr 9 18:23:16 2006 +0100
>>9591:81bc9e9fb40d. The domU kernel is a few days previous to
>>that -- after all of Keir's xvf kthread updates.
>>
>>(XEN) domain_crash_sync called from entry.S (ff158e99)
>>(XEN) Domain 51 (vcpu#1) crashed on cpu#0:
>>(XEN) ----[ Xen-3.0-unstable Not tainted ]----
>>(XEN) CPU: 0
>>(XEN) EIP: 0061:[<c0111df0>]
>>(XEN) EFLAGS: 00010292 CONTEXT: guest
>>(XEN) eax: 00000000 ebx: 01649000 ecx: 7ffdf061 edx: 80000000
>>(XEN) esi: 00000001 edi: c6087030 ebp: c0867fb4 esp: c0867f24
>>(XEN) cr0: 8005003b cr3: 7fc81000
>>(XEN) ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0069 cs: 0061
>>(XEN) Guest stack trace from esp=c0867f24:
>>(XEN) c0866000 c69dd900 c0111e80 c69dd900 c0468438
>>c69dd900 c01051fa
>>00000001
>>(XEN) c0866000 012193bf 00000000 c0866000 c0866000
>>00476385 00000000
>>c011fd55
>>(XEN) c253267c c2532550 c110a240 f88990d7 00005409
>>c0866000 f8528476
>>00005409
>>(XEN) c69dd580 c0867f9c b7ec2ff4 bfe21920 00000000
>>c0866000 c0102e47
>>00000011
>>(XEN) bfe218fc b7ec2ff4 f578d040 00000000 c0866000
>>c01051fa b7ec2ff4
>>00000000
>>(XEN) 00000000 bfe21920 00000000 bfe21908 000016c2
>>0000007b 0000007b
>>00000002
>>(XEN) b7e366d8 00000073 00000246 bfe218fc 0000007b
>>2507f000 b7d2115d
>>
>>...then, very shortly after, in dom0...
>>
>>Unable to handle kernel NULL pointer dereference at virtual
>>address 00000004
>> printing eip:
>>c0161655
>>07fb5000 -> *pde = 00000001:e33ff001
>>077ba000 -> *pme = 00000000:00000000
>>Oops: 0002 [#1]
>>SMP
>>Modules linked in:
>>CPU: 0
>>EIP: 0061:[<c0161655>] Not tainted VLI
>>EFLAGS: 00010046 (2.6.16-xen0 #1)
>>EIP is at cache_alloc_refill+0x185/0x560
>>eax: c065ed80 ebx: ffffffff ecx: 00000010 edx: 00000000
>>esi: c7ac5040 edi: 00000002 ebp: c067ee80 esp: c7a75e94
>>ds: 007b es: 007b ss: 0069
>>Process li-statusd.pl (pid: 24459, threadinfo=c7a74000 task=cdc9e030)
>>Stack: <0>c011bfe2 c0673d40 000000d0 000000d0 00000001
>>000000d0 c0673dc0 c0672c00
>> c065ed80 00000020 c95f6240 c7a74000 c95f6240 c7ac505c 00000001
>>fffffff4
>> 00000000 ceb0ea84 c696d030 c01614c7 fffffff4 ca164a84
>>c011d5cc c0673dc0 Call Trace:
>> [<c011bfe2>] dup_fd+0xc2/0x3b0
>> [<c01614c7>] kmem_cache_alloc+0x77/0x80
>> [<c011d5cc>] copy_process+0xa5c/0x1220
>> [<c0164a9c>] fd_install+0x2c/0x60
>> [<c011de00>] do_fork+0x70/0x200
>> [<c0102e47>] sys_fork+0x37/0x40
>> [<c0105121>] syscall_call+0x7/0xb
>>Code: 56 0c 8b 3c b8 89 7e 14 89 54 8d 14 41 89 4d 00 8b 44
>>24 18 8b 7e 10 3b 78 38 0f 83 3a ff ff ff 4b 83 fb ff 75 c0
>>8b 16 8b 46 04 <89> 42
>>04 89 10 83 7e 14 ff c7 06 00 01 10 00 c7 46 04 00 02 20
>>
>>-Chris
>>
>>
>>_______________________________________________
>>Xen-devel mailing list
>>Xen-devel@lists.xensource.com
>>http://lists.xensource.com/xen-devel
>>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: (XEN) domain_crash_sync called from entry.S (ff158e99)
2006-04-11 19:43 Christopher S. Aker
@ 2006-04-20 2:29 ` Christopher S. Aker
2006-04-20 7:21 ` Keir Fraser
0 siblings, 1 reply; 5+ messages in thread
From: Christopher S. Aker @ 2006-04-20 2:29 UTC (permalink / raw)
To: xen-devel
Another ... this time with Xen 3.0.2-2.
(XEN) domain_crash_sync called from entry.S (ff157585)
(XEN) Domain 32 (vcpu#0) crashed on cpu#1:
(XEN) ----[ Xen-3.0.2-2 Not tainted ]----
(XEN) CPU: 1
(XEN) EIP: 0061:[<c0101347>]
(XEN) EFLAGS: 00010a17 CONTEXT: guest
(XEN) eax: 00000000 ebx: c4a69e54 ecx: 00000001 edx: 00000000
(XEN) esi: 00007ff0 edi: c3d9f550 ebp: c4a69e80 esp: c4a69e00
(XEN) cr0: 8005003b cr3: 7fe2d000
(XEN) ds: 007b es: 007b fs: 0000 gs: 0000 ss: 0069 cs: 0061
(XEN) Guest stack trace from esp=c4a69e00:
(XEN) Fault while accessing guest memory.
(XEN) ----[ Xen-3.0.2-2 Not tainted ]----
(XEN) CPU: 1
(XEN) EIP: e008:[<ff11f593>] put_page_type+0x13/0xa0
(XEN) EFLAGS: 00210296 CONTEXT: hypervisor
(XEN) eax: f6800000 ebx: feca7038 ecx: 001fc94c edx: f6157242
(XEN) esi: a72b9210 edi: a72b9210 ebp: f97adf20 esp: ff23dce4
(XEN) cr0: 80050033 cr3: 7ffda000
(XEN) ds: e010 es: e010 fs: 0000 gs: 0000 ss: e010 cs: e008
(XEN) Xen stack trace from esp=ff23dce4:
(XEN) ffbdf080 ffbf6480 00000001 ff157149 feca7038 a72b9210 001fc94c
ff11f795
(XEN) a72b9210 001aed41 ffbf6514 ff23dfb4 00000000 feca7038 00000007
ff11f360
(XEN) 001fc94c ff11d6b3 ff11b5e6 ff23dd34 ff23dfb4 ffbe6000 feca7000
40030001
(XEN) 40030000 f97adf20 fec9d000 ff11f616 f97adf20 50030001 00000001
ff157149
(XEN) fec9d020 f97adf20 0007fe2d ff11f715 f97adf20 ff23ddb8 ffbf6514
ff23dfb4
(XEN) 00000000 fec9d020 00000004 ff11f3cd 0007fe2d f93a7228 f871c340
ff1254e7
(XEN) 7ffda000 ffbe6000 ffbe6498 60000001 60000000 f73fd438 f73fd438
ff11f616
(XEN) f73fd438 70000001 f871c340 00000002 80000003 ffa58080 f73fd438
ff118718
(XEN) f73fd438 00000000 ffa58080 ff118959 80000003 ffa58080 ffa58090
00000000
Do you think this, and my other issue could be faulty memory? I ran
memtest86 for 24+ hours before I deployed this box, but you never know...
-Chris
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: (XEN) domain_crash_sync called from entry.S (ff158e99)
2006-04-20 2:29 ` Christopher S. Aker
@ 2006-04-20 7:21 ` Keir Fraser
0 siblings, 0 replies; 5+ messages in thread
From: Keir Fraser @ 2006-04-20 7:21 UTC (permalink / raw)
To: Christopher S. Aker; +Cc: xen-devel
On 20 Apr 2006, at 03:29, Christopher S. Aker wrote:
> (XEN) Xen stack trace from esp=ff23dce4:
> (XEN) ffbdf080 ffbf6480 00000001 ff157149 feca7038 a72b9210
> 001fc94c ff11f795
> (XEN) a72b9210 001aed41 ffbf6514 ff23dfb4 00000000 feca7038
> 00000007 ff11f360
> (XEN) 001fc94c ff11d6b3 ff11b5e6 ff23dd34 ff23dfb4 ffbe6000
> feca7000 40030001
> (XEN) 40030000 f97adf20 fec9d000 ff11f616 f97adf20 50030001
> 00000001 ff157149
> (XEN) fec9d020 f97adf20 0007fe2d ff11f715 f97adf20 ff23ddb8
> ffbf6514 ff23dfb4
> (XEN) 00000000 fec9d020 00000004 ff11f3cd 0007fe2d f93a7228
> f871c340 ff1254e7
> (XEN) 7ffda000 ffbe6000 ffbe6498 60000001 60000000 f73fd438
> f73fd438 ff11f616
> (XEN) f73fd438 70000001 f871c340 00000002 80000003 ffa58080
> f73fd438 ff118718
> (XEN) f73fd438 00000000 ffa58080 ff118959 80000003 ffa58080
> ffa58090 00000000
>
> Do you think this, and my other issue could be faulty memory? I ran
> memtest86 for 24+ hours before I deployed this box, but you never
> know...
Did Xen not give a call trace? Also that output doesn't indicate the
reason for the crash, so there must be some bits missing from it.
-- Keir
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2006-04-20 7:21 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-04-13 0:43 (XEN) domain_crash_sync called from entry.S (ff158e99) Ian Pratt
2006-04-13 1:31 ` Nivedita Singhvi
-- strict thread matches above, loose matches on Subject: below --
2006-04-11 19:43 Christopher S. Aker
2006-04-20 2:29 ` Christopher S. Aker
2006-04-20 7:21 ` Keir Fraser
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.