Bug 66201

Summary: AMD atombios stuck
Product: Drivers Reporter: RussianNeuroMancer (russianneuromancer)
Component: Video(DRI - non Intel)Assignee: drivers_video-dri
Status: RESOLVED INVALID    
Severity: normal CC: alexdeucher
Priority: P1    
Hardware: x86-64   
OS: Linux   
Kernel Version: 3.13rc2 Subsystem:
Regression: No Bisected commit-id:
Attachments: dmesg

Description RussianNeuroMancer 2013-11-30 08:15:01 UTC
Created attachment 116861 [details]
dmesg

Please look into attached dmesg.
3.13rc1 didn't tested. 3.12 boot fine. runpm disabled.

~$ lspci | grep VGA
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] BeaverCreek [Radeon HD 6620G]
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Whistler [Radeon HD 6630M/6650M/6750M/7670M/7690M]
Comment 1 Alex Deucher 2013-12-02 18:46:31 UTC
The bug title should be changed.  The atombios messages are just a side effect of the driver trying to access a GPU that has been powered down via vgaswitcheroo.
Comment 2 RussianNeuroMancer 2013-12-02 18:49:15 UTC
So 3.13 trying to power down/up dGPU even if radeon.runpm=1 is not set? runpm is enabled by default?
Comment 3 Alex Deucher 2013-12-02 18:59:48 UTC
(In reply to RussianNeuroMancer from comment #2)
> So 3.13 trying to power down/up dGPU even if radeon.runpm=1 is not set?
> runpm is enabled by default?

runpm is enabled by default in 3.13.
Comment 4 RussianNeuroMancer 2013-12-02 20:02:20 UTC
Thanks for answer. From others reports related to runpm I assume it has to be enabled manually, but mistake.
I tried to disabled runpm and now Linux 3.13 seems like boot fine, like previous releases. So this issue probably duplicate of this one: https://bugs.freedesktop.org/show_bug.cgi?id=62882