From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 77751] New: radeon: unable to set temperature warning levels
Date: Thu, 12 Jun 2014 22:18:50 +0000 [thread overview]
Message-ID: <bug-77751-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=77751
Bug ID: 77751
Summary: radeon: unable to set temperature warning levels
Product: Drivers
Version: 2.5
Kernel Version: 3.15
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: low
Priority: P1
Component: Video(DRI - non Intel)
Assignee: drivers_video-dri@kernel-bugs.osdl.org
Reporter: higuita@gmx.net
Regression: No
I have a old Radeon HD2600XT AGP card, but i think this should apply to all
AMD/ATI cards.
Right now, when i use the "sensors" command i get this
radeon-pci-0100
Adapter: PCI adapter
temp-GPU: +53.0°C (crit = +120.0°C, hyst = +90.0°C)
But the values for critical and warning are too high for this card, specially
as the fan is unable to run as fast as in the past. To me, right now, when the
card reaches about 84ºC it start to lockup and force me to reboot to recover.
So i tried to configure the sensors.conf, but when running "sensors -s" i get:
Error: File /etc/sensors.d/local.conf, line 87: Failed to set value
Error: File /etc/sensors.d/local.conf, line 88: Failed to set value
radeon-pci-0100: At least one "set" statement failed
i have this configured:
chip "radeon-pci-*"
label temp1 "temp-GPU"
set temp1_crit 82
set temp1_crit_hyst 79
Checking the /sys entry to try to manually set the values i see this:
# ls -l /sys/class/hwmon/hwmon1/
total 0
lrwxrwxrwx 1 root root 0 Jun 12 17:20 device -> ../../../0000:01:00.0
-r--r--r-- 1 root root 4096 Jun 12 22:14 name
drwxr-xr-x 2 root root 0 Jun 12 22:14 power
lrwxrwxrwx 1 root root 0 Jun 12 17:20 subsystem ->
../../../../../../class/hwmon
-r--r--r-- 1 root root 4096 Jun 12 22:14 temp1_crit
-r--r--r-- 1 root root 4096 Jun 12 22:14 temp1_crit_hyst
-r--r--r-- 1 root root 4096 Jun 12 22:14 temp1_input
-rw-r--r-- 1 root root 4096 Jun 12 22:14 uevent
So the temp1_crit and temp1_crit_hyst are readonly, that is why it fails to
setup new values and we can only use hardcoded values.
it would be a good idea to allow one to change this value, and even better if
one could automatically slow down the card when it reach the critical level, to
avoid the crash.
--
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2014-06-12 22:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-77751-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.