From: Alison Schofield <alison.schofield@intel.com>
To: Coly Li <colyli@suse.de>
Cc: nvdimm@lists.linux.dev, linux-cxl@vger.kernel.org
Subject: Re: Removing a misleading warning message?
Date: Thu, 17 Oct 2024 07:56:03 -0700 [thread overview]
Message-ID: <ZxElg0RC_S1TY2cd@aschofie-mobl2.lan> (raw)
In-Reply-To: <15237B14-B55B-4737-9A98-D76AEDB4AEAD@suse.de>
+ 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.
> 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
next prev parent reply other threads:[~2024-10-17 14:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-11 9:58 Removing a misleading warning message? Coly Li
2024-10-17 14:56 ` Alison Schofield [this message]
2024-10-18 10:22 ` Jonathan Cameron
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
-- strict thread matches above, loose matches on Subject: below --
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=ZxElg0RC_S1TY2cd@aschofie-mobl2.lan \
--to=alison.schofield@intel.com \
--cc=colyli@suse.de \
--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 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.