From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 98016] [bisected] Fury fails to boot on drm-next-4.9 Date: Fri, 14 Oct 2016 14:50:41 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1752296034==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id 3D01A6ECBE for ; Fri, 14 Oct 2016 14:50:41 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============1752296034== Content-Type: multipart/alternative; boundary="14764566410.C6d0.12516"; charset="UTF-8" --14764566410.C6d0.12516 Date: Fri, 14 Oct 2016 14:50:41 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D98016 --- Comment #11 from Alex Deucher --- Odd. We haven't seen any failures internally with Fiji and 3 VCE rings enabled. Can you provide a log of the failure? Try manually loading amdgpu after boot. E.g., append modprobe.blacklist=3Damdgpu to the kernel command= line and boot to a non-X runlevel, then manually modprobe amdgpu and capture the dmesg output. Please attach the dmesg output from a successful boot as well= .=20=20 If you have remote access via ssh, that would make it easier. What VCE firmware are you using? Can you try the latest version from git and see if that helps: https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmware.git --=20 You are receiving this mail because: You are the assignee for the bug.= --14764566410.C6d0.12516 Date: Fri, 14 Oct 2016 14:50:41 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 11 on bug 98016<= /a> from Alex Deucher 
Odd.  We haven't seen any failures internally with Fiji and 3 =
VCE rings
enabled.  Can you provide a log of the failure?  Try manually loading amdgpu
after boot.  E.g., append modprobe.blacklist=3Damdgpu to the kernel command=
 line
and boot to a non-X runlevel, then manually modprobe amdgpu and capture the
dmesg output. Please attach the dmesg output from a successful boot as well=
.=20=20
If you have remote access via ssh, that would make it easier.  What VCE
firmware are you using?  Can you try the latest version from git and see if
that helps:
https://git.kernel.org/cgit/linux/kernel/git/firmware/linux-firmw=
are.git

You are receiving this mail because:
  • You are the assignee for the bug.
= --14764566410.C6d0.12516-- --===============1752296034== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============1752296034==--