From: Dan Gora <dan.gora@gmail.com>
To: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
xen-devel@lists.xensource.com
Subject: Re: Re: PCI BAR register space written with garbage in HVM guest.
Date: Thu, 18 Mar 2010 15:27:30 -0300 [thread overview]
Message-ID: <4779de451003181127m210171e9xc5fc4ff1772f4782@mail.gmail.com> (raw)
In-Reply-To: <20100318143207.GF14445@phenom.dumpdata.com>
On Thu, Mar 18, 2010 at 11:32 AM, Konrad Rzeszutek Wilk
<konrad.wilk@oracle.com> wrote:
> On Wed, Mar 17, 2010 at 11:14:13PM -0300, Dan Gora wrote:
>> Hi all,
>>
>> I apologize for the length of this message, but I figured that it was
>> probably better to supply too much info rather than too little...
>> I've made some good progress debugging this today. The problem looks
>> pretty bizarre...
>
> I just skimmed through your e-mail and didn't dive in the r8169 code to
> see if there is something there, but I thought you might want to try
> using e1000 instead of r8169 driver and see if that makes it work?
Sure enough that fixed the problem! No more writes on fd 6, no more
PCI BAR regsiter corruption!
That's good enough for me as a workaround. I guess someone else can
have a look at this rtl8139 driver.
thanks!
dan
next prev parent reply other threads:[~2010-03-18 18:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 1:09 PCI BAR register space written with garbage in HVM guest Dan Gora
2010-03-16 1:48 ` Konrad Rzeszutek Wilk
2010-03-16 2:55 ` Dan Gora
2010-03-16 10:27 ` Jan Beulich
2010-03-16 15:20 ` Konrad Rzeszutek Wilk
2010-03-16 15:54 ` Jan Beulich
2010-03-16 10:24 ` Jan Beulich
2010-03-17 0:14 ` Dan Gora
2010-03-17 2:46 ` Konrad Rzeszutek Wilk
2010-03-17 3:31 ` Dan Gora
2010-03-18 2:14 ` Dan Gora
[not found] ` <20100318143207.GF14445@phenom.dumpdata.com>
2010-03-18 18:27 ` Dan Gora [this message]
2010-03-18 18:10 ` Konrad Rzeszutek Wilk
2010-03-18 19:56 ` Dan Gora
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=4779de451003181127m210171e9xc5fc4ff1772f4782@mail.gmail.com \
--to=dan.gora@gmail.com \
--cc=konrad.wilk@oracle.com \
--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).