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: Tue, 12 Jul 2005 18:04:52 +0000
Delivery-date: Tue, 12 Jul 2005 18: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-12 18:04 -------
OK. I've done some more testing, and it appears that this problem is somehow
related to networking. Dom0 crashes as soon as the networking services are
started when DomU is coming up.  As an experiment, I brought up DomU without
networking, and it stayed up. As soon as I started DomU with networking enabled,
however, Dom0 crashed. Below is the trace:

Unable to handle kernel paging request at ffffc20000036000 RIP:
PGD 13e4067 PUD 13e3067 PMD 13e2067 PTE 0
Oops: 0000 [1]
Modules linked in: thermal processor fan button battery ac
Pid: 2712, comm: sshd Not tainted 2.6.12-xen0
RIP: e030:[<ffffffff802afff9>] <ffffffff802afff9>{net_rx_action+1209}
RSP: e02b:ffff88000290d7f8  EFLAGS: 00010202
RAX: ffffc20000035ff0 RBX: ffff88000de9bb60 RCX: 00000000000000ff
RDX: 0000000000000001 RSI: ffffc20000036000 RDI: 000000000000000e
RBP: ffff88000b5f7c80 R08: 00000000000000ff R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000010c1a06e
R13: ffffffff804df7c0 R14: 0000000000000072 R15: ffffffff804e8800
FS:  00002aaaac231040(0000) GS:ffffffff8050ae80(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process sshd (pid: 2712, threadinfo ffff88000290c000, task ffff88000c02ef30)
Stack: ffff88000de9bb60 0000000080397db8 0000000000000001 ffff88000290d840
       ffff88000a93d380 ffffffff8014bd98 0000000000000000 ffff88000c02ef30
       ffffffff8013000e ffffffff80355f6c
Call Trace:<ffffffff8014bd98>{mempool_alloc+152} 

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

Xen-bugs mailing list