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


Re: [Xen-devel] Creating a domU on x86 crashes dom0

To: David F Barrera <dfbp@xxxxxxxxxx>
Subject: Re: [Xen-devel] Creating a domU on x86 crashes dom0
From: Paul Larson <plars@xxxxxxxxxxxxxxxxxxxx>
Date: Wed, 24 Aug 2005 09:45:06 -0500
Cc: "List: Xen Developers" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Bill Burns <billburnseh@xxxxxxxxx>
Delivery-date: Wed, 24 Aug 2005 14:43:19 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1124893460.31388.11.camel@dbarrera_tp>
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>
References: <f320583105082407131d42b5f1@xxxxxxxxxxxxxx> <1124893460.31388.11.camel@dbarrera_tp>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Wed, 2005-08-24 at 09:24 -0500, David F Barrera wrote:
> On Wed, 2005-08-24 at 10:13 -0400, Bill Burns wrote:
> > 
> > I am seeing a very similar symptom with restoring a domU
> > that has networking enabled. The kernel BUG netback.c line 349.
> > 
> > If I create a domU with no networking I can create/save/restore fine.
> I can confirm that. I can create a domU with no networking.
> > 
> > Here is my stack trace for the restore of the domU with networking:
> > 
> >  Bill
> > 
> > kernel BUG at drivers/xen/netback/netback.c:349 (net_rx_action)!
> >  [<c02bd43c>] net_rx_action+0x46c/0x500
> >  [<c0381aff>] br_pass_frame_up_finish+0xf/0x20
> >  [<c0381b8c>] br_pass_frame_up+0x7c/0x80
I've seen this also, see bug #185

If you want to workaround it, just turn off CONFIG_XEN_NETDEV_GRANT_TX
and CONFIG_XEN_NETDEV_GRANT_RX for now in your kernel config.

Paul Larson

Attachment: signature.asc
Description: This is a digitally signed message part

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>