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

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

To: Rik van Riel <riel@xxxxxxxxxx>
Subject: Re: [Xen-devel] xenU kernel doesn't start in unstable
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 14 Jan 2005 09:20:10 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 14 Jan 2005 09:28:00 +0000
Envelope-to: xen+James.Bulpin@xxxxxxxxxxxx
In-reply-to: Your message of "Thu, 13 Jan 2005 11:50:10 EST." <Pine.LNX.4.61.0501131145330.21579@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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
> # 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.

I can't reproduce a crash with the vanilla unstable tree.

> 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.

Which kernel is your patch against? The plain 2.6.10 dmi_scan.c only
uses bt_ioremap() AFAICT, and it already checks the return value for
NULL. 

 -- Keir


-------------------------------------------------------
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