From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeremy Fitzhardinge Subject: Re: Re: Crash on blktap shutdown Date: Wed, 24 Feb 2010 16:37:42 -0800 Message-ID: <4B85C656.1060109@goop.org> References: <4B85AE5C.8050603@goop.org> <1267055355.5962.503.camel@agari.van.xensource.com> <4B85BBAC.6000704@goop.org> <1267057784.5962.688.camel@agari.van.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1267057784.5962.688.camel@agari.van.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Daniel Stodden Cc: Xen-devel List-Id: xen-devel@lists.xenproject.org On 02/24/2010 04:29 PM, Daniel Stodden wrote: > 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. > Perhaps. I got all the others on normal domain shutdown, but this one was on machine reboot. I'll try to repro (as I boot the test kernel with your patch in it). J