From: Mitar <mitar.git@tnode.com>
To: saverio.pub2@gmail.com
Cc: bhelgaas@google.com, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI/DOE: Add debug messages for transaction failures
Date: Wed, 4 Nov 2026 00:29:22 +0100 [thread overview]
Message-ID: <20261103232922.252762-1-mitar.git@tnode.com> (raw)
In-Reply-To: <20260721193310.1179300-1-saverio.pub2@gmail.com>
Hi!
On Tue, Jul 21, 2026, Saverio Miroddi wrote:
> On a WD_BLACK SN8100 NVMe device (15b7:5050, firmware 830ZRR0A), whose
> mailbox creation fails on every boot, these messages identified the
> failure: the device accepts the Discovery request but never presents a
> response, and the transaction times out with the Busy bit still set:
>
> pci 0000:05:00.0: DOE: [500] response timeout, status: 0x00000001
> pci 0000:05:00.0: DOE: [500] failed to cache features : -5
> pci 0000:05:00.0: DOE: [500] failed to create mailbox: -5
The same happens here with a WD_BLACK SN8100 (15b7:5050) on newer
firmware, 930BRI19, in a Framework Laptop 13 (AMD Ryzen AI 300) on
Linux 7.0. Both errors are logged at every boot, and the drive
otherwise works normally:
pci 0000:bf:00.0: DOE: [500] failed to cache features : -5
pci 0000:bf:00.0: DOE: [500] failed to create mailbox: -5
So the firmware update did not change it. As the mailbox never answers,
would a quirk which skips DOE discovery for this device be acceptable,
instead of the two errors at every boot?
Mitar
prev parent reply other threads:[~2026-11-03 23:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 19:33 [PATCH] PCI/DOE: Add debug messages for transaction failures Saverio Miroddi
2026-07-21 19:35 ` sashiko-bot
2026-11-03 23:29 ` Mitar [this message]
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=20261103232922.252762-1-mitar.git@tnode.com \
--to=mitar.git@tnode.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=saverio.pub2@gmail.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 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.