Re: ACPID stuck in an endless loop - prevents login

[Chris Capon <ttabyss@gmail.com>]

On 2012-09-14 13:28, Camaleón wrote:
> On Fri, 14 Sep 2012 08:48:11 -0400, Chris Capon wrote:
>
> > On 2012-09-13 13:07, Camaleón wrote:
> > > On Wed, 12 Sep 2012 14:54:20 -0400, Chris Capon wrote:
> > >
> > > > After a recent Debian update, I've been unable to log in to my
> > > > Debian/Linux server using the console and GDM3 won't start - X.org
> > > > crashes part way through the startup.
> > > What can be read from X server error logs?
> > The mga driver is not loading because it thinks a kernel module is
> > already using it.
> (thanks for sending the log)
>   
> > [  1223.466] (EE) mga: The PCI device 0x525 at 01@00:00:0 has a kernel module claiming it.
> > [  1223.466] (EE) mga: This driver cannot operate until it has been unloaded.
> >
> > Is there a way to find out what is using it?

Did some more digging and found out that one of the Matrox kernel 
modules was blocking the X.org mga X server from starting.  The module 
causing the problem is called "matrox_w1".  Don't know what it is used 
for, but as soon as it was blacklisted, X started cleanly and the 
endless loop problem seems to have stopped.

I think I'll file a bug with Debian about it.  This must be a recent 
problem.

Thanks for your help, Camaleón.