dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 202263] New: AMDGPU: DRM couldn't schedule ib on ring (-22)
Date: Mon, 14 Jan 2019 15:17:10 +0000	[thread overview]
Message-ID: <bug-202263-2300@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 202263
           Summary: AMDGPU: DRM couldn't schedule ib on ring (-22)
           Product: Drivers
           Version: 2.5
    Kernel Version: 4.19.12-1-default
          Hardware: Intel
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Video(DRI - non Intel)
          Assignee: drivers_video-dri@kernel-bugs.osdl.org
          Reporter: e.isik27@gmail.com
        Regression: No

Hello everyone!

I have some troubles with the amdgpu driver.

I'm getting some errors from the kernel when I force to use the discrete GPU.
By the way, I have a hybrid GPU System. (Lenovo Laptop: Intel HD & AMD Radeon
530)  

First of all I cleared the dmesg logs.

Then I executed:

DRI_PRIME=1 glxinfo | grep OpenGL

and then I got this errors:

https://pastebin.com/iaejbQ2t (for full dmesg)

[  422.628116] amdgpu 0000:01:00.0: couldn't schedule ib on ring <sdma0>
[  422.628146] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
[  422.628147] amdgpu 0000:01:00.0: couldn't schedule ib on ring <sdma0>
[  422.628182] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
[  422.628185] amdgpu 0000:01:00.0: couldn't schedule ib on ring <sdma0>
[  422.628212] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
[  422.628214] amdgpu 0000:01:00.0: couldn't schedule ib on ring <sdma0>
[  422.628241] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
[  422.628243] amdgpu 0000:01:00.0: couldn't schedule ib on ring <sdma0>
[  422.628271] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
[  422.628273] amdgpu 0000:01:00.0: couldn't schedule ib on ring <sdma0>
[  422.628300] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
[  422.628301] amdgpu 0000:01:00.0: couldn't schedule ib on ring <sdma0>
[  422.628328] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
[  422.628330] amdgpu 0000:01:00.0: couldn't schedule ib on ring <sdma0>
[  422.628357] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)
[  422.629694] amdgpu 0000:01:00.0: couldn't schedule ib on ring <sdma0>
[  422.629743] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)

But when I set the DRI_PRIME value to 0, this errors doesn't appear.

I also tried with DRI_PRIME=1 glxgears.

There I get TONS of errors like this here:
[  422.628301] amdgpu 0000:01:00.0: couldn't schedule ib on ring <sdma0>
[  422.628328] [drm:amdgpu_job_run [amdgpu]] *ERROR* Error scheduling IBs (-22)

I am using the latest version of OpenSUSE tumbleweed.
Kernel: 4.19.12-1-default

amdgpu is installed & kernel-firmware, too.

Thanks!!

-- 
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

             reply	other threads:[~2019-01-14 15:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-14 15:17 bugzilla-daemon [this message]
2019-01-14 15:24 ` [Bug 202263] AMDGPU: DRM couldn't schedule ib on ring (-22) 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
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@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox