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-users

RE: [Xen-users] Stop 8E with GPL PV Drivers

To: "James Harper" <james.harper@xxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] Stop 8E with GPL PV Drivers
From: "Nick Couchman" <Nick.Couchman@xxxxxxxxx>
Date: Fri, 24 Oct 2008 23:16:48 -0600
Cc: XEN Mailing List <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 24 Oct 2008 22:17:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Okay, I just did a clean Windows install, ran all of the updates, and then installed the GPLPV drivers.  As soon as the install was finishing up (as Windows is actually installing all of the devices), I get exactly the same stop screen as mentioned below (0x0000007E).  I'll see if I can get the memory dump for you.
 
-Nick

>>> "James Harper" <james.harper@xxxxxxxxxxxxxxxx> 2008/10/24 22:27 >>>
>
> Okay, here's the latest one...on boot I get:
> 0x0000007E (0xC000001D, 0xF7615BEB, 0xF7A4D8BC, 0xF7A4D5B8)
> xenpci.sys - Address F7615BEB base at F760E000, DateStamp 48d0939f
>
> This time it's dumping the memory to disk - if I can manage to extract
the
> dump file from disk I'll try to figure out a way to get it to you.
>

Sounds like your system is correct. Even if this was caused by the GPLPV
drivers originally, I'm not sure if the crash dump now is going to tell
us anything useful. The 0x8E one would have been nice to have though.

0xC000001D == STATUS_ILLEGAL_INSTRUCTION, but unfortunately that doesn't
tell me too much by itself.

Was a driver name mentioned in the 0x8E crash dump that you remember?

James



This e-mail may contain confidential and privileged material for the sole use of the intended recipient. If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information. In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way. If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox. Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.

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