WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] RE: blue screen in windows balloon driver

To: "MaoXiaoyun" <tinnycloud@xxxxxxxxxxx>
Subject: RE: [Xen-devel] RE: blue screen in windows balloon driver
From: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Date: Mon, 14 Mar 2011 14:52:54 +1100
Cc: xen devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 13 Mar 2011 20:53:31 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <BLU157-w2726FD166F4A1231D33002DACC0@xxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <BLU157-w6407B20CA375D42DAB1348DADC0@xxxxxxx><AEC6C66638C05B468B556EA548C1A77D01C559AC@trantor><BLU157-w56096891695C107FBB1243DADE0@xxxxxxx><BLU157-w3689F78415A43CC5997DD7DADE0@xxxxxxx><BLU157-w7B83FF68CB4CEE8B140C6DADE0@xxxxxxx><AEC6C66638C05B468B556EA548C1A77D01C55A4E@trantor><BLU157-w38E9B522F8710956C4992ADAC10@xxxxxxx>, <BE58E0A1-AE23-4274-9644-24DB8456512D@xxxxxxxxxxxxxxxx><BLU157-w9D31FCDD666C6D7BD73CEDAC10@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55AC7@trantor><BLU157-w655070D9CFE092D78C011DDAC10@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55ACA@trantor><BLU157-w172C0AC95FCE2C2B836BDBDAC10@xxxxxxx> <AEC6C66638C05B468B556EA548C1A77D01C55ACC@trantor>, <AEC6C66638C05B468B556EA548C1A77D01C55ACD@trantor> <BLU157-w35E669BF00DC04327E4E93DAC00@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55B39@trantor> <BLU157-w3311FE380E5D57DD810827DAC00@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55B44@trantor> <BLU157-w564C179CAAF26EC5D7559DAC00@xxxxxxx>, <AEC6C66638C05B468B5 56EA548C ,,,,,,1A77D0 1, C, 5, 5, B, 4, 6@trantor> <BLU157-w446CEE35E592FE12EF0180DAC30@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55B88@trantor> <BLU157-w5382FC5FCC26C6EE8EC18BDAC30@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55BB3@trantor> <BLU157-w62FFC7240FD65345A0B3A8DAC30@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55BB7@trantor> <BLU157-w30368B861A4BFFF8A8DB9DDAC30@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55BBA@trantor> <BLU157-w28F0FE7DA9D129E9003136DAC30@xxxxxxx>, <AEC6C66638C05B468B556EA548C1A77D01C55BBD@trantor> <BLU157-w826F2EDB9C1A7077BA524DAC30@xxxxxxx>, <019001cbdd41$1ccfbc20$566f3460$@harper@bendigoit.com.au> <BLU157-w2726FD166F4A1231D33002DACC0@xxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acvh7wK+tmi2qf9vS1Cvu4HC2YK+OwABuhDg
Thread-topic: [Xen-devel] RE: blue screen in windows balloon driver
> Hi James:
> 
>       I am still working on the blue screen issue.
> 
>      This time I found 6 more machines to test. Two machines confronts
a new
> blue screen in
> 2 days long test.
> 
> KERNEL_STACK_INPAGE_ERROR
> stop:0x00000077(0xc0000185,0xc0000185,0x00000000,0x009d9000)
> 
> 
>       Attached is the log, cp1, 9, 15, 16, 17, 20, are broken, and has
the log
> like:
> -----------------------------
> 12944494073046: XenVbd --> XenVbd_HwScsiResetBus
> 12944494073046: XenVbd     IRQL = 31
> 12944494073046: XenVbd     Completing in-flight srb 892C7058 with
status
> SRB_STATUS_BUS_RESET
> 12944494073046: XenVbd <-- XenVbd_HwScsiResetBus
> 12944494073046: XenPCI     Grant Entry 16382 for ISCS still in use by
ISCS
> 12944494073046:
> *** Assertion failed: !xpdd->gnttbl_table[ref].flags
> ***   Source File: e:\download\win-pvdrivers.hg\xenpci\gnttbl.c, line
120
>  ---------------------------
> 

That Assertion only happens in dump mode though right? Due to the delays
in requests getting completed, dump mode is still seeing request
completions from non-dump mode. I should have a fix for that in a
minute.

Bug check 0x77 means that windows couldn't read the page into memory
from the page file. This could still be caused by timeouts. The first
and second parameter 0xc0000185 means 'STATUS_IO_DEVICE_ERROR' which I
guess would be consistent with windows repeatedly trying to read the
pagefile and then giving up after multiple timeout/reset cycles.

James

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>