linux-kernel - Re: spd5118 driver occasionally produces erroneous values

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CACsxjPbnUKf9yeEbgVNLTNm=mP-_Lk0bT2LhWnA-21-E3PgFEA@mail.gmail.com>
Date: Fri, 21 Nov 2025 04:17:58 +1100
From: ‍小太 <nospam@...a.moe>
To: Armin Wolf <W_Armin@....de>
Cc: Guenter Roeck <linux@...ck-us.net>, linux-kernel@...r.kernel.org, 
	linux-hwmon@...r.kernel.org
Subject: Re: spd5118 driver occasionally produces erroneous values

On Fri, 21 Nov 2025 at 03:07, Armin Wolf <W_Armin@....de> wrote:
>
> Can you share the output of "dmesg"?

I've attached my full dmesg log

Here's a snippet with just the i2c lines

[    0.322130] i2c i2c-3: Failed to register i2c client ITE8853:01 at 0x40 (-16)
[    4.186803] usb 7-10: Product: i2c-tiny-usb
[   69.398654] i2c_dev: i2c /dev entries driver
[   69.449382] i2c i2c-7: adapter quirk: no zero length (addr 0x0018,
size 0, write)
[   69.450495] i2c i2c-7: adapter quirk: no zero length (addr 0x0019,
size 0, write)
[   69.450835] i2c i2c-7: adapter quirk: no zero length (addr 0x001a,
size 0, write)
[   69.451133] i2c i2c-7: adapter quirk: no zero length (addr 0x001b,
size 0, write)
[   69.451408] i2c i2c-7: adapter quirk: no zero length (addr 0x001c,
size 0, write)
[   69.451657] i2c i2c-7: adapter quirk: no zero length (addr 0x001d,
size 0, write)
[   69.451890] i2c i2c-7: adapter quirk: no zero length (addr 0x001e,
size 0, write)
[   69.452108] i2c i2c-7: adapter quirk: no zero length (addr 0x001f,
size 0, write)
[   69.452320] i2c i2c-8: adapter quirk: no zero length (addr 0x0018,
size 0, write)
[   69.452535] i2c i2c-8: adapter quirk: no zero length (addr 0x0019,
size 0, write)
[   70.514088] i2c-tiny-usb 7-10:1.0: version 2.01 found at bus 007 address 008
[   70.527063] i2c i2c-0: new_device: Instantiated device spd5118 at 0x50
[   70.533038] i2c i2c-0: new_device: Instantiated device spd5118 at 0x52
[   70.538641] i2c i2c-1: new_device: Instantiated device spd5118 at 0x50
[   70.547163] i2c i2c-1: new_device: Instantiated device spd5118 at 0x52
[   70.632683] i2c i2c-16: connected i2c-tiny-usb device
[   70.633821] usbcore: registered new interface driver i2c-tiny-usb
[   70.816736] i2c i2c-16: new_device: Instantiated device max6698 at 0x1c
[  372.852782] i2c_designware AMDI0010:01: timeout in disabling adapter
[  867.404574] i2c_designware AMDI0010:02: timeout in disabling adapter
[ 1930.415660] i2c_designware AMDI0010:01: timeout in disabling adapter
[ 2472.401446] i2c_designware AMDI0010:01: timeout in disabling adapter
[ 3502.860186] i2c_designware AMDI0010:01: timeout in disabling adapter
[ 5490.395984] i2c_designware AMDI0010:02: timeout in disabling adapter
[ 5947.521600] i2c_designware AMDI0010:01: timeout in disabling adapter
[ 6259.677005] i2c_designware AMDI0010:02: timeout in disabling adapter
[ 7670.424328] i2c_designware AMDI0010:01: timeout in disabling adapter
[ 8173.714358] i2c_designware AMDI0010:02: timeout in disabling adapter
[10705.679828] i2c_designware AMDI0010:02: timeout in disabling adapter
[11987.681353] i2c_designware AMDI0010:01: timeout in disabling adapter
[12559.704756] i2c_designware AMDI0010:01: timeout in disabling adapter
[12995.593960] i2c_designware AMDI0010:01: timeout in disabling adapter
[13526.433816] i2c_designware AMDI0010:01: timeout in disabling adapter

>
> Personally i suspect that the SPD hub is faulty, as according to [1] HWiNFO
> seems to simply filter out suspicious temperature values.
>
> [1] https://www.hwinfo.com/forum/threads/ddr5-spd-hub-temperature-occasionally-spiking.8976/

The values mentioned in that thread don't seem to match with the
erroneous values I'm seeing.
In fact the erroneous values I'm seeing don't even appear to be consistent

If the SPD hub is faulty, it would be a systemic failure right?
Since these 4 sticks are all brand new (and EXPO not enabled yet),
though of the same batch

View attachment "dmesg.log" of type "text/x-log" (179087 bytes)