From: bugzilla-daemon@kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 216143] [bisected] garbled screen when starting X + dmesg cluttered with "[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed in the dependencies handling -1431655766!"
Date: Sat, 27 Aug 2022 13:56:38 +0000 [thread overview]
Message-ID: <bug-216143-2300-oomGZSh7Ok@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216143-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216143
--- Comment #14 from Michel Dänzer (michel@daenzer.net) ---
(In reply to Erhard F. from comment #13)
> I'll close here as it's clear this is not strictly an AMD driver issue.
Not really clear; there could be buggy amdgpu driver code, which happens not to
result in noticeable issues in practice when compiled by GCC.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2022-08-27 13:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 21:44 [Bug 216143] New: [bisected] garbled screen when starting X + dmesg cluttered with "[drm:amdgpu_cs_ioctl [amdgpu]] *ERROR* Failed in the dependencies handling -1431655766!" bugzilla-daemon
2022-06-17 21:45 ` [Bug 216143] " bugzilla-daemon
2022-06-17 21:45 ` bugzilla-daemon
2022-06-17 21:45 ` bugzilla-daemon
2022-06-17 22:08 ` bugzilla-daemon
2022-06-27 21:31 ` bugzilla-daemon
2022-06-28 0:04 ` bugzilla-daemon
2022-07-02 22:14 ` bugzilla-daemon
2022-07-10 11:02 ` bugzilla-daemon
2022-07-18 23:59 ` bugzilla-daemon
2022-08-15 14:09 ` bugzilla-daemon
2022-08-15 14:10 ` bugzilla-daemon
2022-08-27 13:46 ` bugzilla-daemon
2022-08-27 13:51 ` bugzilla-daemon
2022-08-27 13:56 ` bugzilla-daemon [this message]
2022-08-27 14:22 ` bugzilla-daemon
2022-11-14 22:58 ` bugzilla-daemon
2022-11-14 23:00 ` bugzilla-daemon
2023-02-16 23:21 ` 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-216143-2300-oomGZSh7Ok@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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.