Re: DRM oops while starting second X.org session in chroot

From: Frans Pop
Date: Sun Mar 15 2009 - 02:50:52 EST


On Sunday 15 March 2009, Dave Airlie wrote:
> On Sun, Mar 15, 2009 at 12:34 AM, Frans Pop <elendil@xxxxxxxxx> wrote:
> > I had the oops below today after I tried to start a second X.org
> > session in a chroot using 'startx -- :1'. I think the problem here is
> > that the driver was loaded, but that the corresponding device did not
> > exist in /dev in the chroot (forgot to bind mount it). If that is the
> > cause, it would be nice if it was handled more gracefully than this
> > :-P
>
> Its a bug in userspace we can't do anything about at this point,
>
> The problem is we attach some information to the device inode and if
> you starting using an alternate inode it screws up, I think Thomas had
> suggested ways aruond this.
> We could probably make it a WARN_ON and fail DRI setup.

Yes, that's what I'd expect. At least not allow it to hang the primairy X
session. I understand that you cannot magically make DRI work in this
situation.

Note that I did start X.Org successfully in the chroot a bit earlier when
I did have /dev/ bind mounted to /<mychroot>/dev/.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/