From: Luca Carlon <carlon.luca@gmail.com>
To: w_armin@gmx.de
Cc: carlon.luca@gmail.com, jdelvare@suse.com,
linux-hwmon@vger.kernel.org, linux-kernel@vger.kernel.org,
linux@roeck-us.net, lucas.demarchi@intel.com
Subject: Re: Suspend/resume failing due to SPD5118
Date: Sun, 4 May 2025 20:41:17 +0200 [thread overview]
Message-ID: <20250504184117.4795-1-carlon.luca@gmail.com> (raw)
In-Reply-To: <9625330e-e3e9-49ea-9979-653091dfbe16@gmx.de>
> Please you load the i2c-dev module (sudo modprobe i2c-dev) and share the results of the following commands:
>
> sudo i2cdump 1 0x50
> sudo i2cdump 1 0x51
>
> This should return the register contents of the spd5118 devices. Please make sure that the spd5118 driver
> as been blacklisted and unloaded before executing those commands.
Hello,
I followed what you asked:
# lsmod | grep spd
# modprobe i2c-dev
# lsmod | grep i2c
i2c_algo_bit 24576 2 xe,i915
i2c_i801 40960 0
i2c_smbus 20480 1 i2c_i801
i2c_mux 16384 1 i2c_i801
i2c_hid_acpi 12288 0
i2c_hid 45056 1 i2c_hid_acpi
i2c_dev 28672 0
# i2cdump 1 0x50
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1, address 0x50, mode byte
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
80: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
90: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
a0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
b0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
c0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
d0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
e0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
f0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
# i2cdump 1 0x51
No size specified (using byte-data access)
WARNING! This program can confuse your I2C bus, cause data loss and worse!
I will probe file /dev/i2c-1, address 0x51, mode byte
Continue? [Y/n]
0 1 2 3 4 5 6 7 8 9 a b c d e f 0123456789abcdef
00: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
10: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
20: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
30: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
40: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
50: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
60: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
70: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
80: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
90: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
a0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
b0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
c0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
d0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
e0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
f0: XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XX XXXXXXXXXXXXXXXX
> Could you also please tell us the name of the RAM sticks you are using?
Of course. I have two 32GB modules. One was provided with the machine and it
would be difficult for me to reach that physically. The other one is simple
to reach and I installed it myself: it is marketed as Crucial CL46 - CT32G56C46S5.
This is what I can get from dmidecode:
Handle 0x0002, DMI type 17, 92 bytes
Memory Device
Array Handle: 0x0001
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 32 GB
Form Factor: SODIMM
Set: None
Locator: Controller0-ChannelA/B-DIMM0
Bank Locator: BANK 0/1
Type: DDR5
Type Detail: Synchronous
Speed: 5600 MT/s
Manufacturer: Micron Technology
Serial Number: E97A5953
Asset Tag: None
Part Number: CT32G56C46S5.C16D
Rank: 2
Configured Memory Speed: 3600 MT/s
Minimum Voltage: Unknown
Maximum Voltage: Unknown
Configured Voltage: 1.1 V
Memory Technology: DRAM
Memory Operating Mode Capability: Volatile memory
Firmware Version: Not Specified
Module Manufacturer ID: Bank 1, Hex 0x2C
Module Product ID: Unknown
Memory Subsystem Controller Manufacturer ID: Unknown
Memory Subsystem Controller Product ID: Unknown
Non-Volatile Size: None
Volatile Size: 32 GB
Cache Size: None
Logical Size: None
Handle 0x0003, DMI type 17, 92 bytes
Memory Device
Array Handle: 0x0001
Error Information Handle: Not Provided
Total Width: 64 bits
Data Width: 64 bits
Size: 32 GB
Form Factor: SODIMM
Set: None
Locator: Controller0-ChannelA/B-DIMM1
Bank Locator: BANK 0/1
Type: DDR5
Type Detail: Synchronous
Speed: 5600 MT/s
Manufacturer: SK Hynix
Serial Number: 2C3B11DE
Asset Tag: None
Part Number: HMCG88AGBSA095N
Rank: 2
Configured Memory Speed: 3600 MT/s
Minimum Voltage: Unknown
Maximum Voltage: Unknown
Configured Voltage: 1.1 V
Memory Technology: DRAM
Memory Operating Mode Capability: Volatile memory
Firmware Version: Not Specified
Module Manufacturer ID: Bank 1, Hex 0xAD
Module Product ID: Unknown
Memory Subsystem Controller Manufacturer ID: Unknown
Memory Subsystem Controller Product ID: Unknown
Non-Volatile Size: None
Volatile Size: 32 GB
Cache Size: None
Logical Size: None
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.
Please let me know if I did something wrong.
Thank you.
Luca Carlon
next prev parent reply other threads:[~2025-05-04 18:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 22:59 Suspend/resume failing due to SPD5118 Lucas De Marchi
2024-12-20 1:20 ` Guenter Roeck
2025-05-02 23:07 ` carlon.luca
2025-05-02 23:51 ` Armin Wolf
2025-05-03 0:33 ` Luca Carlon
2025-05-03 0:14 ` Guenter Roeck
2025-05-03 0:58 ` Luca Carlon
2025-05-03 1:40 ` Guenter Roeck
2025-05-04 16:59 ` Armin Wolf
2025-05-04 18:41 ` Luca Carlon [this message]
2025-05-04 23:31 ` Guenter Roeck
2025-05-05 0:27 ` Armin Wolf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250504184117.4795-1-carlon.luca@gmail.com \
--to=carlon.luca@gmail.com \
--cc=jdelvare@suse.com \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lucas.demarchi@intel.com \
--cc=w_armin@gmx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox