From: David F Barrera <dfbp@us.ibm.com>
To: "List: Xen Developers" <xen-devel@lists.xensource.com>
Subject: Creating a domU on x86 crashes dom0
Date: Wed, 24 Aug 2005 08:25:59 -0500 [thread overview]
Message-ID: <1124889959.31385.6.camel@dbarrera_tp> (raw)
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
next reply other threads:[~2005-08-24 13:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-24 13:25 David F Barrera [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-08-24 14:13 Creating a domU on x86 crashes dom0 Bill Burns
2005-08-24 14:24 ` David F Barrera
2005-08-24 14:45 ` Paul Larson
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=1124889959.31385.6.camel@dbarrera_tp \
--to=dfbp@us.ibm.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.