[Bug 1231228] New: jc42 creating temperature alarms with bogus min/max values
https://bugzilla.suse.com/show_bug.cgi?id=1231228 Bug ID: 1231228 Summary: jc42 creating temperature alarms with bogus min/max values Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: Kernel:Drivers Assignee: kernel-bugs@suse.de Reporter: jimoe@sma-inc.us QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- opensuse tumbleweed 20240927 linux 6.11.0-1-default x86_64 A recent kernel update (to 6.11.0) brought the awareness of sensor jc42, which monitors the temperature of DIMMs. I discovered it by the following entry in the system journal: 2024-10-01T10:34:40-07:00 sma-station14l sensord[148139]: Sensor alarm: Chip jc42-i2c-6-1b: DIMM Temp: 40.2 C (min = 0.0 C, max = 0.0 C) [ALARM] The min and max values are not appropriate values. I created a conf file for jc42, jc42.conf, since none was standard in sensors3.conf and added it to /etc/sensors.d/. Contents: # Chip: jc42-i2c-6-1b # Adapter: SMBus PIIX4 adapter port 0 at 0b00 # chip "jc42-*" label "temp1" "DIMM Temp" set temp1_min 00 set temp1_max 60 set temp1_max_hyst 56 # The only entry that had an effect is “label.” The set commands do nothing. Am I missing something? -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1231228 https://bugzilla.suse.com/show_bug.cgi?id=1231228#c2 pallas wept <pallaswept@proton.me> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |pallaswept@proton.me --- Comment #2 from pallas wept <pallaswept@proton.me> --- I'm trying to avoid hijacking as I am not sure these are the same issue, but they are clearly related. I thought this might be of interest: https://bugzilla.opensuse.org/show_bug.cgi?id=1231312 TLDR: broken jc42 on 6.11.0 Hope that helps, good luck OP. -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1231228 https://bugzilla.suse.com/show_bug.cgi?id=1231228#c3 --- Comment #3 from James Moe <jimoe@sma-inc.us> --- Created attachment 877756 --> https://bugzilla.suse.com/attachment.cgi?id=877756&action=edit dmesg for kernel 6.10.9 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1231228 https://bugzilla.suse.com/show_bug.cgi?id=1231228#c4 --- Comment #4 from James Moe <jimoe@sma-inc.us> --- Created attachment 877757 --> https://bugzilla.suse.com/attachment.cgi?id=877757&action=edit hwinfo for kernel 6.10.9 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1231228 https://bugzilla.suse.com/show_bug.cgi?id=1231228#c5 --- Comment #5 from James Moe <jimoe@sma-inc.us> --- Created attachment 877758 --> https://bugzilla.suse.com/attachment.cgi?id=877758&action=edit dmesg for kernel 6.11.0 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1231228 https://bugzilla.suse.com/show_bug.cgi?id=1231228#c6 --- Comment #6 from James Moe <jimoe@sma-inc.us> --- Created attachment 877759 --> https://bugzilla.suse.com/attachment.cgi?id=877759&action=edit hwinfo for kernel 6.11.0 -- You are receiving this mail because: You are on the CC list for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1231228 https://bugzilla.suse.com/show_bug.cgi?id=1231228#c7 James Moe <jimoe@sma-inc.us> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(jimoe@sma-inc.us) | --- Comment #7 from James Moe <jimoe@sma-inc.us> --- Both the dmesg and hwinfo files were created shortly after a system restart. -- You are receiving this mail because: You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠suse.com