On some AMD graphic card, I can reproduce the issue even with the xserver-xorg-lts-precise and quantal backported kernel (3.5.x).
The 100% Xorg CPU consumption can also be reproduced by logging out from the desktop system (back to lightdm) besides suspending the system. Both scenarios happens with high possibility (though not always, but usually in dozens of times). BTW, the virtual terminal switching leads to blank screen. When the Xorg occupied 100% CPU, ctrl+c in gdb, the backtrace: (gdb) bt #0 0x00007fb22e17b633 in __pread_nocancel () from /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x00007fb22e38dc1b in ?? () from /usr/lib/x86_64-linux-gnu/libpciaccess.so.0 #2 0x00007fb22b89a29f in amd_xs113_int10_x_inl () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so #3 0x00007fb22b892dfb in ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so #4 0x00007fb22b886515 in X86EMU_exec () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so #5 0x00007fb22b89b246 in amd_xs113_int10_xf86ExecX86int10 () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so #6 0x00007fb22b3e52fd in xf86ExecX86int10 () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so #7 0x00007fb229bdd3ed in VBESetVBEMode () from /usr/lib/xorg/modules/libvbe.so #8 0x00007fb22b416ce3 in ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so #9 0x00007fb22b416b34 in atiddxVBESetConsoleMode () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so #10 0x00007fb22b53508b in xdl_xs113_atiddxLeaveVT () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/drivers/fglrx_drv.so #11 0x00007fb22eef6282 in ?? () #12 0x00007fb22bf5f30e in ?? () from /usr/lib/x86_64-linux-gnu/xorg/extra-modules/modules/extensions/libglx.so #13 0x00007fb22eedbc27 in xf86Wakeup () #14 0x00007fb22ee9fb1b in WakeupHandler () #15 0x00007fb22eff8a06 in WaitForSomething () #16 0x00007fb22ee9b4f2 in ?? () #17 0x00007fb22ee8a15a in ?? () #18 0x00007fb22cdf276d in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #19 0x00007fb22ee8a4b1 in _start () -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to fglrx-installer in Ubuntu. https://bugs.launchpad.net/bugs/1105171 Title: X.Org is stuck in a loop on resume from S3 Status in amd: In Progress Status in “fglrx-installer” package in Ubuntu: In Progress Bug description: X.Org is stuck in a loop on resume from S3. Only doing Alt+Sysrq+K kills X and allows the system to go back to the login screen. When it was stuck in the loop I could clearly see the laptop backlight being switched on and off while the screen remained black. Note: installing xserver-xorg-lts-precise (and keeping the backported kernel) solves the issue ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: xserver-xorg-core-lts-quantal 2:1.13.0-0ubuntu6.1~precise2 ProcVersionSignature: Ubuntu 3.5.0-22.34~precise1-generic 3.5.7.2 Uname: Linux 3.5.0-22-generic x86_64 ApportVersion: 2.0.1-0ubuntu17.1 Architecture: amd64 Date: Fri Jan 25 16:00:45 2013 InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130125) MarkForUpload: True ProcEnviron: TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: xorg-server-lts-quantal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1105171/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
