xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: <djmagee@mageenet.net>
To: Jeremy Fitzhardinge <jeremy@goop.org>, Fantu <fantonifabio@tiscali.it>
Cc: "Xu, Dongxiao" <dongxiao.xu@intel.com>, xen-devel@lists.xensource.com
Subject: RE: Big network problem on recent kernel update fromxen/stable2.6.32.x
Date: Wed, 9 Jun 2010 18:48:50 -0400	[thread overview]
Message-ID: <EECC125FCE18E740AF561189E1260285052575@mnetexch2.adamapps.host> (raw)
In-Reply-To: <4C0FDDEB.7000305@goop.org>

I can confirm that reverting 528ea798f02... fixes the problem for me.

Doug Magee

-----Original Message-----
From: xen-devel-bounces@lists.xensource.com
[mailto:xen-devel-bounces@lists.xensource.com] On Behalf Of Jeremy
Fitzhardinge
Sent: Wednesday, June 09, 2010 2:31 PM
To: Fantu
Cc: Xu, Dongxiao; xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] Big network problem on recent kernel update
fromxen/stable2.6.32.x

On 06/09/2010 07:45 AM, Fantu wrote:
> i rebuild from commit 930edab1aba24f1807fd9ab8127006115bbd3422 and
network
> work, i think how the network problem was introduced by this commit:
> commit	528ea798f02ccb03023e72cbda665ed5c3eec6b1
> Merge branch 'xen/dom0/backend/netback-tasklet' into xen/next
>
> * xen/dom0/backend/netback-tasklet:
>   xen/netback: Use Kernel thread to replace the tasklet.
>   xen/netback: Multiple tasklets support.
>   xen/netback: Introduce a new struct type page_ext.
>   xen/netback: Move global/static variables into struct xen_netbk.
>  
> Maybe some problem with new commit not see in xen/next but see in
xen/stable
> because in xen/stable there are merging of 2.6.32.x upstream and in
xen/next
> no, there are some differences between xen/next and xen/stable who
cause
> some unexpected behaviours
>   

OK, that makes sense.  I hadn't had any problems with it, but it could
be v. dependent on how your system is configured.

Does "git revert -m 1 528ea798f02ccb03023e72cbda665ed5c3eec6b1" and
rebuilding fix the problem? If so, I'll revert it in stable until we can
sort it out.

Dongxiao, can you investigate this?

Thanks,
    J

>
> Fantu wrote:
>   
>> I see only today how with last build of kernel do from last commit
>> (27ed1b0e0dae5f1d5da5c76451bc84cb529128bd) do network of windows xp
domU
>> with gplpv 0.11.0.213 unusable, ping lost or over 1 second unable to
>> connect with rdp to domU, unable to use network from domU and
viceversa
>> Also with build with 2.6.32.14 (from commit
>> e8734951b7a8d838050277696541a7e57183bdce) have problem
>> but my last build with 2.6.32.13 not have network problem, I can not
>> remember committing but i have build on 26 may if just remember
>> All these build have same config: 
>> http://old.nabble.com/file/p28805128/config-2.6.32.15 config 
>>
>>     
>   


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

  reply	other threads:[~2010-06-09 22:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-07 13:19 Big network problem on recent kernel update from xen/stable2.6.32.x Fantu
2010-06-07 13:53 ` Big network problem on recent kernel update fromxen/stable2.6.32.x djmagee
2010-06-07 15:04   ` Pasi Kärkkäinen
2010-06-07 15:11     ` Michal Novotny
2010-06-07 16:20     ` Big network problem on recent kernel updatefromxen/stable2.6.32.x djmagee
2010-06-09 14:45 ` Big network problem on recent kernel update from xen/stable2.6.32.x Fantu
2010-06-09 15:13   ` Pasi Kärkkäinen
2010-06-09 18:31   ` Jeremy Fitzhardinge
2010-06-09 22:48     ` djmagee [this message]
2010-06-10  1:26     ` Xu, Dongxiao
2010-06-10  5:59       ` Pasi Kärkkäinen

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=EECC125FCE18E740AF561189E1260285052575@mnetexch2.adamapps.host \
    --to=djmagee@mageenet.net \
    --cc=dongxiao.xu@intel.com \
    --cc=fantonifabio@tiscali.it \
    --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 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).