From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206155] amdgpu several warnings while booting Fiji GPU, GPU not activated
Date: Fri, 10 Jan 2020 16:18:51 +0000 [thread overview]
Message-ID: <bug-206155-2300-FJHpQwvRaj@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206155-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=206155
--- Comment #2 from Janpieter Sollie (janpieter.sollie@dommel.be) ---
Well, sorry for the disappointment, but I am 100% human (guess most IT nerds
are not, so this may not be completely correct), but my email address is about
to change, so I hope the new one will have a better level of acceptance ;)
Anyway, some additional info:
- problem occurs only with monitor connected. If not, there's no harm
- tried playing around with fw_load_type, but did not help.
- tried to blacklist amdgpu and load it afterwards, but modprobe hung. A reboot
was the only option here, as the shell was closed, but it became a daemon
process
--
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:[~2020-01-10 16:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-10 14:13 [Bug 206155] New: amdgpu several warnings while booting Fiji GPU, GPU not activated bugzilla-daemon
2020-01-10 16:07 ` Liu, Zhan
2020-01-10 16:07 ` [Bug 206155] " bugzilla-daemon
2020-01-10 16:18 ` bugzilla-daemon [this message]
2020-01-13 8:29 ` bugzilla-daemon
2020-01-18 7:16 ` 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-206155-2300-FJHpQwvRaj@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).