Re: [Xen-devel] Error with NFS and XEN (High network load)

[Roberto Gonzalez Azevedo <rgonzalez@xxxxxxxxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Emmanuel Ackaouy wrote:
> Roberto,
> 
> I can't reproduce this on tip unstable. Tried both fragmented
> UDP tx with ttcp and same NFS dd recipe with NFS over UDP and
> 8k r/w size. I even tried NFSoverTCP for good measure (since
> your recipe didn't explicitly mount -o udp).
> 
> I notice you are running 2.6.16.27. Which xen linux patches
> did you apply? Which changeset of xen-unstable?
>

I'm using 2.6.16.13 and the latest Xen Unstable.
Typing error. Sorry, :)

Using the unstable, only crashes in domU, but xend dies and dom0 not crash.
Using the stable version, crashes in all domains (dom0 e domU).

How to apply the latest gso patches ?

Thanks.

- ----------------------------
Roberto Gonzalez Azevedo


> I wonder what versions of netfront and netback you're using.
> Have you tried tip of unstable with the latest gso patches?
> 
> Emmanuel.
> 
> On Tue, Aug 15, 2006 at 07:58:15PM -0300, Roberto Gonzalez Azevedo wrote:
>> Here is the crash:
>> root@dom0:# xm console machine
>> "
>> Unable to handle kernel NULL pointer dereference at virtual address 00000115
>>  printing eip:
>> *pde = ma 00000000 pa fffff000
>> Oops: 0002 [#1]
>> SMP
>> Modules linked in:
>> CPU:    0
>> EIP:    0061:[<c02f9f99>]    Not tainted VLI
>> EFLAGS: 00010086   (2.6.16.27-xenU_09-08-2006 #3)
>> EIP is at network_tx_buf_gc+0xdb/0x277
>> eax: 00000095   ebx: 00000087   ecx: c0508c54   edx: 00000000
>> esi: c0508380   edi: 00000085   ebp: c0499e98   esp: c0499e70
>> ds: 007b   es: 007b   ss: 0069
>> Process swapper (pid: 0, threadinfo=c0498000 task=c0434500)
>> Stack: <0>c0508c54 00000000 c0498000 c0508000 00026c3f 00026c8b 00026c6e
>> 00000000
>>        c0508408 c0508380 c0499eac c02fa230 c7d98a40 00000000 00000000
>> c0499ed4
>>        c013c911 00000107 c0508000 c0499f3c c0499f3c 00000107 00008380
>> c048d780
>> Call Trace:
>>  [<c0105580>] show_stack_log_lvl+0xb9/0x103
>>  [<c0105766>] show_registers+0x19c/0x232
>>  [<c0105a64>] die+0x116/0x233
>>  [<c01112ca>] do_page_fault+0x4e8/0x8cc
>>  [<c0104ff7>] error_code+0x2b/0x30
>>  [<c02fa230>] netif_int+0x29/0x121
>>  [<c013c911>] handle_IRQ_event+0x3c/0xac
>>  [<c013ca0d>] __do_IRQ+0x8c/0xef
>>  [<c0106a62>] do_IRQ+0x1d/0x29
>>  [<c02ee27b>] evtchn_do_upcall+0x94/0xc8
>>  [<c0105039>] hypervisor_callback+0x3d/0x48
>>  [<c010382f>] xen_idle+0x2d/0x53
>>  [<c01038c0>] cpu_idle+0x6b/0xb6
>>  [<c0102035>] rest_init+0x35/0x37
>>  [<c049a4ed>] start_kernel+0x2e7/0x392
>>  [<c010006f>] 0xc010006f
>> Code: 89 44 24 04 89 14 24 e8 cf 54 ff ff c7 84 9e d8 08 00 00 00 00 00
>> 00 8b 86 d0 00 00 00 89 84 9e d0 00 00 00 89 9e d0 00 00 00 90 <ff> 8f
>> 90 00 00 00 0f 94 c0 84 c0 75 4e 8b 4e 74 83 45 f0 01 8b
>>  <0>Kernel panic - not syncing: Fatal exception in interrupt
>> "
>>
>> And the domU dies ...
>>
>> Is it a bug ?
>> I have reported it in bugzilla as Bug id # 735.
>> Dom0 crashes using Xen Stable (3.0.2.2).
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFE40ViF+EMwkXLsEwRAg+HAJ4pqBYC1PDIJf+xzAPMFTzbN2d5lQCcCcID
kaKigAVdThbevwc3+KiQ9So=
=DsGl
-----END PGP SIGNATURE-----

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