From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nivedita Singhvi Subject: Re: (XEN) domain_crash_sync called from entry.S (ff158e99) Date: Wed, 12 Apr 2006 18:31:24 -0700 Message-ID: <443DA9EC.2070206@us.ibm.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: xen-devel List-Id: xen-devel@lists.xenproject.org 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:[] >>(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:[] 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: >> [] dup_fd+0xc2/0x3b0 >> [] kmem_cache_alloc+0x77/0x80 >> [] copy_process+0xa5c/0x1220 >> [] fd_install+0x2c/0x60 >> [] do_fork+0x70/0x200 >> [] sys_fork+0x37/0x40 >> [] 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