[jaunty] i845 xorg crashes upon playing video

Bug #354889 reported by Andrew on 2009-04-04
26
This bug affects 3 people
Affects Status Importance Assigned to Milestone
xserver-xorg-video-intel (Ubuntu)
High
Unassigned

Bug Description

Binary package hint: xorg

After the LP#304871 bug (https://bugs.launchpad.net/bugs/304871) was fixed, I am unable to watch videos that worked before on my computer using the i845 video card. When I try to play a video, I either get logged out immediately back to the GDM screen, or I receive the following error message:

$ totem MVI_3256.AVI
/var/lib/python-support/python2.6/gdata/tlslite/utils/cryptomath.py:9: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 88 error_code 11 request_code 132 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Running 'totem MVI_3256.AVI --sync' also either logs me out or gives the same error message.

I have tried the following two xorg configurations and both suffer from the same problem:

Section "Device"
        Identifier "Configured Video Device"
        Driver "Intel"
        Option "Legacy3D" "false"
EndSection

Section "Device"
        Identifier "Configured Video Device"
EndSection

Note: Legacy3D false gave me fully working 2D including videos before the LP#304871 bug was fixed but now seems to make no difference

For the record, lspci shows:
00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 03)

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
Package: xorg 1:7.4~5ubuntu18
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.28-11-generic (buildd@palmer) (gcc version 4.3.3 (Ubuntu 4.3.3-5ubuntu4) ) #39-Ubuntu SMP Thu Apr 2 03:00:35 UTC 2009
SourcePackage: xorg
Uname: Linux 2.6.28-11-generic i686

Andrew (at-macmillan) wrote :
VangelistX (vangelistx) wrote :

Which version of xserver-xorg-video-intel are you using?
I found that using xserver-xorg-video-intel 2:2.6.3-0ubuntu4 causing bugs with i915.
Maybe xserver-xorg-video-intel 2:2.6.3-0ubuntu3 is to blame, because when I don't use any of this packages everything works fine.

For details look at:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/354735

Bryce Harrington (bryce) wrote :

the Legacy3D option is gone now (removing it solves issues on 855 chips), so if that option used to fix a problem on 845, that may be why it's reappeared. Sorry about that, thanks for filing the bug, maybe we can find a better solution for your issue, but please stay tuned...

Bryce Harrington (bryce) on 2009-04-04
affects: xorg (Ubuntu) → xserver-xorg-video-intel (Ubuntu)
Derek (bugs-m8y) wrote :

Have been experiencing this the last few weeks, will watch this one for developments.

Bryce Harrington (bryce) wrote :

Let's focus just on the logout problem, I think I know what causes that. Once this is fixed, if the other totem issues still exist, please report separately.

Changed in xserver-xorg-video-intel (Ubuntu):
importance: Undecided → High
status: New → Triaged
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xserver-xorg-video-intel - 2:2.6.3-0ubuntu7

