[Sony VPCSE190X] Broken suspend for i915 with newer kernels using non-default kernel parameters, firmware, and kernel

[Aurelijus Rinkevicius]

I am running a Kubuntu 13.04 on a Sandybridge (Intel HD3000) + unused AMD HD 6630M. Suspend seems to be broken with newer kernels. The last working kernel seems to be ubuntu flavor of 3.8.0-23-generic. The newer kernels 3.8.0-24-generic+ and tested generic 3.9.4, 3.10rc4 seem to be broken.

System does not come back up from a sleep. Gets a blank screen and a fan at max.

When I remove all non-default kernel parameters, boot into a Ubuntu provided kernel, and use the default firmware provided by Ubuntu, suspend works.

---
ApportVersion: 2.9.2-0ubuntu8.4
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: odysei 2423 F.... pulseaudio
 /dev/snd/pcmC0D0p: odysei 2423 F...m pulseaudio
DistroRelease: Ubuntu 13.04
HibernationDevice: RESUME=UUID=8a51a66b-afc7-4aba-af08-adc76ae7bd7a
InstallationDate: Installed on 2012-04-26 (495 days ago)
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
MachineType: Sony Corporation VPCSE190X
MarkForUpload: True
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-25-generic root=UUID=c62018f2-c2bb-4c89-9cba-41700f4452e0 ro pcie_aspm=force i915.i915_enable_rc6=1 radeon.dpm=1 quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
RelatedPackageVersions:
 linux-restricted-modules-3.8.0-25-generic N/A
 linux-backports-modules-3.8.0-25-generic N/A
 linux-firmware 1.106
Tags: raring
Uname: Linux 3.8.0-25-generic x86_64
UpgradeStatus: Upgraded to raring on 2013-04-27 (130 days ago)
UserGroups: adm cdrom debian-tor dip lp lpadmin plugdev sambashare sudo
dmi.bios.date: 06/15/2012
dmi.bios.vendor: INSYDE
dmi.bios.version: R2087H4
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnINSYDE:bvrR2087H4:bd06/15/2012:svnSonyCorporation:pnVPCSE190X:pvrC609YTLP:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VPCSE190X
dmi.product.version: C609YTLP
dmi.sys.vendor: Sony Corporation

[Aurelijus Rinkevicius (odysei)]

System hangs with:

Jun 8 15:20:23 odysei-laptop kernel: [ 187.461782] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting
Jun 8 15:20:23 odysei-laptop kernel: [ 187.461789] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing CEDE (len 62, WS 0, PS 0) @ 0xCEFA

so it is similar to a bug:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1062077

[Aurelijus Rinkevicius (odysei)]

It seems that all 3.9.X are affected 3.9.0, 3.9.1, 3.9.2, 3.9.3, 3.9.4, and 3.9.5
New 3.10 rc5 as well.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[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.11 kernel[0].

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.11-rc1-saucy/

[Aurelijus Rinkevicius (odysei)]

Kernel 3.11rc1 seems to work!

I have put a PC to sleep several times and every time it came back to life. Could be that a severe radeon firmware update saved the day. Will update if it breaks again but I hope not.

[penalvch (penalvch)]

Aurelijus Rinkevicius, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1189142
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://wiki.ubuntu.com/ReportingBugs.

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

apport information

[Aurelijus Rinkevicius (odysei)]

I have also noticed the following things:
1) now it seems to be working again with 3.8.0-25-generic
2) problem is related to Radeon drivers/firmware crosstalk
3) 3.11rc and 3.11.0 series can be introduced with this bug if different radeon firmware is being used, which means the following:
a) I replace firmware in /lib/firmware/radeon with http://people.freedesktop.org/~agd5f/radeon_ucode/
b) install new kernel packages (3.11)
c) I end up with the same bug

Current firmware seems to be working with, at least, several previously broken kernels: 3.8.0-25-generic or 3.8.0-30-generic

Conclusion:
It seems like a particular configuration of firmware and kernel can cause this bug.

[penalvch (penalvch)]

Aurelijus Rinkevicius, if you remove the following non-default kernel parameters does this allow you to suspend in Raring:
pcie_aspm=force
i915.i915_enable_rc6=1
radeon.dpm=1

As well, could you please discuss why specifically you would be using each of them?

[Aurelijus Rinkevicius (odysei)]

