linux-kernel - Re: Suspend/resume failing due to SPD5118

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <310fe3a3-e585-46e0-aae7-3e4d41af1f53@roeck-us.net>
Date: Sun, 4 May 2025 16:31:31 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Luca Carlon <carlon.luca@...il.com>, w_armin@....de
Cc: jdelvare@...e.com, linux-hwmon@...r.kernel.org,
 linux-kernel@...r.kernel.org, lucas.demarchi@...el.com
Subject: Re: Suspend/resume failing due to SPD5118

On 5/4/25 11:41, Luca Carlon wrote:
...
> When I was told that the problem may lie in the i2c bus, I started to search elsewhere
> and this thread came up: https://bugzilla.kernel.org/show_bug.cgi?id=213345. I
> therefore provided in that thread some more info I collected.
> 

 From there:

[    5.416572] i801_smbus 0000:00:1f.4: SPD Write Disable is set

I think you are out of luck. The above is incompatible with spd5118 devices;
See [1] for details. I don't immediately see why that would cause the i2c bus
to lock up, but even if it didn't lock up the bus I don't see a means to get
this to work.

It is still puzzling that reading the i2c data using i2cdump fails. The spd5118
driver should not even probe if that is the case. Maybe Armin has an idea.

Guenter

---
[1] https://lore.kernel.org/linux-i2c/20250430-for-upstream-i801-spd5118-no-instantiate-v2-0-2f54d91ae2c7@canonical.com/