AMD Radeon HD 8570A/8570M [1002:6663] Unable to resume from suspend with proprietary driver

[Po-Hsu Lin]

CID: 201309-14197 HP 242 G2 Notebook PC

This is an I+A hybrid system:
00:02.0 VGA compatible controller [0300]: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06)
01:00.0 Display controller [0380]: Advanced Micro Devices, Inc. [AMD/ATI] Sun PRO [Radeon HD 8570A/8570M] [1002:6663] (rev ff)

With fglrx installed, it can't resume from suspend just like bug 1308954

Steps:
1. Install 14.04.1 + update (3.13.0-45) + fglrx or fglrx-update, reboot.
2. Suspend it.
3. Wake it up

Expected result:
* Everything should works fine after S3.

Actual result:
* System freeze

Note:
With driver version 14.501 downloaded from AMD's website [1] installed.
It will boot into low-graphic mode.
Package that I installed:
fglrx_14.501-0ubuntu1_amd64_UB_14.01.deb
fglrx-amdcccle_14.501-0ubuntu1_amd64_UB_14.01.deb
fglrx-core_14.501-0ubuntu1_amd64_UB_14.01.deb
fglrx-dev_14.501-0ubuntu1_amd64_UB_14.01.deb

[1] http://support.amd.com/en-us/download/desktop?os=Ubuntu%20x86%2064

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-45-generic 3.13.0-45.74
ProcVersionSignature: Ubuntu 3.13.0-45.74-generic 3.13.11-ckt13
Uname: Linux 3.13.0-45-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: ubuntu 1632 F.... pulseaudio
 /dev/snd/controlC0: ubuntu 1632 F.... pulseaudio
CRDA:
 country TW:
  (2402 - 2472 @ 40), (3, 27)
  (5270 - 5330 @ 40), (3, 17), DFS
  (5735 - 5815 @ 40), (3, 30)
CurrentDesktop: Unity
Date: Fri Feb 6 00:55:53 2015
HibernationDevice: RESUME=UUID=e4f99f18-f641-42cf-8870-1a6a8a8c741a
InstallationDate: Installed on 2015-02-05 (0 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Hewlett-Packard HP 242 G2 Notebook PC
ProcFB:
 0 inteldrmfb
 1 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-45-generic root=UUID=a10c7f9d-8d0a-472e-a426-20b14015b1b2 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-45-generic N/A
 linux-backports-modules-3.13.0-45-generic N/A
 linux-firmware 1.127.11
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/08/2013
dmi.bios.vendor: Insyde
dmi.bios.version: B.0B
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 217B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 34.0E
dmi.chassis.asset.tag: 738DIP105Y
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnInsyde:bvrB.0B:bd10/08/2013:svnHewlett-Packard:pnHP242G2NotebookPC:pvr099C200000000000000620100:rvnHewlett-Packard:rn217B:rvrKBCVersion34.0E:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 242 G2 Notebook PC
dmi.product.version: 099C200000000000000620100
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[penalvch (penalvch)]

Po-Hsu Lin / Anthony Wong, as per http://h20564.www2.hp.com/hpsc/swd/public/readIndex?sp4ts.oid=5405183&swLangOid=8&swEnvOid=4158 an update to your computer's buggy and outdated BIOS is available (F.12 A). 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

Once the BIOS is updated, and the information above is provided, then please mark this report Status Confirmed.

Thank you for your understanding.

[Alberto Milone (albertomilone)]

also, please attach your /var/log/Xorg.0.log or, if you can't even ssh into the machine, please reboot and attach /var/log/Xorg.0.log.old

[Po-Hsu Lin (cypressyew)]

Hi Alberto,
It seems that it's not totally frozen. I could still ssh into it.

[Po-Hsu Lin (cypressyew)]

Despite there is no EE message in Xorg.0.log, possible error message could be found in dmesg output after resumed from S3 for a while:
[ 355.356338] <6>[fglrx] ASIC hang happened
[ 355.356342] CPU: 2 PID: 1149 Comm: Xorg Tainted: P OX 3.13.0-45-generic #74-Ubuntu
[ 355.356343] Hardware name: Hewlett-Packard HP 242 G2 Notebook PC/217B, BIOS B.0B 10/08/2013
[ 355.356344] 000000010000359d ffff88024eefdbd0 ffffffff81720eb6 0000000000000000
[ 355.356346] ffff88024eefdbe0 ffffffffa00ea88e 000000010000359c ffffffffa00f993c
[ 355.356347] 0000000000000000 ffffffffa01f305e ffff88024eefdc50 ffffffffa01f2fc9
[ 355.356349] Call Trace:
[ 355.356353] [<ffffffff81720eb6>] dump_stack+0x45/0x56
[ 355.356397] [<ffffffffa00ea88e>] KCL_DEBUG_OsDump+0xe/0x10 [fglrx]
[ 355.356431] [<ffffffffa00f993c>] firegl_hardwareHangRecovery+0x1c/0x30 [fglrx]
[ 355.356495] [<ffffffffa01f305e>] ? _ZN4Asic9WaitUntil15ResetASICIfHungEv+0x1e/0x30 [fglrx]
[ 355.356556] [<ffffffffa01f2fc9>] ? _ZN4Asic9WaitUntil15WaitForCompleteEv+0xb9/0x130 [fglrx]
[ 355.356614] [<ffffffffa01ef915>] ? _ZN4Asic19PM4ElapsedTimeStampEj14_LARGE_INTEGER12_QS_CP_RING_+0xd5/0x160 [fglrx]
[ 355.356644] [<ffffffffa01049f4>] ? MCIL_KernelMutex+0x134/0x320 [fglrx]
[ 355.356702] [<ffffffffa01f7859>] ? _ZN15ExecutableUnits35flush_all_and_invalidate_HDP_cachesE12_QS_CP_RING_+0xc9/0xf0 [fglrx]
[ 355.356759] [<ffffffffa01f74dc>] ? _ZN15ExecutableUnits14PM4idleGfxRingEv+0x1c/0x30 [fglrx]
[ 355.356810] [<ffffffffa01cbaef>] ? _ZN10QS_PRIVATE27synchronizeGraphicOperationEv+0x4f/0x90 [fglrx]
[ 355.356849] [<ffffffffa017c103>] ? _ZN9CMMlegacy29QSSynchronizeGraphicOperationEv+0x23/0x60 [fglrx]
[ 355.356886] [<ffffffffa017aa9d>] ? QSSynchronizeGraphicOperation+0xd/0x20 [fglrx]
[ 355.356914] [<ffffffffa0123728>] ? firegl_cmmqs_WaitForIdle+0x38/0x90 [fglrx]
[ 355.356939] [<ffffffffa00f7829>] ? firegl_lock_device+0x329/0x520 [fglrx]
[ 355.356966] [<ffffffffa00f7ada>] ? firegl_lock+0xba/0x210 [fglrx]
[ 355.356968] [<ffffffff810710e9>] ? ns_capable+0x29/0x50
[ 355.356995] [<ffffffffa00f7a20>] ? firegl_lock_device+0x520/0x520 [fglrx]
[ 355.357020] [<ffffffffa00f40cd>] ? firegl_ioctl+0x1ed/0x250 [fglrx]
[ 355.357043] [<ffffffffa00e21de>] ? ip_firegl_unlocked_ioctl+0xe/0x20 [fglrx]
[ 355.357046] [<ffffffff811d0e30>] ? do_vfs_ioctl+0x2e0/0x4c0
[ 355.357047] [<ffffffff811d1091>] ? SyS_ioctl+0x81/0xa0
[ 355.357050] [<ffffffff811becc9>] ? SyS_writev+0x49/0xc0
[ 355.357052] [<ffffffff8173196d>] ? system_call_fastpath+0x1a/0x1f

For more detailed information, please refer to the attached dmesg output file.

[Alberto Milone (albertomilone)]

That really looks like a problem in the fglrx binary. It's probably worth trying the new unified driver, soon to be available in trusty-proposed.

[Po-Hsu Lin (cypressyew)]

Trusty EOL.