linux-kernel - Re: [PATCH v4 5/6] i2c: smbus: Support DDR5 SPD EEPROMs

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]

Date: Tue, 18 Jun 2024 06:32:16 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Paul Menzel <pmenzel@...gen.mpg.de>
Cc: linux-hwmon@...r.kernel.org, linux-i2c@...r.kernel.org,
 linux-kernel@...r.kernel.org, devicetree@...r.kernel.org,
 Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Wolfram Sang <wsa+renesas@...g-engineering.com>,
 René Rebe <rene@...ctcode.de>,
 Thomas Weißschuh <linux@...ssschuh.net>,
 Armin Wolf <W_Armin@....de>, Stephen Horvath <s.horvath@...look.com.au>
Subject: Re: [PATCH v4 5/6] i2c: smbus: Support DDR5 SPD EEPROMs

Hi Paul,

On 6/18/24 03:25, Paul Menzel wrote:
[ ... ]
> 
>      $ ls -l /sys/bus/i2c/drivers/spd5118/0-0050/eeprom
>      -r--r--r-- 1 root root 1024 Jun 18 12:17 /sys/bus/i2c/drivers /spd5118/0-0050/eeprom
>      $ cp /sys/bus/i2c/drivers/spd5118/0-0050/eeprom /tmp
>      cp: error reading '/sys/bus/i2c/drivers/spd5118/0-0050/eeprom': No such device or address

That suggests that the i801 driver got an error when trying some chip operation.
Unfortunately I have no idea what that error or the failed operation might be.

>      $ od -t x1 /sys/bus/i2c/drivers/spd5118/0-0050/eeprom
>      od: /sys/bus/i2c/drivers/spd5118/0-0050/eeprom: read error: No such device or address
>      0000000
> 
>> sudo i2cdump -y -f 0 0x50
> 
>      $ sudo LD_LIBRARY_PATH=~/src/i2c-tools/lib tools/i2cdump -y -f 0 0x50
>      No size specified (using byte-data access)
>      Error: Could not open file `/dev/i2c-0' or `/dev/i2c/0': No such file or directory
> 
This should work after you load the "i2c-dev" module.

If you get it to work, please provide the output. Maybe it helps tracking down
the problem.

Thanks,
Guenter