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] xen vif bug

To: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] xen vif bug
From: Tony Hoyle <tmh@xxxxxxxxxxxx>
Date: Thu, 07 Jun 2007 20:52:58 +0100
Delivery-date: Thu, 07 Jun 2007 12:51:15 -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 1.5.0.10 (Windows/20070221)
Hi,

Is this the best place to report a bug?

I accidentally wrote the following in a config file:

vif         = [ 'mac==aa:00:f4:77:74:1e' ]

The == caused the network driver to oops!  Some sanity check missing
somewhere..

I've confirmed that removing the == and using the exact same configuration otherwise does not cause the bugcheck.

kernel BUG at net/core/dev.c:3326!
invalid opcode: 0000 [1] SMP
CPU 0
Modules linked in:
Pid: 9, comm: xenwatch Not tainted 2.6.20-1-xen-amd64 #1
RIP: e030:[<ffffffff8039d4cf>] [<ffffffff8039d4cf>] unregister_netdevice+0x68/0x214
RSP: e02b:ffff88000009fe20  EFLAGS: 00010206
RAX: 0000000000000003 RBX: ffff8800001a0000 RCX: 0000000000000000
RDX: 0000000000000000 RSI: ffffffff8045ab0e RDI: ffffffff804c5980
RBP: ffffffff80369d86 R08: 000000000000000a R09: 0000000000000005
R10: ffff88000009a410 R11: ffffffff8036b43c R12: ffff880000015d20
R13: ffff880000015d68 R14: ffffffff8028e3d8 R15: ffff8800001a0000
FS:  0000000000000000(0000) GS:ffffffff804d8000(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000 CR0: 000000008005003b
CR2: 0000000000000000 CR3: 0000000000201000 CR4: 0000000000002620
Process xenwatch (pid: 9, threadinfo ffff88000009e000, task ffff88000009a850)
Stack:  ffffffff8028e3d8 ffff8800001a0000 ffffffff80369d86 ffffffff8039d68c
 0000000000000005 ffffffff8036bc74 ffff88000009d400 ffff8800001a0500
 ffff880004443ac0 ffff88000009d400 ffffffff804be868 ffff880000015d68
Call Trace:
 [<ffffffff8028e3d8>] keventd_create_kthread+0x0/0x65
 [<ffffffff80369d86>] xenwatch_thread+0x0/0x145
 [<ffffffff8039d68c>] unregister_netdev+0x11/0x17
 [<ffffffff8036bc74>] backend_changed+0x838/0x86d
 [<ffffffff8028e3d8>] keventd_create_kthread+0x0/0x65
 [<ffffffff80368462>] xenbus_read_driver_state+0x26/0x36
 [<ffffffff80369d86>] xenwatch_thread+0x0/0x145
 [<ffffffff8028e3d8>] keventd_create_kthread+0x0/0x65
 [<ffffffff803691a6>] xenwatch_handle_callback+0x15/0x48
 [<ffffffff80369eb3>] xenwatch_thread+0x12d/0x145
 [<ffffffff8028e570>] autoremove_wake_function+0x0/0x2e
 [<ffffffff80369d86>] xenwatch_thread+0x0/0x145
 [<ffffffff80232abd>] kthread+0xd1/0x100
 [<ffffffff8025af68>] child_rip+0xa/0x12
 [<ffffffff8028e3d8>] keventd_create_kthread+0x0/0x65
 [<ffffffff802329ec>] kthread+0x0/0x100
 [<ffffffff8025af5e>] child_rip+0x0/0x12


Code: 0f 0b eb fe f6 83 90 00 00 00 01 74 08 48 89 df e8 11 ff ff
RIP  [<ffffffff8039d4cf>] unregister_netdevice+0x68/0x214
 RSP <ffff88000009fe20>
 <4>XENBUS: Timeout connecting to device: device/vif/0 (state 5)

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

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