All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 207673] radeon: crash due to over temperature
Date: Wed, 13 May 2020 12:20:57 +0000	[thread overview]
Message-ID: <bug-207673-2300-d8mgesXYVt@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207673-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=207673

--- Comment #2 from phileimer (phil@jpmr.org) ---
I can give more information about the over temperature problem :

* if I keep the 120C limit, the card runs at power level 3 until the driver
crashes

* limiting at 100C allows the driver to decrease power level to 2 after a small
overshoot, i.e. the temperature reaches 103/104C

* once at power level 2, the temperature stabilizes around 96C

* to test further, I decreased the case fan speed, and then, even with the 100C
limit, the card continues to run at power level 2 until the driver crashes
around 112C

So, there seems to be 2 problems :
* the default 120C is clearly too high, at least for this board/chip
* the temperature limit is used to go from PWL 3 to PWL 2, but there's no
decrease to a lower PWL (1 or 0), as a safe measure

-- 
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

  parent reply	other threads:[~2020-05-13 12:21 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-10 13:43 [Bug 207673] New: radeon: crash due to over temperature bugzilla-daemon
2020-05-10 13:46 ` [Bug 207673] " bugzilla-daemon
2020-05-13 12:20 ` bugzilla-daemon [this message]
2020-06-22 14:10 ` [Bug 207673] amdgpu/radeon: " bugzilla-daemon
2020-06-22 14:11 ` bugzilla-daemon
2020-06-22 14:14 ` bugzilla-daemon
2020-06-22 14:16 ` bugzilla-daemon
2020-06-27 12:44 ` 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-207673-2300-d8mgesXYVt@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.