All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202263] AMDGPU: DRM couldn't schedule ib on ring (-22)
Date: Tue, 15 Jan 2019 08:30:58 +0000	[thread overview]
Message-ID: <bug-202263-2300-Ydx5WwKb9I@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-202263-2300@https.bugzilla.kernel.org/>

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

--- Comment #5 from Emre Işık (e.isik27@gmail.com) ---
I found this line in my dmesg logs:

> [drm:atom_op_jump [amdgpu]] *ERROR* atombios stuck in loop for more than
> 5secs aborting

So I searched and found some threads about TLP and AMDGPU problems.
They told they removed TLP, so I (just for testing) removed TLP from my Laptop
system and then the errors are gone.
It worked. But TLP shouldn't be removed because it is responsible about the
power managment. Should I just install "tuned" or other TLP-like programs or is
this error a kernel issue?

Thanks, again!

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2019-01-15  8:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14 15:17 [Bug 202263] New: AMDGPU: DRM couldn't schedule ib on ring (-22) bugzilla-daemon
2019-01-14 15:24 ` [Bug 202263] " bugzilla-daemon
2019-01-15  7:07 ` bugzilla-daemon
2019-01-15  7:07 ` bugzilla-daemon
2019-01-15  7:08 ` bugzilla-daemon
2019-01-15  8:30 ` bugzilla-daemon [this message]
2019-01-15 17:11 ` bugzilla-daemon
2019-01-16  8:41 ` bugzilla-daemon
2019-01-16 11:41 ` bugzilla-daemon
2019-01-16 16:02 ` bugzilla-daemon
2019-01-16 16:12 ` 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-202263-2300-Ydx5WwKb9I@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.