[Asus M70SR] Slow system after resume from suspend

[Roman Dinga]

Hello,

For quite some time I've been experiencing problems with Ubuntu after resume from suspend. I have an Asus M70SR notebook with ATI Radeon Mobility HD3470 and using the open-source driver for it (from Quantal official repository). Currently I have Ubuntu 12.10 installed, but the same was happening before with 12.04. It doesn't matter if I use Unity, Gnome-Shell or Gnome Classic - the slow down is always there. My /etc/X11/xorg-conf looks like this:

Section "Device"
 Identifier "ATI Radeon 3470HD"
 Driver "ati"
 Option "AccelMethod" "EXA"
 Option "AccelDFS" "true"
 Option "EnablePageFlip" "true"
 Option "SwapbuffersWait" "off"
 Option "ColorTiling" "on"
 Option "ColorTiling2D" "on"
EndSection

To give you some picture about it:

Glxgears BEFORE suspend:
ATTENTION: default value of option vblank_mode overridden by environment.
ATTENTION: default value of option vblank_mode overridden by environment.
ATTENTION: option value of option vblank_mode ignored.
4007 frames in 5.0 seconds = 801.315 FPS
3867 frames in 5.0 seconds = 773.359 FPS
3918 frames in 5.0 seconds = 782.475 FPS
3879 frames in 5.0 seconds = 774.902 FPS
3859 frames in 5.0 seconds = 771.025 FPS

Glxgears AFTER resume from suspend:
ATTENTION: default value of option vblank_mode overridden by environment.
ATTENTION: default value of option vblank_mode overridden by environment.
ATTENTION: option value of option vblank_mode ignored.
519 frames in 5.0 seconds = 103.466 FPS
455 frames in 5.0 seconds = 90.993 FPS
449 frames in 5.0 seconds = 89.738 FPS
553 frames in 5.0 seconds = 110.366 FPS
530 frames in 5.0 seconds = 105.835 FPS

As you can see the performance after resume from suspend is about 1/8th of the normal. The workaround is to kill the X server (Ctrl-Alt-Backspace) and login again, the problem is gone then. However, it's quite annoying to have to close all open apps and then reopen them again.

As you can see, I use vblank_mode=0 option and in Compiz the Vsync is turned off. The measuring was done from Gnome Classic session, but I can experience the same slowdown in Unity and in Gnome Shell as well.

Best regards,
Roman Dinga
---
ApportVersion: 2.6.1-0ubuntu10
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: diniadeedee 5475 F.... pulseaudio
 /dev/snd/controlC0: diniadeedee 5475 F.... pulseaudio
 /dev/snd/pcmC0D0p: diniadeedee 5475 F...m pulseaudio
