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


Re: [Xen-devel] crashes

To: James Harper <JamesH@xxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] crashes
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 29 Jul 2004 10:29:45 +0100
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 29 Jul 2004 10:33:38 +0100
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Thu, 29 Jul 2004 16:23:58 +1000." <BFCDB849-C89D-47E0-94B8-D2942756B52C@mimectl>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
[Resending with top post as my mailer successfully hid my last

Is this the same 'ping other domain while diffing large files' test
that we were using to trigger the blkdev mismerge bug? If so, did
everything seem to work okay for a short while after that bug was
fixed, but has become broken again now?

If this is a bug that triggers after DOM0's memory map is mixed around
(no longer contiguous) then it may be easier to find after I add code
next week that will reverse DOM0's address space if you make a debug
build of Xen. It's already found one bug (in pci_alloc_consistent())
that I'll fix on Monday, and check the debug code in at the same

 -- Keir

> i'm having random crashes under load (diff & pings). No messages in the logs 
> or anything, just reboots or hangs. When I went to look at the screen after a 
> hang to see if there was an oops or anything like it, the screen was blanked 
> and wouldn't wake up - anyone know how to stop that behaviour?

This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
Xen-devel mailing list

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