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 128] x86_64 - Dom0 crashed while running LTP on DomU

To: xen-bugs@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-bugs] [Bug 128] x86_64 - Dom0 crashed while running LTP on DomU
From: bugzilla-daemon@xxxxxxxxxxxxxxxxxxx
Date: Mon, 01 Aug 2005 16:00:03 +0000
Delivery-date: Mon, 01 Aug 2005 16:00:07 +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-08-01 16:00 -------
Dom0 crashed again today, Aug 1, while running LTP on both Dom0 and a DomU. This
is occurring on an x86_64 machine, FC4 platform.

Here's the last portion on the console log:

Bridge firewalling registered
kjournald starting.  Commit interval 5 seconds
EXT3-fs: mounted filesystem with ordered data mode.
store_evtchn = 12
XENBUS xs_read_watch: 0
Unable to handle kernel paging request at 0000001000000004 RIP:
PGD d817067 PUD 0
Oops: 0002 [1]
Modules linked in: video thermal processor fan button battery ac
Pid: 132, comm: kswapd0 Not tainted 2.6.12-xen0
RIP: e030:[<ffffffff80180da3>] <ffffffff80180da3>{prune_dcache+67}
RSP: e02b:ffff88000f0a1df8  EFLAGS: 00010283
RAX: 0000001000000004 RBX: ffff88000f5283f0 RCX: ffff88000b0349c0
RDX: ffffffff804500e0 RSI: ffffffff80180410 RDI: ffffffff80507a28
RBP: ffff88000c2c95a0 R08: 0000000000000003 R09: 0000000000000000
R10: 0000000000000000 R11: ffffffff80182cf0 R12: 0000000000000078
R13: 0000000000000080 R14: 0000000000000080 R15: 000000000000000c
FS:  00002aaaabe731c0(0000) GS:ffffffff8053b180(0000) knlGS:0000000000000000
CS:  e033 DS: 0000 ES: 0000
Process kswapd0 (pid: 132, threadinfo ffff88000f0a0000, task ffff88000f09f6d0)
Stack: ffff88000f0a1df8 0000000000000082 ffff8800013fb4c0 00000000000000d0
       000000000000b690 ffffffff80180ef7 0000000000000020 ffffffff801543d1
       0000000000000000 ffffffff8044dc80
Call Trace:<ffffffff80180ef7>{shrink_dcache_memory+23}

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

Xen-bugs mailing list

<Prev in Thread] Current Thread [Next in Thread>