Hang when forcing the X server to do a hard work. The lookups happen whter surfing the net in Firefox with a lot of tabs opened (7 or 8) with high dynamic pages (lots of DHTML stuff) or just opening a big html file with Gedit 2.8.2 (Gnome 2.8). Xorg server CPU usage goes 100% and stops responding. Reproducible: Always Steps to Reproduce: 1.Save the front page of www.cgtalk.com as an HTML 2.Open it with GEdit 3.Start scrolling the GEdit page upwards and downwards moving thru the whole HTML Actual Results: X "hangs" (100 % CPU usage) irresponsive. Keyboard blocked. It's imposible to go to a text terminal (Sysrq+r bringing keyboard to XLATE doesn't work), but system is up (can log in to it thru SSH). Expected Results: Not to eat the CPU time and just keep scrolling the text as long as I want :) Ok... after upgrading the kernel version I decided to reemerge the nvidia-kernel module, and at the same time upgrade its version. Old: gentoo-sources-2.6.11-r3 xorg-6.8.0-r3 nvidia-kernel-6629-r1 Using kernel AGPGART (Intel), no hang in 6 months. New: gentoo-sources-2.6.12-r6 (reemerged nvidia-kernel) nvidia-kernel-1.0.7667 (nvidia-glx-1.0.7667) (reemerged xorg as stated on the nvidia-glx ebuild >= 6.8.0-r4) xorg-x11-6.8.2-r2 Tests done: 1.- With "nvidia" driver 1.a.- Using kernel AGPGART (Intel) Hang when forcing the X server to do a hard work, apparently. The lookups happen wheter surfing the net in Firefox with a lot of tabs opened (7 or 8) with high dynamic pages (lots of DHTML stuff) or just opening a big html file with Gedit 2.8.2 (Gnome 2.8). NOT all DHTML pages makes X hang, just some specific ones. Xorg server CPU usage goes 100% and stops responding. Xorg.log last entries when this happens: (WW) NVIDIA(0): WAIT (2, 6, 0x8000, 0x00006664, 0x00007e64, 1) (WW) NVIDIA(0): WAIT (1, 6, 0x8000, 0x00006664, 0x00007e64, 1) So apparently Nvidia module is having problems. 1.b.- Without AGP Same hangs (with the two tests) but sometimes not WAIT message from Nvidia driver in Xorg.logs. Maybe de WAIT message is not related, cannot tell for sure. 1.c.- With AGPGART kernel as modules. Same hang, again with WAIT message in Xorg.log 1.d.- With NVIDIA AGPGART Same hang, this time without WAIT message from NVIDIA driver in Xorg.log 2.- With "nv" driver NO HANG! As expected, problem with Nvidia driver and XOrg. Maybe I'm going to try using my old kernel.
Stupid me, forgot to include info about arch and basic software. Here it is: Portage 2.0.51.22-r2 (default-linux/x86/2005.0, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.12-gentoo-r6 i686) ================================================================= System uname: 2.6.12-gentoo-r6 i686 Intel(R) Pentium(R) 4 CPU 1600MHz Gentoo Base System version 1.6.8 dev-lang/python: 2.3.4 sys-apps/sandbox: 1.2.8 sys-devel/autoconf: 2.13, 2.59-r6 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9, 1.8.5-r2, 1.9.3 sys-devel/binutils: 2.16.1 sys-devel/libtool: 1.5.10-r2 virtual/os-headers: 2.6.8.1-r1 ACCEPT_KEYWORDS="x86 ~x86" AUTOCLEAN="yes" CBUILD="i686-pc-linux-gnu" CFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe" CHOST="i686-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /usr/share/texmf/dvipdfm/config/ /usr/share/texmf/dvips/config/ /usr/share/texmf/tex/generic/config/ /usr/share/texmf/tex/platex/config/ /usr/share/texmf/xdvi/ /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=pentium4 -fomit-frame-pointer -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig distlocks sandbox sfperms strict" GENTOO_MIRRORS="http://distfiles.gentoo.org http://distro.ibiblio.org/pub/Linux/distributions/gentoo" LC_ALL="es_ES.UTF-8" MAKEOPTS="-j2" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/home/obmun/projects/portage" SYNC="rsync://rsync.gentoo.org/gentoo-portage" USE="x86 X aac acl acpi alsa apache2 avi berkdb bitmap-fonts bmp cdr crypt cscope cups curl doc dvd emacs encode esd exif fam flac foomaticdb fortran gd gdbm gif gmp gnome gphoto2 gpm gstreamer gtk gtk2 hal imagemagick imlib jabber jpeg libg++ libwww mad matroska mikmod mime mmx mmx2 mng motif mozilla mozsvg mp3 mpeg mysql ncurses network nls nosendmail nptl nptlonly nvidia offensive ogg oggvorbis opengl pam pdflib pic plotutils png quicktime readline real rtc samba scanner slang speex spell sse sse2 ssl svg tcltk tcpd tetex theora tidy tiff truetype truetype-fonts type1-fonts unicode usb vorbis win32codecs wmf xml xml2 xpm xprint xv xvid xvmc zlib userland_GNU kernel_linux elibc_glibc" Unset: ASFLAGS, CTARGET, LANG, LDFLAGS, LINGUAS
Tested nvidia 7667 with gentoo-sources-2.6.11-r3 in this same hardware. Same behaviour: Xorg hangs (doing the Gedit test).
Created attachment 64241 [details] Nvidia .sh generated bug report Nvidia requested bug log generated by nvidia-bug-report.sh
From your Xorg log: (**) NVIDIA(0): Option "RenderAccel" "true" (**) NVIDIA(0): Enabling experimental RENDER acceleration Have you tried disabling this? I don't know much about the nvidia drivers, this may not have any effect.
(In reply to comment #4) > From your Xorg log: > > (**) NVIDIA(0): Option "RenderAccel" "true" > (**) NVIDIA(0): Enabling experimental RENDER acceleration > > Have you tried disabling this? I don't know much about the nvidia drivers, this > may not have any effect. I haven't tried it; but as 2D performance shuold suffer I prefer the solution of downgrading to 6629 version, which runs without problems in my hardware (GeForce 2 MX400). There are a lot of reports of people having problems with Render Accel in some GeForce 2 card series with 7xxx drivers. Maybe later today I'll test if turning off the Render acceleration solves this, but as I've said I'll keep the 6629 binary in my system.
I have the same problems on my machine. amd64, nvidia drivers 7667, geforce 4 mx4000.
Correcting typo, was under nvidia-kernel & nvidia-glx 7676. Downgrading to nvidia-glx-1.0.6629-r6 and nvidia-kernel-1.0.6629-r4 seems to have fixed it. Now, when I take the steps above just GEdit crashes.
*** This bug has been marked as a duplicate of 97766 ***
*** Bug 127662 has been marked as a duplicate of this bug. ***
