From: Christoph Hellwig <hch@lst.de>
To: "Grochowski, Maciej" <Maciej.Grochowski@sony.com>
Cc: Keith Busch <kbusch@kernel.org>, Christoph Hellwig <hch@lst.de>,
"sagi@grimberg.me" <sagi@grimberg.me>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: [PATCH] nvme-pci: fix resume after AER recovery
Date: Thu, 2 Feb 2023 11:18:18 +0100 [thread overview]
Message-ID: <20230202101818.GB14931@lst.de> (raw)
In-Reply-To: <BYAPR13MB2486C8E796FC7EA0A8C6EAC981D19@BYAPR13MB2486.namprd13.prod.outlook.com>
On Wed, Feb 01, 2023 at 10:58:40PM +0000, Grochowski, Maciej wrote:
> Hi Keith!
>
> I updated kernel on my machine into 5.15.87 sources and I run same experiment with aer_inject tool.
> As a result I got followed error and nvme disappeared:
>
> nvme 0000:02:00.0: can't change power state from D3cold to D0 (config space inaccessible)
I've been trying to look for this code in latest upstream and it has
changed entirely. Any chance you could do a quick run with Linux 6.1?
next prev parent reply other threads:[~2023-02-02 10:18 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-30 10:14 [PATCH] nvme-pci: fix resume after AER recovery Christoph Hellwig
2023-01-30 18:35 ` Keith Busch
2023-01-30 18:43 ` Keith Busch
2023-01-30 18:54 ` Grochowski, Maciej
2023-01-31 8:58 ` Christoph Hellwig
2023-01-31 15:22 ` Keith Busch
2023-02-01 22:58 ` Grochowski, Maciej
2023-02-02 10:18 ` Christoph Hellwig [this message]
2023-02-02 18:47 ` Grochowski, Maciej
2023-02-02 19:43 ` Keith Busch
2023-02-03 1:29 ` Grochowski, Maciej
2023-02-03 1:37 ` Keith Busch
2023-02-03 18:45 ` Grochowski, Maciej
2023-02-06 14:02 ` Javier.gonz
2023-02-06 15:42 ` Christoph Hellwig
2023-02-06 16:22 ` Keith Busch
2023-02-06 17:51 ` Javier.gonz
2023-02-07 1:51 ` Grochowski, Maciej
2023-02-07 8:29 ` Javier.gonz
2023-02-07 10:36 ` Klaus Jensen
2023-02-07 19:05 ` Grochowski, Maciej
2023-02-08 6:43 ` Klaus Jensen
2023-02-08 17:26 ` Grochowski, Maciej
2023-02-08 17:39 ` Keith Busch
2023-02-08 22:38 ` Grochowski, Maciej
2023-02-09 7:55 ` Javier.gonz
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=20230202101818.GB14931@lst.de \
--to=hch@lst.de \
--cc=Maciej.Grochowski@sony.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
/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