|
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@xxxxxxxxxxxxxxxx> 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.
| 
