Bug 2073270

Summary: kernel: nvme0: Admin Cmd(0x6), I/O Error (sct 0x0 / sc 0x2) DNR
Product: [Fedora] Fedora Reporter: Chris Murphy <bugzilla>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED RAWHIDE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: acaringi, adscvr, airlied, alciregi, bskeggs, hdegoede, hpa, jarodwilson, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-10-06 03:21:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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/