Comment 12 for bug 1910562

Hi Gabriele,

Thank you for the bug report and the help with the investigation!

I apologize that this bug was marked as Expired; this is done by an automatic process after a period of inactivity. Somehow this fell through the cracks of our triage process, but now we're on it again :-).

Thank you for following up on Paride's request for further tests. I'm wondering here: I know that the 'sensors' command lets you specify which chips you want to get the temperature for, and given that this problem seems to happen every time you execute the command, then I think it's worth trying to pinpoin which chip is causing the problem here. Could you please try to run the command several times, specifying the different chip names each time, and see what happens? Maybe there's nothing to it, but we never know.

Another thing I was going to ask you is this: based on your comments, it seemed to me that you were able to reproduce this problem not only in Ubuntu, but also in other distributions. Is that correct? If it is, do you think you could test a pristine Linux kernel (from https://kernel.org)? If the bug reproduces with it, then I would recommend opening a bug report against the upstream Linux project.

For this specific bug, I think it's worth adding the Ubuntu Linux kernel package and seeing what the kernel folks have to say. Maybe they can come up with other things you can try to determine what's going on.

I'm setting this bug status back to New and adding the Ubuntu Linux package to it. I'm also going to subscribe myself to this bug so that we don't miss any more updates from you. Thank you.