All of lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 05 Jun 2014 22:38:29 +0000	[thread overview]
Message-ID: <bug-51381-2300-0VHUS73eOS@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 #18 from Teofilis Martisius <Teofilis.Martisius@gmail.com> ---
Hello,

I tried removing radeon.dpm=1, it did NOT fix the issue. I think my GPUs are
considered "stable" by now- it's not a new laptop.

Let me know if you need anything else.

Sincerely,
Teofilis Martisius

[    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.15.0-rc8
root=UUID=6b66e960-0da6-4a99-abfe-f23614b50db9 ro quiet radeon.audio=0
modeset=1 radeon.no_wb=1

.....

[   59.122053] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[   59.122183] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
CE56 (len 62, WS 0, PS 0) @ 0xCE72
[   59.122315] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
BB62 (len 1036, WS 4, PS 0) @ 0xBC5F
[   59.122448] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
BAF8 (len 76, WS 0, PS 8) @ 0xBB00
[   60.722717] radeon 0000:01:00.0: Wait for MC idle timedout !
[   60.923224] radeon 0000:01:00.0: Wait for MC idle timedout !
[   60.942019] [drm] PCIE GART of 1024M enabled (table at 0x0000000000273000).
[   60.942140] radeon 0000:01:00.0: WB enabled
[   60.942148] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
0x0000000040000c00 and cpu addr 0xffff880089552c00
[   60.942153] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
0x0000000040000c0c and cpu addr 0xffff880089552c0c
[   60.951189] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
0x0000000000072118 and cpu addr 0xffffc90011cb2118
[   61.178505] [drm:r600_ring_test] *ERROR* radeon: ring 0 test failed
(scratch(0x8504)=0xFFFFFFFF)
[   61.178637] [drm:evergreen_resume] *ERROR* evergreen startup failed on
resume
[   66.180845] [drm:atom_op_jump] *ERROR* atombios stuck in loop for more than
5secs aborting
[   66.180974] [drm:atom_execute_table_locked] *ERROR* atombios stuck executing
C50C (len 1136, WS 0, PS 0) @ 0xC536
[   66.219989] vgaarb: device changed decodes:
PCI:0000:01:00.0,olddecodes=io+mem,decodes=none:owns=none
[   66.219995] vgaarb: device changed decodes:
PCI:0000:00:01.0,olddecodes=io+mem,decodes=none:owns=none

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

  parent reply	other threads:[~2014-06-05 22:38 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
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 [this message]
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-0VHUS73eOS@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.