From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "Sironi, Filippo" <sironi@amazon.de>,
Christoph Hellwig <hch@lst.de>,
Jaroslav Pulchart <jaroslav.pulchart@gooddata.com>,
"Greenberg, Aviv" <aggreenb@amazon.com>,
"Dutta, Soumyaroop" <duttaso@amazon.com>,
"Priescu, Valentin" <priescuv@amazon.de>,
"Machulsky, Zorik" <zorik@amazon.com>
Cc: "linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>,
"niklas.cassel@wdc.com" <niklas.cassel@wdc.com>
Subject: Re: "nvme nvmeX: IO queues not created" with "Amazon.com, Inc. NVMe SSD Controller" from 5.19.y (issue bisected)
Date: Tue, 20 Sep 2022 11:41:58 +0200 [thread overview]
Message-ID: <18e67378-1365-5e36-981b-13cada73bcda@leemhuis.info> (raw)
In-Reply-To: <3E46620F-C371-4108-9A74-AA1A624AA9A5@amazon.de>
Hi, this is your Linux kernel regression tracker.
On 07.09.22 11:58, Sironi, Filippo wrote:
> Adding more folks (Soumyaroop, Valentin, and Zorik) involved in the investigation, which is by now concluded.
Has any progress been made to get this regression fixed? I might be
missing something, but from here it looks like nothing happened since
two weeks. Thing is: ideally it shouldn't take this long to fix
regressions in production releases, as explained in
https://docs.kernel.org/process/handling-regressions.html
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
P.S.: As the Linux kernel's regression tracker I deal with a lot of
reports and sometimes miss something important when writing mails like
this. If that's the case here, don't hesitate to tell me in a public
reply, it's in everyone's interest to set the public record straight.
#regzbot poke
> On 07.09.22, 11:13, "Sironi, Filippo" <sironi@amazon.de> wrote:
>
> I'm aware of a customer contact regarding this issue and I know that the team responsible for the NVMe implementation is investigating.
> Adding Aviv since he's closer to this space than I am and may have more insights into how the investigation is progressing.
>
> On 07.09.22, 08:30, "Christoph Hellwig" <hch@lst.de> wrote:
>
> CAUTION: This email originated from outside of the organization. Do not click links or open attachments unless you can confirm the sender and know the content is safe.
>
>
>
> Filippo,
>
> can you help figuring out what is going on with this Amazon controller?
>
> On Wed, Sep 07, 2022 at 08:05:05AM +0200, Jaroslav Pulchart wrote:
> > Hello,
> >
> > I would like to report a regression issue in 5.19.y in NVMe driver.
> >
> > The issue is reproducible at AWS EC2 instances with local NVMe storage
> > like "r5d.*". Kernel report "IO queues not created":
> > [ 2.936641] nvme nvme0: 2/0/0 default/read/poll queues <- EBS volume
> > [ 2.939493] nvme nvme1: 2/0/0 default/read/poll queues <- EBS volume
> > [ 2.940797] nvme nvme2: IO queues not created <- Local volume
> > with 5.19.y (kernel 5.19) and the nvme storage cannot be used.
> >
> > I bisected the issue to commit
> > "aa41d2fe60ee2e4452b0f9ca9f0f6d80a4ff9f9d" (nvme: set controller
> > enable bit in a separate write). Reverting it makes the nvme device
> > working again:
> > [ 3.025599] nvme nvme0: 2/0/0 default/read/poll queues
> > [ 3.032467] nvme nvme2: 8/0/0 default/read/poll queues
> > [ 3.040040] nvme nvme1: 2/0/0 default/read/poll queues
> >
> > Best,
> > --
> > Jaroslav Pulchart
> > Sr. Principal SW Engineer
> > GoodData
> ---end quoted text---
>
>
>
>
>
> Amazon Development Center Germany GmbH
> Krausenstr. 38
> 10117 Berlin
> Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
> Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
> Sitz: Berlin
> Ust-ID: DE 289 237 879
>
>
next prev parent reply other threads:[~2022-09-20 9:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 6:05 "nvme nvmeX: IO queues not created" with "Amazon.com, Inc. NVMe SSD Controller" from 5.19.y (issue bisected) Jaroslav Pulchart
2022-09-07 6:29 ` Christoph Hellwig
2022-09-07 9:13 ` Sironi, Filippo
2022-09-07 9:58 ` Sironi, Filippo
2022-09-20 9:41 ` Thorsten Leemhuis [this message]
2022-09-20 19:42 ` Keith Busch
2022-09-21 8:59 ` Sironi, Filippo
2022-09-20 19:53 ` Dutta, Soumyaroop
2022-09-08 10:41 ` "nvme nvmeX: IO queues not created" with "Amazon.com, Inc. NVMe SSD Controller" from 5.19.y (issue bisected) #forregzbot Thorsten Leemhuis
2022-09-21 10:03 ` Thorsten Leemhuis
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=18e67378-1365-5e36-981b-13cada73bcda@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=aggreenb@amazon.com \
--cc=duttaso@amazon.com \
--cc=hch@lst.de \
--cc=jaroslav.pulchart@gooddata.com \
--cc=linux-nvme@lists.infradead.org \
--cc=niklas.cassel@wdc.com \
--cc=priescuv@amazon.de \
--cc=sironi@amazon.de \
--cc=zorik@amazon.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;
as well as URLs for NNTP newsgroup(s).