From: Bill Burns <billburnseh@gmail.com>
To: "List: Xen Developers" <xen-devel@lists.xensource.com>
Subject: Re: Creating a domU on x86 crashes dom0
Date: Wed, 24 Aug 2005 10:13:39 -0400 [thread overview]
Message-ID: <f320583105082407131d42b5f1@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1858 bytes --]
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.
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
[<c0381af0>] br_pass_frame_up_finish+0x0/0x20
[<c0381c77>] br_handle_frame_finish+0xe7/0x160
[<c0385e48>] br_nf_pre_routing_finish+0x178/0x420
[<e0e432d4>] veth_recv_interrupt+0x1a4/0x610 [egenera_veth]
[<c033dc4d>] nf_iterate+0x5d/0x90
[<c0385cd0>] br_nf_pre_routing_finish+0x0/0x420
[<c0385cd0>] br_nf_pre_routing_finish+0x0/0x420
[<c033e0ae>] nf_hook_slow+0x7e/0x140
[<c034336a>] rt_intern_hash+0x2aa/0x3e0
[<c014d598>] kmem_cache_alloc+0x98/0xb0
[<c0344891>] ip_route_input_mc+0x231/0x2e0
[<c033dc4d>] nf_iterate+0x5d/0x90
[<c033dc4d>] nf_iterate+0x5d/0x90
[<c032b981>] kfree_skbmem+0x21/0x30
[<c03471a0>] ip_local_deliver+0x110/0x250
[<c0347793>] ip_rcv+0x323/0x4f0
[<c0347960>] ip_rcv_finish+0x0/0x280
[<c033280d>] netif_receive_skb+0x20d/0x260
[<c033291b>] process_backlog+0xbb/0x190
[<c0125cb2>] tasklet_action+0x72/0x120
[<c01257f9>] __do_softirq+0x69/0x100
[<c0125915>] do_softirq+0x85/0xa0
[<c01259f5>] irq_exit+0x35/0x40
[<c010e7c2>] do_IRQ+0x22/0x30
[<c01055c6>] evtchn_do_upcall+0x66/0xa0
[<c010e7c2>] do_IRQ+0x22/0x30
[<c0109df8>] hypervisor_callback+0x2c/0x34
[<c01077b8>] xen_idle+0x38/0x90
[<c0107845>] cpu_idle+0x35/0x50
[<c0104023>] rest_init+0x23/0x40
[<c0104080>] init+0x0/0x120
[<c044e8da>] start_kernel+0x1ba/0x210
[<c044e390>] unknown_bootoption+0x0/0x240
Kernel panic - not syncing: BUG!
[-- Attachment #1.2: Type: text/html, Size: 2245 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2005-08-24 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 14:13 Bill Burns [this message]
2005-08-24 14:24 ` Creating a domU on x86 crashes dom0 David F Barrera
2005-08-24 14:45 ` Paul Larson
-- strict thread matches above, loose matches on Subject: below --
2005-08-24 13:25 David F Barrera
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f320583105082407131d42b5f1@mail.gmail.com \
--to=billburnseh@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.