WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] domU crashing, trying to determine why

To: micah anderson <micah@xxxxxxxxxx>
Subject: Re: [Xen-devel] domU crashing, trying to determine why
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Sun, 2 Jan 2011 14:59:13 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 02 Jan 2011 05:00:11 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <87ipy89lu3.fsf@xxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <87mxnka0yg.fsf@xxxxxxxxxxxxxxxx> <20110101214106.GE2754@xxxxxxxxxxx> <87ipy89lu3.fsf@xxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Sat, Jan 01, 2011 at 07:43:32PM -0500, micah anderson wrote:
> On Sat, 1 Jan 2011 23:41:06 +0200, Pasi Kärkkäinen <pasik@xxxxxx> wrote:
> > On Sat, Jan 01, 2011 at 02:16:55PM -0500, Micah Anderson wrote:
> > > 
> > > I'm having a domU that is regularly crashing, without any obvious reason
> > > why. I set 'on_crash=preserve' to try and get a crash to try and get
> > > some clues, but what I got doesn't too obvious to me. I was hoping
> > > someone here would be able to give me some clues. 
> > > 
> > > Thanks for any clues anyone can give! Here is what I managed to eke out:
> > > 
> > > root@guillemot:/etc/xen# /usr/lib/xen-3.2-1/bin/xenctx -s 
> > > /boot/System.map-2.6.26-2-xen-686 11 0
> > 
> > So the domU has only 1 vcpu? 
> 
> No, I did this for both vcpus, the second one is below:
> 

True, I somehow missed the other one.
Did you check debian bugreports if there are other reports like this? 

-- Pasi

> > > root@guillemot:/etc/xen# /usr/lib/xen-3.2-1/bin/xenctx -s 
> > > /boot/System.map-2.6.26-2-xen-686 11 1
> > > eip: c0170f39 file_kill+0x27 flags: 00001202 i nz
> > > esp: e74cbf2c
> > > eax: ec825e98     ebx: d7033a80   ecx: ee07207f   edx: e7672e80
> > > esi: d7033a80     edi: ed3942c0   ebp: ed396be8
> > >  cs: 00000061      ds: 0000007b    fs: 000000d8    gs: 00000000
> > > 
> > > Stack:
> > >  00000010 c01710ae ed420f00 e81b3a78 e82d5cfc e7218b00 e74ca000 c016080d
> > >  c123f020 e81b3a78 c01608e7 000001e8 c123f020 e7218b00 e7218b4c 00000000
> > >  c011c723 00000000 e59bba80 c01214aa 00000001 e7447a80 e7688580 00000000
> > >  e76885c0 00000000 ed4ebd00 00000000 e74ca000 c0121998 00000000 00000000
> > > 
> > > Code:
> > > 13 8b 43 04 89 42 04 89 10 89 5b 04 89 1b f0 fe 05 40 42 38 c0 <0f> b7 15 
> > > 40 42 38 c0 38 f2 0f 95 
> > > 
> > > Call Trace:
> > >   [<c0170f39>] file_kill+0x27  <--
> > >   [<c01710ae>] __fput+0xd2 
> > >   [<c016080d>] remove_vma+0x25 
> > >   [<c01608e7>] exit_mmap+0xbc 
> > >   [<c011c723>] mmput+0x24 
> > >   [<c01214aa>] do_exit+0x1ad 
> > >   [<c0121998>] do_group_exit+0x94 
> > >   [<c01219ce>] sys_exit_group+0xd 
> > >   [<c0103f76>] syscall_call+0x7 
> > >   [<c02c0000>] zone_wait_table_init+0x47 
> 



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