Re: Big network problem on recent kernel update from xen/stable2.6.32.x

[Jeremy Fitzhardinge <jeremy@goop.org>]

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 
>>
>>     
>