From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Muench Subject: Re: Oops when modprobing ivtv outside of dom0 Date: Sun, 3 Jul 2005 20:04:38 -0400 Message-ID: References: Reply-To: David Muench Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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, Dave On 7/3/05, Keir Fraser wrote: >=20 > On 3 Jul 2005, at 20:54, David Muench wrote: >=20 > > 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. >=20 > 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=3Dy 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. >=20 > -- Keir >=20 >=20 --=20 David Muench - davemuench@gmail.com Jabber ID: dave@jabber.wasteland.org