Description of problem:
On recent update to RHEL 6.5 x86_64 workstation
xorg-x11-server 1.13.0-11.1.el6_4.2 freezes up intermittently.
I am using display driver for nvidia.
Version-Release number of selected component (if applicable):
How reproducible: Intermittent
Steps to Reproduce:
Expected results: Should not freeze
Created attachment 832584 [details]
xorg log file
I have three desktops that have been experiencing the same problem. My users state that this primarily happens when they are using the scroll bar in firefox. Though they have seen the same behaviour when using the mouse to move between windows.
machine-a$ lspci | grep -i vga
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller (rev 03)
machine-b$ lspci | grep -i vga
01:00.0 VGA compatible controller: NVIDIA Corporation GF108GL [Quadro 600] (rev
machine-c$ lspci | grep -i vga
01:00.0 VGA compatible controller: NVIDIA Corporation GF108GL [Quadro 600] (rev a1)
All machines are fully up-to-date as of 12/12/2013.
$ rpm -qa | grep -i xorg-x11 | grep -v drv
When X freezes, I can SSH into the system, and the system is fully responsive. I have gone through the logs, but have not seen anything obvious. RAM and CPU usage are both low.
When I kill Firefox the display is not updated. I killed all the user running processes (gnome, Firefox, etc..) and the display still showed a full desktop environment (still frozen). Switching to a different tty (Ctrl+Alt+F[1-6]) failed as long of trying to kill X by send Ctrl+Alt+Backspace.
I had my users boot into kernel 2.6.32-358.11.1 and the problem persisted (they are normally running 2.6.32-431). I had one user boot into runlevel 3, log-in to tty1 and issue startx, however the freeze still occurred.
Let me know what information / logs you need from me.
Try removing the x11-drv-glamor package or removing the config from /usr/share/X11/xorg.conf.d/glamor.conf.
Users of the proprietary NVIDIA driver are hitting the same issue: https://email@example.com/msg00799.html
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.