From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46103) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YsSXr-0003hP-Mw for qemu-devel@nongnu.org; Wed, 13 May 2015 05:01:43 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YsSXl-0000Bv-Nx for qemu-devel@nongnu.org; Wed, 13 May 2015 05:01:39 -0400 Received: from mx1.redhat.com ([209.132.183.28]:37011) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YsSXl-0000Ba-Is for qemu-devel@nongnu.org; Wed, 13 May 2015 05:01:33 -0400 Message-ID: <555312E5.4060103@redhat.com> Date: Wed, 13 May 2015 11:01:25 +0200 From: Paolo Bonzini MIME-Version: 1.0 References: <5549C424.3080203@msgid.tls.msk.ru> <554B024B.90101@msgid.tls.msk.ru> <554B0A67.5050107@msgid.tls.msk.ru> <554B3188.30308@msgid.tls.msk.ru> <5551AA52.3000904@msgid.tls.msk.ru> In-Reply-To: <5551AA52.3000904@msgid.tls.msk.ru> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] Bug report - Windows XP guest failure List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Michael Tokarev , Peter Crosthwaite Cc: G 3 , qemu-devel qemu-devel On 12/05/2015 09:22, Michael Tokarev wrote: > 12.05.2015 04:05, Peter Crosthwaite wrote: >> On Thu, May 7, 2015 at 2:34 AM, Michael Tokarev wrote: > ... >>>> Ok, I can reproduce this, winXP BSODs on boot in tcg mode. >>>> Git bisect points to this: >>>> >>>> commit 23820dbfc79d1c9dce090b4c555994f2bb6a69b3 >>>> Author: Peter Crosthwaite >>>> Date: Mon Mar 16 22:35:54 2015 -0700 >>>> >>>> exec: Respect as_translate_internal length clamp >>> >>> This winXP BSOD happens on x86_64 target too. Reverting the >>> above commit from git master fixes the BSOD. >> >> Any useful info about IO addresses on that BSOD? The last issue with >> this patch was IOPort code relying on the bug that this patch fixed. >> This could be similar and if we can track the failure to a particular >> address we can fix properly rather than another revert of that patch. > > Oh. I didn't know this patch has been reverted before. Anyway, I disabled > auto-reboot on BSOD on my winXP (what a "useful" feature!) and here's what > I see. > > IRQ_NOT_LESS_OR_EQUAL > STOP: 0x0A (0x16, 0x02, 0x00, 0x80500EFC) > > (with some amount of leading zeros stripped). > > When this happens, win does something for quite some time, the BSOD comes > after quite significant delay. > > Is there anything else I can look at, maybe some crash dump or something? > I haven't done any windows debugging before. I would just put a breakpoint on the new condition introduced by the commit, and see what causes the breakage. Paolo