xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Fantu <fantonifabio@tiscali.it>
To: xen-devel@lists.xensource.com
Subject: Re: Big network problem on recent kernel update from xen/stable2.6.32.x
Date: Wed, 9 Jun 2010 07:45:01 -0700 (PDT)	[thread overview]
Message-ID: <28831366.post@talk.nabble.com> (raw)
In-Reply-To: <28805128.post@talk.nabble.com>


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


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 
> 

-- 
View this message in context: http://old.nabble.com/Big-network-problem-on-recent-kernel-update-from-xen-stable2.6.32.x-tp28805128p28831366.html
Sent from the Xen - Dev mailing list archive at Nabble.com.

  parent reply	other threads:[~2010-06-09 14:45 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 ` Fantu [this message]
2010-06-09 15:13   ` Big network problem on recent kernel update from xen/stable2.6.32.x Pasi Kärkkäinen
2010-06-09 18:31   ` Jeremy Fitzhardinge
2010-06-09 22:48     ` Big network problem on recent kernel update fromxen/stable2.6.32.x djmagee
2010-06-10  1:26     ` Big network problem on recent kernel update from xen/stable2.6.32.x 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=28831366.post@talk.nabble.com \
    --to=fantonifabio@tiscali.it \
    --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).