Hi Chrisotpher,

I ran it with 3.11rc6 that was installed while "unstable" radeon firmware were in place (/lib/firmware/radeon) with all the parameters removed - same effect, i.e., suspend does not come back (usually it does after 5 mins or so, so there is a kernel loop going on)

radeon.dpm=1 is a kernel 3.11 power saving feature for radeons.
i915.i915_enable_rc6=1, should be enabled by default by now (I set it long time ago). https://wiki.ubuntu.com/Kernel/PowerManagement/PowerSavingTweaks
pcie_aspm=force - https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Power_Management_Guide/ASPM.html, since I generally use intel integrated graphics as switching still su*** in linux, I want to turn off unused radeon under the PCIe bridge.

Hope this helps.

[penalvch (penalvch)]

Aurelijus Rinkevicius, if you disable the discrete AMD graphics card in BIOS, and remove:
pcie_aspm=force
i915.i915_enable_rc6=1
radeon.dpm=1

would anything change when attempting suspend with http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.11-saucy/ ?

[Aurelijus Rinkevicius (odysei)]

Christopher, my bios does not allow disabling AMD graphis, the best I can do is disable PEG (I guess PCIexpress graphics), which probably did not do a thing as it is in the advanced menu.

Anyway, the removal of suggested options did not change anything. However, I have noticed the following:
Using an old and incomplete radeon firmware radeon goes crazy at the boot:
Sep 7 17:23:49 odysei-laptop kernel: [ 3.087970] [drm] radeon: 512M of GTT memory ready.
Sep 7 17:23:49 odysei-laptop kernel: [ 3.090118] radeon 0000:01:00.0: radeon_uvd: Can't load firmware "radeon/SUMO_uvd.bin"
Sep 7 17:23:49 odysei-laptop kernel: [ 3.090169] [drm] GART: num cpu pages 131072, num gpu pages 131072
Sep 7 17:23:49 odysei-laptop kernel: [ 3.090784] [drm] PCIE gen 2 link speeds already enabled
Sep 7 17:23:49 odysei-laptop kernel: [ 3.091978] [drm] Loading TURKS Microcode
Sep 7 17:23:49 odysei-laptop kernel: [ 3.094240] smc: error loading firmware "radeon/TURKS_smc.bin"
Sep 7 17:23:49 odysei-laptop kernel: [ 3.094298] ni_cp: Failed to load firmware "radeon/TURKS_smc.bin"
Sep 7 17:23:49 odysei-laptop kernel: [ 3.094372] [drm:evergreen_startup] *ERROR* Failed to load firmware!
Sep 7 17:23:49 odysei-laptop kernel: [ 3.094430] radeon 0000:01:00.0: disabling GPU acceleration

however, in this case my suspend seems to work. If I use a newer firmware that does not complain, suspend is broken.

[penalvch (penalvch)]

Aurelijus Rinkevicius, just to clarify, when you remove all the requested kernel parameters, boot into the Ubuntu kernel, and use the default firmware provided by Ubuntu, suspend works?

[Aurelijus Rinkevicius (odysei)]

That is correct. However, the firmware does not work properly then (log excerpt was pasted above).

Side note: I suspect that Ubuntu has shipped some kernel/firmware updates in the recent past as previously broken kernels came back to life from a suspend. At the time of original post they were broken.

[jerger (jerger)]

Found an workaround on ubuntu13.10:

##### vi /etc/pm/power.d/20_disable_ati
#!/bin/sh

# Action script ensure that unattended-upgrades is finished
# before a hibernate
#
# Copyright: Copyright (c) 2009 Michael Vogt
# License: GPL-2
#
echo OFF > /sys/kernel/debug/vgaswitcheroo/switch

##### vi /etc/pm/sleep.d/20_reenable_ati
#!/bin/sh

# Action script ensure that unattended-upgrades is finished
# before a hibernate
#
# Copyright: Copyright (c) 2009 Michael Vogt
# License: GPL-2
#
echo ON > /sys/kernel/debug/vgaswitcheroo/switch

[penalvch (penalvch)]

jerger, thank you for your comment. This bug is not about vgaswitcheroo, so your problem is not considered part of the scope of this report, or vice versa. If you have a bug in Ubuntu, please feel free to 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://help.ubuntu.com/community/ReportingBugs