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/
Home Products Support Community News


[Xen-bugs] [Bug 735] New: Error with NFS and XEN Unstable (High network

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 735] New: Error with NFS and XEN Unstable (High network load)
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Thu, 10 Aug 2006 08:53:30 -0700
Delivery-date: Thu, 10 Aug 2006 08:54:45 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Reply-to: bugs@xxxxxxxxxxxxxxxxxx
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

           Summary: Error with NFS and XEN Unstable (High network load)
           Product: Xen
           Version: unstable
          Platform: x86
               URL: http://www.censanet.com.br
        OS/Version: Linux-2.6
            Status: NEW
          Severity: critical
          Priority: P1
         Component: Unspecified
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: rgonzalez@xxxxxxxxxxxxxxx

Error with NFS and XEN Unstable (High network load):

On domU machine:
root@domU:# mount -t nfs real-machine-not-xen-or-any-virtual:/mnt /data

root@domU:# time dd if=/dev/zero of=/data/test.txt bs=16k count=16384

My hardware is Dell PowerEdge 1850, network card module e1000.

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]
Modules linked in:
CPU:    0
EIP:    0061:[<c02f9f99>]    Not tainted VLI
EFLAGS: 00010086   ( #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
       c0508408 c0508380 c0499eac c02fa230 c7d98a40 00000000 00000000
       c013c911 00000107 c0508000 c0499f3c c0499f3c 00000107 00008380
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 ...

Xen Unstable, Kernel 
(dom0 = Ubuntu 6.0.6 Dapper, domU = Slackware 10.2)

Configure bugmail: 
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>