From: Andreas Kinzler <ml-xen-devel@hfp.de>
To: xen-devel@lists.xensource.com,
James Harper <james.harper@bendigoit.com.au>
Subject: Re: RE: BSOD in GPLPV rev928 in xennet.sys
Date: Fri, 10 Jun 2011 10:44:07 +0200 [thread overview]
Message-ID: <4DF1D957.10708@hfp.de> (raw)
In-Reply-To: <AEC6C66638C05B468B556EA548C1A77D01D5794C@trantor>
>> -----Original Message-----
>> From: Andreas Kinzler [mailto:ml-xen-devel@hfp.de]
>> Sent: Thursday, 9 June 2011 04:38
>> To: xen-devel@lists.xensource.com; James Harper
>> Subject: BSOD in GPLPV rev928 in xennet.sys
>>
>> Hello James,
>>
>> on Windows 2008 R2 SP1 I get a BSOD on GPLPV setup. After some
> analyzing
>> I found that it is a "null ptr read" in the call to
>> NdisFreeToNPagedLookasideList. File is xennet6_tx.c line 336.
>>
>> length = XenNet_QueryData(&pi, coalesce_remaining);
>> va = NdisBufferVirtualAddressSafe(pi.curr_mdl,
> LowPagePriority);
>> if (!va)
>> {
>> KdPrint((__DRIVER_NAME " failed to map buffer va -
> partial
>> send\n"));
>> coalesce_remaining = 0;
>> remaining -= min(PAGE_SIZE, remaining);
>> NdisFreeToNPagedLookasideList(&xi->tx_lookaside_list,
>> coalesce_buf);
>> }
>> else
>> {
>>
> I can't see how that situation could arise without there being some
> memory corruption somewhere... coalesce_buf is checked for NULL before
> the call to NdiFreeToNPageLookasideList. Did you get the "Failed to map
> buffer va - partial send" message in the logs?
I am not running any debuggers, I got the information from analyzing
disassembled code listings and the minidump. I may have a look at
debuggers (my time is somewhat limited).
Would you consider the rev928 version stable? What is the latest stable
version in your opinion?
Regards Andreas
prev parent reply other threads:[~2011-06-10 8:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 18:38 BSOD in GPLPV rev928 in xennet.sys Andreas Kinzler
2011-06-09 8:56 ` James Harper
2011-06-10 8:44 ` Andreas Kinzler [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DF1D957.10708@hfp.de \
--to=ml-xen-devel@hfp.de \
--cc=james.harper@bendigoit.com.au \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).