public inbox for linux-cxl@vger.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Alison Schofield <alison.schofield@intel.com>
Cc: Coly Li <colyli@suse.de>, <nvdimm@lists.linux.dev>,
	<linux-cxl@vger.kernel.org>, "Bowman, Terry" <kibowman@amd.com>
Subject: Re: Removing a misleading warning message?
Date: Fri, 18 Oct 2024 11:22:10 +0100	[thread overview]
Message-ID: <20241018112210.00004179@Huawei.com> (raw)
In-Reply-To: <ZxElg0RC_S1TY2cd@aschofie-mobl2.lan>

On Thu, 17 Oct 2024 07:56:03 -0700
Alison Schofield <alison.schofield@intel.com> wrote:

> + linux-cxl mailing list
> 
> On Fri, Oct 11, 2024 at 05:58:52PM +0800, Coly Li wrote:
> > Hi list,
> > 
> > Recently I have a report for a warning message from CXL subsystem,
> > [ 48.142342] cxl_port port2: Couldn't locate the CXL.cache and CXL.mem capability array header.
> > [ 48.144690] cxl_port port3: Couldn't locate the CXL.cache and CXL.mem capability array header.
> > [ 48.144704] cxl_port port3: HDM decoder capability not found
> > [ 48.144850] cxl_port port4: Couldn't locate the CXL.cache and CXL.mem capability array header.
> > [ 48.144859] cxl_port port4: HDM decoder capability not found
> > [ 48.170374] cxl_port port6: Couldn't locate the CXL.cache and CXL.mem capability array header.
> > [ 48.172893] cxl_port port7: Couldn't locate the CXL.cache and CXL.mem capability array header.
> > [ 48.174689] cxl_port port7: HDM decoder capability not found
> > [ 48.175091] cxl_port port8: Couldn't locate the CXL.cache and CXL.mem capability array header.
> > [ 48.175105] cxl_port port8: HDM decoder capability not found
> > 
> > After checking the source code I realize this is not a real bug, just a warning message that expected device was not detected.

I'd like to understand a little more about the hardware.
Superficially this looks to be a screaming about non spec compliant (i.e. broken) ports.

Are these on a switch or all root ports?  What is connected to the ports?

Understanding what exactly is going on may affect how this is suppressed (which seems
reasonable to do if this is production hardware).

There have been a few mentions of 'late' register validity on specific root ports. Maybe
that is going on here? +CC Terry.

Jonathan 

> > But from the above warning information itself, users/customers are worried there is something wrong (IMHO indeed not).
> > 
> > Is there any chance that we can improve the code logic that only printing out the warning message when it is really a problem to be noticed? 
> > 
> > Thanks in advance.
> > 
> > Coly Li   
> 


  reply	other threads:[~2024-10-18 10:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <15237B14-B55B-4737-9A98-D76AEDB4AEAD@suse.de>
2024-10-17 14:56 ` Removing a misleading warning message? Alison Schofield
2024-10-18 10:22   ` Jonathan Cameron [this message]
2024-10-18 19:32   ` Dan Williams
2024-10-21  5:05     ` Coly Li
2024-12-09  4:02     ` Li Ming
2024-12-10 20:30       ` Dan Williams
2024-12-11 14:48         ` Li Ming
2024-10-14  7:12 Coly Li

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=20241018112210.00004179@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --cc=alison.schofield@intel.com \
    --cc=colyli@suse.de \
    --cc=kibowman@amd.com \
    --cc=linux-cxl@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    /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