From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 207673] New: radeon: crash due to over temperature
Date: Sun, 10 May 2020 13:43:24 +0000 [thread overview]
Message-ID: <bug-207673-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=207673
Bug ID: 207673
Summary: radeon: crash due to over temperature
Product: Drivers
Version: 2.5
Kernel Version: 5.6.x and previous
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: high
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: phil@jpmr.org
Regression: No
Created attachment 289045
--> https://bugzilla.kernel.org/attachment.cgi?id=289045&action=edit
kernel log + lspci + glxinfo + patch
The radeon driver crashes because of an over temperature of my
AMD Cape Verde Pro graphic card.
On my system, there's no overclocking, and the power management mode is the
default one, with power_method dpm, power_dpm_state balanced and
power_dpm_force_performance_level auto.
This GPU is used for display and opencl computing.
The default over temperature value in r600_dpm is 120C, which seems to be too
high for this chip/card.
I patched my system to have a 100C limit, and I've no crash anymore.
(I tried 110C, and it's still too high).
Attached are the full kernel log of the crash event, the lspci and glxinfo for
the graphic card, and the proposed patch.
--
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 reply other threads:[~2020-05-10 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-10 13:43 bugzilla-daemon [this message]
2020-05-10 13:46 ` [Bug 207673] radeon: crash due to over temperature bugzilla-daemon
2020-05-13 12:20 ` bugzilla-daemon
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@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.