| |
|
 |
|
 |
|
|
|
| |
|
|
xen-bugs
[Xen-bugs] [Bug 93] x86_64 - Dom0 crashes when DomU is created.
http://bugzilla.xensource.com/cgi-bin/bugzilla/show_bug.cgi?id=93
------- Additional Comments From jyoung5@xxxxxxxxxx 2005-07-14 18:18 -------
Under Fedora Core 4 I see something a little different. I am able to bring up
the ethernet interface on domU. But in the middle of a ping test (ping
google.com) the kernel panics:
Unable to handle kernel NULL pointer dereference at 0000000000000c20 RIP:
<ffffffff80118a76>{do_page_fault+486}
PGD 1df2f067 PUD 1ddeb067 PMD 0
Oops: 0000 [1]
CPU 0
Modules linked in: amd64_agp agpgart
Pid: 0, comm: swapper Not tainted 2.6.12-xen0
RIP: e030:[<ffffffff80118a76>] <ffffffff80118a76>{do_page_fault+486}
RSP: e02b:ffffffff805599b0 EFLAGS: 00010202
RAX: 000000001ef3d067 RBX: 0000000000000c20 RCX: 0000000000000000
RDX: 0000000000000067 RSI: 00000000084c2067 RDI: ffff800000000000
RBP: 0000000000000000 R08: 00000000000000ff R09: 0000000000000010
R10: 0000000000000010 R11: 0000000000000216 R12: ffffffff80559ac0
R13: ffffffff80101c20 R14: ffffc20000016000 R15: ffffffff80440380
FS: 00002aaaaaacb900(0000) GS:ffffffff80545100(0000) knlGS:0000000000000000
CS: e033 DS: 0000 ES: 0000
Process swapper (pid: 0, threadinfo ffffffff80558000, task ffffffff80440380)
Stack: ffffffff8037542c ffffffff80559a68 ffffffff8037cd6c ffffffff80559a68
ffffffff803b34d0 ffff88001ef59000 0000000000000000 ffff880000030001
ffffffff80375a44 ffffffff803b34d0
Call Trace:<ffffffff8037542c>{nf_iterate+92}
<ffffffff8037cd6c>{ip_route_input+60}
<ffffffff803b34d0>{br_dev_queue_push_xmit+0}
<ffffffff80375a44>{nf_hook_slo}
<ffffffff803b34d0>{br_dev_queue_push_xmit+0} <ffffffff80375a44>{nf_hook_slo}
<ffffffff8037542c>{nf_iterate+92} <ffffffff8037e870>{ip_rcv_finish+0}
<ffffffff8010e357>{error_exit+0} <ffffffff802c6068>{net_rx_action+1224}
<ffffffff80375a44>{nf_hook_slow+100}
<ffffffff803b7e00>{br_nf_pre_routing_f}
<ffffffff803b8ebd>{br_nf_pre_routing+1741} <ffffffff80126f93>{__wake_up_com}
<ffffffff8037ce02>{ip_route_input+210} <ffffffff8037542c>{nf_iterate+92}
<ffffffff803b40b0>{br_handle_frame_finish+0}
<ffffffff8037542c>{nf_iterate+} <ffffffff8037e870>{ip_rcv_finish+0}
<ffffffff80375a44>{nf_hook_slow+100}
<ffffffff8037e870>{ip_rcv_finish+0} <ffffffff8037f1bc>{ip_rcv+1068}
<ffffffff8036d5a5>{netif_receive_skb+357}
<ffffffff8036d644>{netif_receive_} <ffffffff80130299>{tasklet_action+105}
<ffffffff801303c0>{__do_softirq+112}
<ffffffff8013047d>{do_softirq+61} <ffffffff801114d9>{do_IRQ+57}
<ffffffff8010a5e6>{evtchn_do_upcall+118}
<ffffffff8010e3e1>{do_hypervisor_c} <ffffffff8010c751>{xen_idle+81}
<ffffffff8010c751>{xen_idle+81}
<ffffffff8010c793>{cpu_idle+51} <ffffffff8057a79f>{start_kernel+495}
<ffffffff8057a18b>{_sinittext+395}
Code: 48 8b 0b 48 85 c9 74 1e 48 89 c8 48 89 ca 48 c1 e8 0c 81 e2
RIP <ffffffff80118a76>{do_page_fault+486} RSP <ffffffff805599b0>
CR2: 0000000000000c20
<0>Kernel panic - not syncing: Aiee, killing interrupt handler!
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs
|
|
|
| |
|
Home