[Bug 51381] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo

bugzilla-daemon at bugzilla.kernel.org bugzilla-daemon at bugzilla.kernel.org
Wed Jun 4 14:51:12 PDT 2014


https://bugzilla.kernel.org/show_bug.cgi?id=51381

--- Comment #14 from Teofilis Martisius <Teofilis.Martisius at gmail.com> ---
Hi,

Thank you for very quick response.

I have just tried v3.15rc7 from Debian Experimental, it still has this same
problem. I have attached an excerpt from dmesg at the end of this message. I'll
attach a full dmesg log as well.

I have tried same kernel with radeon.runpm=0, and it works correctly. I can run
glxgears on both my primary and my secondary GPU with "xrandr
--setprovideroffloadsink xx yy" and "DRI_PRIME=1 glxgears". Both work
correctly.

So disabling power management works as a workaround. However, it's just a
workaround, and it would be interesting to get the underlying issue fixed.

I'll try 3.15rc8 next, see if that has any improvements.

P.S. My current kernel boot-time options are:

quiet radeon.audio=0 modeset=1 radeon.dpm=1 radeon.no_wb=1 radeon.runpm=0

I'm running Debian/Sid. Could it be something broken in userspace interfering?

Sincerely,
Teofilis Martisius

======

[   55.886107] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[   55.886234] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
CE56 (len 62, WS 0, PS 0) @ 0xCE72
[   55.889662] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
BB62 (len 1036, WS 4, PS 0) @ 0xBC5F
[   55.892979] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
BAF8 (len 76, WS 0, PS 8) @ 0xBB00
[   55.896345] [drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed
[   57.418996] radeon 0000:01:00.0: Wait for MC idle timedout !
[   57.609356] radeon 0000:01:00.0: Wait for MC idle timedout !
[   57.628060] [drm] PCIE GART of 1024M enabled (table at 0x0000000000273000).
[   57.628181] radeon 0000:01:00.0: WB enabled
[   57.628189] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000040000c00 and cpu addr 0xffff88014876ac00
[   57.628194] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000040000c0c and cpu addr 0xffff88014876ac0c
[   57.637229] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000072118 and cpu addr 0xffffc90011cb2118
[   57.844594] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed
(scratch(0x8504)=0xFFFFFFFF)
[   57.844724] [drm:evergreen_resume] *ERROR* evergreen startup failed on
resume
[   57.847954] [drm:radeon_pm_resume_dpm] *ERROR* radeon: dpm resume failed

-- 
You are receiving this mail because:
You are watching the assignee of the bug.


More information about the dri-devel mailing list