Re: [Xen-devel] Oops when modprobing ivtv outside of dom0

[David Muench <davemuench@xxxxxxxxx>]

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 <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
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel