> which has a ton of debugging > options including KASAN, but nothing seems to point the finger at something > originating in amd_sfh code. Is it possible the hardware itself (the mp2/sfh > chip) is corrupting memory somehow after some misstep in > initialization/de-initialization? Also if you look at my report, you'll see I > have no devices/sensors detected by amd_sfh - I wonder if other reporters all > have this in common? (noted in dmesg output above from another user) Given that Basavaraj Natikar never really addressed Chris earlier report from months ago and the severeness of the problem I'd wonder if we should revert the culprit to resolve this quickly, unless some proper fix comes into sight soon. Sadly from a quick look that would require multiple reverts afaics. :-/ Ciao, Thorsten
