From: <dan.j.williams@intel.com>
To: Marc Herbert <marc.herbert@linux.intel.com>,
Smita Koralahalli <Smita.KoralahalliChannabasappa@amd.com>,
<linux-efi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-cxl@vger.kernel.org>
Cc: Ard Biesheuvel <ardb@kernel.org>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
"Ira Weiny" <ira.weiny@intel.com>,
Dan Williams <dan.j.williams@intel.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Yazen Ghannam <yazen.ghannam@amd.com>,
Terry Bowman <terry.bowman@amd.com>,
Dave Jiang <dave.jiang@intel.com>, <tony.luck@intel.com>,
Gregory Price <gourry@gourry.net>
Subject: Re: "invalid agent type: 1" in acpi/ghes, cper: Recognize and cache CXL Protocol errors
Date: Mon, 28 Jul 2025 08:01:36 -0700 [thread overview]
Message-ID: <688790d087cde_119681005b@dwillia2-mobl4.notmuch> (raw)
In-Reply-To: <8e67a97c-530d-4a1c-ab72-3992a6c5db83@linux.intel.com>
Marc Herbert wrote:
> On 2025-07-22 12:24, Marc Herbert wrote:
> > Hi Smita,
> >
> > The code below triggers the error "invalid agent type: 1" in Intel
> > validation (internal issue 15018133056)
>
> The same test case also triggers the other, warning message "CXL CPER no
> device serial number".
>
> I heard that "device" serial numbers are only for... devices and that
> even then it's not always mandatory. So maybe that other message should
> be downgraded from warning to the "info" level?
Agree. Care to send a fixup series?
This is a benefit / endorsement of your test updates [1] to catch
unexpected warn/err.
[1]: http://lore.kernel.org/20250611235256.3866724-1-marc.herbert@linux.intel.com
next prev parent reply other threads:[~2025-07-28 15:02 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 8:44 [PATCH v6 0/6] acpi/ghes, cper, cxl: Process CXL CPER Protocol errors Smita Koralahalli
2025-01-23 8:44 ` [PATCH v6 1/6] efi/cper, cxl: Prefix protocol error struct and function names with cxl_ Smita Koralahalli
2025-02-04 0:12 ` Fan Ni
2025-02-05 19:17 ` Gregory Price
2025-01-23 8:44 ` [PATCH v6 2/6] efi/cper, cxl: Make definitions and structures global Smita Koralahalli
2025-02-04 0:16 ` Fan Ni
2025-02-05 19:16 ` Gregory Price
2025-02-06 10:54 ` Jonathan Cameron
2025-02-06 16:14 ` Gregory Price
2025-02-06 17:14 ` Konstantin Ryabitsev
2025-02-06 17:32 ` Gregory Price
2025-01-23 8:44 ` [PATCH v6 3/6] efi/cper, cxl: Remove cper_cxl.h Smita Koralahalli
2025-02-04 0:20 ` Fan Ni
2025-02-05 19:18 ` Gregory Price
2025-01-23 8:44 ` [PATCH v6 4/6] acpi/ghes, cper: Recognize and cache CXL Protocol errors Smita Koralahalli
2025-02-03 18:59 ` Luck, Tony
2025-02-05 19:35 ` Gregory Price
2025-02-05 22:21 ` Dan Williams
2025-07-22 19:24 ` "invalid agent type: 1" in " Marc Herbert
2025-07-23 7:13 ` Marc Herbert
2025-07-24 14:49 ` Fabio M. De Francesco
2025-07-25 11:04 ` Jonathan Cameron
2025-07-28 15:01 ` dan.j.williams [this message]
2025-07-28 16:25 ` Koralahalli Channabasappa, Smita
2025-07-29 5:41 ` Marc Herbert
2025-07-29 15:52 ` Koralahalli Channabasappa, Smita
2025-07-29 17:39 ` dan.j.williams
2025-01-23 8:44 ` [PATCH v6 5/6] acpi/ghes, cxl/pci: Process CXL CPER Protocol Errors Smita Koralahalli
2025-02-03 19:03 ` Luck, Tony
2025-02-12 21:04 ` Koralahalli Channabasappa, Smita
2025-02-05 19:50 ` Gregory Price
2025-02-05 22:58 ` Dan Williams
2025-02-12 20:57 ` Koralahalli Channabasappa, Smita
2025-01-23 8:44 ` [PATCH v6 6/6] cxl/pci: Add trace logging for CXL PCIe Port RAS errors Smita Koralahalli
2025-01-24 16:36 ` Ira Weiny
2025-02-05 20:01 ` Gregory Price
2025-02-05 23:06 ` Dan Williams
2025-02-03 17:09 ` [PATCH v6 0/6] acpi/ghes, cper, cxl: Process CXL CPER Protocol errors Dave Jiang
2025-02-06 18:38 ` Dave Jiang
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=688790d087cde_119681005b@dwillia2-mobl4.notmuch \
--to=dan.j.williams@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=alison.schofield@intel.com \
--cc=ardb@kernel.org \
--cc=dave.jiang@intel.com \
--cc=gourry@gourry.net \
--cc=ira.weiny@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marc.herbert@linux.intel.com \
--cc=terry.bowman@amd.com \
--cc=tony.luck@intel.com \
--cc=vishal.l.verma@intel.com \
--cc=yazen.ghannam@amd.com \
/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