From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Christopher S. Aker" Subject: Re: 2.6.28 domU panics in blk_invoke_request_fn() Date: Wed, 14 Jan 2009 11:03:50 -0500 Message-ID: <496E0CE6.703@theshore.net> References: <4964D25F.5010900@theshore.net> <496D2730.9040002@goop.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <496D2730.9040002@goop.org> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jeremy Fitzhardinge Cc: xen devel List-Id: xen-devel@lists.xenproject.org Jeremy Fitzhardinge wrote: > Christopher S. Aker wrote: >> Below are two similar panics we've captured thus far with some light >> testing of 2.6.28 domUs across our Xen cluster. The kernel binary and >> associated files can be found here: > > How frequently does this occur? > > Did it just started appearing on 2.6.28, but .27.x is OK? Does it > happen often enough that you could practically bisect? This is new in 2.6.28. So far it's occurring randomly so bisecting isn't an option. > Could you compile the kernel with CONFIG_BUG_VERBOSE enabled so that it > at prints some source/line info? The location of the BUG isn't obvious. I've compiled in CONFIG_DEBUG_BUGVERBOSE and redeployed the kernels. I'll post to our community forums asking for wider testing. > What's your dom0? 3.2.1 (+/- a few changesets), 64 bit hypervisor, with dom0 2.6.18.8 PAE from xenbits at changeset number 622 and the other host's dom0 at 524. -Chris