Faulty graphics behaviour when resuming from suspend with intel graphics drivers

[julien]

Waking from suspend, everything seems normal, except the graphical elements and text on my desktop are not drawn properly. Sometimes, moving the mouse over icons can cause them to be redrawn, sometimes not. It appears not to matter how I initiate the suspend (e.g. by closing laptop lid, or by calling pm-suspend explicitly) and it appears not to matter whether I am using an external display or the laptop's own screen. All other hardware appears to be working, and I can restart the laptop by clicking where the icons ought to be. The only symptom seems to be that the drawing does not happen correctly.

---
ApportVersion: 2.17.2-0ubuntu1.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: julienl 1792 F.... pulseaudio
 /dev/snd/controlC0: julienl 1792 F.... pulseaudio
DistroRelease: Ubuntu 15.04
HibernationDevice: RESUME=UUID=2233869d-5832-469c-a447-f4da17530958
InstallationDate: Installed on 2015-06-21 (91 days ago)
InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: Dell Inc. XPS 13 9343
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-25-generic root=UUID=d161d0e8-74e3-4914-abff-8cfa0af8df95 ro quiet splash video=SVIDEO-1:d vt.handoff=7
ProcVersionSignature: Ubuntu 3.19.0-25.26-generic 3.19.8-ckt2
RelatedPackageVersions:
 linux-restricted-modules-3.19.0-25-generic N/A
 linux-backports-modules-3.19.0-25-generic N/A
 linux-firmware 1.143.3
Tags: vivid
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
Uname: Linux 3.19.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo users vboxusers
_MarkForUpload: True
dmi.bios.date: 05/15/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0TM99H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA04:bd05/15/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

[penalvch (penalvch)]

julien, thank you for reporting this and helping make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1486036

[julien (jrmlhermitte)]

apport information

[julien (jrmlhermitte)]

apport information

[julien (jrmlhermitte)]

apport information

[julien (jrmlhermitte)]

apport information

[julien (jrmlhermitte)]

apport information

[julien (jrmlhermitte)]

apport information

[julien (jrmlhermitte)]

apport information

[julien (jrmlhermitte)]

apport information

[julien (jrmlhermitte)]

apport information

[julien (jrmlhermitte)]

apport information

[julien (jrmlhermitte)]

apport information

[julien (jrmlhermitte)]

apport information

[julien (jrmlhermitte)]

apport information

[julien (jrmlhermitte)]

apport information

[julien (jrmlhermitte)]

apport information

[julien (jrmlhermitte)]

ok i have done so. thanks!

[julien (jrmlhermitte)]

Hi Christopher,

     Thanks for the reply and the information on the BIOS update. I have
updated to the new BIOS (saved the EXE file to USB key and updated BIOS
from the BIOS), but it did not resolve the problem. Here is the result of:
$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
A05
07/14/2015

It seems that others with different machines are having an issue that
appears to be similar to mine. Perhaps this is related to the driver? I
strongly suspect that upon resume it is playing with the resolution and
changing to a funny unknown mode (from what I see in the Xorg logs). The
issue may be more exaggerated for me compared to others because I am using
a different window display manager (FVWM).

If you hear of any other updates on this issue, please let me know, thanks!

julien

On Sun, Sep 20, 2015 at 11:53 AM, Christopher M. Penalver <
<email address hidden>> wrote:

> julien, as per http://www.dell.com/support/home/us/en/19/product-
> support/product/xps-13-9343-laptop/drivers an update to your computer's
> buggy and outdated BIOS is available (A05). If you update to this
> following https://help.ubuntu.com/community/BIOSUpdate does it change
> anything?
>
> If it doesn't, could you please both specify what happened, and provide
> the output of the following terminal command:
> sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
>
> For more on BIOS updates and linux, please see
> https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette
> .
>
> Please note your current BIOS is already in the Bug Description, so
> posting this on the old BIOS would not be helpful. As well, you don't
> have to create a new bug report.
>
> Once the BIOS is updated, and the information above is provided, then
> please mark this report Status Confirmed.
>
> Thank you for your understanding.
>
> ** Tags added: bios-outdated-a05
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1486036
>
> Title:
> Faulty graphics behaviour when resuming from suspend with intel
> graphics drivers
>
> Status in linux package in Ubuntu:
> Incomplete
>
> Bug description:
> I will copy and paste an excerpt from the link below. Is this the
> right place to post the bug?
>
> Waking from suspend, everything seems normal, except the graphical
> elements and text on my desktop are not drawn properly. Sometimes,
> moving the mouse over icons can cause them to be redrawn, sometimes
> not. It appears not to matter how I initiate the suspend (e.g. by
> closing laptop lid, or by calling pm-suspend explicitly) and it
> appears not to matter whether I am using an external display or the
> laptop's own screen.
>
> All other hardware appears to be working, and I can restart the laptop
> by clicking where the icons ought to be. The only symptom seems to be
> that the drawing does not happen correctly.
>
> I'm not sure what additional information I should provide to help
> diagnose the problem, so please advise me.
>
> Also, if this is more likely to be a xfce issue, then please change
> the package on the bug report.
...

[julien (jrmlhermitte)]

Here is some more insight, output from my /var/log/Xorg.0.log. When I close and re-open my laptop lid, I get the following (I tried it twice in this case):

