Bug 25883 - Strange Psensor order on an Intel NUC8i5
Summary: Strange Psensor order on an Intel NUC8i5
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Kernel and Drivers maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-12-15 13:13 CET by Bjarne Thomsen
Modified: 2021-09-07 14:11 CEST (History)
1 user (show)

See Also:
Source RPM: kernel-5.4.3-1.mga7.src.rpm, psensor-1.2.0-5.mga7.src.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Bjarne Thomsen 2019-12-15 13:13:48 CET 
Description of problem:
Psensor:
temp1
temp1
temp2
Composite
Sensor 2
Package id 0
core 0
core 1
core 2
core 3
temp1

I would have expected Package id 0 to be the first one.
I remember that this strange ordering was sorted out in the latest version of 5.3.13.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
Comment 1 Lewis Smith 2019-12-17 20:22:58 CET 
(In reply to Bjarne Thomsen from comment #0)
"Psensor is a graphical hardware temperature monitor for Linux."
For graphical things, a screenshot often helps.
> I remember that this strange ordering was sorted out in the latest version
> of 5.3.13.
Are you saying that this problem existed in the past (but was not bugged; did/does it matter?), but disappeared with kernel 5.3.13? And it has re-appeared with the latest kernel 5.4.2?
One would suspect psensor itself, but that has not been altered for a long time.

Assigning to kernel team re the Description; CC'ing Rémi as registered psensor maintainer.

Source RPM: kernel-5.4.3-1.mga7.src.rpm => kernel-5.4.3-1.mga7.src.rpm, psensor-1.2.0-5.mga7.src.rpm
CC: (none) => rverschelde

Lewis Smith 2019-12-17 20:23:50 CET

Assignee: bugsquad => kernel

Comment 2 Bjarne Thomsen 2020-01-17 14:04:44 CET 
This is not really important. You can remove it.
Comment 3 Aurelien Oudelet 2021-07-06 13:14:18 CEST 
Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.
Comment 4 Marja Van Waes 2021-09-07 14:11:00 CEST 
Hi bug reporter and hi assignee and others involved,

Please reopen this bug report if it is still valid for Mageia 8 or 9(cauldron), and change "Version:" in the upper left of this report accordingly.

This report is being closed as OLD because it was filed against Mageia 7, for which  support ended on June 30th 2021.

Thanks,
Marja

Resolution: (none) => OLD
Status: NEW => RESOLVED
Note You need to log in before you can comment on or make changes to this bug.