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

[Xen-users] Linux DomU network crash on NetBSD Dom0

To: xen-users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Linux DomU network crash on NetBSD Dom0
From: Martin Emrich <emme@xxxxxxxxxxxxxx>
Date: Fri, 21 Mar 2008 14:03:43 +0100
Delivery-date: Fri, 21 Mar 2008 06:05:37 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Thunderbird 2.0.0.12 (X11/20080227)
Hi!

I have installed NetBSD as a Dom0 on a Box (NetBSD 4.0 i386 with Xen
3.1.3 Non-PAE), and try to run a Debian DomU with the current
linux-2.6.18.8 Xen kernel built with the Xen 3.2.0 sources (also Non-PAE).

The DomU boots fine, but as soon as I try to use the network interface
(network-bridged on Dom0), I get this:

====================
root@hackbox:~# dhclient eth1
Internet Systems Consortium DHCP Client V3.0.4
Copyright 2004-2006 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/

------------[ cut here ]------------
kernel BUG at
/root/xen-hg/linux-2.6.18-xen.hg/drivers/xen/netfront/netfront.c:785!
invalid opcode: 0000 [#1]
SMP
Modules linked in: loop
CPU:    0
EIP:    0061:[<c0260434>]    Not tainted VLI
EFLAGS: 00010286   (2.6.18.8-xenU #1)
EIP is at network_alloc_rx_buffers+0x534/0x570
eax: 00000000   ebx: dfbcd240   ecx: c1530000   edx: c15302c0
esi: c1560bc0   edi: c1530368   ebp: de827e38   esp: de827dd4
ds: 007b   es: 007b   ss: 0069
Process ifconfig (pid: 2008, ti=de826000 task=df9f6a70 task.ti=de826000)
Stack: 00000240 00000000 0001ebf6 debf4500 c1530f9c c1530000 00000081
00000000
       00000000 c15302c0 00000000 00000240 debf6000 00000001 df91a838
00000001
       ffffffff de827e34 c0127bec c14ff0c0 000000d0 df9840e4 c15302c0
c1530000
Call Trace:
 [<c0105ce9>] show_stack_log_lvl+0xa9/0xd0
 [<c0105f4d>] show_registers+0x1bd/0x240
 [<c0106107>] die+0x137/0x300
 [<c0106368>] do_trap+0x98/0xe0
 [<c0106bf1>] do_invalid_op+0xa1/0xb0
 [<c010580b>] error_code+0x2b/0x30
 [<c0263377>] network_open+0x67/0x100
 [<c027762d>] dev_open+0x3d/0x90
 [<c0275bf5>] dev_change_flags+0x55/0x130
 [<c02b2a8c>] devinet_ioctl+0x4ac/0x6a0
 [<c02b2fce>] inet_ioctl+0x8e/0xb0
 [<c026b0e6>] sock_ioctl+0x126/0x230
 [<c017a1c5>] do_ioctl+0x35/0x90
 [<c017a277>] vfs_ioctl+0x57/0x2b0
 [<c017a511>] sys_ioctl+0x41/0x70
 [<c010565f>] syscall_call+0x7/0xb
Code: 8b bc 10 f8 14 00 00 85 ff 75 3a ff 4d d8 83 7d d8 ff 75 e3 ba ff
ff ff ff e9 d0 fd ff ff 0f 0b 15 03 74 41 30 c0 e9 a6 fc ff ff <0f> 0b
11 03 74 41 30 c0 e9 75 fc ff ff 0f 0b 22 00 88 b2 2e c0
EIP: [<c0260434>] network_alloc_rx_buffers+0x534/0x570 SS:ESP 0069:de827dd4
 <0>Kernel panic - not syncing: Fatal exception in interrupt
===========================

Then the DomU restarts.

Is this a bug or an incompatibility between the Xen 3.1.3 hypervisor and
the kernel built for 3.2.0?

Thanks,

Martin

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

<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-users] Linux DomU network crash on NetBSD Dom0, Martin Emrich <=