Ubuntu
mesa package

Unexplained X Crash On Intel Sandybridge

Bug #800778 reported by Scott Kitterman
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
mesa (Fedora)
Fix Released
High
mesa (Ubuntu)
Fix Released
Medium
Unassigned
Natty
Invalid
Medium
Unassigned

Bug Description

From Xorg.0.log.old:

Fatal server error:
[ 41896.470] Wrong event type 0.

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: libgl1-mesa-dri 7.10.2-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic-pae 2.6.38.2
Uname: Linux 2.6.38-8-generic-pae i686
Architecture: i386
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: kwin
DRM.card0.DP.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.DP.2:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.DP.3:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.HDMI.A.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.HDMI.A.2:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.HDMI.A.3:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
DRM.card0.LVDS.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1366x768 1366x768
 edid-base64: AP///////wAGrywxAAAAAAAUAQSQHRB4AhWFl1hTiiYlUFQAAAABAQEBAQEBAQEBAQEBAQEBihtWZlAAIDAwIDYAJaQQAAAaihtWbFEA+jAwIDYAJaQQAAAaAAAA/gBXSkgyUoBCMTMzWFczAAAAAAAAQSGWAREAAAEBCiAgAG4=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
Date: Wed Jun 22 12:14:41 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: kubuntu
EcryptfsInUse: Yes
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Dell Device [1028:0492]
InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Beta i386 (20110330)
MachineType: Dell Inc. Latitude E6320
ProcEnviron:
 LANGUAGE=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic-pae root=UUID=10b6d215-8885-4d35-bd14-ad581ad031b0 ro quiet splash vt.handoff=7
Renderer: Unknown
SourcePackage: mesa
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/02/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A01
dmi.board.name: 0GJF11
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA01:bd03/02/2011:svnDellInc.:pnLatitudeE6320:pvr01:rvnDellInc.:rn0GJF11:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6320
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.23-1ubuntu6
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.2-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.2-0ubuntu2
version.xserver-xorg: xserver-xorg 1:7.6+4ubuntu3
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu4
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-4ubuntu7.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu7

Related branches

lp:ubuntu/oneiric/mesa
Revision history for this message
In , Aaron (aaron-redhat-bugs) wrote :

Description of problem:
X server restarts itself randomly

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg-1.10.0-3.fc15.x86_64

How reproducible:
Seems to happen every couple of hours

Steps to Reproduce:
Cannot reproduce reliably yet

Actual results:
X server experiences fatal error and shuts down. From Xorg.0.log:

...
[ 29300.659]
Fatal server error:
[ 29300.661] Wrong event type 0.
[ 29300.661]
[ 29300.661]
Please consult the Fedora Project support
         at http://wiki.x.org
 for help.
[ 29300.661] Please also check the log file at "/var/log/Xorg.0.log" for additional information.
[ 29300.661]
[ 29300.673] (II) Power Button: Close
[ 29300.673] (II) UnloadModule: "evdev"
[ 29300.673] (II) Unloading evdev
[ 29300.676] (II) Video Bus: Close
[ 29300.676] (II) UnloadModule: "evdev"
[ 29300.676] (II) Unloading evdev
[ 29300.682] (II) Sleep Button: Close
[ 29300.682] (II) UnloadModule: "evdev"
[ 29300.682] (II) Unloading evdev
[ 29300.694] (II) Integrated Camera: Close
[ 29300.694] (II) UnloadModule: "evdev"
[ 29300.694] (II) Unloading evdev
[ 29300.697] (II) AT Translated Set 2 keyboard: Close
[ 29300.697] (II) UnloadModule: "evdev"
[ 29300.697] (II) Unloading evdev
[ 29300.714] (II) UnloadModule: "synaptics"

Expected results:
X doesn't restart randomly.

Additional info:
This started happening after adding the kernel parameter "nouveau.noaccel=1" to work around bug #684608.

Revision history for this message
In , Matěj (matj-redhat-bugs) wrote :

Thanks for the bug report. We have reviewed the information you have provided above, and there is some additional information we require that will be helpful in our diagnosis of this issue.

Please add drm.debug=0x04 to the kernel command line, restart computer, and attach

* your X server config file (/etc/X11/xorg.conf, if available),
* X server log file (/var/log/Xorg.*.log)
* output of the dmesg command, and
* system log (/var/log/messages)

to the bug report as individual uncompressed file attachments using the bugzilla file attachment link above.

We will review this issue again once you've had a chance to attach this information.

Thanks in advance.

Revision history for this message
In , Aaron (aaron-redhat-bugs) wrote :

Created attachment 486197
Xorg.0.log.old immediately after the crash

Revision history for this message
In , Aaron (aaron-redhat-bugs) wrote :

Created attachment 486201
dmesg immediately after the crash

It looks like the dmesg buffer has been filled 10 times over by this point, so let me know if there are any earlier messages you need to see.

Revision history for this message
In , Aaron (aaron-redhat-bugs) wrote :

Created attachment 486202
/var/log/messages from today (2 crashes)

Revision history for this message
In , Aaron (aaron-redhat-bugs) wrote :

Has anyone been able to reproduce this? I'm surprised that there haven't been any me-toos yet.

Assuming it's not just me, I think this bug should be upgraded to urgent. It essentially renders F15 unusable on a decent swag of modern laptops, e.g. Latitudes, Thinkpads, EliteBooks and Macbooks.

- nouveau is unusable due to bug 684608, which may not be fixed for F15
- There are no official nVidia drivers for this chipset which work with such a recent version of X (-ignoreABI results in a segfault)
- This bug renders the fallback desktop useless (again, assuming it's not just me for some reason)

Revision history for this message
In , Ben (ben-redhat-bugs) wrote :

*** Bug 691135 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Timon (timon-redhat-bugs) wrote :

I catched this bug once with openchrome driver.

Revision history for this message
In , Ben (ben-redhat-bugs) wrote :

Yeah, I'm going to reassign this to the xserver for now. I'm going to assume it's not a driver issue until someone tells me otherwise!

Revision history for this message
In , Tomas (tomas-redhat-bugs) wrote :

Created attachment 491877
dmesg

Revision history for this message
In , Tomas (tomas-redhat-bugs) wrote :

Created attachment 491878
/var/log/messages

Revision history for this message
In , Tomas (tomas-redhat-bugs) wrote :

Created attachment 491879
Xorg.0.log.old

Revision history for this message
In , Tomas (tomas-redhat-bugs) wrote :

Description of problem:
I hit the same or similar issue described at #comment 0, with the exception that
I do not have the "nouveau.noaccel=1" kernel parameter.

Version-Release number of selected component (if applicable):
xorg-x11-server-Xorg.x86_64 1.10.0-7.fc15

How reproducible:
Once is 10-15 minutes.

Steps to Reproduce:
No exact steps. Usually happens when browsing web with firefox. I tend to say
that it happens when I do something with the mouse, but not sure.

Created attachments, the crash is at ~725sec:
dmesg #comment 9
/var/log/messages #comment 10
Xorg.0.log.old #comment 11

Additional info:
I also see the following in the /var/log/messages, do not know whether it is related:
kernel: [ 2.787518] [drm] nouveau 0000:01:00.0: 512 MiB GART (aperture)
kernel: [ 2.787532] [drm] nouveau 0000:01:00.0: PGRAPH: unsupported chipset, please report!
kernel: [ 2.788181] [drm] nouveau 0000:01:00.0: PGRAPH: unknown config: 2/0/0/0, 1
kernel: [ 2.791419] [drm] nouveau 0000:01:00.0: failed to load fuc409d

Smolt HW Profile:
http://www.smolts.org/client/show/pub_6d8c5b3a-7897-443c-bf74-3bb979abdd07

Revision history for this message
In , Adam (adam-redhat-bugs) wrote :

"wrong event type 0" is generated by the input handling code, there's not going to be any dependence on video hardware here.

Revision history for this message
In , Tomas (tomas-redhat-bugs) wrote :

During the last two evenings it crashed 18 times, during the last 2.5 hours 7 times, it is very annoying. Sometimes it crashes within 3 minutes since the previous crash.
Could you please estimate the time frame of fixing this bug? Could it get higher priority or be classified as F15Blocker, F15-accepted?

I am not pushy, just need to decide whether to revert to Fedora 14 so I can use my laptop.

Please let me know if/how I can help.

Thanks.

Revision history for this message
In , Peter (peter-redhat-bugs) wrote :

can you reproduce this reliably? it's a bug in the server, but I don't know what triggers it.

Revision history for this message
In , Tomas (tomas-redhat-bugs) wrote :

I cannot give exact steps but it happens frequently enough to be able to generate additional reports. Let me know what you need.
I am also quite confident that it is something with the mouse / pointing device. It is HW independent, occurs with two different mouses and once it even happened while I was working with the touch-pad (no mouse attached).
I tend to say that only moving the cursor is enough, no need for clicking, I am not 100% sure.

P.S. It crashed twice while I was writing this.

Revision history for this message
In , Peter (peter-redhat-bugs) wrote :

There's a scratch build available at the url below. It includes an extra patch for debugging purposes which should hopefully help finding out how we get to this point. Please try it out and attach the Xorg.log (which should have a backtrace) once it crashes.

http://koji.fedoraproject.org/koji/taskinfo?taskID=3053292

Revision history for this message
In , Tomas (tomas-redhat-bugs) wrote :

Created attachment 497424
Xorg.0.log.old with Backtrace

Attached please find the Xorg.0.log with Backtrace.

Revision history for this message
In , Tomas (tomas-redhat-bugs) wrote :

Another two backtraces from Xorg.0.log(s):

[ 4959.186] dix: invalid event type 0
[ 4959.189] ff 00 00 00 06 00 00 00
[ 4959.189] 98 01 00 00 d4 ab 4b 00
[ 4959.189] 0a 00 00 00 0a 00 00 00
[ 4959.189] 00 00 00 00 de 04 00 00
[ 4959.189]
Backtrace:
[ 4959.191] 0: /usr/bin/X (xorg_backtrace+0x2f) [0x45dd7f]
[ 4959.191] 1: /usr/bin/X (0x400000+0x45bf3) [0x445bf3]
[ 4959.191] 2: /usr/bin/X (mieqEnqueue+0x33) [0x4a0883]
[ 4959.191] 3: /usr/bin/X (xf86PostMotionEventM+0xa3) [0x47dc23]
[ 4959.191] 4: /usr/bin/X (xf86PostMotionEventP+0x52) [0x47dd42]
[ 4959.191] 5: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7f3f4e9de000+0x498b) [0x7f3f4e9e298b]
[ 4959.191] 6: /usr/bin/X (0x400000+0x6b678) [0x46b678]
[ 4959.191] 7: /usr/bin/X (0x400000+0x119be0) [0x519be0]
[ 4959.191] 8: /lib64/libpthread.so.0 (0x3b8d800000+0xf3c0) [0x3b8d80f3c0]
[ 4959.191] 9: /lib64/libpthread.so.0 (pthread_cond_wait+0xc5) [0x3b8d80b985]
[ 4959.191] 10: /usr/lib64/dri/swrast_dri.so (0x7f3f54772000+0x6bb53) [0x7f3f547ddb53]
[ 4959.191] 11: /lib64/libpthread.so.0 (0x3b8d800000+0x7cd1) [0x3b8d807cd1]
[ 4959.191] 12: /lib64/libc.so.6 (clone+0x6d) [0x3b8d0dfd3d]
[ 4959.191]
Fatal server error:
[ 4959.191] Wrong event type 255. Aborting server

===============================================================================

[ 50769.184] dix: invalid event type 0
[ 50769.186] ff 00 00 00 06 00 00 00
[ 50769.186] 98 01 00 00 20 ad 06 03
[ 50769.186] 0a 00 00 00 0a 00 00 00
[ 50769.187] 00 00 00 00 bb 05 00 00
[ 50769.187]
Backtrace:
[ 50769.187] 0: /usr/bin/X (xorg_backtrace+0x2f) [0x45dd7f]
[ 50769.187] 1: /usr/bin/X (0x400000+0x45bf3) [0x445bf3]
[ 50769.187] 2: /usr/bin/X (mieqEnqueue+0x33) [0x4a0883]
[ 50769.187] 3: /usr/bin/X (xf86PostMotionEventM+0xa3) [0x47dc23]
[ 50769.188] 4: /usr/bin/X (xf86PostMotionEventP+0x52) [0x47dd42]
[ 50769.188] 5: /usr/lib64/xorg/modules/input/evdev_drv.so (0x7fb69f19a000+0x498b) [0x7fb69f19e98b]
[ 50769.188] 6: /usr/bin/X (0x400000+0x6b678) [0x46b678]
[ 50769.188] 7: /usr/bin/X (0x400000+0x119be0) [0x519be0]
[ 50769.188] 8: /lib64/libpthread.so.0 (0x3b8d800000+0xf3c0) [0x3b8d80f3c0]
[ 50769.188] 9: /lib64/libpthread.so.0 (pthread_cond_wait+0xc5) [0x3b8d80b985]
[ 50769.188] 10: /usr/lib64/dri/swrast_dri.so (0x7fb6a4f2e000+0x6bb53) [0x7fb6a4f99b53]
[ 50769.188] 11: /lib64/libpthread.so.0 (0x3b8d800000+0x7cd1) [0x3b8d807cd1]
[ 50769.188] 12: /lib64/libc.so.6 (clone+0x6d) [0x3b8d0dfd3d]
[ 50769.188]
Fatal server error:
[ 50769.188] Wrong event type 255. Aborting server

Revision history for this message
In , Tomas (tomas-redhat-bugs) wrote :

Another backtrace:

[ 51729.176] dix: invalid event type 0
[ 51729.178] 00 00 00 00 00 00 00 00
[ 51729.179] 00 00 00 00 00 00 00 00
[ 51729.179] 00 00 00 00 00 00 00 00
[ 51729.179] 00 00 00 00 00 00 00 00
[ 51729.179]
Backtrace:
[ 51729.179] 0: /usr/bin/X (xorg_backtrace+0x2f) [0x45dd7f]
[ 51729.179] 1: /usr/bin/X (0x400000+0x45bf3) [0x445bf3]
[ 51729.179] 2: /usr/bin/X (mieqProcessDeviceEvent+0x3f) [0x4a0c9f]
[ 51729.180] 3: /usr/bin/X (mieqProcessInputEvents+0xb0) [0x4a0ee0]
[ 51729.180] 4: /usr/bin/X (ProcessInputEvents+0xd) [0x46b6fd]
[ 51729.180] 5: /usr/bin/X (0x400000+0x2e99c) [0x42e99c]
[ 51729.180] 6: /usr/bin/X (0x400000+0x22e1a) [0x422e1a]
[ 51729.180] 7: /lib64/libc.so.6 (__libc_start_main+0xed) [0x3b8d02143d]
[ 51729.180] 8: /usr/bin/X (0x400000+0x23101) [0x423101]
[ 51729.180]
Fatal server error:
[ 51729.180] Wrong event type 0. Aborting server

Revision history for this message
In , Dave (dave-redhat-bugs) wrote :

http://kojipkgs.fedoraproject.org/scratch/airlied/task_3059966/

After some discussion today we think this might be a problem with signals and threads, there scratch build above is a new mesa build, please install and let me know if it makes any difference.

Revision history for this message
In , Tomas (tomas-redhat-bugs) wrote :

Created attachment 497908
Xorg.0.log.old with Backtrace

Sorry for the bad news, it still crashes, see the attached log.

# yum list installed | egrep '^(xorg-x11-serv|mesa)'
mesa-debuginfo.x86_64 7.11-0.9.20110509.0.fc15.da @/mesa-debuginfo-7.11-0.9.20110509.0.fc15.da.x86_64
mesa-dri-drivers.x86_64 7.11-0.9.20110509.0.fc15.da @/mesa-dri-drivers-7.11-0.9.20110509.0.fc15.da.x86_64
mesa-dri-filesystem.x86_64 7.11-0.9.20110509.0.fc15.da @/mesa-dri-filesystem-7.11-0.9.20110509.0.fc15.da.x86_64
mesa-dri-llvmcore.x86_64 7.11-0.9.20110509.0.fc15.da @/mesa-dri-llvmcore-7.11-0.9.20110509.0.fc15.da.x86_64
mesa-libGL.x86_64 7.11-0.9.20110509.0.fc15.da @/mesa-libGL-7.11-0.9.20110509.0.fc15.da.x86_64
mesa-libGLU.x86_64 7.11-0.9.20110509.0.fc15.da @/mesa-libGLU-7.11-0.9.20110509.0.fc15.da.x86_64
xorg-x11-server-Xephyr.x86_64 1.10.1-14.bz688693.fc15 @/xorg-x11-server-Xephyr-1.10.1-14.bz688693.fc15.x86_64
xorg-x11-server-Xorg.x86_64 1.10.1-14.bz688693.fc15 @/xorg-x11-server-Xorg-1.10.1-14.bz688693.fc15.x86_64
xorg-x11-server-common.x86_64 1.10.1-14.bz688693.fc15 @/xorg-x11-server-common-1.10.1-14.bz688693.fc15.x86_64
xorg-x11-server-debuginfo.x86_64 1.10.1-14.bz688693.fc15 @/xorg-x11-server-debuginfo-1.10.1-14.bz688693.fc15.x86_64
xorg-x11-server-utils.x86_64 7.5-5.fc15 @fedora

Revision history for this message
In , Tomas (tomas-redhat-bugs) wrote :

And another backtrace:

[ 2769.175] dix: invalid event type 0
[ 2769.177] 00 00 00 00 00 00 00 00
[ 2769.177] 00 00 00 00 00 00 00 00
[ 2769.178] 0a 00 00 00 0a 00 00 00
[ 2769.178] 00 00 00 00 00 00 00 00
[ 2769.178]
Backtrace:
[ 2769.178] 0: /usr/bin/X (xorg_backtrace+0x2f) [0x45dd7f]
[ 2769.178] 1: /usr/bin/X (0x400000+0x45bf3) [0x445bf3]
[ 2769.178] 2: /usr/bin/X (mieqProcessDeviceEvent+0x3f) [0x4a0c9f]
[ 2769.178] 3: /usr/bin/X (mieqProcessInputEvents+0xb0) [0x4a0ee0]
[ 2769.178] 4: /usr/bin/X (ProcessInputEvents+0xd) [0x46b6fd]
[ 2769.179] 5: /usr/bin/X (0x400000+0x2e99c) [0x42e99c]
[ 2769.179] 6: /usr/bin/X (0x400000+0x22e1a) [0x422e1a]
[ 2769.179] 7: /lib64/libc.so.6 (__libc_start_main+0xed) [0x3b8d02143d]
[ 2769.179] 8: /usr/bin/X (0x400000+0x23101) [0x423101]
[ 2769.179]
Fatal server error:
[ 2769.179] Wrong event type 0. Aborting server
[ 2769.179]
[ 2769.179]

Revision history for this message
In , Peter (peter-redhat-bugs) wrote :

I'm wondering if there are two overlapping bugs. Look at the backtraces, one comes from the event generation code (evdev, xf86PostMotionEvent, mieqEnqueue) and one from event processing (mieqProcessInputEvents, etc.).

Have you seen both since the mesa upgrade or just the latter?

Revision history for this message
In , Dave (dave-redhat-bugs) wrote :

I just realised I inverted the signal mask in my mesa patch, so I've done another scratch build that might have a better chance of working

http://kojipkgs.fedoraproject.org/scratch/airlied/task_3064769/

Please give this one a go.

Revision history for this message
In , Tomas (tomas-redhat-bugs) wrote :

Good news. No crash since I installed the last May 11th mesa update.
I used the machine only during the last two evenings. I can report back in another couple of days.

Thanks!

Revision history for this message
In , Tomas (tomas-redhat-bugs) wrote :

Still no crash. I consider the issue fixed.
Let me know, if you need anything else.

Thanks to all!

Revision history for this message
In , Dave (dave-redhat-bugs) wrote :

I've pushed a new mesa to updates-testing that contains the fix.

Revision history for this message
In , Tomas (tomas-redhat-bugs) wrote :

The mesa from updates-testing works fine (no crashes) with xorg-x11-server from the fedora repo.

Revision history for this message
In , Peter (peter-redhat-bugs) wrote :

Thanks for testing. I'm closing this as CURRENTRELEASE.

http://koji.fedoraproject.org/koji/buildinfo?buildID=245099
https://admin.fedoraproject.org/updates/mesa-7.11-0.11.20110525.0.fc15

Revision history for this message
Scott Kitterman (kitterman) wrote :
Revision history for this message
Robert Hooker (sarvatt) wrote :

This is referenced in https://bugzilla.redhat.com/show_bug.cgi?id=688693 and was fixed by http://cgit.freedesktop.org/mesa/mesa/commit/?id=a95ec18549b677b5e9912ca9e2c92df5cfef3b4e

Can you please try out https://launchpad.net/~sarvatt/+archive/orange which contains the backport? It was marked for inclusion in 7.10 stable but hasn't been pulled into there yet.

Robert Hooker (sarvatt)
Changed in mesa (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Scott Kitterman (kitterman) wrote : Re: [Bug 800778] Re: Unexplained X Crash On Intel Sandybridge

Installed the update and no issues noted. The crash is rare, so it's hard to
tell if this helped.

Revision history for this message
Scott Kitterman (kitterman) wrote :

I was having trouble with losing X when unplugging an external monitor before I installed this update. I'm not now (but it's a different monitor). Could this be related to this fix?

Revision history for this message
In , Peter (peter-redhat-bugs) wrote :

*** Bug 682593 has been marked as a duplicate of this bug. ***

Revision history for this message
Chris Halse Rogers (raof) wrote :

