Xorg driver locks up and screen goes blank (black) - i915_gem_retire_work_handler+0x2a/0x70

Bug #384960 reported by Amit Kucheria
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
X.Org X server
Fix Released
Medium
xserver-xorg-video-intel (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Binary package hint: xorg

On my Karmic upgrade, Xorg periodically just blanks out (black screen) and I can never get it back.

Sshing into the machine shows the following attached logs (/var/log/kern.log)

Jun 6 00:12:59 k2 kernel: [56280.880058] INFO: task events/0:9 blocked for more than 120 seconds.
Jun 6 00:12:59 k2 kernel: [56280.880065] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 6 00:12:59 k2 kernel: [56280.880072] events/0 D c07bcee0 0 9 2
Jun 6 00:12:59 k2 kernel: [56280.880081] f7077f1c 00000046 00000001 c07bcee0 f7057284 c07bcee0 c07bcee0 c07bcee0
Jun 6 00:12:59 k2 kernel: [56280.880096] f7057284 e74cef33 00003311 c07bcee0 f5d616c0 00003311 f7056ff0 f6864414
Jun 6 00:12:59 k2 kernel: [56280.880110] f6864418 ffffffff f7077f48 c053b356 c06f1340 f686441c f7056ff0 f686441c
Jun 6 00:12:59 k2 kernel: [56280.880124] Call Trace:
Jun 6 00:12:59 k2 kernel: [56280.880139] [<c053b356>] __mutex_lock_slowpath+0xc6/0x130
Jun 6 00:12:59 k2 kernel: [56280.880148] [<c053b0d0>] mutex_lock+0x20/0x40
Jun 6 00:12:59 k2 kernel: [56280.880181] [<f85844da>] i915_gem_retire_work_handler+0x2a/0x70 [i915]
Jun 6 00:12:59 k2 kernel: [56280.880191] [<c014b8ae>] run_workqueue+0x6e/0x140
Jun 6 00:12:59 k2 kernel: [56280.880215] [<f85844b0>] ? i915_gem_retire_work_handler+0x0/0x70 [i915]
Jun 6 00:12:59 k2 kernel: [56280.880224] [<c014ba08>] worker_thread+0x88/0xf0
Jun 6 00:12:59 k2 kernel: [56280.880233] [<c014f900>] ? autoremove_wake_function+0x0/0x40
Jun 6 00:12:59 k2 kernel: [56280.880241] [<c014b980>] ? worker_thread+0x0/0xf0
Jun 6 00:12:59 k2 kernel: [56280.880249] [<c014f5a6>] kthread+0x46/0x80
Jun 6 00:12:59 k2 kernel: [56280.880256] [<c014f560>] ? kthread+0x0/0x80
Jun 6 00:12:59 k2 kernel: [56280.880265] [<c0103f57>] kernel_thread_helper+0x7/0x10

ProblemType: Bug
Architecture: i386
Date: Tue Jun 9 00:34:09 2009
DistroRelease: Ubuntu 9.10
MachineType: LENOVO 1703Y1F
Package: xorg 1:7.4~5ubuntu21
ProcCmdLine: root=UUID=c7f80e1a-7946-415c-b54b-8fab9d413770 ro quiet splash crashkernel=384M-2G:64M@16M,2G-:128M@16M
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LC_PAPER=a4
ProcVersionSignature: Ubuntu 2.6.30-8.9-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4~5ubuntu21
 libgl1-mesa-glx 7.4.1-1ubuntu1
 libdrm2 2.4.11-0ubuntu1
 xserver-xorg-video-intel 2:2.7.99.1+git20090602.ec2fde7c-0ubuntu2
 xserver-xorg-video-ati 1:6.12.2-2ubuntu1
SourcePackage: xorg
Uname: Linux 2.6.30-8-generic i686
dmi.bios.date: 03/31/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7BETD5WW (2.16 )
dmi.board.name: 1703Y1F
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: L3AB437
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7BETD5WW(2.16):bd03/31/2008:svnLENOVO:pn1703Y1F:pvrThinkPadX60s:rvnLENOVO:rn1703Y1F:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 1703Y1F
dmi.product.version: ThinkPad X60s
dmi.sys.vendor: LENOVO
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.30-8-generic

Revision history for this message
In , Alex Bennée (ajbennee) wrote :

Created an attachment (id=25269)
Xorg Log File (Tiling off)

Revision history for this message
In , Alex Bennée (ajbennee) wrote :

Created an attachment (id=25270)
GDM Display with tiling off (right of display cliped)

Revision history for this message
In , Alex Bennée (ajbennee) wrote :

Created an attachment (id=25271)
dmesg once X/GDM restarted with tiling re-enabled

Revision history for this message
In , Alex Bennée (ajbennee) wrote :

Created an attachment (id=25272)
GDM display with tilling switched on on obvious corruption on the screen

Revision history for this message
In , Alex Bennée (ajbennee) wrote :

Created an attachment (id=25273)
Xorg Log File (Tilling On)

Revision history for this message
In , Alex Bennée (ajbennee) wrote :

Created an attachment (id=25274)
xorg.conf

Revision history for this message
In , Alex Bennée (ajbennee) wrote :

My setup is Gentoo, the current relevant packages are:

* x11-base/xorg-server
      Latest version available: 1.5.3-r5
      Latest version installed: 1.5.3-r5
      Size of files: 5,545 kB
      Homepage: http://xorg.freedesktop.org/
      Description: X.Org X servers
      License: xorg-server MIT

* x11-base/xorg-x11
      Latest version available: 7.2
      Latest version installed: 7.2
      Size of files: 0 kB
      Homepage: http://xorg.freedesktop.org
      Description: An X11 implementation maintained by the X.Org Foundation (meta package)
      License: as-is

* x11-base/xorg-x11
      Latest version available: 7.2
      Latest version installed: 7.2
      Size of files: 0 kB
      Homepage: http://xorg.freedesktop.org
      Description: An X11 implementation maintained by the X.Org Foundation (meta package)
      License: as-is

* x11-libs/libX11
      Latest version available: 1.1.5
      Latest version installed: 1.1.5
      Size of files: 1,547 kB
      Homepage: http://xorg.freedesktop.org/
      Description: X.Org X11 library
      License: libX11

* x11-libs/libdrm
      Latest version available: 2.4.6
      Latest version installed: 2.4.6
      Size of files: 407 kB
      Homepage: http://dri.freedesktop.org/
      Description: X.Org libdrm library
      License: libdrm

* x11-drivers/xf86-video-intel
      Latest version available: 2.7.0
      Latest version installed: 2.7.0
      Size of files: 762 kB
      Homepage: http://xorg.freedesktop.org/
      Description: X.Org driver for Intel cards
      License: xf86-video-intel

Revision history for this message
In , Alex Bennée (ajbennee) wrote :

Created an attachment (id=25275)
lscpi -v -v output showing my hardware setup

I hope this isn't too rare an Intel chipset. It's only just started giving decent 3D performance again after the A17 patch went in.

Revision history for this message
In , Jesse Barnes (jbarnes-virtuousgeek) wrote :

Your config appears to be failing pretty hard; you don't get the memory layout debug output and for some reason you're falling back to using software rendering. Can you try removing all the lines from the intel section of your xorg.conf except the "accelmethod" "uxa" one?

The second dmesg is just one line, might be good to get the whole thing.

And a backtrace might help here too, can you attach gdb to X right after you start it so that when it crashes you can do a 'bt'?

Revision history for this message
In , Alex Bennée (ajbennee) wrote :

There isn't much in the Intel section of the xorg.conf. If I comment everything but the UXA and driver out it won't start at all.

Here is the backtrace I got once I reset the config and got the usual corruption followed by crash:

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7f365f9ce6f0 (LWP 7107)]
0x00007f365bd3d118 in ?? () from /usr/lib/libdrm_intel.so.1
(gdb) bt
#0 0x00007f365bd3d118 in ?? () from /usr/lib/libdrm_intel.so.1
#1 0x00007f365bd3d017 in ?? () from /usr/lib/libdrm_intel.so.1
#2 0x00007f365bd3d4ac in ?? () from /usr/lib/libdrm_intel.so.1
#3 0x00007f365bf60bc2 in intel_batch_flush () from /usr/lib64/xorg/modules/drivers//intel_drv.so
#4 0x00007f365bf6ba1e in ?? () from /usr/lib64/xorg/modules/drivers//intel_drv.so
#5 0x00000000005134f9 in ?? ()
#6 0x00000000004ef931 in ?? ()
#7 0x000000000044c08f in BlockHandler ()
#8 0x00000000004de78b in WaitForSomething ()
#9 0x00000000004487fb in Dispatch ()
#10 0x0000000000430735 in main ()
(gdb)