---------------
xserver-xorg-video-intel (2:2.6.3-0ubuntu7) jaunty; urgency=low

  * Add 119_drm_bo_unreference_needs_null.patch:
    - The first time through the Xv code, an allocated buffer is
      unreferenced but the pointer is not reset to NULL. Thus, the next time
      a video is played, -intel thinks it has a valid buffer and crashes
      when it tries to access the freed memory. Fixes a number of crashes
      reported since moving to the 2.6.3 driver.
    - Fixes crash on i945 with frame buffer width > 2048. DRI is disabled
      on this chipset when the frame buffer exceeds this width.
      (LP: #354688)
    - Fixes crash on i865 where DRI is off because of patch 116
      (LP: #352760)
    - Fixes crash on i845 starting after 304871 was fixed
      (LP: #354889)
    - Fixes crash on i830 when manually disabling DRI
      (LP: #347527)

 -- Bryce Harrington <email address hidden> Mon, 06 Apr 2009 14:28:29 -0700

Changed in xserver-xorg-video-intel (Ubuntu):
status: Triaged → Fix Released
Andrew (at-macmillan) wrote :

Upgraded to version: 2:2.6.3-0ubuntu8 and happy to report that 2d is working again including video using the default xorg.conf. No more getting logged out or totem errors.

Thank you!

For completeness, I tried to enable desktop effects. It did a search for driver screen and then failed gracefully with an error that desktop effects could not be enabled. Since I don't use desktop effects anyway, I did no further testing on this issue.

Derek (bugs-m8y) wrote :

Lucky you.
I updated to latest as of an hour ago. No custom xorg.conf - basically bare-bones Jaunty.
While as Bryce suspected, this did fix the X crash, it did not fix the:

The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.

Dell Latitude D610 Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 03)

(II) intel(0): I2C bus "CRTDDC_A" initialized.
(II) intel(0): I2C bus "CRTDDC_A" removed.
(II) intel(0): EDID vendor "SEC", prod id 16984
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1024x768"x0.0 65.00 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (48.4 kHz)
(II) intel(0): Modeline "1024x768"x0.0 54.16 1024 1048 1184 1344 768 771 777 806 -hsync -vsync (40.3 kHz)
(II) intel(0): EDID vendor "SEC", prod id 16984
(II) intel(0): xf86BindGARTMemory: bind key 2 at 0x05070000 (pgoffset 20592)
(II) intel(0): xf86UnbindGARTMemory: unbind key 2
(EE) intel(0): Failed to pin xv buffer

I do get that after every failure - also, some flickering of the screen, in blocks.
Bryce, you mentioned a 2nd bug, should I be putting this comment there?

Derek (bugs-m8y) wrote :

"solved"
unfortunately, not in a way I'd like.

Back when I was in Ibex (which worked fine apart from crashing hedgears, an opengl/sdl game) ubuntu had reconfigured xorg.conf to support attaching it to another monitor as I did occasionally with this laptop.

Section "Screen"
 Identifier "Default Screen"
 Monitor "Configured Monitor"
 Device "Configured Video Device"
# SubSection "Display"
# Virtual 2384 768
# EndSubSection
EndSection

Commenting out the virtual display fixed things - perhaps a memory issue with the large virtual size? WAG from someone who doesn't understand the internals.

This seems like an easy thing for users to trigger though :-/
And I suppose it means it will just try to make this change again, the next time I plug it into the external monitor.

Derek (bugs-m8y) wrote :

... hedgewars would be the game. just so I don't confuse curious people hitting this thread then googling :)

Derek (bugs-m8y) wrote :

One other nice side effect. Disabling the virtual caused my frame rate in hedgewars to double.
Now if only I could do that conveniently. Might have to add a script.

Aethralis (aethralis) wrote :

I just would like to comment and mention, that this bug seems not to be fixed. I suffer from exactly the same problem (and "solution" is the same too) as Derek. All updates as of today applied.

Seems I'm having this problem too with all the latest updates installed.

Derek (bugs-m8y) wrote :

https://wiki.ubuntu.com/ReinhardTartler/X/RevertingIntelDriverTo2.4

I'm linking to this page for people in the bug.
I found it while trying to figure out why the Intel driver in Jaunty was not functioning on one machine.

I am *not* going to revert to this driver on the laptop above since if this is in fact the Ibex driver, there were random crashes in OpenGL in the aforementioned game "hedgewars" with the Ibex driver.

But. Still mentioning it in the hope that it is of use to others.
For me, disabling the larger virtual area was an adequate workaround.

cleggton (mat-cleggville) wrote :

I also see this bug, currently using 2:2.6.3-0ubuntu9. Probably worth noting here that I am running a dual head setup.

Vern Ceder (vceder) wrote :

I am also getting this bug, also with 2:2.6.3-0ubuntu9. I'm using a Lenovo X60 tablet in a dual head setup with a large virtual area - geometry 2704x1050+0+0

Jordan Hall (jordan-hall) wrote :

Having this issue with Jaunty as well. My graphics chip is a different Intel chip though:

00:00.0 Host bridge: Intel Corporation Mobile 915GM/PM/GMS/910GML Express Processor to DRAM Controller (rev 04)
00:02.0 VGA compatible controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04)
00:02.1 Display controller: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller (rev 04)

Running on a eeePC 900, in a dual-head set-up. Totem returns the following terminal output when I attempt to load a video:

/var/lib/python-support/python2.6/gdata/tlslite/utils/cryptomath.py:9: DeprecationWarning: the sha module is deprecated; use the hashlib module instead
  import sha
The program 'totem' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
  (Details: serial 85 error_code 11 request_code 132 minor_code 19)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

new bug for intel video playback failure in Jaunty: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/371275

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers