[SOLVED] 14.1: Xorg bug

mattca · 11-29-2013, 10:31 AM

Hi all, I have two laptops that I've recently upgraded to 14.1. Both were using 14.0 before the upgrade without issue. I previously used ratpoison on both, but decided to try KDE out this time around.

On one (my personal laptop), KDE works fine.

On my work laptop however, after about 30 minutes or so of use it locks up and I have to hard boot using the power key. Using ratpoison I get more uptime, but it also can lock up after a while.

Attached is my Xorg.0.log from a lockup.

I think it's related to this bug. According to my google research, it doesn't seem to be limited to a particular distribution or even graphics card.

Although, it may be worthwhile to note that the laptop with lockups has an nvidia card (using the nouveau driver), and the working laptop does not (not sure which one, I'll update when I get home).

Edit: It's also probably important to note that I never experienced a lockup like this with 14.0.

This is the laptop that locks up:

Code:

         [Fri Nov 29, 11:26:16] [~]
         [root@euler] # lspci  | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GF119M [NVS 4200M] (rev a1)

Any ideas? Anything I can do to mitigate this issue?

Thanks!

bartgymnast · 11-29-2013, 11:58 AM

The bug is still open.

people on ubuntu forums reported that applying below config solved their issue

Code:

 Option "AccelMethod" "EXA"

to their x-video card config.

phenixia2003 · 11-29-2013, 12:03 PM

Hello,

According to the last message in this thread, there's this patch which has been committed to the xorg 1.15 branch.

--
SeB

mattca · 12-18-2013, 09:27 AM

Oddly enough, the problem seems to have gone away on its own.

I was getting ready to rebuild and reinstall the X server, and thought I'd try the nvidia driver first, just in case that helped. I also stopped using Chrome and switched back to Firefox.

Anyway, the nvidia driver was terrible and I had to switch back immediately. Since doing so I haven't had a single lock up. I'm not sure if it's a side effect of installing the nvidia driver, or if Chrome was causing the issue, but I'm happy either way.