Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 10 Dec 2012 19:43:26 +0100
From:      David Demelier <demelier.david@gmail.com>
To:        Hooman Oroojeni <oroojeny@gmail.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Xorg got stuck sometimes
Message-ID:  <50C62D4E.50901@gmail.com>
In-Reply-To: <50ABD5EF.6000100@gmail.com>
References:  <50ABBFFF.4080409@gmail.com> <CADZoPbBm4SD_kxOOMrqihhJdSwDu7m9pJkt7MO619JR2AEXzOQ@mail.gmail.com> <50ABD5EF.6000100@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 20/11/2012 20:11, David Demelier wrote:
> On 20/11/2012 19:18, Hooman Oroojeni wrote:
>> Try to rebuild Xorg with WITHOUT_NOUVEAU. That maybe helpfull.
>>
>> Cheers
>>
>> On Tue, Nov 20, 2012 at 5:38 PM, David Demelier
>> <demelier.david@gmail.com <mailto:demelier.david@gmail.com>> wrote:
>>
>>     Hi there,
>>
>>     Sometimes, Xorg got stuck but I can't reproduce it always. When it
>>     appears, Xorg just stop being usable and mouse / keyboard can't be
>>     used also, switching to tty does not work at all and the screen is
>>     frozen.
>>
>>     But I still can use ssh to connect the broken host and shutdown it
>>     normally, Xorg will use 100% of CPU when it breaks like this.
>>
>>     I noticed this message when it appears :
>>
>>     EQ overflowing. The server is probably stuck in an infinite loop.
>>
>>     I'm using the nvidia nvidia-driver-304.64 on FreeBSD 9.1-RC3
>>
>>     Cheers,
>>     --
>>     David Demelier
>>     _________________________________________________
>>     freebsd-questions@freebsd.org <mailto:freebsd-questions@freebsd.org>
>>     mailing list
>> http://lists.freebsd.org/__mailman/listinfo/freebsd-__questions
>> <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>;
>>     To unsubscribe, send any mail to
>>     "freebsd-questions-__unsubscribe@freebsd.org
>>     <mailto:freebsd-questions-unsubscribe@freebsd.org>"
>>
>>
>>
>>
>> -- 
>>
>>
>>
>>
>
> WITHOUT_NOUVEAU is already in my make.conf..
>
> Cheers,
>

Let see if the 310.19 version will clear the problem, by the way why 
this version is not in the ports yet, because of the ports freeze?




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50C62D4E.50901>