Alex Deucher <alexander.deucher@amd.com> 2017-03-08 18:25:15 -0500 drm/amdgpu: expose GPU sensor related information commit 5ebbac4b5c9159130046bf7c56b7f4c71ca7d1b7 This particular commit introduced this error. $ sensors -j { "amdgpu-pci-0008":{ "Adapter": "PCI adapter", "vddgfx":{ ERROR: Can't get value of subfeature in0_input: Can't read }, "vddnb":{ ERROR: Can't get value of subfeature in1_input: Can't read }, "temp1":{ "temp1_input": 12.000, "temp1_crit": 120.000, "temp1_crit_hyst": 90.000 } }, "it8603-isa-0290":{ "Adapter": "ISA adapter", "CPU Fan":{ "fan1_input": 2509.000, "fan1_min": 200.000, "fan1_alarm": 0.000 }, "Mobo Fan":{ "fan2_input": 0.000, "fan2_min": 600.000, "fan2_alarm": 1.000 }, "AMD A6-7400K Radeon R5":{ "temp1_input": 44.000, "temp1_max": 127.000, "temp1_min": -45.000, "temp1_alarm": 0.000, "temp1_type": 4.000, "temp1_offset": 0.000 }, "Asus A68HM-K Mobo":{ "temp2_input": 45.000, "temp2_max": -33.000, "temp2_min": 53.000, "temp2_alarm": 1.000, "temp2_type": 4.000, "temp2_offset": 0.000 } } }
That commit just exposes the temperature via an ioctl interface. It doesn't affect the hwmon sysfs API. How did you determine that that was the problematic one?
It wasn't the case before when VDDGFX and VDDNB were not exposed. Are these (and the missing in0_input/in1_input probes) present on APUs?
What chip do you have? Voltage hwmon is not implemented on all APUs.
AMD A6-7400K Radeon R5
(In reply to Bong Cosca from comment #4) > AMD A6-7400K Radeon R5 No hwmon support for voltage on that family.
So does it make sense to expose VDDGFX and VDDNB at all? Or should this be fixed in lm_sensors?
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/779.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.