[GM45] system frozen after a period of inactivity

Bug #383973 reported by Nicolò Chieffo
46
This bug affects 8 people
Affects Status Importance Assigned to Milestone
gnome-power-manager (Ubuntu)
Invalid
Undecided
Unassigned
linux (Ubuntu)
Won't Fix
Undecided
Unassigned
xserver-xorg-video-intel (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

My system freezes after a period of inactivity, after the screen is blanked I cannot recover it.

[17040.776121] Call Trace:
[17040.776142] [<ffffffff806d9467>] __mutex_lock_slowpath+0xd7/0x160
[17040.776155] [<ffffffff802436b1>] ? finish_task_switch+0x51/0x110
[17040.776163] [<ffffffff806d9186>] mutex_lock+0x26/0x50
[17040.776200] [<ffffffffa0240ec8>] i915_gem_retire_work_handler+0x38/0x90 [i915]
[17040.776222] [<ffffffffa0240e90>] ? i915_gem_retire_work_handler+0x0/0x90 [i915]
[17040.776232] [<ffffffff802643d5>] run_workqueue+0x95/0x170
[17040.776239] [<ffffffff80264554>] worker_thread+0xa4/0x120
[17040.776249] [<ffffffff80268e90>] ? autoremove_wake_function+0x0/0x40
[17040.776256] [<ffffffff802644b0>] ? worker_thread+0x0/0x120
[17040.776265] [<ffffffff80268a35>] kthread+0x55/0xa0
[17040.776273] [<ffffffff802130ca>] child_rip+0xa/0x20
[17040.776281] [<ffffffff802689e0>] ? kthread+0x0/0xa0
[17040.776288] [<ffffffff802130c0>] ? child_rip+0x0/0x20

ProblemType: Bug
Architecture: amd64
Date: Fri Jun 5 17:31:24 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=f2f2f06b-2789-4704-8267-388f1e8bc9ca
MachineType: Dell Inc. Latitude E6400
Package: linux-image-2.6.30-8-generic 2.6.30-8.9
ProcCmdLine: root=UUID=0f5f2103-da7b-4e52-ab7f-df158e2f816a ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.30-8.9-generic
RelatedPackageVersions: linux-backports-modules-2.6.30-8-generic N/A
SourcePackage: linux
Uname: Linux 2.6.30-8-generic x86_64
dmi.bios.date: 12/17/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0RX493
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/17/2008:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0RX493:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6400
dmi.sys.vendor: Dell Inc.

Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :

This bug today presented even with -7 kernel, so the problem should be in the intel driver.

Immediately after the screen blanks I can recover it moving the mouse.
I left the pc on for 30 minutes. Now it's not possible to recover it.

Revision history for this message
Nicolò Chieffo (yelo3) wrote : apport-collect data

Architecture: amd64
DistroRelease: Ubuntu 9.10
MachineType: Dell Inc. Latitude E6400
Package: xserver-xorg-video-intel 2:2.7.99.1+git20090602.ec2fde7c-0ubuntu2
PackageArchitecture: amd64
ProcCmdLine: root=UUID=0f5f2103-da7b-4e52-ab7f-df158e2f816a ro quiet splash
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_US.UTF-8
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
Uname: Linux 2.6.30-8-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/17/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0RX493
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA11:bd12/17/2008:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0RX493:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6400
dmi.sys.vendor: Dell Inc.
fglrx: Not loaded
system:
 distro: Ubuntu
 architecture: x86_64kernel: 2.6.30-8-generic

Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Revision history for this message
Nicolò Chieffo (yelo3) wrote :
Bryce Harrington (bryce)
summary: - system frozen after a period of inactivity
+ [GM45] system frozen after a period of inactivity
Geir Ove Myhr (gomyhr)
tags: added: gm45 intel karmic xorg
Revision history for this message
Nicolò Chieffo (yelo3) wrote :

I also added gnome-power-manager because when I close the laptop lid it freezes again (if set to blank screen)

Changed in gnome-power-manager (Ubuntu):
status: New → Invalid
Revision history for this message
Chris Halse Rogers (raof) wrote :

Marking gnome-power-manager task as invalid. I see no incorrect behaviour from the power manager.

I also see this bug. It appears to be triggered by turning off the display with DPMS. Once the display has been turned off, X seems unable to turn it back on. The laptop is still responsive - network & activity continues, and if KMS is enabled, SAKing X will turn the screen back on. Confirming for the DDX component; I'm not sure why this would be kernel-related when not using KMS. I'll do some more testing.

Changed in xserver-xorg-video-intel (Ubuntu):
status: New → Confirmed
Revision history for this message
Chris Halse Rogers (raof) wrote :

Argh. I might have been premature in discounting the kernel. "xset dpms force {off|standby|suspend}" does *not* trigger this bug. Perhaps it's something to do with turning off the backlight?

Revision history for this message
Nicolò Chieffo (yelo3) wrote : Re: [Bug 383973] Re: [GM45] system frozen after a period of inactivity

try to wait some minutes, after setting the dpms off

Revision history for this message
Ivan Stetsenko (stetzen) wrote :

I've noted similar behaviour on

00:02.0 VGA compatible controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 0c)

Revision history for this message
bonsiware (bonsiware-deactivatedaccount) wrote :

same here on:
00:02.1 Display controller: Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (rev 03)

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

I've also tried xset dpms force off and left there for 1 hour. no freeze.
Is it possible that gnome-power manager uses another method?

Revision history for this message
Wicla (wicla) wrote :

Here's another device which is experiencing the same problem.
00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)

Revision history for this message
Nicolò Chieffo (yelo3) wrote :
  • dmesg.log Edit (55.5 KiB, text/x-log; charset=UTF-8; name="dmesg.log")

I managed to ssh to my box after the crash: I collected the dmesg output.
I cannot even reboot because sudo reboot crashes

Bryce Harrington (bryce)
description: updated
Revision history for this message
Nicolò Chieffo (yelo3) wrote :

xset causes the crash (well tested twice):
- sleep 10; xset dpms force off
- close the lid
- go to sleep
- wake up
- open the lid
everything black!

description: updated
Revision history for this message
Nicolò Chieffo (yelo3) wrote :

Bryce, since I can ssh login after the crash, can you tell me which commands should I execute to gather as most info as possible?

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

This has the same call trace as 388357, but that does not necessarily prove it is a dupe - the only real way is to collect a batchbuffer dump. Please follow the directions on this page to collect it. A dump is also required in order for us to forward the bug upstream for further work:

https://wiki.ubuntu.com/X/Troubleshooting/Freeze#How%20to%20Get%20a%20Batchbuffer%20Dump%20(-intel%20only)

Changed in xserver-xorg-video-intel (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Robert Hooker (sarvatt) wrote :

This is a very common dpms problem that was fixed just recently in the intel driver, and the regression was introduced in the "Sync DRI2 CopyRegion to vertical retrace" commit on 6/02 that snuck into karmic. If you want to test the fix, please add this PPA to your sources and pull in all of the upgrades.

https://launchpad.net/~xorg-edgers/+archive/ppa

The commits that fixed it were
http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=5d80e24b5fc6d6028028da6ded35389c08bfce29
and
http://cgit.freedesktop.org/xorg/driver/xf86-video-intel/commit/?id=f0270bbb47baed78a0ff6189ae20d3ac322ec02b

The bug upstream is:
https://bugs.freedesktop.org/show_bug.cgi?id=22383

Revision history for this message
Nicolò Chieffo (yelo3) wrote :

yes, it seems fixed with the PPA you gave me

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xserver-xorg-video-intel - 2:2.7.99.901+git20090702.74227141-0ubuntu1

---------------
xserver-xorg-video-intel (2:2.7.99.901+git20090702.74227141-0ubuntu1) karmic; urgency=low

  [Robert Hooker]
  * Update to git 20090702 (master branch) up to commit 74227141
   - Treat disabled CRTCs as "not covering" for scanline wait purposes.
     Fixes problems returning from a dpms off state.
     (LP: #390917, #383973, #390633, #385448, #388357)
   - Add an xorg.conf option to control swapbuffers behavior.
   - Set hot plug interrupt to detect HDMI output.
   - Add a pipe-a quirk for Dell mini
     (LP: #395306)
   - Add a pipe-a quirk for thinkpad x30
     (LP: #304614)
   - Reenable XvMC support in UXA. Now includes vld support.
   - Fix EDID for LVDS output device to add the default modes in UMS.
     (LP: #385832)
   - Export EDID when using KMS, so Display options shows info correctly
     (LP: #395140)
   - Fixes for SDVO LVDS mode detection.
   - Fix major performance regression of trapezoid rendering in UXA.
   - Fixes for hangs when GL compositing is used with multiple monitors
     with different refresh rates.
   - Support for new IGDNG devices.
   - Only get the VBIOS in non-KMS mode
   - Add a few error messages for DRM initialization
   - Don't try to pin buffers in KMS mode
   - Fix 945GM VT switch in UMS
   - Clear the bo on the rotate scratch pixmap (Fixes problems with rotation)
   - uxa: Fix segfault on source-only picture usage with FallbackDebug.
   - Various XvMC fixes.
  * Merge with Debian experimental. Remaining Ubuntu changes:
   - Add lpia architecture
  * Drop patches since they're already upstream:
    - 110_quirk_hp_mini.patch
    - 117_quirk_thinkpad_x30.patch
    - 118_pixmap_inline_funcs.patch
    - 119_fix_drawable_abuse.patch
    - 120_fix_dri2_vblank_syncing_segfault.patch
    - 121_dont_change_blank_sync_width.patch
    - 122_wait_for_vblank_to_sub_border_color.patch
    - 123_kms_export_edid.patch

 -- Bryce Harrington <email address hidden> Thu, 09 Jul 2009 14:02:45 -0700

Changed in xserver-xorg-video-intel (Ubuntu):
status: Incomplete → Fix Released
tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Incomplete → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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