Dear Maintainer,

After upgrading to Debian 13 this error appears:

[  679.920353] ata1.00: exception Emask 0x10 SAct 0x80 SErr 0x4050000 action 0xe frozen
[  679.920387] ata1.00: irq_stat 0x00000040, connection status changed
[  679.920402] ata1: SError: { PHYRdyChg CommWake DevExch }
[  679.920423] ata1.00: failed command: WRITE FPDMA QUEUED
[  679.920433] ata1.00: cmd 61/08:38:80:dd:56/00:00:00:00:00/40 tag 7 ncq dma 4096 out
                        res 40/00:01:00:4f:c2/00:00:00:00:00/00 Emask 0x10 (ATA bus error)
[  679.920467] ata1.00: status: { DRDY }
[  679.920491] ata1: hard resetting link
[  680.636348] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  680.655174] ata1.00: configured for UDMA/33
[  680.666772] ata1: EH complete
[  686.708535] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[  686.727689] ata1.00: configured for UDMA/33

Dear Maintainer,


This bug report is for a kernel panic that occurs on an Intel NUC8i7BEH system running the official Debian 13 "trixie" stable release. The issue is consistently triggered by high-volume I/O operations and appears to be related to the NVMe driver.

Hardware:

    System: Intel NUC8i7BEH

    Storage: Corsair Force MP510 NVMe SSD

The problem first appeared after an upgrade from Debian 12 "bookworm," where the system was fully stable and the bug did not occur. I have since performed a clean installation of Debian 13 to rule out an upgrade-specific issue, and the problem persists.

The kernel panic causes a complete system freeze, followed by the inability to boot the system normally. I have attached the smartctl output, which shows Invalid Field in Command errors, strongly suggesting a low-level NVMe driver issue. This correlates with existing bug report #1110765.

I have also taken proactive steps to address potential hardware causes, including installing extra cooling to ensure the NVMe drive and CPU are not overheating. The bug manifests regardless of the installed desktop environment (tested with both GNOME Wayland and XFCE), indicating it is a kernel-level issue.

Steps to Reproduce:

    Perform a clean installation of Debian 13 "trixie" with kernel 6.12.41+deb13-amd64 on an Intel NUC8i7BEH with a Corsair Force MP510 NVMe drive.

    Boot into the newly installed system.

    Perform a high-volume data transfer to the NVMe drive (e.g., restoring a large backup from an external drive).

    The system will experience a kernel panic and subsequent freeze. A smartctl self-test of the NVMe drive will show an Invalid Field in Command error. The system may refuse to boot afterward.

Diagnostics and Additional Information:

    Kernel version: 6.12.41+deb13-amd64

    Operating System: Debian 13 "trixie" (stable)

    Initial smartctl output:

smartctl 7.4 2023-08-01 r5530 [x86_64-linux-6.12.41+deb13-amd64] (local build)
Copyright (C) 2002-23, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Force MP510
Serial Number:                      19368238000128884331
Firmware Version:                   ECFM22.5
PCI Vendor/Subsystem ID:            0x1987
IEEE OUI Identifier:                0x6479a7
Total NVM Capacity:                 960,197,124,096 [960 GB]
Unallocated NVM Capacity:           0
Controller ID:                      1
NVMe Version:                       1.3
Number of Namespaces:               1
Namespace 1 Size/Capacity:          960,197,124,096 [960 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            6479a7 2642953331
Local Time is:                      Thu Aug 14 10:43:15 2025 EEST
Firmware Updates (0x12):            1 Slot, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x005d):     Comp DS_Mngmt Wr_Zero Sav/Sel_Feat Timestmp
Log Page Attributes (0x08):         Telmtry_Lg
Maximum Data Transfer Size:         512 Pages
Warning  Comp. Temp. Threshold:     75 Celsius
Critical Comp. Temp. Threshold:     80 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +    11.52W       -        -    0  0  0  0        0       0
 1 +     8.09W       -        -    1  1  1  1        0       0
 2 +     6.37W       -        -    2  2  2  2        0       0
 3 -   0.0490W       -        -    3  3  3  3     2000    2000
 4 -   0.0018W       -        -    4  4  4  4    25000   25000

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         2
 1 -    4096       0         1

=== START OF SMART DATA SECTION ===
SMART overall-health self-assessment test result: PASSED

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        41 Celsius
Available Spare:                    100%
Available Spare Threshold:          5%
Percentage Used:                    7%
Data Units Read:                    32,613,209 [16.6 TB]
Data Units Written:                 25,252,731 [12.9 TB]
Host Read Commands:                 283,819,368
Host Write Commands:                116,460,699
Controller Busy Time:               954
Power Cycles:                       1,591
Power On Hours:                     3,973
Unsafe Shutdowns:                   137
Media and Data Integrity Errors:    0
Error Information Log Entries:      856
Warning  Comp. Temperature Time:    120
Critical Comp. Temperature Time:    0
Thermal Temp. 1 Transition Count:   604
Thermal Temp. 2 Transition Count:   104
Thermal Temp. 1 Total Time:         10020
Thermal Temp. 2 Total Time:         892

Error Information (NVMe Log 0x01, 16 of 63 entries)
Num   ErrCount  SQId   CmdId  Status  PELoc          LBA  NSID    VS  Message
  0        856     0  0x1005  0x4004  0x028            0     0     -  Invalid Field in Command

Read Self-test Log failed: Invalid Field in Command (0x2002)




The bug is not present in the Debian 12 "bookworm" kernel, suggesting a regression introduced between the two major releases.