[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
** Changed in: xserver-xorg-video-intel (Ubuntu) Status: Confirmed => Triaged -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
I was wrong about the improved stacktrace, when I looked carefully at it I noticed that for some reason I'm getting symbols for some addresses in the DRI module but not all addresses. I find this a little bit strange. Anyway, I can also repro this bug using the 2.3.1 driver that bryce provided a test .deb for here: http://people.ubuntu.com/~bryce/Testing/intel/hardy-i386/xserver-xorg-video-intel_2.3.1-1ubuntu1_i386.deb Below is the backtrace (slightly different) that I'm getting with the new 2.3.1 version of the driver: Program received signal SIGABRT, Aborted. 0xb7f2d410 in __kernel_vsyscall () (gdb) bt full #0 0xb7f2d410 in __kernel_vsyscall () No symbol table info available. #1 0xb7cd0085 in raise () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #2 0xb7cd1a01 in abort () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #3 0xb7cc910e in __assert_fail () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #4 0xa7620d68 in bm_fake_NotifyContendedLockTake () from /usr/lib/dri/i965_dri.so No symbol table info available. #5 0xa7626871 in LOCK_HARDWARE () from /usr/lib/dri/i965_dri.so No symbol table info available. #6 0xa763fff5 in ?? () from /usr/lib/dri/i965_dri.so No symbol table info available. #7 0xa7640545 in brw_draw_prims () from /usr/lib/dri/i965_dri.so No symbol table info available. #8 0xa76dc96c in ?? () from /usr/lib/dri/i965_dri.so No symbol table info available. #9 0xb7b55686 in __glXDisp_DrawArrays () from /usr/lib/xorg/modules/extensions//libglx.so No symbol table info available. #10 0xb7b3332d in DoRender () from /usr/lib/xorg/modules/extensions//libglx.so No symbol table info available. #11 0xb7b3344c in __glXDisp_Render () from /usr/lib/xorg/modules/extensions//libglx.so No symbol table info available. #12 0xb7b37996 in __glXDispatch () from /usr/lib/xorg/modules/extensions//libglx.so No symbol table info available. #13 0x081506de in ?? () No symbol table info available. #14 0x0808d8df in Dispatch () No symbol table info available. #15 0x0807471b in main () No symbol table info available. (gdb) -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
I can confirm this bug, been having it in gutsy too. for some time it seemed to be less frequent, then - about a week ago - an update for kernel came that made this bug readily reproducible again. my system: Kubuntu Hardy Intel GMA965/X3100, default drivers electricsheep screensaver. I seem to be having those hangups not only after/while the screensaver is running, but also sometimes just after loading KDE or plugging- in/disconnecting the power chord. more details (dmesg, lspci, xorg.conf) coming up tomorrow. -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
Could you upload the whole backtrace with symbols then please? I guess the Intel devs are mostly interested in the 2.3.1 one. The dbg package for this driver is available at http://mirrors.kernel.org/debian/pool/main/x/xserver-xorg-video-intel/xserver-xorg-video-intel-dbg_2.3.1-1_i386.deb . -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
Ah, thanks for the tip unggnu, that's a nice workaround for textured video. By the way, I was able to figure out why my backtrace didn't have full symbols. The two dbg packages you mentioned does not cover everything, it's also necessary to install libgl1-mesa-dri-dbg in order to get symbols for i965_dri.so functions. So next time you see an intel x.org driver bug, tell them to install these dbg packages: xserver-xorg-core-dbg xserver-xorg-video-intel-dbg libgl1-mesa-dri- dbg Thirdly, I also discovered one more clue about this bug. I tried to turn off Compiz and then the bug doesn't repro at all. I ran the screensaver for three days and three nights, no sign of the bug. When I turned compiz back on the bug happened again after just 2 hours. -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
Just for the records you can use Overlay with the Debnian SID driver with mplayer -vo xv:port= where is the port number you get from xvinfo for the video overlay adaptor. -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
Sorry, I have over read it. The restarting process is Gdm, your login manager. You can stop Gdm after console login with the command "sudo /etc/init.d/gdm stop" but you have to start X manually afterwards. I guess the command "startx gnome" should do it but I haven't tested it. -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
unggnu, are you able to answer the two questions I posted above about why/how X.org automatically restarts? -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
Ah, there was in fact some information related to the crash in the /var/log/Xorg.0.log.old file! I'm attaching it now. It's not much but the end of it says: (WW) intel(0): ESR is 0x0001 (WW) intel(0): PRB0_CTL (0x0001f001) indicates ring buffer enabled (WW) intel(0): PRB0_HEAD (0x95e1c1a0) and PRB0_TAIL (0x0001fd30) indicate ring buffer not flushed (WW) intel(0): Existing errors found in hardware state. ** Attachment added: "/var/log/Xorg.0.log.old taken directly after booting up after experiencing crash" http://launchpadlibrarian.net/14752765/Xorg.0.log.old -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
After about an hour of CPU hogging pain with the new driver I reverted to the old Hardy driver. I then change my power options to say that "Never blank out screen" and I also set my screensaver timeout to 1 minute. Then I went to sleep. I just woke up and this bug had reproduced. I believe I can actually get this bug to repro whenever I want, the only thing I have to do is to leave the busy spheres screensaver on without setting the screen to blank out. When I got back to the machine this morning I found it hung but the graphics was not yet corrupted. When I checked the already attached gdb from ssh the program had received a SIGABRT with the following backtrace: (gdb) bt full #0 0xb7ef5410 in __kernel_vsyscall () No symbol table info available. #1 0xb7c98085 in raise () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #2 0xb7c99a01 in abort () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #3 0xb7c9110e in __assert_fail () from /lib/tls/i686/cmov/libc.so.6 No symbol table info available. #4 0xa75f0d68 in bm_fake_NotifyContendedLockTake () from /usr/lib/dri/i965_dri.so No symbol table info available. #5 0xa75f6871 in LOCK_HARDWARE () from /usr/lib/dri/i965_dri.so No symbol table info available. #6 0xa760fff5 in ?? () from /usr/lib/dri/i965_dri.so No symbol table info available. #7 0x0840e880 in ?? () No symbol table info available. #8 0xb7bd7a0c in __pthread_mutex_unlock_usercnt () from /lib/tls/i686/cmov/libpthread.so.0 No symbol table info available. #9 0xa7610545 in brw_draw_prims () from /usr/lib/dri/i965_dri.so No symbol table info available. #10 0xa76ac96c in ?? () from /usr/lib/dri/i965_dri.so No symbol table info available. #11 0x0840e880 in ?? () No symbol table info available. #12 0x08862030 in ?? () No symbol table info available. #13 0xbfe30d30 in ?? () No symbol table info available. #14 0x0001 in ?? () No symbol table info available. #15 0x in ?? () No symbol table info available. (gdb) At this point I used the "c" command to resume execution and the computer then went into the corrupted graphics defect mode and then it printed this in gdb: Program terminated with signal SIGABRT, Aborted. The program no longer exists. After this the computer hung in exactly the same way that I was originally. Even could I could not execute anymore commands in gdb, I could clearly see the X.org process still alive and taking 100% CPU. -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
Some glitches maybe come frome the fact the MigrationHeuristic isn't greedy per default with the Debian driver. If you want to get a backtrace please reinstall the standard driver like describe above and the dbg packages mentioned in the backtrace howto. You can only get a backtrace if you use ssh from a remote system or something similar. -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
I don't have INTEL_BATCH=1 set (I basically don't have any non-standard configuration options available, just pure ubuntu default. The only change I did was to activate evdev for my X.org input (makes my mouse smooth and low-latency). I really hope they can get textured video optimized a little bit, it's a very nice thing to have. I've also noticed some other glitches though, like for instance the screensaver preview dialog is rendering the preview surface at a fixed location even though I move around the gtk window, and also there is some random pixel dirt shown temporarily when I launch the firefox window. Anyway, I just figured out that I can attach gdb _BEFORE_ the hang and see if that yields a backtrace (not sure why I didn't think of that in the beginning). So I got "sudo gdb" started from a ssh client now and I got the screensaver chewing away. Of course, this bug only happens once a week or so it's probably going to take a long time for me before I get a shoot at capturing a backtrace (and then maybe the symbols will be screwed up or so, even though I have installed a bunch of dbg packages specified on the Ubuntu X debugging webpage). I might even revert back to the original driver and then try the "have gdb attach" trick on it. I'll post again when I have more info. -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
I was very unhappy that upstream made textured video standard while it isn't really usable. That's why still overlay is used in Ubuntu release afaik. I guess the best thing to test it is to let the pc just run with the screensaver enabled. Btw. do you have added INTEL_BATCH=1 to environment file or somewhere else? It is known to break things. -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
I tried upgrading to the new driver. One happy moment was that I now get textured video (so they I move totem the video surface now moves with it), that's just awesome. One not so good thing though is that this new driver consumes HUGE amounts of CPU. When I play a 320x240 pixel .OGG file (which was downloaded from youtube), my computer grinds away at 100% CPU just playing that single video (check out the attached screenshot). This is a dual core 2GHz, 2GB machine and with the previous driver playing that same .OGG file was barely noticable on the CPU meter. I will see how long I can last using this new driver. I'll keep it for a few days though for sure, to see if this freeze bug happens again. Thanks for responding so quickly unggnu! I also have another, non-related idea; instead of asking users to complete these long lists of tasks, as seen here: https://wiki.ubuntu.com/X/Reporting#head-8c2902c284112c960b29386ea3d2f97fd3c57109 and here: http://intellinuxgraphics.org/how_to_report_bug.html Maybe someone could create a script that gathers and submits all the necessary information? I know that the ALSA project did this for sound cards and it has been VERY successful for them in getting more issues resolved with less effort. Check out their script here: http://hg.alsa-project.org/alsa/raw-file/2ea9a8a108ea/alsa-info.sh If this bug repros with the new driver I will post about it here right away. Again, thanks for the help so far! ** Attachment added: "the new driver seems to hog a lot of CPU" http://launchpadlibrarian.net/14701651/that_hurts.png -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
First of all, as I explained above this bug does not allow me to launch any "sudo" operation and in particular I cannot start "sudo gdb" so I will not be able to obtain a backtrace. This is in itself a problem because it means some X.org bugs cannot be efficiently debugged at all (it's probably going to be a looong time before airlied's non-root x.org patches, see http://airlied.livejournal.com/59521.html, make it into ubuntu so maybe someone should start to figure out what on earth could possibly block ALL SUDO operations on the system?). Moving on, here is some of the additional information (this information was extracted after a reboot, when the system was operating connectly again): "uname -a" reports Linux 2.6.24-16.386 #1 Thu Apr 10 12:50:06 UTC 2008 i86 GNU/Linux ** Attachment added: "dmesg" http://launchpadlibrarian.net/14701101/dmesg.log -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
** Attachment added: "lspci" http://launchpadlibrarian.net/14701110/lspci.log -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
** Attachment added: "xrandr --verbose" http://launchpadlibrarian.net/14701119/xrandr_verbose.log -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
The easiest way to test a nearly current Intel driver is to use the Debian sid driver in Hardy I guess. You have to remove the old i810 driver because the new one doesn't work parallel. sudo apt-get remove xserver-xorg-video-i810 xserver-xorg-video-all Download the current driver from http://mirrors.kernel.org/debian/pool/main/x/xserver-xorg-video-intel/xserver-xorg-video-intel_2.3.1-1_i386.deb and install it. After that restart X and check if your problem is gone. If you have made changes to your xorg.conf generate a new one please (sudo dpkg-reconfigure xserver-xorg) or just remove it to be sure. If you want to reset everything do the follow commands. sudo apt-get remove xserver-xorg-video-intel sudo apt-get install xserver-xorg-video-all Afterwards you will have the standard hardy driver again. Btw. I am pretty sure this doesn't work everytime but atm Sid and Ubuntu stable are similar from the libs and apps. -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
The data mentioned in the Intel Howto was dedicated to upstream bug report. The data needed for an Xorg Ubuntu bug report is described here https://wiki.ubuntu.com/X/Reporting and except of the backtrace you have posted any needed data afaik. -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 234768] Re: periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM]
Btw. many thanks for reporting it upstream. For future reports there is howto which data should be uploaded for Intel drivers http://intellinuxgraphics.org/how_to_report_bug.html since there seems to be some information missing. Thanks again. -- periodic Xorg crashes w/ high cpu usage after OpenGL screensaver [965GM] https://bugs.launchpad.net/bugs/234768 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
