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: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Oops when modprobing ivtv outside of dom0
From: David Muench <davemuench@xxxxxxxxx>
Date: Sun, 3 Jul 2005 20:04:38 -0400
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 04 Jul 2005 00:03:28 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=BusSwp4Erel09lr49tIBHtUKvXFfDD2ZUrxf3GplUXQ03d2N1vf81bLrtDPU5z+2FhpejRFPtR+gyem44mhUw7giQq5UHCSFRZm/YSKLXPe9+J7Ix/dTU3p/0XZvzjYsz2kTOZSpzZkZwcsyuMxfHly31SrxMZbHSJ7MGh6I+Qs=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <a89b55ed8d2a2603fc46dac910a16ed7@xxxxxxxxxxxx>
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> <a89b55ed8d2a2603fc46dac910a16ed7@xxxxxxxxxxxx>
Reply-to: David Muench <davemuench@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Keir,

I think you're on to something there. I compiled a debug version of
xen (all I needed was a debug version of xen.gz, right?) and while the
ivtv modules loaded without any complaints, as soon as I started
capturing video there were a series of panics and the box went into a
semi-hung state. I'm back in my non debug xen now and everything is
working perfectly again in dom0.

Thanks very much,

On 7/3/05, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
> 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

David Muench - davemuench@xxxxxxxxx
Jabber ID: dave@xxxxxxxxxxxxxxxxxxxx

Xen-devel mailing list