Bug 66201 - AMD atombios stuck
Summary: AMD atombios stuck
Status: RESOLVED INVALID
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(DRI - non Intel) (show other bugs)
Hardware: x86-64 Linux
: P1 normal
Assignee: drivers_video-dri
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-30 08:15 UTC by RussianNeuroMancer
Modified: 2013-12-02 20:02 UTC (History)
1 user (show)

See Also:
Kernel Version: 3.13rc2
Subsystem:
Regression: No
Bisected commit-id:

Attachments
dmesg (81.00 KB, application/octet-stream)
2013-11-30 08:15 UTC, RussianNeuroMancer 		Details
Add an attachment (proposed patch, testcase, etc.)

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
Note You need to log in before you can comment on or make changes to this bug.