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: Fri, 08 Jul 2005 20:18:15 +0000
Delivery-date: Fri, 08 Jul 2005 20:18:19 +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-08 20:18 -------
This is the correct OOPS output:

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: 2815, comm: sshd Not tainted
RIP: e030:[<ffffffff802a9ae8>] <ffffffff802a9ae8>{net_rx_action+1208}
RSP: e02b:ffff8800028ab6e8  EFLAGS: 00010202
RAX: ffffc20000035ff0 RBX: ffff88000c1cf360 RCX: 00000000000000ff
RDX: 0000000000000001 RSI: ffffc20000036000 RDI: 000000000000000e
RBP: ffff88000af26380 R08: 00000000000000ff R09: 0000000000000000
R10: 0000000000000000 R11: 0000000000000206 R12: 0000000028d7306e
R13: ffffffff804d3e40 R14: 0000000000000072 R15: ffffffff804dce80
FS:  00002aaaac231040(0000) GS:ffffffff804ff700(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process sshd (pid: 2815, threadinfo ffff8800028aa000, task ffff88000b438ba0)
Stack: ffff88000c1cf360 000000000f9f5200 0000000000000001 ffffffff802c67c0
       0000000e00000004 ffff88000f9fe800 0000000000000000 ffffffff8034feac
       ffff8800028ab790 ffff88000bcfc200
Call Trace:<ffffffff802c67c0>{scsi_delete_timer+16}

Note: I had originally changed the network script incorrectly, which resulted in
my original report. However, this is the correct output.

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

Xen-bugs mailing list