If you want I can set X rebuilding with debug symbols

Revision history for this message
In , Alex Bennée (ajbennee) wrote :

Created an attachment (id=25288)
Latest dmesg output

Booted machine, failed to start X, reverted config back to original, restarted, corruption and crash.

Revision history for this message
In , Alex Bennée (ajbennee) wrote :

Created an attachment (id=25289)
Xorg Log File (failed start)

This is with the "Intel" section pared back to just the Driver and AccelMethod lines. Didn't start at all, I suspect it needed to know where my monitor was?

Revision history for this message
In , Alex Bennée (ajbennee) wrote :

Created an attachment (id=25290)
Xorg Log File (Latest corruption and crash log)

Revision history for this message
In , Alex Bennée (ajbennee) wrote :
Download full text (6.4 KiB)

More complete backtrace:

[Switching to Thread 0x7f1e743bc6f0 (LWP 6585)]
drm_intel_gem_bo_unreference_locked (bo=0x15d6e30) at intel_bufmgr_gem.c:585
585 intel_bufmgr_gem.c: No such file or directory.
 in intel_bufmgr_gem.c
(gdb) bt
#0 drm_intel_gem_bo_unreference_locked (bo=0x15d6e30) at intel_bufmgr_gem.c:585
#1 0x00007f1e7072b017 in drm_intel_gem_bo_unreference_locked (bo=0x1573b90) at intel_bufmgr_gem.c:561
#2 0x00007f1e7072b4ac in drm_intel_gem_bo_unreference (bo=0x1573b90) at intel_bufmgr_gem.c:599
#3 0x00007f1e7094ebc2 in intel_batch_flush (pScrn=0x1279760, flushed=<value optimized out>) at i830_batchbuffer.c:204
#4 0x00007f1e70959a1e in I830BlockHandler (i=0, blockData=0x0, pTimeout=0x7fff7c3edde8, pReadmask=0x7cb9c0) at i830_driver.c:2656
#5 0x00000000005134f9 in AnimCurScreenBlockHandler (screenNum=0, blockData=0x0, pTimeout=0x7fff7c3edde8, pReadmask=0x7cb9c0) at animcur.c:199
#6 0x00000000004ef931 in compBlockHandler (i=0, blockData=0x0, pTimeout=0x7fff7c3edde8, pReadmask=0x7cb9c0) at compinit.c:163
#7 0x000000000044c08f in BlockHandler (pTimeout=0x7fff7c3edde8, pReadmask=0x7cb9c0) at dixutils.c:383
#8 0x00000000004de78b in WaitForSomething (pClientsReady=0x1574050) at WaitFor.c:223
#9 0x00000000004487fb in Dispatch () at dispatch.c:375
#10 0x0000000000430735 in main (argc=9, argv=0x7fff7c3edfa8, envp=<value optimized out>) at main.c:438
(gdb) frame 0
#0 drm_intel_gem_bo_unreference_locked (bo=0x15d6e30) at intel_bufmgr_gem.c:585
585 in intel_bufmgr_gem.c
(gdb) info locals
bucket = (struct drm_intel_gem_bo_bucket *) 0x12836d0
tiling_mode = 0
bufmgr_gem = <value optimized out>
(gdb) p *$
The history is empty.
(gdb) p *$bucket
Attempt to take contents of a non-pointer value.
(gdb) p *bucket
$1 = {head = {prev = 0x7f1e7094ef90, next = 0x1279760}, max_entries = -1, num_entries = 1}
(gdb) x/5i $pc
0x7f1e7072b118 <drm_intel_gem_bo_unreference_locked+328>: mov %rdx,0x8(%rax)
0x7f1e7072b11c <drm_intel_gem_bo_unreference_locked+332>: mov %rdx,(%rbx)
0x7f1e7072b11f <drm_intel_gem_bo_unreference_locked+335>: add $0x18,%rsp
0x7f1e7072b123 <drm_intel_gem_bo_unreference_locked+339>: pop %rbx
0x7f1e7072b124 <drm_intel_gem_bo_unreference_locked+340>: pop %rbp
(gdb) p/x $rdx
$2 = 0x15d6eb0
(gdb) p/x $rax
$3 = 0x7f1e7094ef90
(gdb) source /tmp/
.ICE-unix/ .X0-lock .X11-unix/ keyring-Fddiyp/ orbit-alex/ ssh-FczORk6606/
(gdb) directory ~alex/src/xorg
xorg/ xorg2/
(gdb) directory ~alex/src/xorg/
app/ font/ more_debug.log working.log
build.log git_xorg.sh old/ working_vs_nonworking.txt
buildenv.sh hang_and_glitch.log piglit/ working_vs_nonworking_unified.txt
buildit.sh hw.txt pixman/ xcb/
core install/ proto/ xkeyboard-config/
data/ kernel_oops.txt report.txt ...

