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


[Xen-bugs] [Bug 93] x86_64 - Dom0 crashes when DomU is created.

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 93] x86_64 - Dom0 crashes when DomU is created.
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 11 Jul 2005 14:04:54 +0000
Delivery-date: Mon, 11 Jul 2005 14:04:57 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-bugs-request@lists.xensource.com?subject=help>
List-id: Xen Bugzilla <xen-bugs.lists.xensource.com>
List-post: <mailto:xen-bugs@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-bugs>, <mailto:xen-bugs-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-bugs-bounces@xxxxxxxxxxxxxxxxxxx

------- Additional Comments From dbarrera@xxxxxxxxxx  2005-07-11 14:04 -------
The problem *seems* to be related to networking. When I start a DomU, if the
networking is not setup properly, the DomU comes up, without networking of
course, but it seems functional enough. When the network bridge is setup
properly, however, Dom0 crashes.

Here's the trace from today's build, same as previous:

Unable to handle kernel NULL pointer dereference at 0000000000000c20 RIP:
PGD d03c067 PUD 1659067 PMD 0
Oops: 0000 [1]
Modules linked in: thermal processor fan button battery ac
Pid: 0, comm: swapper Not tainted
RIP: e030:[<ffffffff80117a08>] <ffffffff80117a08>{do_page_fault+408}
RSP: e02b:ffffffff80515a00  EFLAGS: 00010202
RAX: 00000000013e4067 RBX: 0000000000000c20 RCX: 0000000000000000
RDX: 0000000000000067 RSI: 00000000093e4067 RDI: ffff800000000000
RBP: 0000000000000000 R08: 00000000000000ff R09: 0000000000000000
R10: 0000000000001000 R11: 0000000000000206 R12: 0000000000000c20
R13: ffffffff80515b00 R14: ffffc20000036000 R15: ffffffff8041d180
FS:  0000000000000000(0000) GS:ffffffff80500b00(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process swapper (pid: 0, threadinfo ffffffff80514000, task ffffffff8041d180)
Stack: ffff88000f7f8360 ffff880007468600 ffffffff8038d660 0000000000000000
       ffffffff80515b00 ffffffff803c2bf2 0000000000000000 0000000b0000000e
       ffff880005516012 ffff880000030001
Call Trace:<ffffffff8038d660>{__br_forward+0}

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

Xen-bugs mailing list