From: Jean Delvare <jdelvare@suse.de>
To: Al Ma <AlMa0@ro.ru>
Cc: 1110749@bugs.debian.org, linux-i2c@vger.kernel.org
Subject: Re: ee1004: DDR4 SPD cannot be read, decode-dimms fails, “Failed to select page 0 (-6)”
Date: Fri, 11 Sep 2026 13:56:04 +0200 [thread overview]
Message-ID: <20260911135604.6c2451e7@endymion> (raw)
In-Reply-To: <812847a5-5630-4d26-8012-c816e6d1db32@ro.ru>
On Sun, 30 Aug 2026 17:35:57 +0200, Al Ma wrote:
> > Please try unloading the ee1004 driver, then running i2cdetect again.
>
> Here we go:
>
> # modprobe -r ee1004 && i2cdetect -y 0 && modprobe ee1004
> 0 1 2 3 4 5 6 7 8 9 a b c d e f
> 00: 08 -- -- -- -- -- -- --
> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 40: -- -- -- -- 44 -- -- -- -- -- -- -- -- -- -- --
> 50: -- -- -- -- -- -- 56 -- -- -- -- -- -- -- -- --
> 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 70: -- -- -- -- -- -- -- --
>
> What next?
This confirms my guess that the device at 0x56 is not an SPD EEPROM.
Next steps would be as follows:
* Short term, you want to blacklist the ee1004 driver on your system.
It is not a good idea to load a driver which binds to the wrong
device.
* Still short term, we should look into the ee1004 auto-detection logic
and see it it can be made more reliable.
* Mid term, we may want to add a kernel option to disable automatic
probing of SPD EEPROMs. I seem to recall some proposals but it looks
like they never made it into the upstream kernel. I'm not sure if
this should be a system-wide switch (handled by the i2c core) or a
per-driver setting (e.g. a new flag in i2c-i801's disable_features
parameter).
* Still mid term, we probably want to blacklist SPD probing explicitly
for your motherboard (we'll need to know the contents of
/sys/devices/virtual/dmi/id/board_vendor and
/sys/devices/virtual/dmi/id/board_name on your system). Maybe this
can be implemented as an empty entry in mux_dmi_table (as in, we know
the board requires multiplexing, but we don't know yet to implement
it on that board).
* Long term, we need the hardware vendor to provide technical
information about the board so that we can implement SMBus
multiplexing support in the i2c-i801 driver (if that's really how
things are implemented on your board - that's only a guess from me at
this point). Asus provided information about their Z8 series long ago
and I was able to add support for it back then. It would be wonderful
if they could provide similar information about the WS C422 PRO/SE so
that a kernel developer can add support.
--
Jean Delvare
SUSE L3 Support
next prev parent reply other threads:[~2026-09-11 11:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ff6982d3-cf60-436b-9107-420924cdabe3@ro.ru>
[not found] ` <handler.1110749.B.1754853823932687.ack@bugs.debian.org>
2026-08-25 0:31 ` ee1004: DDR4 SPD cannot be read, decode-dimms fails, “Failed to select page 0 (-6)” Al Ma
2026-08-30 11:07 ` Jean Delvare
2026-08-30 15:35 ` Al Ma
2026-09-11 11:56 ` Jean Delvare [this message]
2026-09-11 20:33 ` Al Ma
2026-09-23 14:06 ` Bug#1110749: " Uwe Kleine-König
2026-09-26 13:59 ` Al Ma
2026-09-26 14:04 ` Typo correction: " Al Ma
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=20260911135604.6c2451e7@endymion \
--to=jdelvare@suse.de \
--cc=1110749@bugs.debian.org \
--cc=AlMa0@ro.ru \
--cc=linux-i2c@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.