Partition became read-only on a wake up after suspend

Hello!

I’m new to EndeavourOS. I got it installed recently and so far it’s very great. There is only issue, but it makes the whole experience pretty flaw. I’m using EndeavourOS on my Laptop. If I close the lid or go to suspend via systemctl suspend, then after wake up partition of the system became read-only. This, unfortunately, ruin the experience, as it’s hard to imaging to use laptop without going to suspend at all.

I searched all over the net and on this forum in particular, but have not found anything useful to me. So far everything I looked at looks ok on me system and I don’t know there to dig further. I will appreciate any help.

My laptop is Tuxedo Pulse Gen 2. It’s a laptop with AMD cpu with integrated graphics. I use Hyprland as compositor, the dm is ssdm. Basically, I installed EndeavourOS with sway and then installed Hyprland over it.

Screenfetch info
OS: EndeavourOS Linux x86_64
Host: TUXEDO Pulse 15 Gen2 Standard
Kernel: 6.3.9-arch1-1
Uptime: 15 mins
Packages: 831 (pacman)
Shell: bash 5.1.16
Resolution: 2560x1440
DE: Hyprland
Theme: Arc-Dark [GTK2/3]
Icons: Qogir-dark [GTK2/3]
Terminal: alacritty
Terminal Font: Fira Code
CPU: AMD Ryzen 7 5700U with Radeon Graphics (16) @ 1.800GHz
GPU: AMD ATI 05:00.0 Lucienne
Memory: 1480MiB / 15372MiB

I have 2 Linux installed on my Laptop, there is pair of Ubuntu + Swap (/dev/nvme0n1p2 + /dev/nvme0n1p3) and pair of EndeavourOS + Swap (/dev/nvme0n1p3 + /dev/nvme0n1p4). The bootloader is EFI (/dev/nvme0n1p1)

fdisk -l
Disk /dev/nvme0n1: 465.76 GiB, 500107862016 bytes, 976773168 sectors
Disk model: Samsung SSD 980 PRO 500GB
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: B59E18AF-360B-4063-96F9-D35F77578D13

Device             Start       End   Sectors   Size Type
/dev/nvme0n1p1      2048   1050623   1048576   512M EFI System
/dev/nvme0n1p2   1050624 193568767 192518144  91.8G Linux filesystem
/dev/nvme0n1p3 959995904 976773119  16777216     8G Linux swap
/dev/nvme0n1p4 210765824 959995903 749230080 357.3G Linux filesystem
/dev/nvme0n1p5 193568768 210765823  17197056   8.2G Linux swap

Partition table entries are not in disk order.

So, the system became read-only, so it’s hard to capture logs. But here is the photo.

Photo of journalctl after wake up

I have 2 dracut files, here there are:

/etc/dracut.conf.d/eos-defaults.conf
omit_dracutmodules+=" network cifs nfs brltty "
compress="zstd"
/etc/dracut.conf.d/resume.conf

add_dracutmodules+=" resume "

Also, smartctl of my swap partition

smartctl -a /dev/nvme0n1p5
smartctl 7.3 2022-02-28 r5338 [x86_64-linux-6.3.9-arch1-1] (local build)
Copyright (C) 2002-22, Bruce Allen, Christian Franke, www.smartmontools.org

=== START OF INFORMATION SECTION ===
Model Number:                       Samsung SSD 980 PRO 500GB
Serial Number:                      S5GYNX0W400365P
Firmware Version:                   5B2QGXA7
PCI Vendor/Subsystem ID:            0x144d
IEEE OUI Identifier:                0x002538
Total NVM Capacity:                 500,107,862,016 [500 GB]
Unallocated NVM Capacity:           0
Controller ID:                      6
NVMe Version:                       1.3
Number of Namespaces:               1
Namespace 1 Size/Capacity:          500,107,862,016 [500 GB]
Namespace 1 Utilization:            119,253,168,128 [119 GB]
Namespace 1 Formatted LBA Size:     512
Namespace 1 IEEE EUI-64:            002538 b431b1eefd
Local Time is:                      Sat Jul  1 14:44:25 2023 BST
Firmware Updates (0x16):            3 Slots, no Reset required
Optional Admin Commands (0x0017):   Security Format Frmw_DL Self_Test
Optional NVM Commands (0x0057):     Comp Wr_Unc DS_Mngmt Sav/Sel_Feat Timestmp
Log Page Attributes (0x0f):         S/H_per_NS Cmd_Eff_Lg Ext_Get_Lg Telmtry_Lg
Maximum Data Transfer Size:         128 Pages
Warning  Comp. Temp. Threshold:     82 Celsius
Critical Comp. Temp. Threshold:     85 Celsius

Supported Power States
St Op     Max   Active     Idle   RL RT WL WT  Ent_Lat  Ex_Lat
 0 +     8.49W       -        -    0  0  0  0        0       0
 1 +     4.48W       -        -    1  1  1  1        0     200
 2 +     3.18W       -        -    2  2  2  2        0    1000
 3 -   0.0400W       -        -    3  3  3  3     2000    1200
 4 -   0.0050W       -        -    4  4  4  4      500    9500

Supported LBA Sizes (NSID 0x1)
Id Fmt  Data  Metadt  Rel_Perf
 0 +     512       0         0

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

SMART/Health Information (NVMe Log 0x02)
Critical Warning:                   0x00
Temperature:                        30 Celsius
Available Spare:                    100%
Available Spare Threshold:          10%
Percentage Used:                    0%
Data Units Read:                    516,981 [264 GB]
Data Units Written:                 901,840 [461 GB]
Host Read Commands:                 3,712,389
Host Write Commands:                12,683,357
Controller Busy Time:               204
Power Cycles:                       181
Power On Hours:                     34
Unsafe Shutdowns:                   17
Media and Data Integrity Errors:    0
Error Information Log Entries:      0
Warning  Comp. Temperature Time:    0
Critical Comp. Temperature Time:    0
Temperature Sensor 1:               30 Celsius
Temperature Sensor 2:               30 Celsius

Error Information (NVMe Log 0x01, 16 of 64 entries)
No Errors Logged

Finally:

cat /etc/fstab
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a device; this may
# be used with UUID= as a more robust way to name devices that works even if
# disks are added and removed. See fstab(5).
#
# <file system>             <mount point>  <type>  <options>  <dump>  <pass>
UUID=2430-5E2F                            /efi           vfat    defaults,noatime 0 2
UUID=41bb1846-ed39-451e-be02-d4b52c80c91d /              ext4    defaults,noatime 0 1
tmpfs                                     /tmp           tmpfs   defaults,noatime,mode=1777 0 0
UUID=e6e01d5d-3983-45a5-bfed-dc1f3457e2b8 none swap defaults 0 0

I would appreciate if anyone can help. Now, I’m stuck and do not even know where to look at. I hope some of the above logs help.

The log in the posted image (it should be posted in text, instead of image) mentions errors on a different partition.

Check all previous time for errors, to see error status in time:

journalctl -p3

Don’t post terminal output in image, please.

