From: "Luck, Tony" <tony.luck@intel.com>
To: Koba Ko <koba.ko@canonical.com>
Cc: Markus Elfring <Markus.Elfring@web.de>,
"linux-edac@vger.kernel.org" <linux-edac@vger.kernel.org>,
"kernel-janitors@vger.kernel.org"
<kernel-janitors@vger.kernel.org>, Borislav Petkov <bp@alien8.de>,
"James Morse" <james.morse@arm.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Robert Richter <rric@kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] EDAC/i10nm: shift exponent is negative
Date: Tue, 4 Jul 2023 03:14:45 +0000 [thread overview]
Message-ID: <1D7C9A01-C95A-429C-AC06-94D6188BC4EC@intel.com> (raw)
In-Reply-To: <CAJB-X+UB+eYoYOOVH2bqnnVEJcLrxaj5A7-zyfgBM7hOf4y8zw@mail.gmail.com>
Interesting. This isn’t some odd shaped DIMM.
You are just getting a failed read from the register.
So trying to decode all-ones.
I’ll try to look at the full log you linked when I’m
on a computer instead of a phone.
> [ 4.032335] EDAC DEBUG: skx_get_dimm_attr: bad ranks = 3 (raw=0xffffffff)
> [ 4.032337] EDAC DEBUG: skx_get_dimm_attr: bad rows = 7 (raw=0xffffffff)
> [ 4.032338] EDAC DEBUG: skx_get_dimm_attr: bad cols = 3 (raw=0xffffffff)
next prev parent reply other threads:[~2023-07-04 3:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 16:25 [PATCH][V2] " Koba Ko
[not found] ` <4ec2b7d2-11a5-6ab6-087a-175ed31faca4@web.de>
2023-07-03 21:51 ` [PATCH v2] " Luck, Tony
2023-07-04 1:50 ` Koba Ko
2023-07-04 3:14 ` Luck, Tony [this message]
2023-07-05 4:08 ` Luck, Tony
2023-07-05 8:45 ` Koba Ko
2023-07-05 15:22 ` Luck, Tony
2023-07-06 14:11 ` Zhuo, Qiuxu
2023-07-06 17:40 ` Koba Ko
2023-07-07 3:34 ` Zhuo, Qiuxu
2023-07-09 15:42 ` Koba Ko
2023-07-10 1:18 ` Zhuo, Qiuxu
2023-07-10 6:25 ` Dan Carpenter
2023-07-10 8:08 ` Zhuo, Qiuxu
2023-07-04 2:20 ` Koba Ko
2023-07-04 4:59 ` Koba Ko
[not found] ` <9c27530e-21f9-15ce-5116-5af5b0c25f53@web.de>
2023-07-04 8:05 ` Koba Ko
2023-07-04 8:17 ` Koba Ko
[not found] ` <706f49e8-d536-651a-2f19-394518633b53@web.de>
2023-07-04 8:59 ` [v2/v3] " Koba Ko
2023-07-04 12:02 ` [PATCH][V2] " Dan Carpenter
2023-07-04 12:32 ` Koba Ko
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=1D7C9A01-C95A-429C-AC06-94D6188BC4EC@intel.com \
--to=tony.luck@intel.com \
--cc=Markus.Elfring@web.de \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=koba.ko@canonical.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=rric@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®