Read more...

Revision history for this message
In , Alex Bennée (ajbennee) wrote :

Ok a little unwrapping of macros later and I get:

Program received signal SIGSEGV, Segmentation fault.
0x00007fc30a950921 in drm_intel_gem_bo_unreference_locked (bo=0x2862eb0) at intel_bufmgr_gem.c:591
591 (&bucket->head)->prev->next = (&bo_gem->head);
(gdb) x/5i $pc
0x7fc30a950921 <drm_intel_gem_bo_unreference_locked+446>: mov %rax,0x8(%rdx)
0x7fc30a950925 <drm_intel_gem_bo_unreference_locked+450>: mov -0x18(%rbp),%rdx
0x7fc30a950929 <drm_intel_gem_bo_unreference_locked+454>: sub $0xffffffffffffff80,%rdx
0x7fc30a95092d <drm_intel_gem_bo_unreference_locked+458>: mov -0x10(%rbp),%rax
0x7fc30a950931 <drm_intel_gem_bo_unreference_locked+462>: mov %rdx,(%rax)
(gdb) p &bucket->head
$1 = (drmMMListHead *) 0x24fb6d0
(gdb) p *$
$2 = {prev = 0x7fc30ab75f90, next = 0x24f1760}
(gdb) p *$->prev
$3 = {prev = 0x53fd8948d0894855, next = 0x289a8b4808ec8348}
(gdb) p *$->prev->next
Cannot access memory at address 0x53fd8948d089485d

I'm a little confused myself to the whole ->prev->next thing, surely (assuming prev wasn't broken) it would always point back to &bucket->head?

Revision history for this message
In , Alex Bennée (ajbennee) wrote :

Reassigning to anholt following IRC conversation with jbarnes as the crash looks very libdrm related.

Revision history for this message
In , Alex Bennée (ajbennee) wrote :

Created an attachment (id=25328)
Xorg Log File (Working system, KMS disabled)

Following discussion on IRC and looking at a working setup (i.e.
disable KMS) the following seems to be the case.

1. With KMS enabled the intel driver doesn't get any memory
allocation.
2. This should probably be a fatal error rather than just
informational
3. In this state of affairs libdrm can see a corrupt list of memory
and crash

However 2 & 3 are probably symptoms of 1.

Let me know if there is any more information I can provide.

Revision history for this message
In , Alex Bennée (ajbennee) wrote :

This behaviour seems to have progressed since on the latest intel-drm-next. I can now get a working login. However video playback locks the X server and mode switching doesn't seem to work. dmesg shows:

0.272044] Call Trace:
0.272053] [<ffffffff804bfce6>] ? thread_return+0x3e/0xaa
0.272058] [<ffffffff804c0589>] __mutex_lock_slowpath+0xdf/0x129
0.272062] [<ffffffff804c092d>] mutex_lock+0x23/0x3b
0.272067] [<ffffffff803cecd3>] i915_gem_retire_work_handler+0x2d/0x6b
0.272073] [<ffffffff80247666>] worker_thread+0x176/0x20f
0.272078] [<ffffffff803ceca6>] ? i915_gem_retire_work_handler+0x0/0x6b
0.272083] [<ffffffff8024b463>] ? autoremove_wake_function+0x0/0x3d
0.272087] [<ffffffff802474f0>] ? worker_thread+0x0/0x20f
0.272091] [<ffffffff802474f0>] ? worker_thread+0x0/0x20f
0.272095] [<ffffffff8024b061>] kthread+0x5b/0x88
0.272101] [<ffffffff8020c0ba>] child_rip+0xa/0x20
0.272105] [<ffffffff8024b006>] ? kthread+0x0/0x88
0.272109] [<ffffffff8020c0b0>] ? child_rip+0x0/0x20

Should I close this bug and raise a new one?

Revision history for this message
Amit Kucheria (amitk) wrote :

Binary package hint: xorg

On my Karmic upgrade, Xorg periodically just blanks out (black screen) and I can never get it back.

Sshing into the machine shows the following attached logs (/var/log/kern.log)

Jun 6 00:12:59 k2 kernel: [56280.880058] INFO: task events/0:9 blocked for more than 120 seconds.
Jun 6 00:12:59 k2 kernel: [56280.880065] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
Jun 6 00:12:59 k2 kernel: [56280.880072] events/0 D c07bcee0 0 9 2
Jun 6 00:12:59 k2 kernel: [56280.880081] f7077f1c 00000046 00000001 c07bcee0 f7057284 c07bcee0 c07bcee0 c07bcee0
Jun 6 00:12:59 k2 kernel: [56280.880096] f7057284 e74cef33 00003311 c07bcee0 f5d616c0 00003311 f7056ff0 f6864414
Jun 6 00:12:59 k2 kernel: [56280.880110] f6864418 ffffffff f7077f48 c053b356 c06f1340 f686441c f7056ff0 f686441c
Jun 6 00:12:59 k2 kernel: [56280.880124] Call Trace:
Jun 6 00:12:59 k2 kernel: [56280.880139] [<c053b356>] __mutex_lock_slowpath+0xc6/0x130
Jun 6 00:12:59 k2 kernel: [56280.880148] [<c053b0d0>] mutex_lock+0x20/0x40
Jun 6 00:12:59 k2 kernel: [56280.880181] [<f85844da>] i915_gem_retire_work_handler+0x2a/0x70 [i915]
Jun 6 00:12:59 k2 kernel: [56280.880191] [<c014b8ae>] run_workqueue+0x6e/0x140
Jun 6 00:12:59 k2 kernel: [56280.880215] [<f85844b0>] ? i915_gem_retire_work_handler+0x0/0x70 [i915]
Jun 6 00:12:59 k2 kernel: [56280.880224] [<c014ba08>] worker_thread+0x88/0xf0
Jun 6 00:12:59 k2 kernel: [56280.880233] [<c014f900>] ? autoremove_wake_function+0x0/0x40
Jun 6 00:12:59 k2 kernel: [56280.880241] [<c014b980>] ? worker_thread+0x0/0xf0
Jun 6 00:12:59 k2 kernel: [56280.880249] [<c014f5a6>] kthread+0x46/0x80
Jun 6 00:12:59 k2 kernel: [56280.880256] [<c014f560>] ? kthread+0x0/0x80
Jun 6 00:12:59 k2 kernel: [56280.880265] [<c0103f57>] kernel_thread_helper+0x7/0x10

ProblemType: Bug
Architecture: i386
Date: Tue Jun 9 00:34:09 2009
DistroRelease: Ubuntu 9.10
MachineType: LENOVO 1703Y1F
Package: xorg 1:7.4~5ubuntu21
ProcCmdLine: root=UUID=c7f80e1a-7946-415c-b54b-8fab9d413770 ro quiet splash crashkernel=384M-2G:64M@16M,2G-:128M@16M
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
 LC_PAPER=a4
ProcVersionSignature: Ubuntu 2.6.30-8.9-generic
RelatedPackageVersions:
 xserver-xorg 1:7.4~5ubuntu21
 libgl1-mesa-glx 7.4.1-1ubuntu1
 libdrm2 2.4.11-0ubuntu1
 xserver-xorg-video-intel 2:2.7.99.1+git20090602.ec2fde7c-0ubuntu2
 xserver-xorg-video-ati 1:6.12.2-2ubuntu1
SourcePackage: xorg
Uname: Linux 2.6.30-8-generic i686
dmi.bios.date: 03/31/2008
dmi.bios.vendor: LENOVO
dmi.bios.version: 7BETD5WW (2.16 )
dmi.board.name: 1703Y1F
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: L3AB437
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7BETD5WW(2.16):bd03/31/2008:svnLENOVO:pn1703Y1F:pvrThinkPadX60s:rvnLENOVO:rn1703Y1F:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 1703Y1F
dmi.product.version: ThinkPad X60s
dmi.sys.vendor: LENOVO
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: i686kernel: 2.6.30-8-generic

Revision history for this message
Amit Kucheria (amitk) wrote :
Revision history for this message
Amit Kucheria (amitk) wrote :
Changed in xorg-server:
status: Unknown → Confirmed
Revision history for this message
In , Gordon Jin (gordon-jin) wrote :

(In reply to comment #18)
> This behaviour seems to have progressed since on the latest intel-drm-next. I
> can now get a working login. However video playback locks the X server and mode
> switching doesn't seem to work. dmesg shows:
> 0.272044] Call Trace:
> 0.272053] [<ffffffff804bfce6>] ? thread_return+0x3e/0xaa
> 0.272058] [<ffffffff804c0589>] __mutex_lock_slowpath+0xdf/0x129
> 0.272062] [<ffffffff804c092d>] mutex_lock+0x23/0x3b
> 0.272067] [<ffffffff803cecd3>] i915_gem_retire_work_handler+0x2d/0x6b
> 0.272073] [<ffffffff80247666>] worker_thread+0x176/0x20f
> 0.272078] [<ffffffff803ceca6>] ? i915_gem_retire_work_handler+0x0/0x6b
> 0.272083] [<ffffffff8024b463>] ? autoremove_wake_function+0x0/0x3d
> 0.272087] [<ffffffff802474f0>] ? worker_thread+0x0/0x20f
> 0.272091] [<ffffffff802474f0>] ? worker_thread+0x0/0x20f
> 0.272095] [<ffffffff8024b061>] kthread+0x5b/0x88
> 0.272101] [<ffffffff8020c0ba>] child_rip+0xa/0x20
> 0.272105] [<ffffffff8024b006>] ? kthread+0x0/0x88
> 0.272109] [<ffffffff8020c0b0>] ? child_rip+0x0/0x20
> Should I close this bug and raise a new one?

yes, I think so. And you can refer to http://intellinuxgraphics.org/how_to_report_bug.html when filing bugs. Thanks.

Timo Aaltonen (tjaalton)
affects: xorg (Ubuntu) → xserver-xorg-video-intel (Ubuntu)
Changed in xorg-server:
status: Confirmed → Fix Released
Revision history for this message
Amit Kucheria (amitk) wrote : Re: [Bug 384960] Re: Xorg driver locks up and screen goes blank (black) - i915_gem_retire_work_handler+0x2a/0x70

On 09 Jun 10, Bug Watch Updater wrote:
> ** Changed in: xorg-server
> Status: Confirmed => Fix Released
>

What package version is this fix released in? Should be using Bryce's
pvt PPA or the Ubuntu X Edgers PPA?

Revision history for this message
Bryce Harrington (bryce) wrote :

> On 09 Jun 10, Bug Watch Updater wrote:
> > ** Changed in: xorg-server
> > Status: Confirmed => Fix Released
> >
>
> What package version is this fix released in? Should be using Bryce's
> pvt PPA or the Ubuntu X Edgers PPA?

Actually, the upstream bug this is connected to is reporting two separate issues. The first of the two issues is the one that is fixed. You are seeing the second issue. mdz is seeing the same problem and collected some good debug info so I've forwarded his upstream:

  https://bugs.freedesktop.org/show_bug.cgi?id=22336

I'll set yours as a dupe of his.

Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Confirmed
Geir Ove Myhr (gomyhr)
tags: added: 945gm freeze karmic
Revision history for this message
Jeffrey Baker (jwbaker) wrote :

I don't think this is relate to xorg#21480 ... but I do think launchpad #395855 is probably a dupe of this. xorg#22383 seems more closely related. xorg#22336 seems like a red herring.

Revision history for this message
Jeffrey Baker (jwbaker) wrote :

Sorry I got those last two bugs swapped. xorg 22336 seems like the relevant one.

Bryce Harrington (bryce)
Changed in xserver-xorg-video-intel (Ubuntu):
status: Confirmed → Triaged
Revision history for this message
Bryce Harrington (bryce) wrote :

The upstream bug is marked fixed, although it's a little ambiguous what exactly the fix is. In any case I know from other people's testing that a HUGE amount of bugs of this class have been fixed in recent months so it's a good guess this bug is gone.

If I'm wrong, Amit please reopen with a fresh Xorg.0.log and I'll follow up with upstream.

Changed in xserver-xorg-video-intel (Ubuntu):
status: Triaged → Fix Released
Revision history for this message
Amit Kucheria (amitk) wrote : Re: [Bug 384960] Re: Xorg driver locks up and screen goes blank (black) - i915_gem_retire_work_handler+0x2a/0x70

On 09 Jul 21, Bryce Harrington wrote:
> The upstream bug is marked fixed, although it's a little ambiguous what
> exactly the fix is. In any case I know from other people's testing that
> a HUGE amount of bugs of this class have been fixed in recent months so
> it's a good guess this bug is gone.
>
> If I'm wrong, Amit please reopen with a fresh Xorg.0.log and I'll follow
> up with upstream.

I haven't seen this in a while now. So I assume it got fixed somewhere
along the way. THanks.

Revision history for this message
Søren Holm (sgh) wrote :

Apparently it can still happen. I'm running AJuty with 2.6.30 and newest intel-drivers from X-swat PPA

Revision history for this message
iuuuuan (ivan-janes) wrote :

I have similar issues on Dell Optiplex GX260. Ubuntu 9.10 is fully updated. I have updated Bios from version A05 to A09 - this didn't helped a lot.

lspci -vv shows :

00:02.0 VGA compatible controller: Intel Corporation 82845G/GL[Brookdale-G]/GE Chipset Integrated Graphics Device (rev 01)
 Subsystem: Dell Device 0126
 Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
 Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0
 Interrupt: pin A routed to IRQ 16
 Region 0: Memory at e8000000 (32-bit, prefetchable) [size=128M]
 Region 1: Memory at ff680000 (32-bit, non-prefetchable) [size=512K]
 Capabilities: <access denied>
 Kernel driver in use: i915
 Kernel modules: i915

I have added in /etc/X11/xorg.conf in section "Device" (don't know if this has any effect) :

Option "AccelMethod" "uxa"

I have commented out in etc/X11/xorg.conf in section "Module" :
# Load "glx"
# Load "GLcore"
# Load "dri"
# Load "v4l"

Currently it is working fine. I will report again if there will be any new lockups. I have attached my xorg.conf.

Changed in xorg-server:
importance: Unknown → Medium
Changed in xorg-server:
importance: Medium → Unknown
Changed in xorg-server:
importance: Unknown → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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