dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 100666] amdgpu coolers never stoping linux
Date: Wed, 28 Feb 2018 04:21:34 +0000	[thread overview]
Message-ID: <bug-100666-502-nuWruoeKVc@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-100666-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1920 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=100666

--- Comment #15 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Luke McKee from comment #14)
> Alex thanks for your help.
> 
> How it gets the rom is probably the same as this shell script using the pci
> method listed on that github link in the last comment.
> 
> # To read ROM you first need to write `1` to it, then read it, and then write
> # `0` to it as described in the documentation. The reason is that the content
> # is not provided by default, by writing `1` to it you are telling the driver
> # to make it accessible.
> CARD_ID=0
> CARD_ROM="/sys/class/drm/card${CARD_ID}/device/rom"
> FILE_ROM="amdgpu-rom.bin"
> 
> echo 1 > $CARD_ROM
> cat $CARD_ROM > $FILE_ROM
> echo 0 > $CARD_ROM
> echo "Saved as ${FILE_ROM}"
> 
> --
> output:
> cat: /sys/class/drm/card0/device/rom: Input/output error
> [Not] Saved as amdgpu-rom.bin

That should generally work for desktop discrete cards.  You need to be root
however.

> 
> Is there any other user-space accessible methods to extract / write the rom
> in Linux? Now only focusing on comparing the pp table to other roms not
> modifying it.

You can read the amdgpu_vbios file in debugfs.  That will dump the copy of the
vbios that the driver is using.

> Maybe the powerplay is an atom-bios issue perhaps. If it's still broken in
> this 4.16-rc1 version I'm trying out now I'll open a ticket.
> 
> For your reference this is the ticket that claims powerplay dpm is fixed in
> newer kernels / dc=1 in 4.15.
> https://bugs.freedesktop.org/show_bug.cgi?id=100443#c37

There's no confirmation that specifically enabling dc fixed it.

Anyway, we are cluttering up this bug with potentially unrelated information. 
Please file a new bug for your issue and we can discuss it there.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 3149 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

  parent reply	other threads:[~2018-02-28  4:21 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
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 [this message]
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-nuWruoeKVc@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