[g45] X Server Crashes / intel video card 4500MHD on Sony Vaio laptop

[cdir]

Binary package hint: xserver-xorg-video-intel

I have a fresh and updated install of ubuntu in my Sony Vaio VGN-SR250FN.

Indeed the fresh installation didn't correctly recognize the video card and i changed the xorg.conf settings to:

Section "Device"
 Identifier "Configured Video Device"
 Driver "intel"

After that the screen resolution and performance worked fine.

But when using Mozilla or Glest that stresses the video carf i got these many errors:

daemon.log:Mar 2 21:02:00 aleplacencia-laptop gdm[5474]: WARNING: gdm_slave_xioerror_handler: ha ocurrido un error fatal de X - Reiniciando :0
daemon.log:Mar 4 00:50:28 aleplacencia-laptop gdm[5448]: WARNING: gdm_slave_xioerror_handler: ha ocurrido un error fatal de X - Reiniciando :0
daemon.log:Mar 4 01:19:00 aleplacencia-laptop gdm[5498]: WARNING: gdm_slave_xioerror_handler: ha ocurrido un error fatal de X - Reiniciando :0
daemon.log:Mar 4 01:54:00 aleplacencia-laptop gdm[5491]: WARNING: gdm_slave_xioerror_handler: ha ocurrido un error fatal de X - Reiniciando :0
daemon.log:Mar 6 20:19:00 aleplacencia-laptop gdm[5528]: WARNING: gdm_slave_xioerror_handler: ha ocurrido un error fatal de X - Reiniciando :0
daemon.log:Mar 8 02:46:00 aleplacencia-laptop gdm[5961]: WARNING: gdm_slave_xioerror_handler: ha ocurrido un error fatal de X - Reiniciando :0
daemon.log.0:Mar 2 00:47:32 aleplacencia-laptop gdm[5479]: WARNING: gdm_slave_xioerror_handler: ha ocurrido un error fatal de X - Reiniciando :0
daemon.log.0:Mar 2 01:07:02 aleplacencia-laptop gdm[5512]: WARNING: gdm_slave_xioerror_handler: ha ocurrido un error fatal de X - Reiniciando :0
syslog:Mar 8 02:46:00 aleplacencia-laptop gdm[5961]: WARNING: gdm_slave_xioerror_handler: ha ocurrido un error fatal de X - Reiniciando :0

I've reading about this, and it seems to be a very generic error of X.

On last crash, i recolected some information and found this errors and warnings not present on a normal session log:

Xorg.0.log:(EE) [drm] Could not set DRM device bus ID.
Xorg.0.log:(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
Xorg.0.log:(WW) intel(0): ESR is 0x00000001
Xorg.0.log:(WW) intel(0): PRB0_CTL (0x0001f001) indicates ring buffer enabled

The behaviour of bug is that X crashes suddenly, and gets to login window ... i can login after that, but the configuration has changed and effects and disabled, and even if screen layout looks fine, when trying to start Glest (this is the program that makes the bug occur more frequently, but not exclusively) the video performance is very degradaded and the system can even freeze.

i'm attaching as much information i can:

Linux aleplacencia-laptop 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64 GNU/Linux
Description: Ubuntu 8.10
Release: 8.10

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
Package: xserver-xorg-video-intel 2:2.4.1-1ubuntu10.3
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=es_CL.UTF-8
 SHELL=/bin/bash
ProcVersion: Linux version 2.6.27-11-generic (buildd@crested) (gcc version 4.3.2 (Ubuntu 4.3.2-1ubuntu11) ) #1 SMP Thu Jan 29 19:28:32 UTC 2009

SourcePackage: xserver-xorg-video-intel
Uname: Linux 2.6.27-11-generic x86_64
xkbcomp:

[lspci]
00:00.0 Host bridge [0600]: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub [8086:2a40] (rev 07)
 Subsystem: Sony Corporation Device [104d:9033]
00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
 Subsystem: Sony Corporation Device [104d:9033]

[cdir (carlos-insunza)]

the crash just happened again, and my logs get similar errors:

Xorg.0.log:(EE) [drm] Could not set DRM device bus ID.
Xorg.0.log:(EE) intel(0): [dri] DRIScreenInit failed. Disabling DRI.
Xorg.0.log:(WW) intel(0): ESR is 0x00000001
Xorg.0.log:(WW) intel(0): PRB0_CTL (0x0001f001) indicates ring buffer enabled
Xorg.0.log:(WW) intel(0): Existing errors found in hardware state.

and daemon.log:
Mar 10 00:23:32 aleplacencia-laptop gdm[5479]: WARNING: gdm_slave_xioerror_handler: ha ocurrido un error fatal de X - Reiniciando :0
Mar 10 00:23:33 aleplacencia-laptop acpid: client connected from 9486[0:0]
Mar 10 00:23:36 aleplacencia-laptop gdmgreeter[9505]: Gtk-WARNING: Imposible encontrar el motor de temas en la ruta al _modulo: «ubuntulooks»,
Mar 10 00:23:57 aleplacencia-laptop x-session-manager[9529]: WARNING: Application 'libcanberra-login-sound.desktop' failed to register before timeout

and user.log:
Mar 10 00:23:37 aleplacencia-laptop bonobo-activation-server (aleplacencia-9509): could not associate with desktop session: Failed to connect to socket /tmp/dbus-OWHUOnJRNS: Conexión rechazada
Mar 10 00:23:46 aleplacencia-laptop pulseaudio[9589]: ltdl-bind-now.c: Failed to find original dlopen loader.
Mar 10 00:23:46 aleplacencia-laptop pulseaudio[9591]: pid.c: Stale PID file, overwriting.
Mar 10 00:23:46 aleplacencia-laptop pulseaudio[9591]: main.c: setrlimit(RLIMIT_NICE, (31, 31)) failed: Operación no permitida
Mar 10 00:23:46 aleplacencia-laptop pulseaudio[9591]: main.c: setrlimit(RLIMIT_RTPRIO, (9, 9)) failed: Operación no permitida
Mar 10 00:23:57 aleplacencia-laptop pulseaudio[9591]: module-x11-xsmp.c: X11 session manager not running.
Mar 10 00:23:57 aleplacencia-laptop pulseaudio[9591]: module.c: Failed to load module "module-x11-xsmp" (argument: ""): initialization failed.

and these seems linked to the crash too:

aleplacencia@aleplacencia-laptop:/var/log/gdm$ more \:0.log.1

X.Org X Server 1.5.2
Release Date: 10 October 2008
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.24-16-server x86_64 Ubuntu
Current Operating System: Linux aleplacencia-laptop 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64
Build Date: 24 October 2008 09:06:49AM
xorg-server 2:1.5.2-2ubuntu3 (<email address hidden>)
 Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
Module Loader present
Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Mar 9 21:33:31 2009
(==) Using config file: "/etc/X11/xorg.conf"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Type "ONE_LEVEL" has 1 levels, but <RALT> has 2 symbols
> Ignoring extra symbols
Errors from xkbcomp are not fatal to the X server
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: T...

[cdir (carlos-insunza)]

is anyone able to give a direction to this problem?

[cdir (carlos-insunza)]

any advise to get more information about the crash?

[Geir Ove Myhr (gomyhr)]

cdir, I think the first thing I would do is to check the newest jaunty release (http://cdimage.ubuntu.com/releases/9.04/ - alpha6 is currently the latest version). The GM45 graphics chipset is pretty new, and there has been a number of bugs for this chipset that have been corrected in the driver in Jaunty (currently 2.6.3).

If the problem is still there in Jaunty, I would test the drivers in https://launchpad.net/~xorg-edgers/+archive/ppa, and if it is still a problem, report the bug to the upstream developers.

You can test Jaunty by either using a LiveCD or installing it on your computer. Since Intrepid doesn't seem to serve you very well, you may benefit from installing Jaunty even though it is not completely finished yet. I have it on my laptop and the only inconveniences are that there is a ton of upgrades almost every day (takes a decent internet connection) and that these upgrades may change the desktop experience on a daily basis as well.

[cdir (carlos-insunza)]

Bryce, could you tell me what does the state change to confirmed does mean? and if you need anything of me.

[Bryce Harrington (bryce)]

On Tue, Mar 24, 2009 at 05:34:01AM -0000, cdir wrote:
> Bryce, could you tell me what does the state change to confirmed does
> mean? and if you need anything of me.

I've marked it confirmed because you have correctly filed the bug report
with the necessary data files.

From this data, this seems to be the relevant error message:

  X: ../common/dri_bufmgr_fake.c:579: dri_bufmgr_fake_contended_lock_take:
  Assertion `_fence_test(bufmgr_fake, block->fence)' failed.

Note that you are not experiencing a crash but rather an error exit,
which have the same result from a user perspective, but indicates a
different approach for debugging it.

What you need to do next is follow the directions in this comment:

  https://bugs.edge.launchpad.net/ubuntu/+bug/339433/comments/5

Bryce

[Bryce Harrington (bryce)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.