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

RE: [Xen-devel] Netfront crashes after domain migration.

To: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: RE: [Xen-devel] Netfront crashes after domain migration.
From: Stefan Berger <stefanb@xxxxxxxxxx>
Date: Fri, 30 Jun 2006 18:06:29 -0400
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 30 Jun 2006 15:07:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D068C7C@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

xen-devel-bounces@xxxxxxxxxxxxxxxxxxx wrote on 06/30/2006 05:49:41 PM:

> Live or non-live?  Is this a new bug?
>

It was non-live and occurred twice. I rebooted the target machine in the meantime and now cannot reproduce it anymore.

   Stefan

> > I am migrating a domain accross the network and get the following
> error.
> > Both machines are running the latest checkout - up to changeset 10574.
> >
> >    Stefan
> >
> >
> > ------------[ cut here ]------------
> > kernel BUG at drivers/xen/netfront/netfront.c:607!
> > invalid opcode: 0000 [#1]
> > SMP
> > Modules linked in:
> > CPU:    0
> > EIP:    0061:[<c0265e72>]    Not tainted VLI
> > EFLAGS: 00010086   (2.6.16.13-xen #4)
> > EIP is at network_alloc_rx_buffers+0x362/0x380
> > eax: ffffffe4   ebx: ffffffe4   ecx: c0041060   edx: 00000801
> > esi: 00000101   edi: c0040380   ebp: 00000100   esp: c047bec0
> > ds: 007b   es: 007b   ss: 0069
> > Process xenwatch (pid: 8, threadinfo=c047a000 task=c100e570)
> > Stack: <0>c33b49c0 c0041ee0 c0040428 c33b49c0 c439de80 00000025
> 000000db
> > c0040000
> >       c0040000 c025b93d 00000000 c0479e00 c047a000 c0429300 00000005
> > c0040000
> >       00000025 00000101 00000101 c0040380 c02671d1 c0429300 c047a000
> > c0040000
> > Call Trace:
> > [<c025b93d>] xenbus_scanf+0x1d/0x50
> > [<c02671d1>] network_connect+0x1e1/0x230
> > [<c0265677>] backend_changed+0x37/0x70
> > [<c025ca38>] otherend_changed+0x78/0x80
> > [<c025be82>] xenwatch_handle_callback+0x12/0x50
> > [<c025c00c>] xenwatch_thread+0x14c/0x160
> > [<c025be70>] xenwatch_handle_callback+0x0/0x50
> > [<c0134d90>] autoremove_wake_function+0x0/0x50
> > [<c0134d90>] autoremove_wake_function+0x0/0x50
> > [<c011972d>] complete+0x3d/0x60
> > [<c025bec0>] xenwatch_thread+0x0/0x160
> > [<c0134885>] kthread+0xa5/0xf0
> > [<c01347e0>] kthread+0x0/0xf0
> > [<c0102efd>] kernel_thread_helper+0x5/0x18
> > Code: a0 00 00 00 8d 14 09 39 c2 0f 46 c2 89 87 a4 00 00 00 e9 7d fd
> ff ff
> > bb 01 00 00 00 8d 4c 24 20 e8 14 b3 e9 ff 3b 44 24 18 eb 85 <0f> 0b 5f
> 02
> > 8c
> > 8f 36 c0 e9 d5 fd ff ff c7 04 24 ac 8f 36 c0 e8
> >
> >
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>