[Bug 1231228] jc42 creating temperature alarms with bogus min/max values
https://bugzilla.suse.com/show_bug.cgi?id=1231228 https://bugzilla.suse.com/show_bug.cgi?id=1231228#c19 Jean Delvare <jdelvare@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jimoe@sma-inc.us) | --- Comment #19 from Jean Delvare <jdelvare@suse.com> --- OK, so temp1_max_hyst does actually exist for the jc42 device, but it's a read-only attribute. In fact the device stores the hysteresis as a relative value, which applies to both the max and the crit limits, so they can't be set independently. Anyway, I'm glad we were able to solve your problem, and I think this bug can be closed now? I'm only wondering if we should include an example jc42 configuration section in /etc/sensors3.conf or /etc/sensors.d/jc42.conf. I'm reluctant to have active set statements by default though, as ideally the limits should be set by the firmware and we shouldn't arbitrarily overwrite them. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply@suse.com