From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 198883] amdgpu: carrizo: Screen stalls after starting X
Date: Tue, 06 Mar 2018 16:39:13 +0000 [thread overview]
Message-ID: <bug-198883-2300-aYvCZq1hXM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-198883-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=198883
--- Comment #39 from Andrey Grodzovsky (andrey.grodzovsky@amd.com) ---
(In reply to Ricardo Ribalda from comment #38)
> Just for the fun of it, I did try the amdgpu.gpu_recovery=1 module parameter,
>
>
> It seems to detect properly the crash, but fails miserably on the recovery.
> The screens blanks and the whole system is unusable: Leds stop blinking, ssh
> does not work... I need to hard reset the system.
>
>
> Thanks!
job timeout message is expected since you indeed have a hanged pipe
GPU recovery failure on CZ is expected since it's another issue we have with
GPU pci config reset hard hang ( I am looking at this also)
I suggest you try to be latest on everything to see if this still happens.
So you already on latest kernel, now pick up latest firmware we have from this
git
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu
Take all the carrizo* files and override the ones you have under you kernel
(usally in /lib/firmware`uname -r`/amdgpu or in kernel specific folder under
lib/firmware
I think you already updated your libdrm/MESA/LLVM but you LLVM is still 5.0
right ? Can you try switching to LLVM 7
--
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
next prev parent reply other threads:[~2018-03-06 16:39 UTC|newest]
Thread overview: 89+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 10:46 [Bug 198883] New: amdgpu: carrizo: Screen stalls after starting X bugzilla-daemon
2018-02-22 10:47 ` [Bug 198883] " bugzilla-daemon
2018-02-22 10:47 ` bugzilla-daemon
2018-02-22 10:47 ` bugzilla-daemon
2018-02-23 13:02 ` bugzilla-daemon
2018-02-23 15:01 ` bugzilla-daemon
2018-02-23 15:02 ` bugzilla-daemon
2018-02-23 15:02 ` bugzilla-daemon
2018-02-23 15:14 ` bugzilla-daemon
2018-02-23 15:19 ` bugzilla-daemon
2018-02-23 15:23 ` bugzilla-daemon
2018-02-23 15:29 ` bugzilla-daemon
2018-02-23 15:29 ` bugzilla-daemon
2018-02-23 15:31 ` bugzilla-daemon
2018-02-23 15:33 ` bugzilla-daemon
2018-02-23 15:34 ` bugzilla-daemon
2018-02-23 15:42 ` bugzilla-daemon
2018-02-23 15:45 ` bugzilla-daemon
2018-02-23 20:20 ` bugzilla-daemon
2018-02-23 21:44 ` bugzilla-daemon
2018-02-24 6:41 ` bugzilla-daemon
2018-02-24 14:04 ` bugzilla-daemon
2018-02-26 16:11 ` bugzilla-daemon
2018-02-27 13:57 ` bugzilla-daemon
2018-02-27 13:58 ` bugzilla-daemon
2018-03-05 13:26 ` bugzilla-daemon
2018-03-05 14:01 ` bugzilla-daemon
2018-03-05 14:02 ` bugzilla-daemon
2018-03-05 14:03 ` bugzilla-daemon
2018-03-05 17:27 ` bugzilla-daemon
2018-03-05 21:22 ` bugzilla-daemon
2018-03-06 8:08 ` bugzilla-daemon
2018-03-06 8:09 ` bugzilla-daemon
2018-03-06 8:23 ` bugzilla-daemon
2018-03-06 8:24 ` bugzilla-daemon
2018-03-06 12:52 ` bugzilla-daemon
2018-03-06 13:38 ` bugzilla-daemon
2018-03-06 13:39 ` bugzilla-daemon
2018-03-06 14:07 ` bugzilla-daemon
2018-03-06 16:39 ` bugzilla-daemon [this message]
2018-03-06 16:53 ` bugzilla-daemon
2018-03-06 17:54 ` bugzilla-daemon
2018-03-09 15:46 ` bugzilla-daemon
2018-03-09 16:08 ` bugzilla-daemon
2018-03-09 18:31 ` bugzilla-daemon
2018-03-09 18:38 ` bugzilla-daemon
2018-03-12 8:12 ` bugzilla-daemon
2018-03-12 11:00 ` bugzilla-daemon
2018-03-12 11:55 ` bugzilla-daemon
2018-03-12 12:04 ` bugzilla-daemon
2018-03-12 12:04 ` bugzilla-daemon
2018-03-12 14:12 ` bugzilla-daemon
2018-03-12 14:32 ` bugzilla-daemon
2018-03-12 14:33 ` bugzilla-daemon
2018-03-12 14:40 ` bugzilla-daemon
2018-03-12 14:41 ` bugzilla-daemon
2018-03-12 14:42 ` bugzilla-daemon
2018-03-14 8:14 ` bugzilla-daemon
2018-03-15 17:59 ` bugzilla-daemon
2018-03-16 11:11 ` bugzilla-daemon
2018-03-16 14:37 ` bugzilla-daemon
2018-03-20 8:48 ` bugzilla-daemon
2018-03-20 11:58 ` bugzilla-daemon
2018-03-20 15:10 ` bugzilla-daemon
2018-03-20 16:27 ` bugzilla-daemon
2018-03-21 8:29 ` bugzilla-daemon
2018-03-21 12:41 ` bugzilla-daemon
2018-03-21 13:45 ` bugzilla-daemon
2018-03-21 14:23 ` bugzilla-daemon
2018-03-21 14:33 ` bugzilla-daemon
2018-03-21 14:33 ` bugzilla-daemon
2018-03-21 14:34 ` bugzilla-daemon
2018-03-22 12:18 ` bugzilla-daemon
2018-03-22 13:27 ` bugzilla-daemon
2018-03-22 13:47 ` bugzilla-daemon
2018-03-22 13:48 ` bugzilla-daemon
2018-03-22 14:02 ` bugzilla-daemon
2018-03-22 14:43 ` bugzilla-daemon
2018-04-08 22:30 ` bugzilla-daemon
2018-04-09 6:39 ` bugzilla-daemon
2018-04-09 13:18 ` bugzilla-daemon
2018-04-10 14:46 ` bugzilla-daemon
2018-04-10 14:49 ` bugzilla-daemon
2018-04-16 14:04 ` bugzilla-daemon
2018-04-16 14:56 ` bugzilla-daemon
2018-04-16 15:13 ` bugzilla-daemon
2018-04-20 12:19 ` bugzilla-daemon
2018-04-20 12:22 ` bugzilla-daemon
2018-04-20 12:23 ` 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-198883-2300-aYvCZq1hXM@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;
as well as URLs for NNTP newsgroup(s).