WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] Big network problem on recent kernel update from xen/sta

To: Fantu <fantonifabio@xxxxxxxxxx>
Subject: Re: [Xen-devel] Big network problem on recent kernel update from xen/stable2.6.32.x
From: Pasi Kärkkäinen <pasik@xxxxxx>
Date: Wed, 9 Jun 2010 18:13:08 +0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 09 Jun 2010 08:13:53 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <28831366.post@xxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <28805128.post@xxxxxxxxxxxxxxx> <28831366.post@xxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.18 (2008-05-17)
On Wed, Jun 09, 2010 at 07:45:01AM -0700, 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.
>  

At least this merge touches dom0 netback.. so if there was a bug in it, it 
could definitely cause the problems..

-- Pasi

> 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.
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel

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