All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yi Zhang <yi.zhang@redhat.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: linux-block <linux-block@vger.kernel.org>
Subject: Re: 5.18-rc1 nvme0: Admin Cmd(0x6), I/O Error (sct 0x0 / sc 0x2) DNR
Date: Fri, 8 Apr 2022 12:42:25 +0800	[thread overview]
Message-ID: <CAHj4cs8Mtv66ikMDTJYQ48spEvF8QYyoD0SrZPDKfgXarpp=dg@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtQkDFs7bt5T=jHO0iZ0zUgvaPpYPf_n4s+URtQXqF2Mew@mail.gmail.com>

Hi Chris

This issue has been reported and you can find more info here.
https://lore.kernel.org/linux-nvme/F2ACCD82-052F-473F-9882-1703147FA662@oracle.com/T/#t

On Fri, Apr 8, 2022 at 11:41 AM Chris Murphy <lists@colorremedies.com> wrote:
>
> Hi,
>
> I'm seeing this never before seen message in the journal, all in red
> text. This is kernel-5.18.0-0.rc1.20220406git3e732ebf7316ac8.19.fc37.x86_64
>
> Apr 07 21:26:30 fovo.local kernel: nvme nvme0: pci function 0000:03:00.0
> Apr 07 21:26:30 fovo.local kernel: nvme0: Admin Cmd(0x6), I/O Error
> (sct 0x0 / sc 0x2) DNR
> Apr 07 21:26:30 fovo.local kernel: nvme nvme0: 8/0/0 default/read/poll queues
> Apr 07 21:26:30 fovo.local kernel:  nvme0n1: p1 p2 p3 p4 p5
>
> 03:00.0 Non-Volatile memory controller [0108]: Toshiba Corporation XG6
> NVMe SSD Controller [1179:011a] (prog-if 02 [NVM Express])
>     Subsystem: Toshiba Corporation Device [1179:0001]
>
> This happens with every boot of this 5.18.0-rc1 kernel, no such
> message for any 5.17.x series kernel.
>
>
> --
> Chris Murphy
>


-- 
Best Regards,
  Yi Zhang


  reply	other threads:[~2022-04-08  4:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08  3:38 5.18-rc1 nvme0: Admin Cmd(0x6), I/O Error (sct 0x0 / sc 0x2) DNR Chris Murphy
2022-04-08  4:42 ` Yi Zhang [this message]
2022-04-08  5:51   ` Chris Murphy

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='CAHj4cs8Mtv66ikMDTJYQ48spEvF8QYyoD0SrZPDKfgXarpp=dg@mail.gmail.com' \
    --to=yi.zhang@redhat.com \
    --cc=linux-block@vger.kernel.org \
    --cc=lists@colorremedies.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.