Jonas Malaco
Jonas Malaco
Can you paste the complete output with `--debug`?
The problem doesn't appear to be related to any particular device supported by liquidctl. Likewise, changing the argument from `'eeprom'` to some other string, while it's a workaround of sorts,...
Thanks, @FeRChImoNdE. It makes sense to be related to the `i801_smbus` (bus). Can you run and paste the output from `sudo decode-dimms`?
Also, I'm guessing that's a DDR5 system, right? And can you also paste the output from `sudo lsmod`?
spd5118 is the hwmon driver, but the issue here is with the general access to SPD data, which used to be done at the eeprom level. `decode-dimms` not being able...
@FeRChImoNdE Can you execute: ``` cat /sys/bus/i2c/devices/i2c-6/0-005*/name ls -l /sys/bus/i2c/devices/i2c-6/0-005*/driver ```
Thanks, I'll take a look. But you were right that the driver we're dealing with is spd5118.
The problem might be related to torvalds/linux@79d0df36b541 ([lore](https://lore.kernel.org/all/[email protected]/)). If that's the case, it should affect me too, as soon as 6.11 lands in ArchLinux. So I'll wait for that, as...
I've been taking another look at this. ~~Can you check if the `eeprom` file is readable (both directly or during liquidctl probing) once the spd5118 is unloaded?~~ Nevermind, the `eeprom`...
The problem has been mitigated in b3913d0. I originally intended to also check whether exposing an unreadable and therefore useless attribute could be considered a kernel bug, and propose a...