DistroRelease: Ubuntu 12.10
HibernationDevice: RESUME=UUID=/etc/initramfs-tools/conf.d/resume
InstallationDate: Installed on 2012-04-29 (268 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 (20120423)
MachineType: ASUSTeK Computer Inc. M70SR
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.7.0-7-generic root=UUID=f66e8c9c-0fd3-46e3-8484-5306b2f24bcb ro quiet splash radeon.pcie_gen2=1 vt.handoff=7
ProcVersionSignature: Ubuntu 3.7.0-7.15-generic 3.7.0
RelatedPackageVersions:
 linux-restricted-modules-3.7.0-7-generic N/A
 linux-backports-modules-3.7.0-7-generic N/A
 linux-firmware 1.98
Tags: quantal
Uname: Linux 3.7.0-7-generic i686
UnreportableReason: This is not an official Ubuntu package. Please remove any third party package and try again.
UpgradeStatus: Upgraded to quantal on 2012-11-05 (78 days ago)
UserGroups: adm audio bluetooth cdrom dip kvm libvirtd lpadmin netdev plugdev sambashare sudo vboxusers video
dmi.bios.date: 03/21/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: M70SR
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr204:bd03/21/2008:svnASUSTeKComputerInc.:pnM70SR:pvr1.0:rvnASUSTeKComputerInc.:rnM70SR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.name: M70SR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1102318/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Fabio Marconi (fabiomarconi)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This bug did not have a package associated with it, which is important for ensuring that it gets looked at by the proper developers. You can learn more about finding the right package at https://wiki.ubuntu.com/Bugs/FindRightPackage . I have classified this bug as a bug in linux.

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://help.ubuntu.com/community/ReportingBugs.

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1102318

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

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

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.8 kernel[0] (Not a kernel in the daily directory) and install both the linux-image and linux-image-extra .deb packages.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

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

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.8-rc4-raring/

[Roman Dinga (roman-dinga)]

apport information

[Roman Dinga (roman-dinga)]

apport information

[Roman Dinga (roman-dinga)]

apport information

[Roman Dinga (roman-dinga)]

apport information

[Roman Dinga (roman-dinga)]

apport information

[Roman Dinga (roman-dinga)]

apport information

[Roman Dinga (roman-dinga)]

apport information

[Roman Dinga (roman-dinga)]

apport information

[Roman Dinga (roman-dinga)]

apport information

[Roman Dinga (roman-dinga)]

apport information

[Roman Dinga (roman-dinga)]

apport information

[Roman Dinga (roman-dinga)]

apport information

[Roman Dinga (roman-dinga)]

apport information

[Roman Dinga (roman-dinga)]

apport information

[Roman Dinga (roman-dinga)]

apport information

[Roman Dinga (roman-dinga)]

apport information

[Roman Dinga (roman-dinga)]

Hello,

I've submitted the apport-collect info. Please notice, that the kernel in it is 3.7.0.7, because I've also tested this with xorg-edgers ppa (with their radeon driver). The situation is a little bit better:

1269 frames in 5.0 seconds = 253.598 FPS
1207 frames in 5.0 seconds = 241.348 FPS
1333 frames in 5.0 seconds = 266.208 FPS
1164 frames in 5.0 seconds = 232.662 FPS

So the FPS is double after resume from suspend than with using normal quantal kernel 3.5.0-22 and regular radeon driver from quantal repository (which were used for my original first testing). I've installed the upstream kernel 3.8 as suggested and will post the result of testing with it as well.

Best regards,
Roman

[Roman Dinga (roman-dinga)]

Hello,

So to finalize the test, I've completely removed the xorg-edgers ppa, then installed the upstream kernel 3.8 and repeated the test:

BEFORE SUSPEND:
2275 frames in 5.0 seconds = 454.603 FPS
1891 frames in 5.0 seconds = 376.568 FPS
1979 frames in 5.0 seconds = 395.401 FPS
1946 frames in 5.0 seconds = 388.845 FPS

AFTER RESUME FROM SUSPEND:
344 frames in 5.0 seconds = 68.662 FPS
312 frames in 5.0 seconds = 62.122 FPS
321 frames in 5.0 seconds = 64.103 FPS
347 frames in 5.0 seconds = 69.071 FPS

So with this upstream kernel, the slowdown is even more visible than with 3.5. It seems that the best situation is with xorg-edgers ppa installed.

BUT I've also noticed one other thing. When I installed the upstream kernel 3.8 for the first time, I forgot to install the extras, so I was thrown into llvmpipe, because radeon driver failed to load. I did a test with that one too and there was NO slowdown nor any change when measuring before suspend and after resume. So with LLVM, all works as it should (though it is choppy, but the framerate is exactly the same before and after suspend). My guess is that the bug is somewhere in the radeon driver (the fact that using xorg-edgers helps it a little bit, supports this).

If you need any additional tests, please let me know.
Best regards,
Roman

[Tuna Büyükçağlar (tunabuyukcaglar)]

Same issue on Lenovo S10-3 netbook, unstable scroll, click action, halts keyboard..

[Bruce Bigby (bbigby)]

For what it's worth, I've had this problem forever with my System 76 panp5 laptop, regardless of the distribution. After being on Ubuntu 10.04 for several years, I recently switch to Fedora 18. On a normal boot, my system is snappy and fine. However, if I suspend and resume, the system is noticably sluggish. When I click on objects, I get a response in about 1/2 to 1 second. Whereas before suspending, the response would be immediate or almost immediate. I'd like to resume to save energy but I just can't tolerate the sluggishness so I just don't. I tried again in Fedora 18 just to see whether the problem went away. It didn't and for me, it hasn't for at least 4 years. :-(

[Roman Dinga (roman-dinga)]

Just a comment regarding this bug: I've moved to Debian 7.0 Wheezy (final version) and this does not happen in it - the responsivness of the system is the same before and after suspend and glxgears gives the same FPS before and after. Just thought I could let you know...

[penalvch (penalvch)]

Roman Dinga, could you please confirm this issue exists with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ . If the issue remains, 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 following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. 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.11-rc4

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

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

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.

[Roman Dinga (roman-dinga)]

Hello,

I'm sorry, but I've switched to Linux Mint Debian Edition some time ago on all my PCs, so I'm not able to test this anymore. With LMDE kernel 3.2.0-4-686-pae #1 SMP Debian 3.2.32-1 i686 GNU/Linux the problem is not present anymore as far as I can see, but no idea if that will help you.

Best regards,
Roman Dinga

[Launchpad Janitor (janitor)]

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

[vellamike (vellamike)]

I have exactly the same problem with Ubuntu 13.10 on a Dell latitude e7240 with Cinnamon and 3.11.0-15-generic.

[Roman Dinga (roman-dinga)]

Hello, just to make additional comment on this: later on I switched to pure Debian and I have not experienced this problem neither on stable Wheezy nor on unstable Sid. Best regards, Roman Dinga

[penalvch (penalvch)]

vellamike, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[Mobman02 (mobman02)]

I have the same issue on Linux Mint and a DELL Latitude E6520.

Ubuntu 13.10, running on LinuxMint 16.

[Mobman02 (mobman02)]

Just to let you know, I have discovered that this bug is coming from the CPU Governor,
on "ondemand", it was never giving me the full power of my CPU's, only 800Mhz of 2.8Ghz.

So I installed https://launchpad.net/indicator-cpufreq and now I can: see why the fuck everything is slow and set the CPU frequency I want.

This does not fix the issue (as the Governor does not get smarter) but I do not have to reboot the system anymore. Hope it helps.

[penalvch (penalvch)]

Mobman02, thank you for your comment. So your hardware and problem may be tracked, please feel free to file a new report with Ubuntu (not linux mint) by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs