Id 002f75f
Component kernel
Count 1
Time 2025-08-29 11:55:05
Command line BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.15.10-200.fc42.x86_64 root=UUID=0548c378-fdad-49db-9a7b-2e4779892f93 ro rootflags=subvol=root rd.luks.uuid=luks-31b94f4a-915c-47ee-af7a-a7c948b23cf4 rhgb quiet
Package kernel-core-6.15.10-200.fc42
Path /var/spool/abrt/oops-2025-08-29-11:55:05-3117-0
Not reportable
A kernel problem occurred, but your kernel has been tainted (flags:GW). Explanation:
W - Kernel issued warning.
Kernel maintainers are unable to diagnose tainted reports.
It’s not merely strange because of its uniquely unreportableness, but also because I appear to have solely hit it once. Consequently, can anyone explain to me what might have caused it? I ask because I’m unable to read most stack traces.
You already posted a list of modules from the abrt.. It is possible one of them is somehow misconfigured/corrupt. If your root uses btrfs, boot a Live USB and use btrfs check --readonly <filesystem> to rule out bitrot.
If CONFIG_MODULE_SIG_FORCE is enabled or module.sig_enforce=1 is supplied on the kernel command line, the kernel will only load validly signed modules for which it has a public key. Otherwise, it will also load modules that are unsigned.
Here:
% grep CONFIG_MODULE_SIG_FORCE /lib/modules/*/config
/lib/modules/6.15.10-200.fc42.x86_64/config:# CONFIG_MODULE_SIG_FORCE is not set
/lib/modules/6.16.2-200.fc42.x86_64/config:# CONFIG_MODULE_SIG_FORCE is not set
/lib/modules/6.16.3-200.fc42.x86_64/config:# CONFIG_MODULE_SIG_FORCE is not set
Assuming none of the modules are rotten, try adding module.sig_enforce=1 to the kernel command line.
Your kernel issued a warning, which causes it to be marked as tainted.
That particular warning happens when the amdgpu driver is completing a DRM (Direct Rendering Manager) data transfer and detects a problem. A comment at the top of the function amdgpu_dm_atomic_commit_tail says:
This will tell DC to commit the constructed DC state from atomic_check, programming the hardware. Any failures here implies a hardware failure, since atomic check should have filtered anything non-kosher.
So your AMD GPU apparently had some kind of hardware hiccup. If it has only happened once, I wouldn’t worry about it.
@gnwiii, although @jjames’s response likely renders this redundant:
#!/usr/bin/env sh
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 2.4G 1 loop /run/rootfsbase
sda 8:0 1 14.5G 0 disk
├─sda1 8:1 1 2.6G 0 part /run/initramfs/live
└─sda2 8:2 1 30M 0 part
zram0 251:0 0 8G 0 disk [SWAP]
nvme0n1 259:0 0 931.5G 0 disk
├─nvme0n1p1 259:1 0 600M 0 part
├─nvme0n1p2 259:2 0 1G 0 part
└─nvme0n1p3 259:3 0 929.9G 0 part
#!/usr/bin/env sh
sudo cryptsetup luksOpen /dev/nvme0n1p3 cryptroot && \
lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 2.4G 1 loop /run/rootfsbase
sda 8:0 1 14.5G 0 disk
├─sda1 8:1 1 2.6G 0 part /run/initramfs/live
└─sda2 8:2 1 30M 0 part
zram0 251:0 0 8G 0 disk [SWAP]
nvme0n1 259:0 0 931.5G 0 disk
├─nvme0n1p1 259:1 0 600M 0 part
├─nvme0n1p2 259:2 0 1G 0 part
└─nvme0n1p3 259:3 0 929.9G 0 part
└─cryptroot 252:0 0 929.9G 0 crypt
#!/usr/bin/env sh
sudo btrfs check --readonly /dev/mapper/cryptroot
Opening filesystem to check...
Checking filesystem on /dev/mapper/cryptroot
UUID: 0548c378-fdad-49db-9a7b-2e4779892f93
[1/8] checking log skipped (none written)
[2/8] checking root items
[3/8] checking extents
[4/8] checking free space tree
[5/8] checking fs roots
[6/8] checking only csums items (without verifying data)
[7/8] checking root refs
[8/8] checking quota groups skipped (not enabled on this FS)
found 219027546112 bytes used, no error found
total csum bytes: 211609660
total tree bytes: 1566031872
total fs tree bytes: 1219887104
total extent tree bytes: 101728256
btree space waste bytes: 274194642
file data blocks allocated: 320589209600
referenced 274643537920
Because:
#!/usr/bin/env sh
grep CONFIG_MODULE_SIG_FORCE /lib/modules/*/config
/lib/modules/6.15.10-200.fc42.x86_64/config:# CONFIG_MODULE_SIG_FORCE is not set
/lib/modules/6.15.9-201.fc42.x86_64/config:# CONFIG_MODULE_SIG_FORCE is not set
/lib/modules/6.16.3-200.fc42.x86_64/config:# CONFIG_MODULE_SIG_FORCE is not set
…I’ll do so. However, what am I looking for? (It successfully booting, with that enabled?)
If you had an incorrectly configured module, this should produce an error. Not all modules are loaded at boot time, so you would need to reproduce conditions where the abrt occurred.
However, because abrt appears to delete (duplicate) recurrences, I don’t know whether I am able to glean anything from it. Except for solely gnome-abrt reporting what that screenshot depicts, both abrt displays the old data, and gnome-abrt directs me to the retained directory of the old report.
This FW16 has passed memtest86+-7.20-2.fc42.x86_64 4 times. [1]
