The x86 build is broken. DomU will not boot on both RHEL 4 and SLES 9,
and dom0 crashes.
changeset: 6375:603f55eaa690ef8d47e54bdb57e20fb3266d8f56
tag: tip
user: kaf24@firebug.cl.cam.ac.uk
date: Wed Aug 24 05:48:24 2005
summary: Initialise syscall32 vsyscall page early, as it may be
needed
On the RHEL 4 box, dom0 did not crash the first time that I attempted to
create a domU. The log showed this:
Red Hat Enterprise Linux AS release 4 (Nahant)
Kernel 2.6.12-xen0 on an i686
lamb5 login: smp_send_stop disable_local_APIC
(XEN) DOM0: (file=mm.c, line=2466) PTE entry 11ed5 for address d0865000
doesn''t match frame 11ede
(XEN) (file=grant_table.c, line=1071) Grant unref rd(1) ld(0) frm(11ed5)
flgs(0).
Red Hat Enterprise Linux AS release 4 (Nahant)
Kernel 2.6.12-xen0 on an i686
lamb5 login:
--
On the second attempt to create a domU, dom0 crashed:
Red Hat Enterprise Linux AS release 4 (Nahant)
Kernel 2.6.12-xen0 on an i686
lamb5 login: (XEN) (file=grant_table.c, line=1152) Bad flags (5) or dom
(0). (NB. expected dom 0)
(XEN) gnttab_donate: gnttab_prepare_for_transfer fails
kernel BUG at drivers/xen/netback/netback.c:349 (net_rx_action)!
[<c030b1dc>] net_rx_action+0x4ac/0x540
[<c045ad06>] __br_forward+0x66/0x80
[<c045aba0>] br_forward_finish+0x0/0x80
[<c045aee8>] br_flood_forward+0x28/0x30
[<c045aca0>] __br_forward+0x0/0x80
[<c045ba11>] br_handle_frame_finish+0x141/0x160
[<c045fb88>] br_nf_pre_routing_finish+0x178/0x420
[<c045b8d0>] br_handle_frame_finish+0x0/0x160
[<c04305d1>] tcp_ack_saw_tstamp+0x21/0x60
[<c0430e2f>] tcp_clean_rtx_queue+0x41f/0x450
[<c011cc3c>] recalc_task_prio+0x8c/0x160
[<c041798d>] nf_iterate+0x5d/0x90
[<c045fa10>] br_nf_pre_routing_finish+0x0/0x420
[<c045fa10>] br_nf_pre_routing_finish+0x0/0x420
[<c0417dee>] nf_hook_slow+0x7e/0x140
[<c045fa10>] br_nf_pre_routing_finish+0x0/0x420
[<c045b8d0>] br_handle_frame_finish+0x0/0x160
[<c04604c9>] br_nf_pre_routing+0x339/0x4b0
[<c045fa10>] br_nf_pre_routing_finish+0x0/0x420
[<c041798d>] nf_iterate+0x5d/0x90
[<c045b8d0>] br_handle_frame_finish+0x0/0x160
[<c045b8d0>] br_handle_frame_finish+0x0/0x160
[<c0417dee>] nf_hook_slow+0x7e/0x140
[<c04056c1>] kfree_skbmem+0x21/0x30
[<c0421236>] ip_rcv+0x86/0x4f0
[<c045b8d0>] br_handle_frame_finish+0x0/0x160
[<c040c54d>] netif_receive_skb+0x20d/0x260
[<c040c65b>] process_backlog+0xbb/0x190
[<c0127cb2>] tasklet_action+0x72/0x120
[<c01277f9>] __do_softirq+0x69/0x100
[<c0127915>] do_softirq+0x85/0xa0
[<c01279f5>] irq_exit+0x35/0x40
[<c010ee32>] do_IRQ+0x22/0x30
[<c01055c6>] evtchn_do_upcall+0x66/0xa0
[<c010a218>] hypervisor_callback+0x2c/0x34
[<c0107ad8>] xen_idle+0x38/0x90
[<c0107b65>] cpu_idle+0x35/0x50
[<c0104023>] rest_init+0x23/0x40
[<c0104080>] init+0x0/0x120
[<c057e8da>] start_kernel+0x1ba/0x210
[<c057e390>] unknown_bootoption+0x0/0x240
Kernel panic - not syncing: BUG!
(XEN) Domain 0 shutdown: rebooting machine.
DomU log:
[...]
lo IP address: 127.0.0.1/8
done
eth0
eth0 IP address: 9.3.189.177/24
done
Setting up service network . . . . . . . . . . . . . .
done.
Assertion ''ref != -ENOSPC'' failed, line 275, file
drivers/xen/blkfront/blkfront.c<1>Unable to handle kernel NULL pointer
dereference at virtual address 00000000 printing eip:
c0256bec
0d8d8000 -> *pde = 00000000:11e95001
0d8da000 -> *pme = 00000000:00000000
>From SLES 9 box:
-----------------
[...]
lo IP address: 127.0.0.1/8
done
eth0
eth0 IP address: 9.3.189.205/24
done
Setting up service network . . . . . . . . . . . . . .
done.
Starting syslog servicesend_request: I/O error, dev sda9, sector 984408
Assertion ''ref != -ENOSPC'' failed, line 275, file
drivers/xen/blkfront/blkfront.c<1>Unable to handle kernel NULL pointer
dereference at virtual address 00000000 printing eip:
c0252ecc
*pde = ma 00000000 pa 55555000
Oops: 0002 [#1]
PREEMPT SMP
Modules linked in:
CPU: 0
EIP: 0061:[<c0252ecc>] Not tainted VLI
EFLAGS: 00010246 (2.6.12-xenU)
EIP is at blkif_queue_request+0x22c/0x300
eax: 00000000 ebx: 1f513000 ecx: 00000000 edx: 00000001
esi: 00000000 edi: ffffffe4 ebp: 00000007 esp: cfcc9d90
ds: 007b es: 007b ss: 0069
Process kjournald (pid: 571, threadinfo=cfcc8000 task=c1302a40)
Stack: c03001e4 c02feea7 00000113 c030020c 0000002a 0000000e 00000000
c12d5980
--
Regards,
David F Barrera
Linux Technology Center
Systems and Technology Group, IBM
"The wisest men follow their own direction. "
Euripides
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
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! _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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 > > [<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! > > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xensource.com > http://lists.xensource.com/xen-devel-- Regards, David F Barrera Linux Technology Center Systems and Technology Group, IBM "The wisest men follow their own direction. " Euripides _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
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/0x80I''ve seen this also, see bug #185 http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=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. -- Thanks, Paul Larson plars@linuxtestproject.org http://www.linuxtestproject.org _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel