[q45] unlocking screensaver - graphics are not updated any more

[iroli]

Binary package hint: xorg

Howto reproduce:

1) lock the screen using ctrl+alt+L
2) press a button

expected behaviour:
3) screen unlock widget rendered
4) type in password, resume session

actual behaviour:
3) screen unlock widget is _not_ drawn
4) blind typing password and pressing enter I *think* unlocks screen, but still no updates to the screen are rendered. I only see the old screen content (screen saver images), mouse cursor however changes it's icon as I move it around the screen.

[52309.278345] ------------[ cut here ]------------
[52309.278350] WARNING: at /build/buildd/linux-2.6.38/kernel/power/suspend_test.c:53 suspend_test_finish+0x86/0x90()
[52309.278351] Hardware name:
[52309.278353] Component: resume devices, time: 10140
[52309.278354] Modules linked in: nls_utf8 udf crc_itu_t binfmt_misc vboxnetadp vboxnetflt vboxdrv parport_pc ppdev snd_hda_codec_analog usblp i915 snd_hda_intel snd_hda_codec drm_kms_helper snd_hwdep snd_pcm snd_seq_midi drm snd_rawmidi snd_seq_midi_event snd_seq i2c_algo_bit snd_timer snd_seq_device video snd joydev soundcore snd_page_alloc tpm_tis psmouse serio_raw tpm tpm_bios lp parport hid_cherry usbhid hid e1000e
[52309.278377] Pid: 5508, comm: pm-suspend Not tainted 2.6.38-8-generic #41-Ubuntu
[52309.278378] Call Trace:
[52309.278383] [<ffffffff81065cef>] ? warn_slowpath_common+0x7f/0xc0
[52309.278385] [<ffffffff81065de6>] ? warn_slowpath_fmt+0x46/0x50
[52309.278388] [<ffffffff810a7556>] ? suspend_test_finish+0x86/0x90
[52309.278390] [<ffffffff810a726c>] ? suspend_devices_and_enter+0xac/0x170
[52309.278392] [<ffffffff810a7450>] ? enter_state+0x120/0x150
[52309.278395] [<ffffffff810a68a6>] ? state_store+0xc6/0x100
[52309.278399] [<ffffffff812dcad7>] ? kobj_attr_store+0x17/0x20
[52309.278402] [<ffffffff811d3cce>] ? sysfs_write_file+0xde/0x160
[52309.278405] [<ffffffff81164df6>] ? vfs_write+0xc6/0x180
[52309.278407] [<ffffffff81165111>] ? sys_write+0x51/0x90
[52309.278410] [<ffffffff8100c002>] ? system_call_fastpath+0x16/0x1b
[52309.278412] ---[ end trace 485d336c8c32034b ]---

ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: xorg 1:7.6+4ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.41-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
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.HDMI.A.1:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 640x480 640x480 720x400
 edid-base64: AP///////wAebdBDc28BAAUPAQPuIht46i7lpFdKnCURUFSlaoAxT0VPYU+BgAEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAeAAAA/QA4Sx5HCwAKICAgICAgAAAA/ABMMTc0MFAKICAgICAgAAAA/AAgCiAgICAgICAgICAgAFk=
DRM.card0.HDMI.A.2:
 status: connected
 enabled: enabled
 dpms: On
 modes: 1280x1024 1152x864 1024x768 1024x768 1024x768 832x624 800x600 800x600 640x480 640x480 720x400
 edid-base64: AP///////wAebdBD6cYBAAEPAQPuIht46i7lpFdKnCURUFSlaoAxT0VPYU+BgAEBAQEBAQEBMCoAmFEAKkAwcBMAUg4RAAAeAAAA/QA4Sx5HCwAKICAgICAgAAAA/ABMMTc0MFAKICAgICAgAAAA/AAgCiAgICAgICAgICAgAJA=
DRM.card0.VGA.1:
 status: disconnected
 enabled: disabled
 dpms: Off
 modes:
 edid-base64:
Date: Mon Apr 11 09:14:39 2011
DistUpgraded: Log time: 2011-04-03 22:04:09.973657
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus:
 virtualbox-ose, 4.0.4, 2.6.35-28-generic, x86_64: installed
 virtualbox-ose, 4.0.4, 2.6.38-7-generic, x86_64: installed
 virtualbox-ose, 4.0.4, 2.6.38-8-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e12] (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device [8086:1004]
   Subsystem: Intel Corporation Device [8086:1004]
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
ProcEnviron:
 LANGUAGE=en
 LANG=de_AT.utf8
 LC_MESSAGES=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-8-generic root=UUID=15f0482a-2d87-4200-9a3e-1145522e8097 ro quiet splash vt.handoff=7
Renderer: Unknown
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to natty on 2011-04-03 (7 days ago)
dmi.bios.date: 04/12/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: CBQ4510H.86A.0121.2010.0412.0911
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DQ45EK
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE30149-211
dmi.chassis.type: 3
dmi.modalias: dmi:bvnIntelCorp.:bvrCBQ4510H.86A.0121.2010.0412.0911:bd04/12/2010:svn:pn:pvr:rvnIntelCorporation:rnDQ45EK:rvrAAE30149-211:cvn:ct3:cvr:
version.compiz: compiz 1:0.9.4+bzr20110407-0ubuntu2
version.ia32-libs: ia32-libs 20090808ubuntu11
version.libdrm2: libdrm2 2.4.23-1ubuntu6
version.libgl1-mesa-dri: libgl1-mesa-dri 7.10.1-0ubuntu3
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1-0ubuntu3
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-4ubuntu6
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu6

[Bryce Harrington (bryce)]

Looks perhaps PM related

[iroli (roland-lezuo)]

PM sound likely as the bug doe not manifest itself when locking the screen for a short period of time. Only if the screensaver is running for a prolonged time the bug seems triggered. Is there a way to provide you with debug information, the system is still responsible an I can log on using a VT.

[Jeremy Foshee (jeremyfoshee)]

iroli,
    Was there any oops text associated with this issue? If so, please attach it to this bug.

Thanks!

~JFo

[iroli (roland-lezuo)]

No, I could not find any logging information indicating a problem at all.

[iroli (roland-lezuo)]

I upgraded to intel 2.15.0 driver (manually compiling from sid sources). The issue is still there, but I have discovered some log entries whcih may pinpoint the problem:

from /var/log/Xorg.0.log

[ 27928.379] (II) intel(0): Modeline "1152x864"x0.0 108.00 1152 1216 1344 1600 864 865 868 900 +hsync +vsync (67.5 kHz)
[ 32578.681] (WW) intel(0): I830DRI2GetMSC:1144 get vblank counter failed: Invalid argument
[ 32578.734] (WW) intel(0): I830DRI2GetMSC:1144 get vblank counter failed: Invalid argument
[ 32578.734] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32578.767] (WW) intel(0): I830DRI2GetMSC:1144 get vblank counter failed: Invalid argument
[ 32578.767] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32578.800] (WW) intel(0): I830DRI2GetMSC:1144 get vblank counter failed: Invalid argument
[ 32578.800] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32578.833] (WW) intel(0): I830DRI2GetMSC:1144 get vblank counter failed: Invalid argument
[ 32578.833] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32580.693] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32580.727] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32580.760] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32580.793] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32580.825] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32580.858] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32580.891] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32580.924] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32580.957] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32580.990] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.023] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.056] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.088] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.121] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.154] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.187] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.220] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.253] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.286] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.319] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.351] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.384] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.417] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.450] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.483] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.516] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 32581.549] (WW) intel(0): first get vblank counter failed: Invalid argument
[ ...

[icb410 (ian-berke)]

I have this bug as well, usually I observe it after suspending my laptop for a long period of time (closing the lid). I'm running Oneiric with
xserver-xorg-video-intel:
  Installed: 2:2.15.901-1ubuntu2
  Candidate: 2:2.15.901-1ubuntu2
  Version table:
 *** 2:2.15.901-1ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ oneiric/main amd64 Packages
        100 /var/lib/dpkg/status

  I don't run a screen saver but the screen lock dialog when I fire back up the computer doesn't appear. To unfreeze I drop to a terminal (ctl-alt-F1) and sigkill compiz (using htop) which restarts it. Then I get the login screen (unless I type my password and enter in the graphics terminal before killing compiz). I get the same errors in my Xorg.0.log file:

[ 13445.959] (EE) intel(0): Couldn't create pixmap for fbcon
[ 13446.020] (II) intel(0): EDID vendor "SEC", prod id 13385
[ 13446.020] (II) intel(0): Printing DDC gathered Modelines:
[ 13446.020] (II) intel(0): Modeline "1366x768"x0.0 70.70 1366 1414 1446 1486 768 770 775 792 -hsync -vsync (47.6 kHz)
[ 13446.360] (II) SynPS/2 Synaptics TouchPad: failed to open grail, no gesture support
[ 13446.360] (--) SynPS/2 Synaptics TouchPad: touchpad found
[ 13446.620] (II) XKB: reuse xkmfile /var/lib/xkb/server-9A8405F3FE0A780485714A4B6DD41909C2CF9F83.xkm
[ 13454.811] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 13478.514] (II) Open ACPI successful (/var/run/acpid.socket)
[ 13478.515] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 13478.515] (EE) intel(0): Couldn't create pixmap for fbcon
[ 13478.570] (II) intel(0): EDID vendor "SEC", prod id 13385

[ 13478.570] (II) intel(0): Printing DDC gathered Modelines:
[ 13478.570] (II) intel(0): Modeline "1366x768"x0.0 70.70 1366 1414 1446 1486 768 770 775 792 -hsync -vsync (47.6 kHz)
[ 13478.721] (II) SynPS/2 Synaptics TouchPad: failed to open grail, no gesture support
[ 13478.721] (--) SynPS/2 Synaptics TouchPad: touchpad found
[ 13478.830] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[ 13478.972] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[ 13478.974] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[ 13478.975] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[ 13479.097] (II) XKB: reuse xkmfile /var/lib/xkb/server-9A8405F3FE0A780485714A4B6DD41909C2CF9F83.xkm
[ 13479.764] (WW) intel(0): I830DRI2GetMSC:1297 get vblank counter failed: Invalid argument
[ 13482.487] (II) XKB: reuse xkmfile /var/lib/xkb/server-9A8405F3FE0A780485714A4B6DD41909C2CF9F83.xkm

[ 13485.513] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[ 13485.513] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 13485.528] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[ 13485.528] (WW) intel(0): first get vblank counter failed: Invalid argument
[ 13485.540] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[ 13485.555] (WW) intel(0): I830DRI2ScheduleWaitMSC:1364 get vblank counter failed: Invalid argument
[ 13485.569] (WW)...

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . If possible, please test the latest release candidate kernel (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the others). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed by the mainline kernel, please add the following tag 'kernel-fixed-upstream-KERNEL-VERSION'. For example, if kernel version 3.1-rc9 fixed and issue, the tag would be: 'kernel-fixed-upstream-v3.1-rc9'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Thanks in advance.

[icb410 (ian-berke)]

I'm testing it now (3.1-rc10)... so far so good but I want to keep testing it for a couple of days since it sometimes seemed a little random. Also, turns out my grub wasn't updating properly before and I never realized I wasn't running an up-to-date kernel (2.6.38-8.42) so this may have been fixed in a v3.0 kernel . I'll post back in a couple of days if everything goes well or not.

[icb410 (ian-berke)]

I'm calling this fixed using kernel3.1-rc10! I haven't had one lockup like I experienced before. Thanks for the great work. Modified the tags as requested.

[penalvch (penalvch)]

iroli, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available (not the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]