From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paolo Bonzini Subject: Re: [PATCH] blkfront: Move blkif_interrupt into a tasklet. Date: Wed, 17 Aug 2011 00:30:40 -0700 Message-ID: <4E4B6E20.2080805@redhat.com> References: <1282546470-5547-1-git-send-email-daniel.stodden@citrix.com> <1282546470-5547-2-git-send-email-daniel.stodden@citrix.com> <4C802934.2000305@goop.org> <4C9B7B69.7080705@redhat.com> <4C9B7F1A.2040302@goop.org> <4C9B826B.10302@redhat.com> <4C9B9E1D.2040501@goop.org> <1313494014833-4704111.post@n5.nabble.com> <20110817023827.GA21468@dumpdata.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20110817023827.GA21468@dumpdata.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: Konrad Rzeszutek Wilk Cc: imammedo , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 08/16/2011 07:38 PM, Konrad Rzeszutek Wilk wrote: >> > I've debugged a bit blk-core warning and can say: >> > - Yes, It is 32-bit PAE kernel and happens only with it so far. >> > - Affects PV xen guest, bare-metal and kvm configs are not affected. >> > - Upstream kernel is affected as well. >> > - Reproduces on xen 4.1.1 and 3.1.2 hosts > And the dom0 is 2.6.18 right? This problem is not present > when you use a 3.0 dom0? Never say never, but why should the dom0 version matter if the problems occurs at an IRET? Igor, perhaps you can try printing the saved_upcall_mask field of the VCPU context in your traces. Paolo