Output of journalctl -p3 -r
EndeavourOS  ❯ > journalctl -p3 -r
Jul 01 15:41:54 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 01 15:41:54 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jul 01 15:41:53 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 01 15:41:51 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Jul 01 15:41:51 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 01 15:41:51 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
-- Boot 4dac4d39553a4da4af7ddc01122e5293 --
Jul 01 14:54:40 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 01 14:54:40 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jul 01 14:54:39 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 01 14:54:37 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Jul 01 14:54:37 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 01 14:54:37 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
-- Boot b96c12d9c24f491c9ada3e36c5e7211b --
Jul 01 14:52:51 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 01 14:52:51 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jul 01 14:52:50 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 01 14:52:48 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Jul 01 14:52:48 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 01 14:52:48 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
-- Boot 96d11e2d84294b41aa57b0ad5b7796fc --
Jul 01 14:52:34 dmitry-tuxedopulse15gen2 kernel: watchdog: watchdog0: watchdog did not stop!
Jul 01 14:49:03 dmitry-tuxedopulse15gen2 sudo[6352]: pam_unix(sudo:auth): auth could not identify password for [dmitry]
Jul 01 14:49:03 dmitry-tuxedopulse15gen2 sudo[6352]: pam_unix(sudo:auth): conversation failed
Jul 01 14:48:55 dmitry-tuxedopulse15gen2 sudo[6347]: pam_unix(sudo:auth): auth could not identify password for [dmitry]
Jul 01 14:48:55 dmitry-tuxedopulse15gen2 sudo[6347]: pam_unix(sudo:auth): conversation failed
Jul 01 14:44:22 dmitry-tuxedopulse15gen2 sudo[5975]:   dmitry : 1 incorrect password attempt ; TTY=pts/0 ; PWD=/etc/dracut.conf.d ; USER=r>
Jul 01 14:25:54 dmitry-tuxedopulse15gen2 sudo[2267]: pam_unix(sudo:auth): auth could not identify password for [dmitry]
Jul 01 14:25:54 dmitry-tuxedopulse15gen2 sudo[2267]: pam_unix(sudo:auth): conversation failed
Jul 01 14:12:08 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 01 14:12:08 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jul 01 14:12:08 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 01 14:12:06 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Jul 01 14:12:06 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 01 14:12:06 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
-- Boot 37f1ff03e6f44165a00c5d89cc8d2503 --
Jul 01 12:26:11 dmitry-tuxedopulse15gen2 kernel: watchdog: watchdog0: watchdog did not stop!
Jul 01 11:58:10 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 01 11:58:10 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jul 01 11:58:09 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 01 11:58:07 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Jul 01 11:58:07 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 01 11:58:07 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
-- Boot 81ff623643c2405e96fa69244c854f40 --
Jul 01 01:59:03 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 01 01:59:03 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jul 01 01:59:02 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 01 01:59:00 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Jul 01 01:59:00 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 01 01:59:00 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
-- Boot c75757713cb0485691ebba6c20ef84e2 --
Jul 01 01:57:34 dmitry-tuxedopulse15gen2 kernel: #PF: error_code(0x0000) - not-present page
Jul 01 01:57:34 dmitry-tuxedopulse15gen2 kernel: #PF: supervisor read access in kernel mode
Jul 01 01:57:34 dmitry-tuxedopulse15gen2 kernel: BUG: kernel NULL pointer dereference, address: 000000000000003a
Jul 01 01:57:30 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 01 01:57:30 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jul 01 01:57:29 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 01 01:57:27 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Jul 01 01:57:27 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 01 01:57:27 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
-- Boot df7e99437f6c45efa8128ac0d792ff8a --
Jul 01 01:56:19 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 01 01:56:19 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jul 01 01:56:18 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 01 01:56:16 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Jul 01 01:56:16 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 01 01:56:16 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
-- Boot a6a9267802c84b60b82baa936bc3563d --
Jul 01 01:44:53 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 01 01:44:53 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jul 01 01:44:53 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 01 01:44:51 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Jul 01 01:44:51 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 01 01:44:51 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
-- Boot 9c42ae2652bb4e6a899edf9b0b031979 --
Jul 01 01:44:35 dmitry-tuxedopulse15gen2 kernel: watchdog: watchdog0: watchdog did not stop!
Jul 01 01:41:39 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 01 01:41:39 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jul 01 01:41:38 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 01 01:41:36 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Jul 01 01:41:36 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 01 01:41:36 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
Jul 01 01:41:35 dmitry-tuxedopulse15gen2 systemd[1]: Failed to activate swap /swapfile.
-- Boot c225c2e587874be492b708a2c7dd91bf --
Jul 01 01:38:06 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 01 01:38:06 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jul 01 01:38:05 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 01 01:38:04 dmitry-tuxedopulse15gen2 systemd[1]: Failed to activate swap /swapfile.
Jul 01 01:38:03 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Jul 01 01:38:03 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 01 01:38:03 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
Jul 01 01:38:02 dmitry-tuxedopulse15gen2 systemd[1]: Failed to activate swap /swapfile.
-- Boot 92222543e57e4b48a26154f0754f7acc --
Jul 01 01:37:46 dmitry-tuxedopulse15gen2 kernel: watchdog: watchdog0: watchdog did not stop!
Jul 01 01:34:04 dmitry-tuxedopulse15gen2 sudo[2960]: pam_unix(sudo:auth): auth could not identify password for [dmitry]
Jul 01 01:34:04 dmitry-tuxedopulse15gen2 sudo[2960]: pam_unix(sudo:auth): conversation failed
Jul 01 01:30:15 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 01 01:30:15 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jul 01 01:30:14 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 01 01:30:12 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Jul 01 01:30:12 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 01 01:30:12 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
-- Boot e9636e61583e420ab999dbf7a79664f4 --
Jul 01 01:29:55 dmitry-tuxedopulse15gen2 kernel: watchdog: watchdog0: watchdog did not stop!
Jul 01 01:21:59 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 01 01:21:59 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jul 01 01:21:59 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 01 01:21:57 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Jul 01 01:21:57 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 01 01:21:57 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
-- Boot 863a39c240784bdc934f59068872fe9d --
Jul 01 01:04:36 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 01 01:04:36 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jul 01 01:04:35 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Jul 01 01:04:33 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Jul 01 01:04:33 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: sending frame failed (-19)
Jul 01 01:04:33 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: FW download error recovery failed (-19)
-- Boot 7030b47a17694aae929ff2f0f1c92275 --
Jul 01 01:02:56 dmitry-tuxedopulse15gen2 firewalld[597]: ERROR: Invalid option: 'NftablesCounters=no'
Jul 01 01:02:56 dmitry-tuxedopulse15gen2 firewalld[597]: ERROR: Invalid option: 'NftablesFlowtable=off'
Jul 01 00:58:25 dmitry-tuxedopulse15gen2 sudo[2652]:   dmitry : 1 incorrect password attempt ; TTY=pts/0 ; PWD=/home/dmitry ; USER=root ; >
Jul 01 00:54:04 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 01 00:54:04 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
-- Boot e508dc9b2b2a4f9cb4410a0bf3163723 --
Jul 01 00:49:45 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jul 01 00:49:45 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
-- Boot fdbaefd9c355417a8683a73458642567 --
Jun 23 20:12:45 dmitry-tuxedopulse15gen2 systemd-logind[575]: Failed to start autovt@tty2.service: Transaction for getty@tty2.service/star>
Jun 23 20:09:02 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jun 23 20:09:02 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
-- Boot 46fc5dc1608e4b4b9a842c284b680ec9 --
Jun 23 19:59:45 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jun 23 19:59:45 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
-- Boot d8ced42404ad43eba18c502db1210209 --
Jun 23 00:10:05 dmitry-tuxedopulse15gen2 kernel: watchdog: watchdog0: watchdog did not stop!
Jun 22 23:37:32 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jun 22 23:37:32 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jun 22 23:37:31 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
-- Boot 869cdb189d5841cf9b8388d86303970a --
Jun 22 21:46:08 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jun 22 21:46:08 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
-- Boot fa9cb01114644d33b8add5ee7d633f4b --
Jun 22 19:54:32 dmitry-tuxedopulse15gen2 kernel: [drm:dc_dmub_srv_wait_idle [amdgpu]] *ERROR* Error waiting for DMUB idle: status=3
Jun 22 19:46:49 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jun 22 19:46:49 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
-- Boot 0204eb9603f14cf287f79b30146a9a63 --
Jun 21 22:46:52 dmitry-tuxedopulse15gen2 kernel: watchdog: watchdog0: watchdog did not stop!
Jun 21 21:54:45 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jun 21 21:54:45 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
-- Boot 5b420846fcf84f068fc95b19b0807fcf --
Jun 21 20:45:05 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jun 21 20:45:05 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
-- Boot 06caae389a96435da8a54a4279a7e951 --
Jun 18 11:48:12 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jun 18 11:48:12 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
-- Boot d483a32de7594ba09207215b6c6d1900 --
Jun 18 10:40:28 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jun 18 10:40:28 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jun 18 10:40:27 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
-- Boot c0c06d88fb0f450aadcc13f17822cc31 --
Jun 18 01:30:03 dmitry-tuxedopulse15gen2 systemd-coredump[31613]: [🡕] Process 2607 (Hyprland) of user 1000 dumped core.

                                                                  Stack trace of thread 2607:
                                                                  #0  0x00007f4984a43c2e n/a (libc.so.6 + 0x11ac2e)
                                                                  #1  0x68d1410164edf159 n/a (n/a + 0x0)
                                                                  ELF object binary architecture: AMD x86-64
Jun 17 20:28:25 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jun 17 20:28:25 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
Jun 17 20:28:24 dmitry-tuxedopulse15gen2 kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
-- Boot 311c3bc07a6b4e2f9a23fb461c4a8945 --
Jun 17 19:06:30 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jun 17 19:06:30 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
-- Boot 00f5b3771152419a86cfc516ff501b4e --
Jun 17 15:26:00 dmitry-tuxedopulse15gen2 kernel: watchdog: watchdog0: watchdog did not stop!
Jun 17 15:25:58 dmitry-tuxedopulse15gen2 systemd-logind[584]: Failed to start autovt@tty2.service: Transaction for getty@tty2.service/star>
Jun 17 15:20:48 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jun 17 15:20:48 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
-- Boot 7ec5b62e44d045c8987f1328315dcfb3 --
Jun 17 13:51:51 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jun 17 13:51:51 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.
-- Boot 048372df2d444d54bed1c56ad5461b78 --
Jun 16 02:31:01 dmitry-tuxedopulse15gen2 systemd-logind[575]: Failed to start autovt@tty4.service: Transaction for getty@tty4.service/star>
Jun 16 02:30:47 dmitry-tuxedopulse15gen2 systemd-coredump[5939]: [🡕] Process 5031 (Hyprland) of user 1000 dumped core.

                                                                 Stack trace of thread 5031:
                                                                 #0  0x00007f6018930c2e n/a (libc.so.6 + 0x11ac2e)
                                                                 #1  0xcabd10c70e499d0b n/a (n/a + 0x0)
                                                                 ELF object binary architecture: AMD x86-64
Jun 16 02:16:47 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: SECUREDISPLAY: query securedisplay TA failed. ret 0x0
Jun 16 02:16:47 dmitry-tuxedopulse15gen2 kernel: amdgpu 0000:05:00.0: amdgpu: Secure display: Generic Failure.

But, as far as I understand, some logs are lost. Once the partition became read-only, the system can’t store logs there. That’s why I tried to capture it via image.

To be honest, it’s very hard to capture logs there. Once the laptop wake up, the system became unusable. I can’t start new terminal (I assume because can’t create new tty device, I saw logs about it). Sometimes old terminal allow me to read some logs, sometimes not. Also, when I try to reboot via reboot command, the system show me an error that the partition is read-only

You should check the disk the input output error is showing when trying to write.

Can you, please, expand your suggestion a little bit more? What exactly you’re proposing to do? It seems it can’t write, because disk partition became read-only. But why it’s becoming read-only during suspend I don’t know

I would boot into a live usb and check the filesystem and the device blocks of nvme

check for badblocks and create file
badblocks -v -b 4096 /dev/$Device-In-Question -o badblocks.txt

ext file systems use
e2fsck to check filesystem
e2fsck -l badblocks.txt /dev/$Device-In-Question
for other file systems use
fsck -l badblocks.txt /dev/$Device-In-Question

If you find badblocks I would advice to make a backup of the drive and prepare to replace it.

Fortunately, no badblocks found