From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 107748] [Intel GFX CI] couldn't schedule ib on ring <uvd>
Date: Thu, 30 Aug 2018 11:55:41 +0000 [thread overview]
Message-ID: <bug-107748-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1246 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=107748
Bug ID: 107748
Summary: [Intel GFX CI] couldn't schedule ib on ring <uvd>
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/AMDgpu
Assignee: dri-devel@lists.freedesktop.org
Reporter: martin.peres@free.fr
When executing the test igt@pm_rpm@system-suspend-execbuf on a KBLg system, we
hit the following bug:
[ 106.635764] amdgpu 0000:01:00.0: couldn't schedule ib on ring <uvd>
[ 106.635901] [drm:amdgpu_uvd_ring_test_ib [amdgpu]] *ERROR* amdgpu: (0)failed
to get destroy ib (-22).
[ 106.635935] [drm:amdgpu_ib_ring_tests [amdgpu]] *ERROR* amdgpu: failed
testing IB on ring 12 (-22).
[ 106.742994] [drm:process_one_work] *ERROR* ib ring test failed (-22).
Full logs:
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_83/fi-kbl-8809g/igt@pm_rpm@system-suspend-execbuf.html
The reproduction rate is so far very low (happened once), but I will use this
bug as a tracker for this issue.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2702 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next reply other threads:[~2018-08-30 11:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-30 11:55 bugzilla-daemon [this message]
2019-03-08 12:07 ` [Bug 107748] [Intel GFX CI] couldn't schedule ib on ring <uvd> bugzilla-daemon
2019-03-08 12:09 ` 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-107748-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.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.