[prev in list] [next in list] [prev in thread] [next in thread] 

List:       xen-devel
Subject:    RE: [Xen-devel] Netfront crashes after domain migration.
From:       Stefan Berger <stefanb () us ! ibm ! com>
Date:       2006-06-30 22:06:29
Message-ID: OFF4392CFB.D94D276C-ON8525719D.00794D1C-8525719D.0079706E () us ! ibm ! com
[Download RAW message or body]

This is a multipart message in MIME format.

This is a multipart message in MIME format.
--=_alternative 0079706B8525719D_=
Content-Type: text/plain; charset="US-ASCII"

xen-devel-bounces@lists.xensource.com 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@lists.xensource.com
> http://lists.xensource.com/xen-devel

--=_alternative 0079706B8525719D_=
Content-Type: text/html; charset="US-ASCII"


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



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


[prev in list] [next in list] [prev in thread] [next in thread] 

Configure | About | News | Add a list | Sponsored by KoreLogic