From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100666] amdgpu coolers never stoping linux
Date: Wed, 28 Feb 2018 01:29:22 +0000 [thread overview]
Message-ID: <bug-100666-502-5XWBmJ3i1v@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100666-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 534 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=100666
--- Comment #8 from Luke McKee <hojuruku@gmail.com> ---
Yeah I documented the workaround too:
https://forum-en.msi.com/index.php?topic=298468.0
Root cause may be able to how amdgpu handles not being able to read it's
powerplay settings because motherboard bioses (old AMI) don't set up MMIO BARs
properly and intel submitted a patch to enforce restrictions on memory address
regions in UEFI.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1348 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-02-28 1:29 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-12 18:21 [Bug 100666] amdgpu coolers never stoping linux bugzilla-daemon
2017-08-06 16:37 ` bugzilla-daemon
2017-08-06 16:57 ` bugzilla-daemon
2017-09-03 8:24 ` bugzilla-daemon
2017-09-08 4:31 ` bugzilla-daemon
2017-09-08 4:52 ` bugzilla-daemon
2017-09-08 4:59 ` bugzilla-daemon
2017-10-22 10:04 ` bugzilla-daemon
2017-10-23 18:01 ` bugzilla-daemon
2018-02-28 1:29 ` bugzilla-daemon [this message]
2018-02-28 2:08 ` bugzilla-daemon
2018-02-28 2:10 ` bugzilla-daemon
2018-02-28 2:36 ` bugzilla-daemon
2018-02-28 3:00 ` bugzilla-daemon
2018-02-28 3:07 ` bugzilla-daemon
2018-02-28 4:06 ` bugzilla-daemon
2018-02-28 4:21 ` bugzilla-daemon
2019-11-19 8:15 ` 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-100666-502-5XWBmJ3i1v@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