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@xxxxxxxxx]
> Sent: Thursday, 30 October 2008 00:42
> To: James Harper
> Cc: xen-users@xxxxxxxxxxxxxxxxxxx; Pekka.Panula@xxxxxxxx
> Subject: RE: [Xen-users] Stop 8E with GPL PV Drivers
>
> 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@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
Home