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] Oops when modprobing ivtv outside of dom0

To: David Muench <davemuench@xxxxxxxxx>
Subject: Re: [Xen-devel] Oops when modprobing ivtv outside of dom0
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Sun, 3 Jul 2005 23:06:13 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 03 Jul 2005 22:09:34 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <bc0c36d305070312541f674e7e@xxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <bc0c36d305070312541f674e7e@xxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 3 Jul 2005, at 20:54, David Muench wrote:

At that point the whole box reboots.

Any help would be appreciated, I've been battling this for a few days
and am not making any progress.

One possibility is that the driver is depending on contiguous physical memory, and domain0 usually happens to get that (but domUs generally will get fragmented physical memory). You could confirm this by making a debug build of Xen (debug=y make) which deliberately jumbles the physical memory map for domain0. It's quite possible that this will then cause the driver to fail on dom0 too. If we can diagnose that this is the problem, it probably won't take much to fix the driver.

 -- Keir

Xen-devel mailing list