qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Michael Tokarev <mjt@tls.msk.ru>,
	Peter Crosthwaite <peter.crosthwaite@xilinx.com>
Cc: G 3 <programmingkidx@gmail.com>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Bug report - Windows XP guest failure
Date: Wed, 13 May 2015 11:01:25 +0200	[thread overview]
Message-ID: <555312E5.4060103@redhat.com> (raw)
In-Reply-To: <5551AA52.3000904@msgid.tls.msk.ru>



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 <mjt@tls.msk.ru> wrote:
> ...
>>>> Ok, I can reproduce this, winXP BSODs on boot in tcg mode.
>>>> Git bisect points to this:
>>>>
>>>> commit 23820dbfc79d1c9dce090b4c555994f2bb6a69b3
>>>> Author: Peter Crosthwaite <peter.crosthwaite@xilinx.com>
>>>> 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

  parent reply	other threads:[~2015-05-13  9:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-06  5:41 [Qemu-devel] Bug report - Windows XP guest failure Programmingkid
2015-05-06  7:35 ` Michael Tokarev
     [not found]   ` <FE644B41-6D14-4C4F-ABAD-5D33A3DDFC48@gmail.com>
2015-05-07  1:11     ` G 3
2015-05-07  6:12       ` Michael Tokarev
2015-05-07  6:47         ` Michael Tokarev
2015-05-07  9:34           ` Michael Tokarev
2015-05-11 21:57             ` Programmingkid
2015-05-12  1:05             ` Peter Crosthwaite
2015-05-12  7:11               ` Paolo Bonzini
2015-05-12  7:22               ` Michael Tokarev
2015-05-12 16:18                 ` John Snow
2015-05-13  9:01                 ` Paolo Bonzini [this message]
2015-06-14  9:55                   ` Mark Cave-Ayland
2015-06-14 14:56                     ` Programmingkid
2015-06-17 12:23                     ` Paolo Bonzini
2015-05-07 15:07           ` Programmingkid

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=555312E5.4060103@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=peter.crosthwaite@xilinx.com \
    --cc=programmingkidx@gmail.com \
    --cc=qemu-devel@nongnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).