From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98016] [bisected] Fury fails to boot on drm-next-4.9
Date: Fri, 14 Oct 2016 14:50:41 +0000 [thread overview]
Message-ID: <bug-98016-502-pokqzFFqeY@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98016-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 820 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98016
--- Comment #11 from Alex Deucher <alexdeucher@gmail.com> ---
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=amdgpu 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.
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
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1683 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:[~2016-10-14 14:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-02 13:31 [Bug 98016] [bisected] Fury fails to boot since vce3: add support for third vce ring bugzilla-daemon
2016-10-02 13:55 ` bugzilla-daemon
2016-10-03 20:08 ` bugzilla-daemon
2016-10-03 20:51 ` [Bug 98016] [bisected] Fury fails to boot on drm-next-4.9 bugzilla-daemon
2016-10-04 9:18 ` bugzilla-daemon
2016-10-04 9:30 ` bugzilla-daemon
2016-10-05 7:08 ` bugzilla-daemon
2016-10-05 9:18 ` bugzilla-daemon
2016-10-10 10:35 ` bugzilla-daemon
2016-10-14 11:39 ` bugzilla-daemon
2016-10-14 14:38 ` bugzilla-daemon
2016-10-14 14:50 ` bugzilla-daemon [this message]
2016-10-14 23:02 ` bugzilla-daemon
2016-10-14 23:03 ` bugzilla-daemon
2016-10-16 18:00 ` bugzilla-daemon
2016-10-25 13:41 ` bugzilla-daemon
2016-12-14 10:58 ` 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-98016-502-pokqzFFqeY@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