All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Xu, Dongxiao" <dongxiao.xu@intel.com>
To: Gerald Turner <gturner@unzane.com>,
	Jeremy Fitzhardinge <jeremy@goop.org>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: RE: Re: new netfront and occasional receive path lockup
Date: Mon, 13 Sep 2010 08:54:52 +0800	[thread overview]
Message-ID: <D5AB6E638E5A3E4B8F4406B113A5A19A2A658C2F@shsmsx501.ccr.corp.intel.com> (raw)
In-Reply-To: <87bp82cxwn.fsf@headboard.unzane.com>

Gerald Turner wrote:
> Gerald Turner <gturner@unzane.com> writes:
> 
>> Jeremy Fitzhardinge <jeremy@goop.org> writes:
>> 
>>>  On 09/12/2010 11:00 AM, Gerald Turner wrote:
>>>> I examined the Debian linux-image-2.6.32-5-xen-amd64 package and
>>>> confirmed the netfront driver is patched with an earlier version
>>>> the smartpoll code. 
>>>> 
>>>> I manually merged Debian's kernel with Jeremy's updates to the
>>>> netfront driver in his git repository.
>>>> 
>>>>   $ git diff
>>>> 5473680bdedb7a62e641970119e6e9381a8d80f4..3b966565a89659f938a4fd662c
>>>> 8475f0c00e0606 
>>>> 
>>>> Deployed this new image on all domU's (except for two of them, as a
>>>> control group) and updated grub kernel parameter with
>>>> xen_netfront.use_smartpoll=0.
>>> 
>>> That's good to hear.  But I also included a fix from Dongxiao which,
>>> if correct, means it should work with use_smartpoll=1 (or nothing,
>>> as that's the default).  Could you verify whether the fix in
>>> cb09635065163a933d0d00d077ddd9f0c0a908a1 does actually work or not?
>>> 
>> 
>> I've been running with use_smartpoll=1 for a few hours this
>> afternoon, looks like Dongxiao's bugfix works.
>> 
> 
> I spoke too soon!  use_smartpoll set to 1 and still exhibits the
> problem, a few domU's lost network after about 60 minutes of uptime.
> Sorry for the bad news... 

Hi Gerald,

Sorry for the inconvinience. I will continue to look into it.

Does this bug only happen when you launch multiple domUs?
I tried a single domU and could not catch the bug.

Thanks,
Dongxiao

  reply	other threads:[~2010-09-13  0:54 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-22 16:43 new netfront and occasional receive path lockup Christophe Saout
2010-08-22 18:37 ` Christophe Saout
2010-08-24  0:53   ` Jeremy Fitzhardinge
2010-08-23 14:26 ` Christophe Saout
2010-08-23 16:04   ` Konrad Rzeszutek Wilk
2010-08-23 17:09     ` Christophe Saout
2010-08-24  0:46 ` Jeremy Fitzhardinge
2010-08-25  0:51   ` Xu, Dongxiao
2010-09-09 18:50     ` Pasi Kärkkäinen
2010-09-10  0:55       ` Jeremy Fitzhardinge
2010-09-10  1:45         ` Xu, Dongxiao
2010-09-10  2:25           ` Jeremy Fitzhardinge
2010-09-10  2:37             ` Xu, Dongxiao
2010-09-10  2:42               ` Jeremy Fitzhardinge
2010-09-12  1:00           ` Gerald Turner
2010-09-12  8:55             ` Jeremy Fitzhardinge
2010-09-12 17:23               ` Pasi Kärkkäinen
2010-09-12 22:40               ` Gerald Turner
2010-09-13  0:03                 ` Gerald Turner
2010-09-13  0:54                   ` Xu, Dongxiao [this message]
2010-09-13  2:12                     ` Gerald Turner
2010-09-13  2:34                       ` Xu, Dongxiao
2010-09-13  4:38                         ` Gerald Turner
2010-09-13 16:01                           ` Gerald Turner
2010-09-13 16:08                             ` Pasi Kärkkäinen
2010-09-13 19:36                               ` Jeremy Fitzhardinge
2010-09-14  8:25                                 ` Ian Campbell
2010-09-14 17:54                                   ` Jeremy Fitzhardinge
2010-09-14 18:44                                     ` Pasi Kärkkäinen
2010-09-15  9:46                                       ` Ian Campbell
2010-09-14  0:26                             ` Xu, Dongxiao

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=D5AB6E638E5A3E4B8F4406B113A5A19A2A658C2F@shsmsx501.ccr.corp.intel.com \
    --to=dongxiao.xu@intel.com \
    --cc=gturner@unzane.com \
    --cc=jeremy@goop.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.