From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 51381] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo
Date: Wed, 04 Jun 2014 21:51:12 +0000 [thread overview]
Message-ID: <bug-51381-2300-KlUc0GjXCA@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-51381-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=51381
--- Comment #14 from Teofilis Martisius <Teofilis.Martisius@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.
next prev parent reply other threads:[~2014-06-04 21:51 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-07 11:00 [Bug 51381] New: [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than 5secs aborting, when disabled via vgaswitcheroo bugzilla-daemon
2012-12-07 14:27 ` [Bug 51381] " bugzilla-daemon
2012-12-07 16:18 ` bugzilla-daemon
2012-12-07 16:22 ` bugzilla-daemon
2012-12-07 16:22 ` bugzilla-daemon
2012-12-07 17:34 ` bugzilla-daemon
2012-12-09 13:55 ` bugzilla-daemon
2013-06-13 17:10 ` bugzilla-daemon
2013-06-13 17:11 ` bugzilla-daemon
2014-05-04 17:28 ` bugzilla-daemon
2014-05-04 17:32 ` bugzilla-daemon
2014-05-04 17:36 ` bugzilla-daemon
2014-05-05 13:33 ` bugzilla-daemon
2014-05-05 17:44 ` bugzilla-daemon
2014-06-04 20:43 ` bugzilla-daemon
2014-06-04 20:59 ` bugzilla-daemon
2014-06-04 21:51 ` bugzilla-daemon [this message]
2014-06-04 21:53 ` bugzilla-daemon
2014-06-05 6:18 ` bugzilla-daemon
2014-06-05 13:21 ` bugzilla-daemon
2014-06-05 22:38 ` bugzilla-daemon
2014-06-05 22:40 ` bugzilla-daemon
2014-06-05 22:43 ` bugzilla-daemon
2014-06-06 7:08 ` bugzilla-daemon
2014-06-06 7:29 ` bugzilla-daemon
2014-06-06 14:17 ` bugzilla-daemon
2014-06-06 21:04 ` bugzilla-daemon
2014-06-06 21:05 ` bugzilla-daemon
2014-06-06 21:13 ` bugzilla-daemon
2014-06-06 21:14 ` bugzilla-daemon
2014-06-09 18:18 ` bugzilla-daemon
2014-06-09 18:19 ` bugzilla-daemon
2014-06-09 18:20 ` bugzilla-daemon
2014-06-09 18:22 ` bugzilla-daemon
2014-06-09 18:27 ` bugzilla-daemon
2014-06-10 6:28 ` bugzilla-daemon
2014-06-10 6:29 ` bugzilla-daemon
2014-06-28 13:12 ` bugzilla-daemon
2014-07-18 16:00 ` bugzilla-daemon
2014-07-19 9:52 ` bugzilla-daemon
2014-09-22 6:00 ` bugzilla-daemon
2014-09-22 21:39 ` bugzilla-daemon
2016-03-12 18:58 ` bugzilla-daemon
2016-04-26 14:35 ` bugzilla-daemon
2016-09-02 3:25 ` bugzilla-daemon
2016-09-02 13:35 ` bugzilla-daemon
2016-09-02 19:59 ` bugzilla-daemon
2016-09-05 21:03 ` bugzilla-daemon
2016-09-08 23:19 ` bugzilla-daemon
2016-09-08 23:21 ` bugzilla-daemon
2016-09-08 23:30 ` bugzilla-daemon
2016-10-11 0:16 ` bugzilla-daemon
2016-10-28 21:24 ` bugzilla-daemon
2016-12-11 16:31 ` bugzilla-daemon
2018-04-07 15:10 ` bugzilla-daemon
2021-02-28 8:07 ` bugzilla-daemon
2021-05-07 9:34 ` bugzilla-daemon
2021-05-07 10:32 ` bugzilla-daemon
2021-05-08 7:31 ` bugzilla-daemon
2021-05-08 17:49 ` bugzilla-daemon
2021-05-08 19:27 ` bugzilla-daemon
2021-05-09 4:16 ` bugzilla-daemon
2021-05-11 10:03 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-51381-2300-KlUc0GjXCA@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.