Mailinglist Archive: opensuse-bugs (6630 mails)
| < Previous | Next > |
[Bug 529483] changes in hwon may overheat CPU
- From: bugzilla_noreply@xxxxxxxxxx
- Date: Sat, 29 Aug 2009 05:27:08 -0600
- Message-id: <20090829112708.46FDFCC7CE@xxxxxxxxxxxxxxxxxxxxxx>
http://bugzilla.novell.com/show_bug.cgi?id=529483
User jdelvare@xxxxxxxxxx added comment
http://bugzilla.novell.com/show_bug.cgi?id=529483#c1
Jean Delvare <jdelvare@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P5 - None |P4 - Low
Status|NEW |ASSIGNED
Severity|Normal |Critical
--- Comment #1 from Jean Delvare <jdelvare@xxxxxxxxxx> 2009-08-29 05:26:58 MDT
---
I am just back from vacation. Thanks for reporting. I am aware of the problem
but could never find the time to work on it.
Can you please clarify what you call "M4" and "M5"?
In general, pwmconfig and fancontrol should be considered as quick hacks rather
than production-ready applications. You have to be very careful when using
them, as you found out yourself already.
Please note that you should NOT use the asus_atk0110 and w83627ehf drivers at
the same time. They are accessing the same chip, which is very dangerous. So if
you switched to the asus_atk0110 driver (which is safer than native drivers on
systems that support it) then you should stop loading the w83627ehf driver
(remove it from /etc/sysconfig/lm_sensors).
So there are two different bugs as I understand it:
1* When asus_atk0110 is loaded, it should not be possible to load w83627ehf
(nor it87 nor any other Super-I/O chip driver Asus may be using). This should
hopefully be solved by ACPI I/O region checks which were accidentally dropped
from the upstream kernel, but should be restored soon.
2* The fancontrol script should check that the run time devices are similar to
the configuration time devices, and refuse to load if not.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
User jdelvare@xxxxxxxxxx added comment
http://bugzilla.novell.com/show_bug.cgi?id=529483#c1
Jean Delvare <jdelvare@xxxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
Priority|P5 - None |P4 - Low
Status|NEW |ASSIGNED
Severity|Normal |Critical
--- Comment #1 from Jean Delvare <jdelvare@xxxxxxxxxx> 2009-08-29 05:26:58 MDT
---
I am just back from vacation. Thanks for reporting. I am aware of the problem
but could never find the time to work on it.
Can you please clarify what you call "M4" and "M5"?
In general, pwmconfig and fancontrol should be considered as quick hacks rather
than production-ready applications. You have to be very careful when using
them, as you found out yourself already.
Please note that you should NOT use the asus_atk0110 and w83627ehf drivers at
the same time. They are accessing the same chip, which is very dangerous. So if
you switched to the asus_atk0110 driver (which is safer than native drivers on
systems that support it) then you should stop loading the w83627ehf driver
(remove it from /etc/sysconfig/lm_sensors).
So there are two different bugs as I understand it:
1* When asus_atk0110 is loaded, it should not be possible to load w83627ehf
(nor it87 nor any other Super-I/O chip driver Asus may be using). This should
hopefully be solved by ACPI I/O region checks which were accidentally dropped
from the upstream kernel, but should be restored soon.
2* The fancontrol script should check that the run time devices are similar to
the configuration time devices, and refuse to load if not.
--
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
| < Previous | Next > |