Bug#1011091: Systems with more than 4 memory slots not supported yet, not instantiating SPD

2022-05-19 Thread Diederik de Haas
Control: forwarded -1 
https://lore.kernel.org/linux-i2c/3837611652787...@vla1-3991b5027d7d.qloud-c.yandex.net/

On Thursday, 19 May 2022 18:45:04 CEST Diederik de Haas wrote:
> Control: forwarded -1 https://www.spinics.net/lists/linux-i2c/msg56885.html

Updated forwarded to lore.kernel.org address as that's better IMO.

signature.asc
Description: This is a digitally signed message part.


Bug#1011091: Systems with more than 4 memory slots not supported yet, not instantiating SPD

2022-05-19 Thread Diederik de Haas
Control: forwarded -1 https://www.spinics.net/lists/linux-i2c/msg56885.html

On Thursday, 19 May 2022 18:30:49 CEST Сергей Фёдоров wrote:
> So far I haven't received a response from any of the four:

It sometimes takes a while.

> But if I get an answer, then I still don't understand how I should tell BTS.

The first line of this email informed the BTS of the upstream conversation, so 
you don't have to do anything more (wrt that).

> will anyone from BTS read it?

All messages to the BTS are (also) send to the maintainer(s), that's how I 
noticed your issue to begin with :)

signature.asc
Description: This is a digitally signed message part.


Bug#1011091: Systems with more than 4 memory slots not supported yet, not instantiating SPD

2022-05-18 Thread Diederik de Haas
On Tuesday, 17 May 2022 14:12:45 CEST Сергей Фёдоров wrote:
> I have sent 4 emails to the addresses that you have informed me.
> In what format should I inform BTS about this?

With an URL to a ML post about it, send a message to 1011...@bug.debian.org 
with all the info on 1 line as the first (or only) line, like this:
Control: forwarded -1 

signature.asc
Description: This is a digitally signed message part.


Bug#1011091: Systems with more than 4 memory slots not supported yet, not instantiating SPD

2022-05-17 Thread Сергей Фёдоров
I have sent 4 emails to the addresses that you have informed me.
In what format should I inform BTS about this?



Bug#1011091: Systems with more than 4 memory slots not supported yet, not instantiating SPD

