Bug 917535

Summary:	Crash when resuming from ram due ATI HDMI audio device
Product:	[Fedora] Fedora	Reporter:	Paulo Fidalgo <paulo.fidalgo.pt>
Component:	kernel	Assignee:	Kernel Maintainer List <kernel-maint>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	19	CC:	gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, paulo.fidalgo.pt
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-11-12 11:54:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Paulo Fidalgo 2013-03-04 09:59:42 UTC

Description of problem:
After seeing this problem several times, I've tried to investigate more, and followed the instructions from:

https://www.kernel.org/doc/Documentation/power/s2ram.txt

I can suspend without problems, but when I press the power button to resume, the system crashes (I don't even have response from Caps Lock key led) and the system fan starts working at full speed.

After an hard-reset (4 secons on power button) in the dmesg I have this:

[    0.733522] MODSIGN: Loaded cert 'Fedora kernel signing key: 94721246cd81d89b40efcb473e45f41d28b8fc76'
[    0.733530] registered taskstats version 1
[    0.734358]   Magic number: 5:916:726
[    0.734368] block loop6: hash matches
[    0.734381] pci 0000:01:00.1: hash matches
[    0.734448] rtc_cmos 00:07: setting system clock to 2013-03-04 09:43:25 UTC (1362390205)

and from lspci -v:

01:00.1 Audio device: Advanced Micro Devices [AMD] nee ATI Caicos HDMI Audio [Radeon HD 6400 Series]
        Subsystem: Toshiba America Info Systems Device 0001
        Flags: bus master, fast devsel, latency 0, IRQ 53
        Memory at cc420000 (64-bit, non-prefetchable) [size=16K]
        Capabilities: <access denied>
        Kernel driver in use: snd_hda_intel


Note: My system bios is updated to the latest version and I've seen this problem from several kernel versions (FC16 and FC17).

Version-Release number of selected component (if applicable):
3.8.1-201.fc18.x86_64

How reproducible:
Always

Kernel parameters:

[    0.000000] Linux version 3.8.1-201.fc18.x86_64 (mockbuild.fedoraproject.org) (gcc version 4.7.2 20121109 (Red Hat 4.7.2-8) (GCC) ) #1 SMP Thu Feb 28 19:23:08 UTC 2013
[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.8.1-201.fc18.x86_64 root=UUID=513f4211-89cb-4b72-a792-9117a54b956e ro rd.md=0 rd.lvm=0 rd.dm=0 KEYTABLE=pt-latin1 quiet SYSFONT=latarcyrheb-sun16 rhgb rd.luks=0 LANG=en_US.UTF-8

Comment 1 Josh Boyer 2013-04-16 19:35:51 UTC

I don't see anything in the bug report that indicates the crash is because of the ATI HDMI audio device.  Did you somehow narrow it down to this?

Is there anything on the screen when it crashes?  A picture of the backtrace is better than nothing.

Comment 2 Paulo Fidalgo 2013-04-17 13:30:19 UTC

This happens when resuming from sleeping, and 
"pci 0000:01:00.1: hash matches" means that the last trace event was just before trying to resume device. So the problem lays in this device driver.

Comment 3 Josh Boyer 2013-07-02 20:30:48 UTC

Are you still seeing this with the 3.9 kernels?

Comment 4 Paulo Fidalgo 2013-07-02 22:03:04 UTC

Yes, currently with all updates and kernel 3.9.6-200.fc18.x86_64 I'm still cannot resume.

Comment 5 Justin M. Forbes 2013-10-18 21:05:13 UTC

*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 18 kernel bugs.

Fedora 18 has now been rebased to 3.11.4-101.fc18.  Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel.

If you have moved on to Fedora 19, and are still experiencing this issue, please change the version to Fedora 19.

If you experience different issues, please open a new bug report for those.

Comment 6 Paulo Fidalgo 2013-10-21 09:19:51 UTC

Updated to fc19 as of kernel 3.11.4-201.fc19.x86_64 this still happens.

Comment 7 Paulo Fidalgo 2013-11-12 11:54:13 UTC

Using the workarounds for https://bugzilla.redhat.com/show_bug.cgi?id=787299#c21
it resumes fine.

I'm going to mark this as duplicated to concentrate the efforts.

*** This bug has been marked as a duplicate of bug 787299 ***