** 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
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 rece
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 i
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
.
--
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
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
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 OpenG
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 OpenG
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://mir
** 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, whi
** 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
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 goi
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 wa
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
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 bi
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 s
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 ac
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
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
Bug
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 c
20 matches
Mail list logo
