Hey, folks: Wondering if anyone has experienced Stop 0x0000008E BSODs when using the GPL PV drivers with a Multiprocessor HVM? Seems to be related to network activity, but it''s very hard to tell. Any suggestions/feedback/etc. would be great. I may try to reduce the number of VCPUs to 1, but I''m thinking it probably has more to do with the Multiprocessor ACPI kernel vs. the actual number of vcpus. Thanks, Nick 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@lists.xensource.com http://lists.xensource.com/xen-users
What version of the drivers? If you have a crash dump, how big is it, and could I download it from you to have a look? Thanks James> -----Original Message----- > From: xen-users-bounces@lists.xensource.com [mailto:xen-users- > bounces@lists.xensource.com] On Behalf Of Nick Couchman > Sent: Saturday, 25 October 2008 12:18 > To: XEN Mailing List > Subject: [Xen-users] Stop 8E with GPL PV Drivers > > Hey, folks: > Wondering if anyone has experienced Stop 0x0000008E BSODs when usingthe> GPL PV drivers with a Multiprocessor HVM? Seems to be related tonetwork> activity, but it''s very hard to tell. Any suggestions/feedback/etc.would> be great. I may try to reduce the number of VCPUs to 1, but I''mthinking> it probably has more to do with the Multiprocessor ACPI kernel vs. the > actual number of vcpus. > > Thanks, > Nick > > ________________________________ > > This e-mail may contain confidential and privileged material for thesole> 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 theintended> 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 immediatelyby> replying to this e-mail and delete the message from your mailbox. > Information contained in this message that does not relate to thebusiness> of SEAKR is neither endorsed by nor attributable to SEAKR._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I''m using 0.9.11-pre18. Unfortunately it doesn''t seem to be generating a crash dump or anything like that - I get the BSOD with the STOP line as the last line and then it just pegs the CPU. I''m running Xen 3.2.1. -Nick>>> "James Harper" <james.harper@bendigoit.com.au> 2008/10/24 19:20 >>>What version of the drivers? If you have a crash dump, how big is it, and could I download it from you to have a look? Thanks James> -----Original Message----- > From: xen-users-bounces@lists.xensource.com [mailto:xen-users- > bounces@lists.xensource.com] On Behalf Of Nick Couchman > Sent: Saturday, 25 October 2008 12:18 > To: XEN Mailing List > Subject: [Xen-users] Stop 8E with GPL PV Drivers > > Hey, folks: > Wondering if anyone has experienced Stop 0x0000008E BSODs when usingthe> GPL PV drivers with a Multiprocessor HVM? Seems to be related tonetwork> activity, but it''s very hard to tell. Any suggestions/feedback/etc.would> be great. I may try to reduce the number of VCPUs to 1, but I''mthinking> it probably has more to do with the Multiprocessor ACPI kernel vs. the > actual number of vcpus. > > Thanks, > Nick > > ________________________________ > > This e-mail may contain confidential and privileged material for thesole> 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 theintended> 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 immediatelyby> replying to this e-mail and delete the message from your mailbox. > Information contained in this message that does not relate to thebusiness> of SEAKR is neither endorsed by nor attributable to SEAKR.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@lists.xensource.com http://lists.xensource.com/xen-users
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. -Nick>>> "James Harper" <james.harper@bendigoit.com.au> 2008/10/24 20:10 >>> > > You want the small memory dump or the full one? The VM has 2GB ofRAM, so> the full one would be pretty large (not sure after compression). I''malso> not sure that it''s generating crash dumps. When it happens again I''ll > give it a few more minutes before I destroy the domain. > > -Nick >It can take a few minutes to even start the dump. Or it could be so crashed that it can''t dump. The kernel memory dump will be fine. If not, what are the other numbers aside from the 8E? 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@lists.xensource.com http://lists.xensource.com/xen-users
> > 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 extractthe> 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 _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Nope, nothing mentioned there. I''m in the process of reconstructing the machine (reinstalling Windows) so I''ll see if I can reproduce this. -Nick>>> "James Harper" <james.harper@bendigoit.com.au> 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 extractthe> 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@lists.xensource.com http://lists.xensource.com/xen-users
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@bendigoit.com.au> 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 extractthe> 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@lists.xensource.com http://lists.xensource.com/xen-users
I have just gone through reproducing this STOP 8E error several times. Very, very strange - I''m on a uniprocessor kernel, now, which doesn''t seem to be helping at all, so looks like it isn''t a Multiproc vs. Uniproc issue. I''ve adjusted several of the Xen PV Network card parameters to try to see if that affected anything, and it still crashes pretty consistently. For what it''s worth, it seems to happen when I''m working in the Symantec Ghost Console. I can run the GhostCast Server just fine and image machines, but the similarity about every single crash is that it''s when I''m working in the Ghost Console where I manage the client configurations, manage tasks on the clients, etc. I''m not so sure it''s a network problem anymore - could be the block device or something else, as well. -Nick On Fri, 2008-10-24 at 22:29 -0600, Nick Couchman wrote:> Nope, nothing mentioned there. I''m in the process of reconstructing > the machine (reinstalling Windows) so I''ll see if I can reproduce > this. > > -Nick > > >>> "James Harper" <james.harper@bendigoit.com.au> 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. >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@lists.xensource.com http://lists.xensource.com/xen-users
Hi Just installed new Windows server 2003 Standard and latest GPLPV ( http://www.meadowcourt.org/downloads/Xen%20PV%20Drivers%200.9.11-pre18.exe ) After installation and windows updates reboot i am also getting STOP 8E and it seems it corrupted filesystem also, atleast now when i am not booting with /GPLPV switch windows console is saysing lots of "recovering orphaned file" messages, it seems its recovering all files on c-drive and after that i am not getting login-screen anymore. Maybe pre-18 drivers broke something or perhaps some windows update, i did run all updates (not IE7) but everything else installed. Maybe that latest MS08-067 is to blame? Terveisin/Regards, Pekka Panula, Net Servant Oy xen-users-bounces@lists.xensource.com wrote on 25.10.2008 04:17:39:> "Nick Couchman" <Nick.Couchman@seakr.com> > Sent by: xen-users-bounces@lists.xensource.com > > 25.10.2008 04:19 > > To > > "XEN Mailing List" <xen-users@lists.xensource.com> > > cc > > Subject > > [Xen-users] Stop 8E with GPL PV Drivers > > Hey, folks: > Wondering if anyone has experienced Stop 0x0000008E BSODs when using > the GPL PV drivers with a Multiprocessor HVM? Seems to be related > to network activity, but it''s very hard to tell. Any suggestions/ > feedback/etc. would be great. I may try to reduce the number of > VCPUs to 1, but I''m thinking it probably has more to do with the > Multiprocessor ACPI kernel vs. the actual number of vcpus. > > Thanks, > Nick > 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@lists.xensource.com > http://lists.xensource.com/xen-users_______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hi > > Just installed new Windows server 2003 Standard and latest GPLPV > (http://www.meadowcourt.org/downloads/Xen%20PV%20Drivers%200.9.11- > pre18.exe > <http://www.meadowcourt.org/downloads/Xen%20PV%20Drivers%200.9.11- > pre18.exe> ) > After installation and windows updates reboot i am also getting STOP8E> and it seems it corrupted filesystem also, atleast now when i am not > booting with /GPLPV switch windows console is saysing lots of"recovering> orphaned file" messages, it seems its recovering all files on c-driveand> after that i am not getting login-screen anymore. > > Maybe pre-18 drivers broke something or perhaps some windows update, idid> run all updates (not IE7) but everything else installed. Maybe thatlatest> MS08-067 is to blame? >Hmmm... I''ve been getting more and more of these reports, but I can''t replicate them. If anyone can run debugview from sysinternals and catch it crashing and send me the output I''d be very grateful! Did it tell you what driver it crashed in in the 0x8e report? Thanks James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> Hi > > Just installed new Windows server 2003 Standard and latest GPLPV > (http://www.meadowcourt.org/downloads/Xen%20PV%20Drivers%200.9.11- > pre18.exe > <http://www.meadowcourt.org/downloads/Xen%20PV%20Drivers%200.9.11- > pre18.exe> ) > After installation and windows updates reboot i am also getting STOP8E> and it seems it corrupted filesystem also, atleast now when i am not > booting with /GPLPV switch windows console is saysing lots of"recovering> orphaned file" messages, it seems its recovering all files on c-driveand> after that i am not getting login-screen anymore. > > Maybe pre-18 drivers broke something or perhaps some windows update, idid> run all updates (not IE7) but everything else installed. Maybe thatlatest> MS08-067 is to blame? >Also, how much memory are you using? Thanks James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
"James Harper" <james.harper@bendigoit.com.au> wrote on 28.10.2008 12:09:10:> Hmmm... I''ve been getting more and more of these reports, but I can''t > replicate them. If anyone can run debugview from sysinternals and catch > it crashing and send me the output I''d be very grateful! > > Did it tell you what driver it crashed in in the 0x8e report?I did not see driver info, but here is a screenshot when it was dumping memory Memory size was 1024, 1 prosessor, pae = 1, acpi = 1, apic = 1. Terveisin/Regards, Pekka Panula, Net Servant Oy _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
I don''t actually get a physical memory dump (even though I have it turned on in the System control panel). I''m also using 1GB of RAM with the same parameters (acpi, apic, and pae). -Nick On Tue, 2008-10-28 at 13:29 +0200, Pekka.Panula@sofor.fi wrote:> > "James Harper" <james.harper@bendigoit.com.au> wrote on 28.10.2008 > 12:09:10: > > > Hmmm... I''ve been getting more and more of these reports, but I > can''t > > replicate them. If anyone can run debugview from sysinternals and > catch > > it crashing and send me the output I''d be very grateful! > > > > Did it tell you what driver it crashed in in the 0x8e report? > > I did not see driver info, but here is a screenshot when it was > dumping memory > > > Memory size was 1024, 1 prosessor, pae = 1, acpi = 1, apic = 1. > > > Terveisin/Regards, > Pekka Panula, Net Servant Oy-- Nick Couchman Manager, Information Technology SEAKR Engineering, Inc. P: 303-790-8499 F: 303-662-8703 x 7724 W: http://www.seakr.com 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@lists.xensource.com http://lists.xensource.com/xen-users
James, Attached is a log file locally on the VM I''m having trouble with up until it crashed. Do I need to boot the VM in debug mode or anything like that? -Nick On Tue, 2008-10-28 at 21:09 +1100, James Harper wrote:> > Hi > > > > Just installed new Windows server 2003 Standard and latest GPLPV > > (http://www.meadowcourt.org/downloads/Xen%20PV%20Drivers%200.9.11- > > pre18.exe > > <http://www.meadowcourt.org/downloads/Xen%20PV%20Drivers%200.9.11- > > pre18.exe> ) > > After installation and windows updates reboot i am also getting STOP > 8E > > and it seems it corrupted filesystem also, atleast now when i am not > > booting with /GPLPV switch windows console is saysing lots of > "recovering > > orphaned file" messages, it seems its recovering all files on c-drive > and > > after that i am not getting login-screen anymore. > > > > Maybe pre-18 drivers broke something or perhaps some windows update, i > did > > run all updates (not IE7) but everything else installed. Maybe that > latest > > MS08-067 is to blame? > > > > Hmmm... I''ve been getting more and more of these reports, but I can''t > replicate them. If anyone can run debugview from sysinternals and catch > it crashing and send me the output I''d be very grateful! > > Did it tell you what driver it crashed in in the 0x8e report? > > Thanks > > James > > >-- Nick Couchman Manager, Information Technology SEAKR Engineering, Inc. P: 303-790-8499 F: 303-662-8703 x 7724 W: http://www.seakr.com 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@lists.xensource.com http://lists.xensource.com/xen-users
This is unlikely, but any chance you have the paging file disabled? I don''t know for sure about XP, but I know 2003 can''t dump with the paging file disabled. Dustin -----Original Message----- From: xen-users-bounces@lists.xensource.com [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Nick Couchman Sent: Tuesday, October 28, 2008 11:17 To: Pekka.Panula@sofor.fi Cc: james.harper@bendigoit.com.au; xen-users@lists.xensource.com Subject: RE: [Xen-users] Stop 8E with GPL PV Drivers I don''t actually get a physical memory dump (even though I have it turned on in the System control panel). I''m also using 1GB of RAM with the same parameters (acpi, apic, and pae). -Nick On Tue, 2008-10-28 at 13:29 +0200, Pekka.Panula@sofor.fi wrote:> > "James Harper" <james.harper@bendigoit.com.au> wrote on 28.10.2008 > 12:09:10: > > > Hmmm... I''ve been getting more and more of these reports, but I > can''t > > replicate them. If anyone can run debugview from sysinternals and > catch > > it crashing and send me the output I''d be very grateful! > > > > Did it tell you what driver it crashed in in the 0x8e report? > > I did not see driver info, but here is a screenshot when it was > dumping memory > > > Memory size was 1024, 1 prosessor, pae = 1, acpi = 1, apic = 1. > > > Terveisin/Regards, > Pekka Panula, Net Servant Oy-- Nick Couchman Manager, Information Technology SEAKR Engineering, Inc. P: 303-790-8499 F: 303-662-8703 x 7724 W: http://www.seakr.com 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@lists.xensource.com http://lists.xensource.com/xen-users _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks for the hint - the page file seems to be enabled, though, and there''s enough free space on the C drive to dump the page file and the memory. Attached is another log file, but there doesn''t seem to be anything directly related to the crash. The last messages are the startup of the Ghost console - the crash happens a few second after that. -Nick On Tue, 2008-10-28 at 11:34 -0400, Dustin Henning wrote:> This is unlikely, but any chance you have the paging file disabled? > I don''t know for sure about XP, but I know 2003 can''t dump with the paging > file disabled. > Dustin > > -----Original Message----- > From: xen-users-bounces@lists.xensource.com > [mailto:xen-users-bounces@lists.xensource.com] On Behalf Of Nick Couchman > Sent: Tuesday, October 28, 2008 11:17 > To: Pekka.Panula@sofor.fi > Cc: james.harper@bendigoit.com.au; xen-users@lists.xensource.com > Subject: RE: [Xen-users] Stop 8E with GPL PV Drivers > > I don''t actually get a physical memory dump (even though I have it > turned on in the System control panel). I''m also using 1GB of RAM with > the same parameters (acpi, apic, and pae). > > -Nick > > On Tue, 2008-10-28 at 13:29 +0200, Pekka.Panula@sofor.fi wrote: > > > > "James Harper" <james.harper@bendigoit.com.au> wrote on 28.10.2008 > > 12:09:10: > > > > > Hmmm... I''ve been getting more and more of these reports, but I > > can''t > > > replicate them. If anyone can run debugview from sysinternals and > > catch > > > it crashing and send me the output I''d be very grateful! > > > > > > Did it tell you what driver it crashed in in the 0x8e report? > > > > I did not see driver info, but here is a screenshot when it was > > dumping memory > > > > > > Memory size was 1024, 1 prosessor, pae = 1, acpi = 1, apic = 1. > > > > > > Terveisin/Regards, > > Pekka Panula, Net Servant Oy-- Nick Couchman Manager, Information Technology SEAKR Engineering, Inc. P: 303-790-8499 F: 303-662-8703 x 7724 W: http://www.seakr.com 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@lists.xensource.com http://lists.xensource.com/xen-users
> > James, > Attached is a log file locally on the VM I''m having trouble with up > until it crashed. Do I need to boot the VM in debug mode or anything > like that? >As you can''t get a crash dump out of it (I assume you have waited a while - sometimes the crash dump takes a minute or two to get going) then the debugger would be the next step. I am expecting that 0x8E is going to be an ASSERT getting triggered, but I need to know what line in the code is being triggered and what the condition is. If you need assistance with the debugger then let me know. Thanks James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> "James Harper" <james.harper@bendigoit.com.au> wrote on 28.10.2008 > 12:09:10: > > > Hmmm... I''ve been getting more and more of these reports, but Ican''t> > replicate them. If anyone can run debugview from sysinternals andcatch> > it crashing and send me the output I''d be very grateful! > > > > Did it tell you what driver it crashed in in the 0x8e report? > > I did not see driver info, but here is a screenshot when it wasdumping> memory >0x8E (0xC0000005, ...) is an access violation, not an ASSERT like I thought. That will be harder to track down unfortunately - there could be memory being overwritten at one point with the crash occurring at some random point some time later. Worst Bug Ever :( I really need to be able to reproduce this but so far I haven''t been able to... Thanks James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Yes, I did wait a little while for the crash dump and no luck. Also, if I have Windows set to restart automatically after a crash it reboots itself almost instantaneously after the 0x0000008E BSOD occurs - I barely have time to see it. I''m not real familiar with the debugger, especially using Xen, so I''m afraid I''ll need some help walking through that one. If you can get me going on the debugger, I''ll be happy to provide you with any information that can be obtained out of it. -Nick>>> "James Harper" <james.harper@bendigoit.com.au> 2008/10/28 17:37 >>> > > James, > Attached is a log file locally on the VM I''m having trouble with up > until it crashed. Do I need to boot the VM in debug mode or anything > like that? >As you can''t get a crash dump out of it (I assume you have waited a while - sometimes the crash dump takes a minute or two to get going) then the debugger would be the next step. I am expecting that 0x8E is going to be an ASSERT getting triggered, but I need to know what line in the code is being triggered and what the condition is. If you need assistance with the debugger then let me know. Thanks 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@lists.xensource.com http://lists.xensource.com/xen-users
James, Here you go - here are the last few lines of the debugger output. I haven''t received the BSOD, but I figured the debugger output was preventing that: XenVbd stat_no_shadows = 0 XenVbd stat_no_grants = 0 XenVbd stat_outstanding_requests = 1 XenVbd stat_interrupts = 954805 XenVbd stat_interrupts_for_me = 348160 XenVbd stat_reads = 56361 XenVbd stat_writes = 296092 XenVbd stat_unaligned_le_4096 = 14 XenVbd stat_unaligned_le_8192 = 0 XenVbd stat_unaligned_le_16384 = 0 XenVbd stat_unaligned_le_32768 = 0 XenVbd stat_unaligned_le_65536 = 0 XenVbd stat_unaligned_gt_65536 = 0 XenVbd stat_no_shadows = 0 XenVbd stat_no_grants = 0 XenVbd stat_outstanding_requests = 1 *** Assertion failed: !in_mdl *** Source File: c:\projects\win-pvdrivers.hg\xennet\xennet_tx.c, line 176 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? Let me know if you need any more info - I''ll happy to provide further debug output, etc. -Nick>>> "James Harper" <james.harper@bendigoit.com.au> 2008/10/28 17:37 >>> > > James, > Attached is a log file locally on the VM I''m having trouble with up > until it crashed. Do I need to boot the VM in debug mode or anything > like that? >As you can''t get a crash dump out of it (I assume you have waited a while - sometimes the crash dump takes a minute or two to get going) then the debugger would be the next step. I am expecting that 0x8E is going to be an ASSERT getting triggered, but I need to know what line in the code is being triggered and what the condition is. If you need assistance with the debugger then let me know. Thanks 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@lists.xensource.com http://lists.xensource.com/xen-users
> > James, > Here you go - here are the last few lines of the debugger output. I > haven''t received the BSOD, but I figured the debugger output was > preventing that: > XenVbd stat_no_shadows = 0 > XenVbd stat_no_grants = 0 > XenVbd stat_outstanding_requests = 1 > XenVbd stat_interrupts = 954805 > XenVbd stat_interrupts_for_me = 348160 > XenVbd stat_reads = 56361 > XenVbd stat_writes = 296092 > XenVbd stat_unaligned_le_4096 = 14 > XenVbd stat_unaligned_le_8192 = 0 > XenVbd stat_unaligned_le_16384 = 0 > XenVbd stat_unaligned_le_32768 = 0 > XenVbd stat_unaligned_le_65536 = 0 > XenVbd stat_unaligned_gt_65536 = 0 > XenVbd stat_no_shadows = 0 > XenVbd stat_no_grants = 0 > XenVbd stat_outstanding_requests = 1 > > *** Assertion failed: !in_mdl > *** Source File: c:\projects\win-pvdrivers.hg\xennet\xennet_tx.c,line> 176 > > Break repeatedly, break Once, Ignore, terminate Process, or terminate > Thread (boipt)? > > Let me know if you need any more info - I''ll happy to provide further > debug output, etc. >That''s the most useful output yet :) I''ll see if I can backtrack and see how that situation could come about... Thanks James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > James, > Here you go - here are the last few lines of the debugger output. I > haven''t received the BSOD, but I figured the debugger output was > preventing that: > XenVbd stat_no_shadows = 0 > XenVbd stat_no_grants = 0 > XenVbd stat_outstanding_requests = 1 > XenVbd stat_interrupts = 954805 > XenVbd stat_interrupts_for_me = 348160 > XenVbd stat_reads = 56361 > XenVbd stat_writes = 296092 > XenVbd stat_unaligned_le_4096 = 14 > XenVbd stat_unaligned_le_8192 = 0 > XenVbd stat_unaligned_le_16384 = 0 > XenVbd stat_unaligned_le_32768 = 0 > XenVbd stat_unaligned_le_65536 = 0 > XenVbd stat_unaligned_gt_65536 = 0 > XenVbd stat_no_shadows = 0 > XenVbd stat_no_grants = 0 > XenVbd stat_outstanding_requests = 1 > > *** Assertion failed: !in_mdl > *** Source File: c:\projects\win-pvdrivers.hg\xennet\xennet_tx.c,line> 176 > > Break repeatedly, break Once, Ignore, terminate Process, or terminate > Thread (boipt)? > > Let me know if you need any more info - I''ll happy to provide further > debug output, etc. >Is it repeatable under the debugger? At first glance, the only way I can see that that breakpoint could be triggered is if the preceeding call to NdisGetFirstBufferFromPacketSafe fails, which isn''t something I''m testing for. Memory corruption caused somewhere else in my drivers is another possibility, but I''m ignoring that possibility for now :) I have just uploaded a xennet_2k3_x86_0.9.11-pre18-update.zip which contain a check for the return of NdisGetFirstBufferFromPacketSafe. Please try it and see what happens - just copy the sys file directly into c:\windows\system32\drivers and then reboot If that is the cause of the problem, you should see a log message of "NdisGetFirstBufferFromPacketSafe failed" instead of the exception. I''ll look at it some more though, just in case there is another possible way it could arrive there... James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> I have just uploaded a xennet_2k3_x86_0.9.11-pre18-update.zip which > contain a check for the return of NdisGetFirstBufferFromPacketSafe. > Please try it and see what happens - just copy the sys file directly > into c:\windows\system32\drivers and then rebootActually, please try xennet_2k3_x86_0.9.11-pre18-update2.zip instead. It has one extra check that I just thought of. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James, Well, the output after copying in the updated xennet.sys driver is about the same: XenVbd stat_no_shadows = 0 XenVbd stat_no_grants = 0 XenVbd stat_outstanding_requests = 1 *** Assertion failed: !in_mdl *** Source File: c:\projects\win-pvdrivers.hg\xennet\xennet_tx.c, line 188 Break repeatedly, break Once, Ignore, terminate Process, or terminate Thread (boipt)? p p XenVbd stat_interrupts = 474358 XenVbd stat_interrupts_for_me = 202752 XenVbd stat_reads = 119170 The line number changed, but I''m guessing that''s because of the code you added. I''ve also attached the full debug output from bootup to shutdown, including the crash, if that''s any help at all. I''m not real familiar with the Windows Debugger, so if there''s another option I should be setting, something I should add to a Watch list, etc., let me know. -Nick On Wed, 2008-10-29 at 20:20 +1100, James Harper wrote:> > I have just uploaded a xennet_2k3_x86_0.9.11-pre18-update.zip which > > contain a check for the return of NdisGetFirstBufferFromPacketSafe. > > Please try it and see what happens - just copy the sys file directly > > into c:\windows\system32\drivers and then reboot > > Actually, please try xennet_2k3_x86_0.9.11-pre18-update2.zip instead. It > has one extra check that I just thought of. > > James-- Nick Couchman Manager, Information Technology SEAKR Engineering, Inc. P: 303-790-8499 F: 303-662-8703 x 7724 W: http://www.seakr.com 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@lists.xensource.com http://lists.xensource.com/xen-users
> This is unlikely, but any chance you have the paging file disabled? > I don''t know for sure about XP, but I know 2003 can''t dump with the paging > file disabled. > DustinThis is off topic, but is there any way i can tune windows paging algorithm or other Virtuall Memeory related parameters similar to linux tunables under /proc/sys/vm/ ? Thanks Alex _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Please give update3 a go. It will still crash, but should dump out the mdl list associated with the packet. I guess Windows is giving me something unexpected... Thanks James> -----Original Message----- > From: Nick Couchman [mailto:Nick.Couchman@seakr.com] > Sent: Thursday, 30 October 2008 00:42 > To: James Harper > Cc: xen-users@lists.xensource.com; Pekka.Panula@sofor.fi > Subject: RE: [Xen-users] Stop 8E with GPL PV Drivers > > James, > Well, the output after copying in the updated xennet.sys driver isabout> the same: > XenVbd stat_no_shadows = 0 > XenVbd stat_no_grants = 0 > XenVbd stat_outstanding_requests = 1 > > *** Assertion failed: !in_mdl > *** Source File: c:\projects\win-pvdrivers.hg\xennet\xennet_tx.c,line> 188 > > Break repeatedly, break Once, Ignore, terminate Process, or terminate > Thread (boipt)? p > p > XenVbd stat_interrupts = 474358 > XenVbd stat_interrupts_for_me = 202752 > XenVbd stat_reads = 119170 > > The line number changed, but I''m guessing that''s because of the codeyou> added. I''ve also attached the full debug output from bootup to > shutdown, including the crash, if that''s any help at all. > > I''m not real familiar with the Windows Debugger, so if there''s another > option I should be setting, something I should add to a Watch list, > etc., let me know. > > -Nick > > On Wed, 2008-10-29 at 20:20 +1100, James Harper wrote: > > > I have just uploaded a xennet_2k3_x86_0.9.11-pre18-update.zipwhich> > > contain a check for the return ofNdisGetFirstBufferFromPacketSafe.> > > Please try it and see what happens - just copy the sys filedirectly> > > into c:\windows\system32\drivers and then reboot > > > > Actually, please try xennet_2k3_x86_0.9.11-pre18-update2.zipinstead. It> > has one extra check that I just thought of. > > > > James > -- > Nick Couchman > Manager, Information Technology > SEAKR Engineering, Inc. > P: 303-790-8499 > F: 303-662-8703 x 7724 > W: http://www.seakr.com > > > > This e-mail may contain confidential and privileged material for thesole> 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 theintended> 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 immediatelyby> replying to this e-mail and delete the message from your mailbox. > Information contained in this message that does not relate to thebusiness> of SEAKR is neither endorsed by nor attributable to SEAKR._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Actually make that update4> -----Original Message----- > From: James Harper > Sent: Thursday, 30 October 2008 14:22 > To: ''Nick Couchman'' > Cc: xen-users@lists.xensource.com; Pekka.Panula@sofor.fi > Subject: RE: [Xen-users] Stop 8E with GPL PV Drivers > > Please give update3 a go. It will still crash, but should dump out themdl> list associated with the packet. I guess Windows is giving mesomething> unexpected... > > Thanks > > James > > > > -----Original Message----- > > From: Nick Couchman [mailto:Nick.Couchman@seakr.com] > > Sent: Thursday, 30 October 2008 00:42 > > To: James Harper > > Cc: xen-users@lists.xensource.com; Pekka.Panula@sofor.fi > > Subject: RE: [Xen-users] Stop 8E with GPL PV Drivers > > > > James, > > Well, the output after copying in the updated xennet.sys driver isabout> > the same: > > XenVbd stat_no_shadows = 0 > > XenVbd stat_no_grants = 0 > > XenVbd stat_outstanding_requests = 1 > > > > *** Assertion failed: !in_mdl > > *** Source File: c:\projects\win-pvdrivers.hg\xennet\xennet_tx.c,line> > 188 > > > > Break repeatedly, break Once, Ignore, terminate Process, orterminate> > Thread (boipt)? p > > p > > XenVbd stat_interrupts = 474358 > > XenVbd stat_interrupts_for_me = 202752 > > XenVbd stat_reads = 119170 > > > > The line number changed, but I''m guessing that''s because of the codeyou> > added. I''ve also attached the full debug output from bootup to > > shutdown, including the crash, if that''s any help at all. > > > > I''m not real familiar with the Windows Debugger, so if there''sanother> > option I should be setting, something I should add to a Watch list, > > etc., let me know. > > > > -Nick > > > > On Wed, 2008-10-29 at 20:20 +1100, James Harper wrote: > > > > I have just uploaded a xennet_2k3_x86_0.9.11-pre18-update.zipwhich> > > > contain a check for the return ofNdisGetFirstBufferFromPacketSafe.> > > > Please try it and see what happens - just copy the sys filedirectly> > > > into c:\windows\system32\drivers and then reboot > > > > > > Actually, please try xennet_2k3_x86_0.9.11-pre18-update2.zipinstead.> It > > > has one extra check that I just thought of. > > > > > > James > > -- > > Nick Couchman > > Manager, Information Technology > > SEAKR Engineering, Inc. > > P: 303-790-8499 > > F: 303-662-8703 x 7724 > > W: http://www.seakr.com > > > > > > > > This e-mail may contain confidential and privileged material for the > sole > > use of the intended recipient. If this email is not intended foryou,> or > > you are not responsible for the delivery of this message to theintended> > recipient, please note that this message may contain SEAKREngineering> > (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 anyway.> If > > you have received this message in error, please notify usimmediately 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@lists.xensource.com http://lists.xensource.com/xen-users
Okay, attached is the output from the debug session - looks like there''s some more info there. Also, FYI, the file you uploaded isn''t a zip file, it''s the actual .sys file. I kept getting a message about a corrupt archive file and finally used the "file" command on Linux and determined that the zip file wasn''t actually a zip file. I was still able to use it, but just thought I''d let you know. -Nick>>> "James Harper" <james.harper@bendigoit.com.au> 2008/10/29 21:53 >>>Actually make that update4> -----Original Message----- > From: James Harper > Sent: Thursday, 30 October 2008 14:22 > To: ''Nick Couchman'' > Cc: xen-users@lists.xensource.com; Pekka.Panula@sofor.fi > Subject: RE: [Xen-users] Stop 8E with GPL PV Drivers > > Please give update3 a go. It will still crash, but should dump out themdl> list associated with the packet. I guess Windows is giving mesomething> unexpected... > > Thanks > > James > > > > -----Original Message----- > > From: Nick Couchman [mailto:Nick.Couchman@seakr.com] > > Sent: Thursday, 30 October 2008 00:42 > > To: James Harper > > Cc: xen-users@lists.xensource.com; Pekka.Panula@sofor.fi > > Subject: RE: [Xen-users] Stop 8E with GPL PV Drivers > > > > James, > > Well, the output after copying in the updated xennet.sys driver isabout> > the same: > > XenVbd stat_no_shadows = 0 > > XenVbd stat_no_grants = 0 > > XenVbd stat_outstanding_requests = 1 > > > > *** Assertion failed: !in_mdl > > *** Source File: c:\projects\win-pvdrivers.hg\xennet\xennet_tx.c,line> > 188 > > > > Break repeatedly, break Once, Ignore, terminate Process, orterminate> > Thread (boipt)? p > > p > > XenVbd stat_interrupts = 474358 > > XenVbd stat_interrupts_for_me = 202752 > > XenVbd stat_reads = 119170 > > > > The line number changed, but I''m guessing that''s because of the codeyou> > added. I''ve also attached the full debug output from bootup to > > shutdown, including the crash, if that''s any help at all. > > > > I''m not real familiar with the Windows Debugger, so if there''sanother> > option I should be setting, something I should add to a Watch list, > > etc., let me know. > > > > -Nick > > > > On Wed, 2008-10-29 at 20:20 +1100, James Harper wrote: > > > > I have just uploaded a xennet_2k3_x86_0.9.11-pre18-update.zipwhich> > > > contain a check for the return ofNdisGetFirstBufferFromPacketSafe.> > > > Please try it and see what happens - just copy the sys filedirectly> > > > into c:\windows\system32\drivers and then reboot > > > > > > Actually, please try xennet_2k3_x86_0.9.11-pre18-update2.zipinstead.> It > > > has one extra check that I just thought of. > > > > > > James > > -- > > Nick Couchman > > Manager, Information Technology > > SEAKR Engineering, Inc. > > P: 303-790-8499 > > F: 303-662-8703 x 7724 > > W: http://www.seakr.com > > > > > > > > This e-mail may contain confidential and privileged material for the > sole > > use of the intended recipient. If this email is not intended foryou,> or > > you are not responsible for the delivery of this message to theintended> > recipient, please note that this message may contain SEAKREngineering> > (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 anyway.> If > > you have received this message in error, please notify usimmediately 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.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@lists.xensource.com http://lists.xensource.com/xen-users
> > Okay, attached is the output from the debug session - looks likethere''s> some more info there. Also, FYI, the file you uploaded isn''t a zipfile,> it''s the actual .sys file. I kept getting a message about a corrupt > archive file and finally used the "file" command on Linux anddetermined> that the zip file wasn''t actually a zip file. I was still able to useit,> but just thought I''d let you know. >D''oh. Yes I must have goofed somewhere. Pity, the version you used didn''t have one extra debug statement in it. I have just uploaded update 5, but maybe wait a bit and I''ll have a proper fix for you. The data that did come out tells me that there were 4 buffers supplied: 14 bytes (Ethernet header) 20 bytes (IP header) 8 bytes (? - normally this would be the ICMP/TCP/UDP header, but I guess you are using another protocol) 0 bytes (???) I''m pretty sure I can see the problem - the original failing ASSERT was to make sure that there was no data left over after we processed the expected data in the buffers. I did that by checking for another buffer on the end. In your case though, even though there is another buffer on the end, it has no data in it, so my check was making an invalid assumption. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
James, Here''s the output with update5: XenNet Something went wrong... analyzing XenNet total_length = 42 XenNet in_mdl = 86232020 XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 86232040 XenNet MmGetMdlByteCount(in_mdl) = 14 XenNet in_mdl = 860FC020 XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 860FC040 XenNet MmGetMdlByteCount(in_mdl) = 20 XenNet in_mdl = 86233020 XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 86233060 XenNet MmGetMdlByteCount(in_mdl) = 8 XenNet in_mdl = 863DDD40 XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 863DDCC0 XenNet MmGetMdlByteCount(in_mdl) = 0 *** Assertion failed: FALSE *** Source File: c:\projects\win-pvdrivers.hg\xennet\xennet_tx.c, line 200 If you need the full output, I''ll be happy to send that along, too. -Nick>>> "James Harper" <james.harper@bendigoit.com.au> 2008/10/30 20:35 >>> > > Okay, attached is the output from the debug session - looks likethere''s> some more info there. Also, FYI, the file you uploaded isn''t a zipfile,> it''s the actual .sys file. I kept getting a message about a corrupt > archive file and finally used the "file" command on Linux anddetermined> that the zip file wasn''t actually a zip file. I was still able to useit,> but just thought I''d let you know. >D''oh. Yes I must have goofed somewhere. Pity, the version you used didn''t have one extra debug statement in it. I have just uploaded update 5, but maybe wait a bit and I''ll have a proper fix for you. The data that did come out tells me that there were 4 buffers supplied: 14 bytes (Ethernet header) 20 bytes (IP header) 8 bytes (? - normally this would be the ICMP/TCP/UDP header, but I guess you are using another protocol) 0 bytes (???) I''m pretty sure I can see the problem - the original failing ASSERT was to make sure that there was no data left over after we processed the expected data in the buffers. I did that by checking for another buffer on the end. In your case though, even though there is another buffer on the end, it has no data in it, so my check was making an invalid assumption. 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@lists.xensource.com http://lists.xensource.com/xen-users
Perfect. I''m just working on a fix. Thanks James> -----Original Message----- > From: Nick Couchman [mailto:Nick.Couchman@seakr.com] > Sent: Friday, 31 October 2008 14:14 > To: James Harper > Cc: xen-users@lists.xensource.com; Pekka.Panula@sofor.fi > Subject: RE: [Xen-users] Stop 8E with GPL PV Drivers > > James, > Here''s the output with update5: > > XenNet Something went wrong... analyzing > XenNet total_length = 42 > XenNet in_mdl = 86232020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 86232040 > XenNet MmGetMdlByteCount(in_mdl) = 14 > XenNet in_mdl = 860FC020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 860FC040 > XenNet MmGetMdlByteCount(in_mdl) = 20 > XenNet in_mdl = 86233020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 86233060 > XenNet MmGetMdlByteCount(in_mdl) = 8 > XenNet in_mdl = 863DDD40 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 863DDCC0 > XenNet MmGetMdlByteCount(in_mdl) = 0 > > *** Assertion failed: FALSE > *** Source File: c:\projects\win-pvdrivers.hg\xennet\xennet_tx.c,line> 200 > > If you need the full output, I''ll be happy to send that along, too. > > -Nick > > >>> "James Harper" <james.harper@bendigoit.com.au> 2008/10/30 20:35 >>> > > > > Okay, attached is the output from the debug session - looks like > there''s > > some more info there. Also, FYI, the file you uploaded isn''t a zip > file, > > it''s the actual .sys file. I kept getting a message about a corrupt > > archive file and finally used the "file" command on Linux and > determined > > that the zip file wasn''t actually a zip file. I was still able touse> it, > > but just thought I''d let you know. > > > > D''oh. Yes I must have goofed somewhere. Pity, the version you used > didn''t have one extra debug statement in it. I have just uploadedupdate> 5, but maybe wait a bit and I''ll have a proper fix for you. > > The data that did come out tells me that there were 4 bufferssupplied:> 14 bytes (Ethernet header) > 20 bytes (IP header) > 8 bytes (? - normally this would be the ICMP/TCP/UDP header, but Iguess> you are using another protocol) > 0 bytes (???) > > I''m pretty sure I can see the problem - the original failing ASSERTwas> to make sure that there was no data left over after we processed the > expected data in the buffers. I did that by checking for anotherbuffer> on the end. In your case though, even though there is another bufferon> the end, it has no data in it, so my check was making an invalid > assumption. > > James > > > ________________________________ > > This e-mail may contain confidential and privileged material for thesole> 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 theintended> 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 immediatelyby> replying to this e-mail and delete the message from your mailbox. > Information contained in this message that does not relate to thebusiness> of SEAKR is neither endorsed by nor attributable to SEAKR._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
> > James, > Here''s the output with update5: > > XenNet Something went wrong... analyzing > XenNet total_length = 42 > XenNet in_mdl = 86232020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 86232040 > XenNet MmGetMdlByteCount(in_mdl) = 14 > XenNet in_mdl = 860FC020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 860FC040 > XenNet MmGetMdlByteCount(in_mdl) = 20 > XenNet in_mdl = 86233020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 86233060 > XenNet MmGetMdlByteCount(in_mdl) = 8 > XenNet in_mdl = 863DDD40 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 863DDCC0 > XenNet MmGetMdlByteCount(in_mdl) = 0 > > *** Assertion failed: FALSE > *** Source File: c:\projects\win-pvdrivers.hg\xennet\xennet_tx.c,line> 200 > > If you need the full output, I''ll be happy to send that along, too. >I''ve pushed a -pre19 up to http://www.meadowcourt.org, but I''ve broken my test machine so I haven''t actually tested it yet. If you can make a snapshot of your DomU disk then give it a go, otherwise wait until I can verify that it at least boots. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
-pre19 should fix this problem. I have just run Microsoft''s NDIS tester and it has found 8 errors and 1 warning. Nothing too major but worth fixing. James> -----Original Message----- > From: Nick Couchman [mailto:Nick.Couchman@seakr.com] > Sent: Friday, 31 October 2008 14:14 > To: James Harper > Cc: xen-users@lists.xensource.com; Pekka.Panula@sofor.fi > Subject: RE: [Xen-users] Stop 8E with GPL PV Drivers > > James, > Here''s the output with update5: > > XenNet Something went wrong... analyzing > XenNet total_length = 42 > XenNet in_mdl = 86232020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 86232040 > XenNet MmGetMdlByteCount(in_mdl) = 14 > XenNet in_mdl = 860FC020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 860FC040 > XenNet MmGetMdlByteCount(in_mdl) = 20 > XenNet in_mdl = 86233020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 86233060 > XenNet MmGetMdlByteCount(in_mdl) = 8 > XenNet in_mdl = 863DDD40 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 863DDCC0 > XenNet MmGetMdlByteCount(in_mdl) = 0 > > *** Assertion failed: FALSE > *** Source File: c:\projects\win-pvdrivers.hg\xennet\xennet_tx.c,line> 200 > > If you need the full output, I''ll be happy to send that along, too. > > -Nick > > >>> "James Harper" <james.harper@bendigoit.com.au> 2008/10/30 20:35 >>> > > > > Okay, attached is the output from the debug session - looks like > there''s > > some more info there. Also, FYI, the file you uploaded isn''t a zip > file, > > it''s the actual .sys file. I kept getting a message about a corrupt > > archive file and finally used the "file" command on Linux and > determined > > that the zip file wasn''t actually a zip file. I was still able touse> it, > > but just thought I''d let you know. > > > > D''oh. Yes I must have goofed somewhere. Pity, the version you used > didn''t have one extra debug statement in it. I have just uploadedupdate> 5, but maybe wait a bit and I''ll have a proper fix for you. > > The data that did come out tells me that there were 4 bufferssupplied:> 14 bytes (Ethernet header) > 20 bytes (IP header) > 8 bytes (? - normally this would be the ICMP/TCP/UDP header, but Iguess> you are using another protocol) > 0 bytes (???) > > I''m pretty sure I can see the problem - the original failing ASSERTwas> to make sure that there was no data left over after we processed the > expected data in the buffers. I did that by checking for anotherbuffer> on the end. In your case though, even though there is another bufferon> the end, it has no data in it, so my check was making an invalid > assumption. > > James > > > ________________________________ > > This e-mail may contain confidential and privileged material for thesole> 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 theintended> 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 immediatelyby> replying to this e-mail and delete the message from your mailbox. > Information contained in this message that does not relate to thebusiness> of SEAKR is neither endorsed by nor attributable to SEAKR._______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users
Thanks, James - looking good so far! I''m curious as to why Symantec Ghost would be the thing to set it off. I also use the iSCSI initiator on this VM (and several others running the pre18 version of the drivers) and that''s never caused a crash, but Ghost was almost guaranteed to crash it. Very strange. I wonder what Pekka has running that was forcing it to crash. Anyway, thanks, again, for the fix and for all the hard work put into these drivers! -Nick>>> "James Harper" <james.harper@bendigoit.com.au> 10/31/08 2:02 AM >>>-pre19 should fix this problem. I have just run Microsoft''s NDIS tester and it has found 8 errors and 1 warning. Nothing too major but worth fixing. James> -----Original Message----- > From: Nick Couchman [mailto:Nick.Couchman@seakr.com] > Sent: Friday, 31 October 2008 14:14 > To: James Harper > Cc: xen-users@lists.xensource.com; Pekka.Panula@sofor.fi > Subject: RE: [Xen-users] Stop 8E with GPL PV Drivers > > James, > Here''s the output with update5: > > XenNet Something went wrong... analyzing > XenNet total_length = 42 > XenNet in_mdl = 86232020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 86232040 > XenNet MmGetMdlByteCount(in_mdl) = 14 > XenNet in_mdl = 860FC020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 860FC040 > XenNet MmGetMdlByteCount(in_mdl) = 20 > XenNet in_mdl = 86233020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 86233060 > XenNet MmGetMdlByteCount(in_mdl) = 8 > XenNet in_mdl = 863DDD40 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 863DDCC0 > XenNet MmGetMdlByteCount(in_mdl) = 0 > > *** Assertion failed: FALSE > *** Source File: c:\projects\win-pvdrivers.hg\xennet\xennet_tx.c,line> 200 > > If you need the full output, I''ll be happy to send that along, too. > > -Nick > > >>> "James Harper" <james.harper@bendigoit.com.au> 2008/10/30 20:35 >>> > > > > Okay, attached is the output from the debug session - looks like > there''s > > some more info there. Also, FYI, the file you uploaded isn''t a zip > file, > > it''s the actual .sys file. I kept getting a message about a corrupt > > archive file and finally used the "file" command on Linux and > determined > > that the zip file wasn''t actually a zip file. I was still able touse> it, > > but just thought I''d let you know. > > > > D''oh. Yes I must have goofed somewhere. Pity, the version you used > didn''t have one extra debug statement in it. I have just uploadedupdate> 5, but maybe wait a bit and I''ll have a proper fix for you. > > The data that did come out tells me that there were 4 bufferssupplied:> 14 bytes (Ethernet header) > 20 bytes (IP header) > 8 bytes (? - normally this would be the ICMP/TCP/UDP header, but Iguess> you are using another protocol) > 0 bytes (???) > > I''m pretty sure I can see the problem - the original failing ASSERTwas> to make sure that there was no data left over after we processed the > expected data in the buffers. I did that by checking for anotherbuffer> on the end. In your case though, even though there is another bufferon> the end, it has no data in it, so my check was making an invalid > assumption. > > James > > > ________________________________ > > This e-mail may contain confidential and privileged material for thesole> 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 theintended> 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 immediatelyby> replying to this e-mail and delete the message from your mailbox. > Information contained in this message that does not relate to thebusiness> of SEAKR is neither endorsed by nor attributable to SEAKR.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@lists.xensource.com http://lists.xensource.com/xen-users
BTW - the 8 errors and 1 warning - are those ones in the pre18 version that you fixed in pre19, or still present in pre19? Just curious... -Nick>>> "James Harper" <james.harper@bendigoit.com.au> 10/31/08 2:02 AM >>>-pre19 should fix this problem. I have just run Microsoft''s NDIS tester and it has found 8 errors and 1 warning. Nothing too major but worth fixing. James> -----Original Message----- > From: Nick Couchman [mailto:Nick.Couchman@seakr.com] > Sent: Friday, 31 October 2008 14:14 > To: James Harper > Cc: xen-users@lists.xensource.com; Pekka.Panula@sofor.fi > Subject: RE: [Xen-users] Stop 8E with GPL PV Drivers > > James, > Here''s the output with update5: > > XenNet Something went wrong... analyzing > XenNet total_length = 42 > XenNet in_mdl = 86232020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 86232040 > XenNet MmGetMdlByteCount(in_mdl) = 14 > XenNet in_mdl = 860FC020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 860FC040 > XenNet MmGetMdlByteCount(in_mdl) = 20 > XenNet in_mdl = 86233020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 86233060 > XenNet MmGetMdlByteCount(in_mdl) = 8 > XenNet in_mdl = 863DDD40 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 863DDCC0 > XenNet MmGetMdlByteCount(in_mdl) = 0 > > *** Assertion failed: FALSE > *** Source File: c:\projects\win-pvdrivers.hg\xennet\xennet_tx.c,line> 200 > > If you need the full output, I''ll be happy to send that along, too. > > -Nick > > >>> "James Harper" <james.harper@bendigoit.com.au> 2008/10/30 20:35 >>> > > > > Okay, attached is the output from the debug session - looks like > there''s > > some more info there. Also, FYI, the file you uploaded isn''t a zip > file, > > it''s the actual .sys file. I kept getting a message about a corrupt > > archive file and finally used the "file" command on Linux and > determined > > that the zip file wasn''t actually a zip file. I was still able touse> it, > > but just thought I''d let you know. > > > > D''oh. Yes I must have goofed somewhere. Pity, the version you used > didn''t have one extra debug statement in it. I have just uploadedupdate> 5, but maybe wait a bit and I''ll have a proper fix for you. > > The data that did come out tells me that there were 4 bufferssupplied:> 14 bytes (Ethernet header) > 20 bytes (IP header) > 8 bytes (? - normally this would be the ICMP/TCP/UDP header, but Iguess> you are using another protocol) > 0 bytes (???) > > I''m pretty sure I can see the problem - the original failing ASSERTwas> to make sure that there was no data left over after we processed the > expected data in the buffers. I did that by checking for anotherbuffer> on the end. In your case though, even though there is another bufferon> the end, it has no data in it, so my check was making an invalid > assumption. > > James > > > ________________________________ > > This e-mail may contain confidential and privileged material for thesole> 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 theintended> 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 immediatelyby> replying to this e-mail and delete the message from your mailbox. > Information contained in this message that does not relate to thebusiness> of SEAKR is neither endorsed by nor attributable to SEAKR.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@lists.xensource.com http://lists.xensource.com/xen-users
Still in -pre19 mostly. In an extended test I can still get a BSoD too, so still a way to go. -----Original Message----- From: "Nick Couchman"<Nick.Couchman@seakr.com> Sent: 31/10/08 11:26:04 PM To: "james.harper@bendigoit.com.au"<james.harper@bendigoit.com.au> Cc: "xen-users@lists.xensource.com"<xen-users@lists.xensource.com>, "Pekka.Panula@sofor.fi"<Pekka.Panula@sofor.fi> Subject: RE: [Xen-users] Stop 8E with GPL PV Drivers BTW - the 8 errors and 1 warning - are those ones in the pre18 version that you fixed in pre19, or still present in pre19? Just curious... -Nick>>> "James Harper" <james.harper@bendigoit.com.au> 10/31/08 2:02 AM >>>-pre19 should fix this problem. I have just run Microsoft''s NDIS tester and it has found 8 errors and 1 warning. Nothing too major but worth fixing. James> -----Original Message----- > From: Nick Couchman [mailto:Nick.Couchman@seakr.com] > Sent: Friday, 31 October 2008 14:14 > To: James Harper > Cc: xen-users@lists.xensource.com; Pekka.Panula@sofor.fi > Subject: RE: [Xen-users] Stop 8E with GPL PV Drivers > > James, > Here''s the output with update5: > > XenNet Something went wrong... analyzing > XenNet total_length = 42 > XenNet in_mdl = 86232020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 86232040 > XenNet MmGetMdlByteCount(in_mdl) = 14 > XenNet in_mdl = 860FC020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 860FC040 > XenNet MmGetMdlByteCount(in_mdl) = 20 > XenNet in_mdl = 86233020 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 86233060 > XenNet MmGetMdlByteCount(in_mdl) = 8 > XenNet in_mdl = 863DDD40 > XenNet MmGetSystemAddressForMdlSafe(in_mdl) = 863DDCC0 > XenNet MmGetMdlByteCount(in_mdl) = 0 > > *** Assertion failed: FALSE > *** Source File: c:\projects\win-pvdrivers.hg\xennet\xennet_tx.c,line> 200 > > If you need the full output, I''ll be happy to send that along, too. > > -Nick > > >>> "James Harper" <james.harper@bendigoit.com.au> 2008/10/30 20:35 >>> > > > > Okay, attached is the output from the debug session - looks like > there''s > > some more info there. Also, FYI, the file you uploaded isn''t a zip > file, > > it''s the actual .sys file. I kept getting a message about a corrupt > > archive file and finally used the "file" command on Linux and > determined > > that the zip file wasn''t actually a zip file. I was still able touse> it, > > but just thought I''d let you know. > > > > D''oh. Yes I must have goofed somewhere. Pity, the version you used > didn''t have one extra debug statement in it. I have just uploadedupdate> 5, but maybe wait a bit and I''ll have a proper fix for you. > > The data that did come out tells me that there were 4 bufferssupplied:> 14 bytes (Ethernet header) > 20 bytes (IP header) > 8 bytes (? - normally this would be the ICMP/TCP/UDP header, but Iguess> you are using another protocol) > 0 bytes (???) > > I''m pretty sure I can see the problem - the original failing ASSERTwas> to make sure that there was no data left over after we processed the > expected data in the buffers. I did that by checking for anotherbuffer> on the end. In your case though, even though there is another bufferon> the end, it has no data in it, so my check was making an invalid > assumption. > > James > > > ________________________________ > > This e-mail may contain confidential and privileged material for thesole> 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 theintended> 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 immediatelyby> replying to this e-mail and delete the message from your mailbox. > Information contained in this message that does not relate to thebusiness> of SEAKR is neither endorsed by nor attributable to SEAKR.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@lists.xensource.com http://lists.xensource.com/xen-users
> > Thanks, James - looking good so far! I''m curious as to why SymantecGhost> would be the thing to set it off. I also use the iSCSI initiator onthis> VM (and several others running the pre18 version of the drivers) and > that''s never caused a crash, but Ghost was almost guaranteed to crashit.> Very strange. I wonder what Pekka has running that was forcing it to > crash. >The crash was caused by the GPLPV drivers failing to respond correctly to an unusual (but not invalid) arrangement of buffers. Windows doesn''t appear to produce this combination (or at least it never has during my testing) but obviously other software does. I''m sure Ghost wouldn''t be the only package to cause it. James _______________________________________________ Xen-users mailing list Xen-users@lists.xensource.com http://lists.xensource.com/xen-users