[X1100] Flickering after resume from RAM

[Tommy Trussell]

Steps to reproduce :
- choose suspend
- resume from ram
=> the screen will flicker while CPU activity is not high

WORKAROUND: Launch an infinite loop that consume CPU :
$ while true; do echo >/dev/null; done

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic i686
.tmp.unity.support.test.0:

ApportVersion: 2.19.1-0ubuntu3
Architecture: i386
CasperVersion: 1.365
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Mar 2 20:00:24 2016
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS482M [Mobility Radeon Xpress 200] [1002:5975] (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:009f]
LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Release i386 (20151021)
Lsusb:
 Bus 001 Device 002: ID 0951:160b Kingston Technology
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Acer Aspire 5100
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: noprompt cdrom-detect/try-usb=true file=/cdrom/preseed/username.seed boot=casper initrd=/casper/initrd.lz quiet splash --- BOOT_IMAGE=/casper/vmlinuz
SourcePackage: xorg
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/22/2008
dmi.bios.vendor: Acer
dmi.bios.version: V3.13
dmi.board.name: Navarro
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAcer:bvrV3.13:bd08/22/2008:svnAcer:pnAspire5100:pvrV3.13:rvnAcer:rnNavarro:rvrN/A:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5100
dmi.product.version: V3.13
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.2+15.10.20151015-0ubuntu1
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Wed Mar 2 13:50:49 2016
xserver.configfile: default
xserver.errors:

xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.17.2-1ubuntu9
xserver.video_driver: radeon

[penalvch (penalvch)]

Tommy Trussell, thank you for reporting this and helping make Ubuntu better.

To see if this is already resolved, could you please test http://cdimage.ubuntu.com/daily-live/current/ (x64, not 32-bit) and advise to the results?

[Tommy Trussell (tommy-trussell)]

I just booted from today's (02 March 2016) xenial-desktop-amd64.iso. I had trouble getting the machine to suspend, but once it did and resumed from suspend, it showed the same flickering screen behavior.

If you need an apport bug collection or any other data from this image, it should work. Let me know

[penalvch (penalvch)]

Tommy Trussell, could you please provide the missing information from https://wiki.ubuntu.com/DebuggingKernelSuspend ?

[Tommy Trussell (tommy-trussell)]

I believe I can do this, however it will take quite a bit more preparation and effort (because of the radeon Xpress 1100 bug I cannot use the display on this laptop after any successful resume from suspend) I am also testing from a live image with no persistent storage, so I will need to do something different, so I will probably back up the laptop's data, wipe the Trusty HWE kernel installation on it, install Xenial, install openssh-server so I can ssh into it, etc. etc..

Before I get started, however I want to confirm my understanding of the instructions linked above --

1) I need to be using an upstream kernel, not the daily xenial kernel in the daily .iso

2) I need to log SIX resume trace cycles (steps 5, 6, 7, 8, 9 and 10) and attach each to the bug report? Or do I need to log EIGHTEEN resume trace cycles (a set of six resume trace cycles for each of the three methods of invoking suspend)?

3) The "resume trace" that gets attached for each of the cycles is the dmesg > dmesg.txt file. Or is there a different trace file you need?

[Tommy Trussell (tommy-trussell)]

Installed xenial from a recent daily image
consulted https://wiki.ubuntu.com/Kernel/MainlineBuilds
    and selected kernel 4.4.3

Installed kernel using these 3 packages
linux-headers-4.4.3-040403_4.4.3-040403.201602251634_all.deb
linux-headers-4.4.3-040403-generic_4.4.3-040403.201602251634_amd64.deb
linux-image-4.4.3-040403-generic_4.4.3-040403.201602251634_amd64.deb

$ uname -a
Linux AcerA5100 4.4.3-040403-generic #201602251634 SMP Thu Feb 25 21:36:25 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

NOTE I have tried suspending the laptop in all the ways I know to suspend it: The Suspend command in the "gear" menu, pressing Power and selecting Suspend from the graphical button, closing the lid, and also by issuing the pm-suspend command.

I usually resume from suspend by pressing the space bar or other random keys on the keyboard, but I have also tried resuming by pressing the power button. (This laptop has a visible switch to suspend when the lid closes, but it does not resume when the lid opens.)

As always, the laptop-s display is unusably scrambled after resume EXCEPT while the processor is near 100%.

The next few comments will include information collected from the process described at https://wiki.ubuntu.com/DebuggingKernelSuspend

[Tommy Trussell (tommy-trussell)]

step 4 wakeup file

[Tommy Trussell (tommy-trussell)]

step 5

[Tommy Trussell (tommy-trussell)]

oops sorry I need to redo step 5

[Tommy Trussell (tommy-trussell)]

second attempt at step 5

the laptop never actually suspended after issuing

sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

so I chose Suspend from the gear menu and the screen blanked briefly and still did not suspend

[Tommy Trussell (tommy-trussell)]

this time I tried issuing the command then choosing Suspend from the menu then pressing power and choosing suspend from the graphical suspend button and then I tried holding down the lid switch for many seconds

the laptop will not go into suspend.

[Tommy Trussell (tommy-trussell)]

echo devices (step 6)

the laptop is still not going into suspend

[Tommy Trussell (tommy-trussell)]

echo platform (step 7)

the laptop still did not suspend

[Tommy Trussell (tommy-trussell)]

processors (stop 8)

the laptop still did not actually suspend (the screen blanks and restores but suspend never happens)

[Tommy Trussell (tommy-trussell)]

core (step 9)

this time, while the laptop never seemed to go into suspend, the display is scrambled (I am entering this via vnc). The scramble is in a different pattern (more consistent than the usual post-suspend scramble)

[Tommy Trussell (tommy-trussell)]

echo none (step 10)

This time entering the sudo sh -c "sync && echo 1 > /sys/power/pm_trace && pm-suspend"

 command DID actually suspend the laptop, and I resumed the laptop by pressing a key on the keyboard.

Now the screen is scrambled as it "normally" does after a suspend.

[Tommy Trussell (tommy-trussell)]

stats (step 11)

[Tommy Trussell (tommy-trussell)]

/var/log/Xorg.0.log (step 12)

[Tommy Trussell (tommy-trussell)]

/var/log/Xorg.0.log.old

[Tommy Trussell (tommy-trussell)]

done for now

[penalvch (penalvch)]

Tommy Trussell, all of those tests aren't what was needed I'm afraid.

As per the article, this would want to be done in the latest mainline kernel (not Ubuntu kernel), following the hyperlinked URL in the article.

[Tommy Trussell (tommy-trussell)]

Yes I followed that link, which identified the mainline kernel 4.4.3 as the one for xenial. Please tell me which kernel I should have installed.

[Tommy Trussell (tommy-trussell)]

I see now; I should use the http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D link and I should ignore the http://people.canonical.com/~kernel/info/kernel-version-map.html

SO I just got back and I will download http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-rc6-wily/

[Tommy Trussell (tommy-trussell)]

merle@AcerA5100:~$ uname -a
Linux AcerA5100 4.5.0-040500rc6-generic #201602281230 SMP Sun Feb 28 17:33:02 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

Step 4 wakeup

[Tommy Trussell (tommy-trussell)]

step 5
freezer

laptop did not suspend using the shell command so I also chose the Suspend command from the Gear menu, which triggered a partial suspend and self-resume (screen went black but power light did not go out and fan did not stop and screen did not get scrambled)

[Tommy Trussell (tommy-trussell)]

step 6
devices
just like before, shell command did not fully suspend, and neither did choosing Suspend from Gear menu, but I did both.

[Tommy Trussell (tommy-trussell)]

step 7
platform

just like before, no real suspend, no screen issues. Issued shell command and when it finished (screen lit up again) and chose Suspend from gear menu with same result

[Tommy Trussell (tommy-trussell)]

step 8
processors

just like before, no real suspend, no screen issues. Issued shell command and when it finished chose Suspend from gear menu

[Tommy Trussell (tommy-trussell)]

step 9
core

same as before ; no real suspend. shell command then Suspend from gear menu

launchpad is reporting a timeout error so I"m having trouble attaching dmesg

[Tommy Trussell (tommy-trussell)]

step 10
none

laptop did go into suspend using shell command and I resumed by pressing keys on the keyboard.

[Tommy Trussell (tommy-trussell)]

step 11
suspend stats

[Tommy Trussell (tommy-trussell)]

Xorg.0.log

[Tommy Trussell (tommy-trussell)]

Xorg.0.log.old

[Tommy Trussell (tommy-trussell)]

done for now

[penalvch (penalvch)]

Tommy Trussell, to clarify the results of comments #25-#35, was the issue reproducible?

[Tommy Trussell (tommy-trussell)]

of all of those suspend attempts, the only one that triggered the scrambled flickering display was the one where it actually suspended: comment #31.

[Tommy Trussell (tommy-trussell)]

with the comments on the "wrong" kernel I had a different scramble pattern in comment #16 but then just like in #31, comment #17 actually suspended the laptop with the same pattern of flicker it "normally" does after resuming from a suspend.

[penalvch (penalvch)]

Tommy Trussell, the issue you are reporting is an upstream one. Could you please report this problem following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel to the appropriate mailing list (TO Rafael J. Wysocki, and Len Brown CC linux-acpi)?

Please provide a direct URL to your post to the mailing list when it becomes available so that it may be tracked.

Thank you for your understanding.