Bug 2073270 - kernel: nvme0: Admin Cmd(0x6), I/O Error (sct 0x0 / sc 0x2) DNR
Summary: kernel: nvme0: Admin Cmd(0x6), I/O Error (sct 0x0 / sc 0x2) DNR
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-08 05:48 UTC by Chris Murphy
Modified: 2022-10-06 03:21 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-06 03:21:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Chris Murphy 2022-04-08 05:48:14 UTC
1. Please describe the problem:

Seeing a scary looking message in the journal, all red text:

Apr 07 21:26:30 fovo.local kernel: nvme0: Admin Cmd(0x6), I/O Error
(sct 0x0 / sc 0x2) DNR


2. What is the Version-Release number of the kernel:
kernel-5.18.0-0.rc1.20220406git3e732ebf7316ac8.19.fc37.x86_64

3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :
Yes, kernel-5.18.0-0.rc1.20220406git3e732ebf7316ac8.19.fc37.x86_64

Doesn't happen in kernel-5.17.1-300.fc36.x86_64 and older.


4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:
Yes, just boot


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:
Yes


6. Are you running any modules that not shipped with directly Fedora's kernel?:
No


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.


The problem is discussed upstream, and is harmless.
https://lore.kernel.org/linux-nvme/Ykskv%2Fgp2s6PWiHp@kbusch-mbp.dhcp.thefacebook.com/


Note You need to log in before you can comment on or make changes to this bug.