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] Re: Crash on blktap shutdown

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] Re: Crash on blktap shutdown
From: Daniel Stodden <daniel.stodden@xxxxxxxxxx>
Date: Wed, 24 Feb 2010 16:29:43 -0800
Cc: Xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Wed, 24 Feb 2010 16:30:18 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4B85BBAC.6000704@xxxxxxxx>
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: <4B85AE5C.8050603@xxxxxxxx> <1267055355.5962.503.camel@xxxxxxxxxxxxxxxxxxxxxxx> <4B85BBAC.6000704@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2010-02-24 at 18:52 -0500, Jeremy Fitzhardinge wrote:
> On 02/24/2010 03:49 PM, Daniel Stodden wrote:
> > On Wed, 2010-02-24 at 17:55 -0500, Jeremy Fitzhardinge wrote:
> >    
> >> When rebooting the machine,  I got this crash from blktap.  The rip maps 
> >> to line 262 in
> >> 0xffffffff812548a1 is in blktap_request_pool_free 
> >> (/home/jeremy/git/linux/drivers/xen/blktap/request.c:262).
> >>      
> > Uhm, where did that RIP come from?
> >
> > pool_free is on the module exit path. The stack trace below looks like a
> > crash from the broadcasted SIGTERM before reboot.
> >    
> 
> Ignore it; I generated it from a different kernel from the one that 
> crashed.  But the other oops I posted should be all consistent and 
> meaningful.

Ignore only the debuginfo quote, right?
Cos this looks like a different issue to me.

Thanks,
Daniel 


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