From mboxrd@z Thu Jan 1 00:00:00 1970 From: fanliang Subject: Look for some help about Windows pv driver Date: Tue, 22 Dec 2009 09:38:39 +0800 Message-ID: <000101ca82a7$7cc3da80$e538a60a@china.huawei.com> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0394634153==" Return-path: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org This is a multi-part message in MIME format. --===============0394634153== Content-type: multipart/alternative; boundary="Boundary_(ID_ohnLBa10WUirghZhhSJ8hg)" This is a multi-part message in MIME format. --Boundary_(ID_ohnLBa10WUirghZhhSJ8hg) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT Hi: Is there any body have used GPL Windows pv driver ? Or WLK tools ? After I installed GPL windows pv driver in my windows vm, I run WLK for a while, and a few minutes later, I got a BSoD with error code STOP0X000000F4 . Used windbg to debug, I got some call stack about the system proccess .It is strange that the call stack include nothing about the pv driver. I'm wandering how can I fix this problem ? Many thanks if some one gave me some suggestions. Tks. Lyman Van --Boundary_(ID_ohnLBa10WUirghZhhSJ8hg) Content-type: text/html; charset=us-ascii Content-transfer-encoding: 7BIT
Hi:
Is there any body have used GPL Windows pv driver ? Or WLK tools ? After I installed GPL windows pv driver in my windows vm, I run WLK for a while, and a few minutes later, I got a BSoD with error code STOP0X000000F4 . Used windbg to debug, I got some call stack about  the system proccess .It is strange that the call stack include nothing about the pv driver. I'm wandering how can I fix this problem ? Many thanks if some one gave me some suggestions.
Tks.
Lyman Van
--Boundary_(ID_ohnLBa10WUirghZhhSJ8hg)-- --===============0394634153== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0394634153==-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Durrant Subject: Re: Look for some help about Windows pv driver Date: Tue, 22 Dec 2009 09:38:19 +0000 Message-ID: <4B30938B.8020809@citrix.com> References: <000101ca82a7$7cc3da80$e538a60a@china.huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <000101ca82a7$7cc3da80$e538a60a@china.huawei.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: fanliang Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org fanliang wrote: > Is there any body have used GPL Windows pv driver ? Or WLK tools ? After > I installed GPL windows pv driver in my windows vm, I run WLK for a > while, and a few minutes later, I got a BSoD with error code > STOP0X000000F4 . Used windbg to debug, I got some call stack about the > system proccess .It is strange that the call stack include nothing about > the pv driver. I'm wandering how can I fix this problem ? Many thanks if > some one gave me some suggestions. First, have a look at http://msdn.microsoft.com/en-us/library/ms789516.aspx and look up the bugcheck code. In your case it's CRITICAL_OBJECT_TERMINATION. If you look at http://msdn.microsoft.com/en-us/library/ms797140.aspx you'll see that parameter 1 of the bugcheck tells you the object type (process or thread), parameter 2 points to the object, parameter 3 points to the process image file name and parameter 4 points to an ASCII string telling you what happened. If you didn't already, then run !analyze -v inside windbg as it will also tell you most of this and decode some of the info for you. Paul -- =============================== Paul Durrant, Software Engineer Citrix Systems (R&D) Ltd. First Floor, Building 101 Cambridge Science Park Milton Road Cambridge CB4 0FY United Kingdom =============================== From mboxrd@z Thu Jan 1 00:00:00 1970 From: fanliang Subject: =?gb2312?B?tPC4tDogW1hlbi1kZXZlbF0gTG9vayBmb3Igc29tZSBoZWxwIGFibw==?= =?gb2312?B?dXQgV2luZG93cyBwdiBkcml2ZXI=?= Date: Tue, 22 Dec 2009 18:36:21 +0800 Message-ID: <000601ca82f2$9a9c6e00$e538a60a@china.huawei.com> References: <4B30938B.8020809@citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=gb2312 Content-Transfer-Encoding: quoted-printable Return-path: In-reply-to: <4B30938B.8020809@citrix.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: 'Paul Durrant' Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org Thanks a lot.=20 I can understand what you said , But what puzzled me is that I saw = nothing about my windows pv driver from the output of !analyze -v inside = windbg .I am not sure that the BSoD had nothing with the windows pv driver. WLK = goes very well in other windows system without pv driver ,so I guess the pv driver cases the BSod.=20 =20 -----=D3=CA=BC=FE=D4=AD=BC=FE----- =B7=A2=BC=FE=C8=CB: Paul Durrant [mailto:paul.durrant@citrix.com]=20 =B7=A2=CB=CD=CA=B1=BC=E4: 2009=C4=EA12=D4=C222=C8=D5 17:38 =CA=D5=BC=FE=C8=CB: fanliang =B3=AD=CB=CD: xen-devel@lists.xensource.com =D6=F7=CC=E2: Re: [Xen-devel] Look for some help about Windows pv driver fanliang wrote: > Is there any body have used GPL Windows pv driver ? Or WLK tools ?=20 > After I installed GPL windows pv driver in my windows vm, I run WLK=20 > for a while, and a few minutes later, I got a BSoD with error code > STOP0X000000F4 . Used windbg to debug, I got some call stack about =20 > the system proccess .It is strange that the call stack include nothing = > about the pv driver. I'm wandering how can I fix this problem ? Many=20 > thanks if some one gave me some suggestions. First, have a look at http://msdn.microsoft.com/en-us/library/ms789516.aspx and look up the bugcheck code. In your case it's CRITICAL_OBJECT_TERMINATION. If you = look at http://msdn.microsoft.com/en-us/library/ms797140.aspx you'll see that parameter 1 of the bugcheck tells you the object type (process or = thread), parameter 2 points to the object, parameter 3 points to the process = image file name and parameter 4 points to an ASCII string telling you what happened. If you didn't already, then run !analyze -v inside windbg as it will = also tell you most of this and decode some of the info for you. Paul --=20 =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D Paul Durrant, Software Engineer Citrix Systems (R&D) Ltd. First Floor, Building 101 Cambridge Science Park Milton Road Cambridge CB4 0FY United Kingdom =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paul Durrant Subject: Re: =?GB2312?B?tPC4tDogW1hlbi1kZXZlbF0gTG9vayBmb3Igc29tZSBoZWxwIA==?= =?GB2312?B?YWJvdXQgV2luZG93cyBwdiBkcml2ZXI=?= Date: Tue, 22 Dec 2009 11:43:24 +0000 Message-ID: <4B30B0DC.8020102@citrix.com> References: <000601ca82f2$9a9c6e00$e538a60a@china.huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset="GB2312" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <000601ca82f2$9a9c6e00$e538a60a@china.huawei.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: fanliang Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org fanliang wrote: > Thanks a lot. > I can understand what you said , But what puzzled me is that I saw nothing > about my windows pv driver from the output of !analyze -v inside windbg .I > am not sure that the BSoD had nothing with the windows pv driver. WLK goes > very well in other windows system without pv driver ,so I guess the pv > driver cases the BSod. > Just because you did not get a direct stack backtrace into a PV driver does not, of course, mean it's not at fault. You need to find out the exact nature of the object that terminated to have a clue as to what happened. Paul -- =============================== Paul Durrant, Software Engineer Citrix Systems (R&D) Ltd. First Floor, Building 101 Cambridge Science Park Milton Road Cambridge CB4 0FY United Kingdom =============================== From mboxrd@z Thu Jan 1 00:00:00 1970 From: "James Harper" Subject: RE: Look for some help about Windows pv driver Date: Tue, 22 Dec 2009 22:55:44 +1100 Message-ID: References: <000101ca82a7$7cc3da80$e538a60a@china.huawei.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Return-path: Content-class: urn:content-classes:message In-Reply-To: <000101ca82a7$7cc3da80$e538a60a@china.huawei.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: fanliang , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org >=20 > Hi: > Is there any body have used GPL Windows pv driver ? Or WLK tools ? I've run the NDIS test a while ago (a seriously good network test suite!) to test some of the IP offload code I'd been working on. I haven't run much of the other stuff though. > After I > installed GPL windows pv driver in my windows vm, I run WLK for a while, and a > few minutes later, I got a BSoD with error code STOP0X000000F4. What version of GPLPV? Parameter 4 of BSoD should be a pointer to a string with some more information... can you tell me what the string contains? I assume it's just the name of the task that crashed which won't tell us much. > Used windbg > to debug, I got some call stack about the system proccess .It is strange that > the call stack include nothing about the pv driver. I'm wandering how can I > fix this problem ? Many thanks if some one gave me some suggestions. Do you know what was being tested? If it was the disk then maybe there is some corruption happening - the WLK is supposed to give things a pretty extreme workout so it could be touching some corner case that we've never seen in real use. One thing I can think of is how GPLPV behaves when allocations to system resources fail (eg memory allocation)... if I don't know how to handle a failure at a specific point I should have at least put an ASSERT in there so that you get a definite crash right at the point of failure, not a strange crash some time later, but maybe I've missed some? If you are not running a fairly recent version of GPLPV then there was a bug that only ever showed up under Call Of Duty 4 in server mode on one specific map that was caused by some buffer corruption on disk read/write. Depending on your version of Dom0 and the version of GPLPV, there should be debug information written out to /var/log/xen/qemu-dm-.log. There might be something useful in there. If you can reproduce the problem pretty quickly, I can make a very very new version of GPLPV available to you for testing. I haven't tested it enough for production use yet but it would be useful to run it through the WLK. It uses the latest WinDDK (7600). Also, if you want the GPLPV symbol files for debugging then I have them for any given recent release, I just don't upload them unless someone wants them as they are big and I don't have a particularly fast link, so just ask if you want them. James