WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] xenU kernel doesn't start in unstable

To: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] xenU kernel doesn't start in unstable
From: Rik van Riel <riel@xxxxxxxxxx>
Date: Thu, 13 Jan 2005 11:50:10 -0500 (EST)
Delivery-date: Thu, 13 Jan 2005 18:04:25 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
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
The xenU kernel in current -unstable tree seems to crash after
bootup, having used just 0.1 seconds of CPU time:

# xm create kernel=/tmp/vmlinuz
Using config file "/etc/xen/xmdefconfig".
Started domain TestDomain, console on port 9640
# xm list
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0      170    0  r----    817.2
TestDomain        40       32    0  ----c      0.1    9640

This is with the xenU_defconfig from the xen bk tree, though
the same crash has also been observed with the Fedora rawhide
kernel.

One place where the system crashes is at dmi scan time, because
__ioremap() is a "return NULL" when CONFIG_XEN_PHYSDEV_ACCESS is
not defined, which makes dmi_iterate's memcpy follow a NULL
pointer.

The next xenU crash seems to be in parse_args - no idea what's
causing that, or why xen0 seems to be working fine ...

--- arch/xen/i386/kernel/dmi_scan.c.orig        2005-01-12 14:55:14.000000000 
-0500
+++ arch/xen/i386/kernel/dmi_scan.c     2005-01-12 16:06:27.000000000 -0500
@@ -105,6 +105,8 @@
        char __iomem *p, *q;

        for (p = q = ioremap(0xF0000, 0x10000); q < p + 0x10000; q += 16) {
+               if (p == NULL)
+                       return -1;
                memcpy_fromio(buf, q, 15);
                if(memcmp(buf, "_DMI_", 5)==0 && dmi_checksum(buf))
                {


-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/xen-devel