[ 1594.192] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 1806.732] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 1806.736] (II) intel(0): switch to mode 1920x1080@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 1806.797] (--) synaptics: DLL0665:01 06CB:76AD UNKNOWN: touchpad found
[ 1809.696] (II) AIGLX: Suspending AIGLX clients for VT switch
[ 1812.650] (II) AIGLX: Resuming AIGLX clients after VT switch
[ 1812.650] (II) intel(0): switch to mode 1920x1080@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none
[ 1812.717] (--) synaptics: DLL0665:01 06CB:76AD UNKNOWN: touchpad found
[ 1821.640] (II) AIGLX: Suspending AIGLX clients for VT switch

Note the line "[ 1806.736] (II) intel(0): switch to mode 1920x1080@60.0 on eDP1 using pipe 0, position (0, 0), rotation normal, reflection none", it seems to be playing around with the resolution.

[penalvch (penalvch)]

julien, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, Y, and Z are numbers corresponding to the kernel version.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

[julien (jrmlhermitte)]

thanks. Is there a simple way to find out which modules I have installed are out of tree? This is the only step that might slow me down. I'll try to figure it out now but if I cannot it might have to wait a few days.

thanks for the support!

[julien (jrmlhermitte)]

Got it working, I have virtualbox but I did not need to uninstall the module to have the new kernel working.
The issue is FIXED!!! This is a miracle!!!!

here is my uname -r:
4.3.0-040300rc2-generic

I could try to do a binary search to pinpoint which kernel fixed this, would this be useful?

thank you! I will report this on the second bug report page, reporting a similar problem:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1452318

:-)

[Sebastian Gebhard (sege)]

I am also affected by this bug.

And for me also kernel version 4.3.0-040300rc2-generic fixes it.

[penalvch (penalvch)]

Gregor Kastner, please do not mark this a duplicate of another report, or vice versa.

[penalvch (penalvch)]

julien, the next step is to fully reverse commit bisect from kernel 3.19 to 4.3-rc2 in order to identify the last bad commit, followed immediately by the first good one. Once this commit has been identified, then it may be reviewed as a candidate for backporting into your release. Could you please do this following https://wiki.ubuntu.com/Kernel/KernelBisection#How_do_I_reverse_bisect_the_upstream_kernel.3F ?

Please note, finding adjacent kernel versions is not fully commit bisecting.

Thank you for your understanding.

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

[julien (jrmlhermitte)]

Christopher,
    Thanks, I have begun the bisection on the kernel version level. I have one question about it.
One of the versions I tried did not work at all (graphics didn't display). Should I label and keep moving on from there or try adjacent versions to this one until I find one where the graphics displays again?

Here is the result so far, I will now go from the precompiled kernels to the source level (might take me some time, I'll try one tonight do the rest another time):
4.3.0-040300rc2-generic good
    v4.1-rc2-vivid good
            v4.0.2-wily good
                v4.0-rc5-vivid good
                    v4.1-rc2-vivid good
                        v4.0-rc1-vivid inconclusive (no graphics show up)
        v3.19.8-vivid bad
3.19.0-25-generic bad

Note that v4.1-rc2-vivid good, v4.0-rc1-vivid and v3.19.8-vivid bad are all adjacent to one another. Will now bisect between v4.1-rc2-vivid good and v4.0-rc1-vivid.

[Timo Aaltonen (tjaalton)]

just try latest vivid distro kernel from proposed, which switches Broadwell to use i915_bpo module (backported from 4.2)

you're probably seeing a GPU hang which is known to happen with 3.19 and one of the reasons for the switch, dmesg should confirm that.

[Gregor Kastner (gregor-kastner)]

[cross-posted from https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1452318]

Awesome, latest kernel from vivid-proposed (3.19.0-30-generic) fixes the issue for me.

Many thanks!

[Bob McChesney (bmcchesney)]

Looks good (for me anyway).

After adding vivid-proposed in Software & Updates, and running:
sudo aptitude install linux-headers-3.19.0-30-generic linux-image-3.19.0-30-generic linux-image-extra-3.19.0-30-generic linux-signed-image-3.19.0-30-generic

I found that my main issue [https://imgur.com/Ey9b0hD] is gone. (I was also having other more rare to reproduce issues but I won't conflate them here; let's see if the original reporter's issue is fixed as I can open a new bug for any outstanding issues.)

For good measure I also installed 3.19.0-29-generic to test and that too also resolved it.

Just out of curiosity, looking at the changelog - http://www.ubuntuupdates.org/package/canonical_kernel_team/vivid/main/base/linux-image-3.19.0-30-generic - was it 1483320 that resolved it? I'm glad that this has been done already as I was starting a commit bisect between Linus' v3.19 and v4.0-rc1 (the latter of which I found to be good) but it was already proving to be painful. This saved me a lot of wasted time.

How long does it generally take for a proposed package to pass testing and reach updates?

Thanks!

[julien (jrmlhermitte)]

will try tonight :-)
thanks for adding it to with http://bugs.launchpad.net/bugs/1483320 and I'll comment on bug#1452318
I definitely think it is prob related (will confirm tonight to add to the statistic :-) )

looks like the difficulty in this bug was more figuring out how to describe it than find it :-D