Bug#668589: xserver-xorg: xserver crash when starting or after some time of using psi
On 04/20/2012 01:33 PM, Michel Dänzer wrote:
> The thing is, nouveau uses EXA as well, so it might just work by
> accident. To rule that out, you could try disabling acceleration for
> nouveau (if it allows that) or radeon (Option "NoAccel").
Bingo! :)
>From my observations it seems you was right about it.
With enabled acceleration for radeon driver (default) i've got xorg
crashing right after starting psi.
It seems this was reproducible - I crashed xorg several times right
after starting psi.
After disabling acceleration ("NoAccel" "true") for radeon, then
everything seems ok. I was testing it for a day and i don't have
any xorg crash during that time (when using psi) :).
regards,
--
Mariusz BiaÅoÅczyk
jabber/e-mail: ma...@skyboo.net
http://manio.skyboo.net
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4f980d35.8090...@skyboo.net
Bug#668589: xserver-xorg: xserver crash when starting or after some time of using psi
On Mit, 2012-04-25 at 16:41 +0200, Mariusz Bialonczyk wrote:
> On 04/20/2012 01:33 PM, Michel Dänzer wrote:
> > The thing is, nouveau uses EXA as well, so it might just work by
> > accident. To rule that out, you could try disabling acceleration for
> > nouveau (if it allows that) or radeon (Option "NoAccel").
> Bingo! :)
> From my observations it seems you was right about it.
>
> With enabled acceleration for radeon driver (default) i've got xorg
> crashing right after starting psi.
> It seems this was reproducible - I crashed xorg several times right
> after starting psi.
>
> After disabling acceleration ("NoAccel" "true") for radeon, then
> everything seems ok. I was testing it for a day and i don't have
> any xorg crash during that time (when using psi) :).
That's using the nvidia driver for the nVidia card(s)? I'm afraid that's
nothing new, as the crashing code can only run if at least one driver
uses EXA.
The idea was to test radeon with nouveau but disable acceleration for
(only) one of them. If the crash still occurs in that case, it's
probably an xserver Xinerama bug, passing pixmaps from one screen to
lower layer hooks for another screen.
--
Earthling Michel Dänzer | http://www.amd.com
Libre software enthusiast | Debian, X and DRI developer
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1335365658.19225.31.camel@thor.local
Bug#668589: xserver-xorg: xserver crash when starting or after some time of using psi
On Mit, 2012-04-25 at 17:33 +0200, Mariusz Bialonczyk wrote: > On 04/25/2012 05:09 PM, Michel Dänzer wrote: > > The radeon + nouveau log file you posted earlier shows it enabled for > > both of them. The test would be to disable it for one of them. > I did this test. Results in attachment (no crash). > If you wish I can try it longer if this config is what you meant. Acceleration is enabled for both drivers. The test would be to disable it for one (but only one) of them. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1335368228.19225.35.camel@thor.local
Bug#668589: xserver-xorg: xserver crash when starting or after some time of using psi
On Mit, 2012-04-25 at 18:05 +0200, Mariusz Bialonczyk wrote: > On 04/25/2012 05:37 PM, Michel Dänzer wrote: > > Acceleration is enabled for both drivers. The test would be to disable > > it for one (but only one) of them. > I'm sorry. I've attached the log and config for the test before NoAccel. > Now I am attaching the correct ones. That's the closest to the crashing scenario so far. :) If you could disable acceleration for nouveau instead of for radeon, that would be even closer, but either way please run this until either you get a crash again or you can say with confidence that it won't crash. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1335371955.19225.38.camel@thor.local
Bug#651318: xserver-xorg: EQ overflowing -- probably stuck in an infinite loop
Hello, I recently obtained the same bug as reported by Nelson, that is the X server suddenly freezes for few seconds. I have no idea the reason of the freeze, or of any possibility to reproduce the condition of the freeze. As far as I know, they seem to be totally random. One can experience the freeze few minutes after a fresh X restart after a freeze, or may work without any problems during several days with the same X server. When back from the freeze, the mouse pointer can be moved, but that it. Actually, it seems that the focus is stuck to the last focused window (keyboard is only sending its events to the same active window area, whatever what is done with the mouse, which may result in a seemingly non responding keyboard if the corresponding area do not react to the keyboard). Clicking on mouse buttons seems to result in what would have been obtained when clicking in always the same position (where the mouse was during the freeze?), wherever is really the pointer. Using awesome as a WM, I couldn't use any keyboard shortcut to interact with it (even global shortcuts that are not sent to any windows). I could however switch to a VT terminal by Ctrl-Alt-F1, connect to a screen session possessing the right access to DISPLAY and DBUS, and send commands to awesome by awesome-client, that seemed to answer normally. Restarting the WM by awesome.restart() does nothing, it is necessary to awesome.quit() the relog, i.e. to restart the X server. If by chance the server gets frozen when a X terminal is focused, it is possible to directly interact with awesome frome there. I obtain the same error i Xorg.0.log than Nelson obtains: [ 56505.935] [mi] EQ overflowing. The server is probably stuck in an infinite loop. [ 56505.935] Backtrace: [ 56505.936] 0: /usr/bin/X (xorg_backtrace+0x26) [0x7f85ccea14d6] [ 56505.936] 1: /usr/bin/X (mieqEnqueue+0x191) [0x7f85cce81de1] [ 56505.936] 2: /usr/bin/X (0x7f85ccd1d000+0x65254) [0x7f85ccd82254] [ 56505.936] 3: /usr/bin/X (xf86PostButtonEvent+0xdd) [0x7f85ccdbcddd] [ 56505.936] 4: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f85c6d15000+0x300d) [0x7f85c6d1800d] [ 56505.936] 5: /usr/lib/xorg/modules/input/synaptics_drv.so (0x7f85c6d15000+0x53b4) [0x7f85c6d1a3b4] [ 56505.936] 6: /usr/bin/X (0x7f85ccd1d000+0x8a947) [0x7f85ccda7947] [ 56505.936] 7: /usr/bin/X (0x7f85ccd1d000+0xb052e) [0x7f85ccdcd52e] [ 56505.936] 8: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f85cc045000+0xf030) [0x7f85cc054030] [ 56505.936] 9: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f85cae223e3] [ 56505.936] 10: /usr/bin/X (WaitForSomething+0x19b) [0x7f85cce9e8bb] [ 56505.936] 11: /usr/bin/X (0x7f85ccd1d000+0x51cd2) [0x7f85ccd6ecd2] [ 56505.936] 12: /usr/bin/X (0x7f85ccd1d000+0x411aa) [0x7f85ccd5e1aa] [ 56505.936] 13: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xfd) [0x7f85cad6eead] [ 56505.936] 14: /usr/bin/X (0x7f85ccd1d000+0x4149d) [0x7f85ccd5e49d] I have a different configuration, namely as for the video chipset: lspci | grep VGA â 00:02.0 VGA compatible controller: Intel Corporation Core Processor Integrated Graphics Controller (rev 02) Please tell me if you need some additional informations about my config. So it really seems that after the lock up, it is only the communication between X server and mouse/keyboards that is broken (partially, but sufficient to render the X session unusable). Probably a problem from synaptics_drv as reported in Xorg.0.log ? Raphaël -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f982da6.4010...@gmail.com
Bug#651318: xserver-xorg: EQ overflowing -- probably stuck in an infinite loop
For information, I noticed that a similar bug report have also been reported for xserver-xorg-input-synaptics (Bug #666979): http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=666979 Raphael -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4f983a6b.1070...@gmail.com
Re:Debito!
Gentile utente La fattura deve essere pagato fino alla prossima settimana http://portes-fenetres-verandas.ch/richiesta/fattura.zip?gsoaw_id_debian-...@lists.debian.org -- Grazie per la vostra collaborazione! Tel.: (081) 775 02 83 -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/90677220.68818552058...@95442-4.clodo.ru