2022-05-16 Thread Diederik de Haas
I had made the following draft, which contains some additional info to which 
you should send your upstream request (it's a bit more then Ben suggested):

On Monday, 16 May 2022 17:45:08 CEST Сергей Фёдоров wrote:
>  I rebuilt the kernel with changing to
> "./linux-source-5.17.6-1/drivers/i2c/i2c-smbus.c"
> 
> line 358:
>   if (slot_count > 4) {
>   dev_warn(>dev,
>"Systems with more than 4 memory slots not 
>supported yet, not instantiating SPD\n"); 
>return;
>   }
> 
> replaced with
>   if (slot_count > 8) {
>   dev_warn(>dev,
>"Systems with more than 8 memory slots not
>supported yet, not instantiating SPD\n"); 
>return;
>   }
> 

The 4 slot limit was specified in 5ace60859e84113b7a185c117fbf2c429d381b59
(upstream commit ID) and the secondary commit message had this:
"Start with just DDR2, DDR3 and DDR4 on x86 for now, and only for systems with
no more than 4 memory slots. These limitations may be lifted later."

This is an upstream issue and a change to '8' should be discussed there.

~/dev/kernel.org/linux$ ./scripts/get_maintainer.pl drivers/i2c/i2c-smbus.c
Wolfram Sang  (maintainer:I2C SUBSYSTEM)
linux-...@vger.kernel.org (open list:I2C SUBSYSTEM)
linux-ker...@vger.kernel.org (open list)

So I'd suggest to send it to linux-...@vger.kernel.org and add the other
2 addresses in the CC and also add "Jean Delvare " to the 
TO or CC as that was the original author of the aforementioned commit.

Could you 'forward' your issue there and if/when done so, notify the BTS of
where that has taken place? Then we can follow its progress as well.


signature.asc
Description: This is a digitally signed message part.


Bug#1011091: Systems with more than 4 memory slots not supported yet, not instantiating SPD

2022-05-16 Thread Ben Hutchings
Control: reassign -1 src:linux 5.17.6-1
Control: forcemerge 1001286 -1
Control: tag -1 upstream

On Mon, 2022-05-16 at 21:55 +0300, Сергей Фёдоров wrote:
> Package: linux-source-5.17
> Version: 5.17.6-1
> Severity: normal
> 
> Dear Maintainer,
> 
> 
> Problems:
> 
> I already wrote about it 07 Dec 2021 21:15:07 +
> (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D1001286 ),
> but so far nothing has changed.
[...]

So there's no need to open a new bug report.

Please contact the upstream maintainers about this at
.

Ben.

-- 
Ben Hutchings
Man invented language to satisfy his deep need to complain.
  - Lily Tomlin


signature.asc
Description: This is a digitally signed message part


Bug#1011091: Systems with more than 4 memory slots not supported yet, not instantiating SPD

2022-05-16 Thread Сергей Фёдоров
Package: linux-source-5.17
Version: 5.17.6-1
Severity: normal

Dear Maintainer,


Problems:

I already wrote about it 07 Dec 2021 21:15:07 +
(https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D1001286 ),
but so far nothing has changed.

1. Systems with more than 4 memory slots not supported yet, not instantiating 
SPD.
Now I have made it so that the system sees 8 slots, as described below, but I 
do not see SPD.

2. Kingston memory slots do not appear on the I2C bus, although I see them in 
the BIOS and can
change their parameters. Nevertheless, Linux works fine.


# decode-dimms
# decode-dimms version 4.3-2

Memory Serial Presence Detect Decoder
By Philip Edelbrock, Christian Zuckschwerdt, Burkart Lingner,
Jean Delvare, Trent Piepho and others

No EEPROM found, the kernel probably does not support your hardware.


Motherboard Asus P9X79pro 2011 year
Chipset: Intel X79 Express Chipset

8 memory slots

8xDIMM. max 64 GB, DDR3 2400(O.C.)/2133(O.C.)/1866/1600/1033/1066 Mhz, non-ECC,
un-buffered memory

Quad channel memory architecture
Supports Intel Extreme Memory Profile (XMP)

Hyper DIMM support is subject to the physical characteristics of infividual 
CPUs.

Processor: Intel(R) Core(TM) i7-3820 CPU @ 3.60GHz
Overclocked to 4.400 GHz with stepping 44.

For memory strips:
Kingston HyperX Fury HX316C10FRK2/16  2x8Gb
Kingston HyperX Fury HX316C10FWK2/16  2x8Gb
Kingston HyperX  KHX16C10B1R/84x8Gb

I believe there are enough motherboards with 8 memory slots.

Debian-11.3.0 64 Sid

Kernel: Linux Linux 5.17.6-1 SMP PREEMPT (SMP w/8 CPU threads) x86_64 GNU/Linux

Kernel driver i2c-i801
Intel Patsburg (PCH)


/var/log/messages

Dec  3 05:28:15 A1 kernel: [1.322527] i801_smbus :00:1f.3: SMBus using 
PCI interrupt
Dec  3 05:28:15 A1 kernel: [1.322911] i2c i2c-0: 4/8 memory slots populated 
(from DMI)
Dec  3 05:28:15 A1 kernel: [1.322914] i2c i2c-0: Systems with more than 4 
memory slots not supported yet, not instantiating SPD

/var/log/syslog

Dec  3 05:28:15 A1 kernel: [1.322527] i801_smbus :00:1f.3: SMBus using 
PCI interrupt
Dec  3 05:28:15 A1 kernel: [1.322911] i2c i2c-0: 4/8 memory slots populated 
(from DMI)
Dec  3 05:28:15 A1 kernel: [1.322914] i2c i2c-0: Systems with more than 4 
memory slots not supported yet, not instantiating SPD

/var/log/kern.log

Dec  3 05:28:15 A1 kernel: [1.322527] i801_smbus :00:1f.3: SMBus using 
PCI interrupt
Dec  3 05:28:15 A1 kernel: [1.322911] i2c i2c-0: 4/8 memory slots populated 
(from DMI)
Dec  3 05:28:15 A1 kernel: [1.322914] i2c i2c-0: Systems with more than 4 
memory slots not supported yet, not instantiating SPD

Viewing log-in led to the idea that so far
Systems with more than 4 memory slots not supported yet, not instantiating SPD

I rebuilt the kernel by changing to 
"./linux-source-5.17.6-1/drivers/i2c/i2c-smbus.c"

line 358:
if (slot_count > 4) {
dev_warn(>dev,
 "Systems with more than 4 memory slots not supported 
yet, not instantiating SPD\n");
return;
}
на
replace with
if (slot_count > 8) {
dev_warn(>dev,
 "Systems with more than 8 memory slots not supported 
yet, not instantiating SPD\n");
return;
}

and now it is written in the logs:

May 12 23:22:33 A1 kernel: [4.094892] i801_smbus :00:1f.3: SMBus using 
PCI interrupt
May 12 23:22:33 A1 kernel: [4.095301] i2c i2c-0: 8/8 memory slots populated 
(from DMI)

For some reason, at least one file is not created automatically in 
"/sys/bus/i2c/drivers/"
for I2C devices "/^\d+-[\da-f]+$/i" like 0-0050 or 2-0051
with a description of the memory parameters.


/etc/modules-load.d/:
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# we use any of the following three to choose from
# eeprom at24 ee1004
eeprom
i2c_i801
i2c_smbus
i2c-dev


# lsmod | sort -u

aesni_intel   380928  0
ahci   49152  10
asus_wmi   61440  1 eeepc_wmi
autofs453248  2
battery28672  1 asus_wmi
button 24576  1 nouveau
cec61440  1 drm_kms_helper
configfs   57344  1
coretemp   20480  0
crc16  16384  1 ext4
crc32c_generic 16384  0
crc32c_intel   24576  18