From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 105354] RIP: dm_update_crtcs_state+0x36b/0x3f0 [amdgpu]
Date: Sat, 31 Mar 2018 13:44:51 +0000 [thread overview]
Message-ID: <bug-105354-502-3ITYlK9ELz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-105354-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 784 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=105354
--- Comment #3 from mikhail.v.gavrilov@gmail.com ---
I couldn't try drm-next-4.17-wip because RX Vega 56 hangs immediately after
start gdm with this kernel: https://bugs.freedesktop.org/show_bug.cgi?id=105833
But I checked this issue on mainline kernel:
https://git.kernel.org/torvalds/t/linux-4.16-rc7.tar.gz and don't saw that it
happens on 4.16-rc7
But I see that on mainline kernel still happens another issue:
[43261.036201] amdgpu 0000:07:00.0: swiotlb buffer is full (sz: 2097152 bytes)
[43261.036205] amdgpu 0000:07:00.0: swiotlb: coherent allocation failed,
size=2097152
https://bugs.freedesktop.org/show_bug.cgi?id=104082
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1978 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 prev parent reply other threads:[~2018-03-31 13:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 4:00 [Bug 105354] RIP: dm_update_crtcs_state+0x36b/0x3f0 [amdgpu] bugzilla-daemon
2018-03-06 4:10 ` bugzilla-daemon
2018-03-27 18:34 ` bugzilla-daemon
2018-03-31 13:44 ` bugzilla-daemon [this message]
2018-06-27 14:54 ` 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-105354-502-3ITYlK9ELz@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox