From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 106054] [vega10] powerplay non critical errors on vega 56 with vega 64bios
Date: Mon, 16 Apr 2018 13:41:57 +0000 [thread overview]
Message-ID: <bug-106054-502-3xpj76g8p3@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-106054-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 273 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=106054
--- Comment #1 from Alex Deucher <alexdeucher@gmail.com> ---
Flashing random vbioses is not supported and will likely void your warranty.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1092 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-04-16 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-15 10:25 [Bug 106054] [vega10] powerplay non critical errors on vega 56 with vega 64bios bugzilla-daemon
2018-04-16 13:41 ` bugzilla-daemon [this message]
2018-04-16 14:40 ` bugzilla-daemon
2019-11-19 8:35 ` 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-106054-502-3xpj76g8p3@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