Concievably.

Since this patch is included in mesa 7.11 and looks like it's fixed this bug, I'll be marking this as fixed in the 7.11 upload to oneiric. If you think that's incorrect, feel free to reopen.

Changed in mesa (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Scott Kitterman (kitterman) wrote :

How about SRU for Natty?

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (3.5 KiB)

This bug was fixed in the package mesa - 7.11-0ubuntu1

---------------
mesa (7.11-0ubuntu1) oneiric; urgency=low

  * Fake merge from Debian experimental, updating previous changelog entries.
    New upstream release fixes infrequent X crash (LP: #800778).
    Remaining Ubuntu changes:
   - debian/control
      + Drop lesstif-dev from Build-Depends; it's in Universe.
      + Comment out GLw libs since it depends on lesstif-dev.
      + Drop i686 swx11 libgl package.
      + Add libdrm-dev to mesa-common-dev Depends.
      + Drop libwayland-dev from Build-Depends; it's in Universe.
      + Update Breaks for Ubuntu versions
      + Enable llvm on armel as well as i386 and amd64
    - debian/rules
      + Use --disable-glw for swx11 targets too.
      + Don't enable motif for swx11 targets.
      + Use lzma compression for binary debs to save CD space.
      + Drop unloved mach64 driver.
      + Use --enable-shared-dricore to claw back CD space.
      + Enable llvmpipe software rasteriser.
      + Enable llvm on armel as well as i386 and amd64
    - debian/patches
      + 100_no_abi_tag.patch
      + 101_ubuntu_hidden_glname.patch
      + 103_savage-expose_fbmodes_with_nonzero_alpha.patch
    - rules, libgl1-mesa-{glx,dev,swx11,swx11-dev}.install.in,
      libgl1-mesa-{glx,swx11}.{postinst,prerm}.in, libgl1-mesa-dev.links.in:
      Install libGL.so* in /usr/lib/mesa to allow things to work with
      alternatives.
    - debian/not-installed:
      + Drop i686 files; we don't build 686-optimised packages in the first
        place.
    - debian/gbp.conf
      + Point at Ubuntu branch to make git-buildpackage less narky.
    - 113_fix_tls.diff: Fix crashes in unrelated code due to TLS usage.
    - debian/patches/111_export_searchdirs_in_dripc.diff:
      + Add drisearchdirs variable to dri.pc so the Xserver can pick up the
        alternate DRI driver dirs.
    - debian/patches/115_llvm_dynamic_linking.diff
      + Dynamically link DRI drivers to libllvm. Saves ~6MiB per DRI driver.
    - debian/patches/116_use_shared_galliumcore.diff:
    - debian/libgl1-mesa-dri.install.in:
      + Link gallium DRI drivers against shared gallium routines to save CD
        space.
  * debian/rules:
  * debian/libgl1-mesa-dri-experimental.install.{i386,amd64}.in
    - Explicitly install i915g only when it has been built, matching what is
      done with r300g.
  * debian/rules:
  * debian/control:
  * debian/libegl1-mesa{,-dev}.install.in:
  * debian/libegl1-mesa.symbols:
    - Enable the Wayland EGL backend.
  * debian/rules:
  * debian/libegl1-mesa.{postinst,prerm,install}.in:
  * debian/libegl1-mesa-dev.{install,links}.in:
  * debian/libgles{1,2}-mesa.install.in:
  * debian/libgles{1,2}-mesa-dev.links.in:
  * debian/libopenvg1-mesa{,-dev}.install.in:
  * debian/libopenvg1-mesa-dev.links.in:
    - Use alternatives for libEGL to match the handling of libGL.
      libEGL (and associated GL|ES and OpenVG libraries) now live in
      /usr/lib/$MULTIARCH/mesa-egl. (LP: #812639)
  * debian/patches/118_fix_24bpp_software_rendering.diff:
    - Cherry pick upstream patch from master fixing graphical corruption when
      using a 24bpp framebuffer and software renderin...

Read more...

Changed in mesa (Ubuntu):
status: Fix Committed → Fix Released
Timo Aaltonen (tjaalton)
Changed in mesa (Ubuntu Natty):
importance: Undecided → Medium
status: New → Triaged
dino99 (9d9)
Changed in mesa (Ubuntu Natty):
status: Triaged → Invalid
Bug Watch Updater (bug-watch-updater)
Changed in mesa (Fedora):
importance: Unknown → High
status: Unknown → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.