Constant Input/Output Error

seth · 2024-11-19 22:27:56

Meaningful memtest86+ runs are measured in days, but before that, has the system been more stable w/o XMP?
What if you test it now w/ XMP re-enabled?

If XMP has deterministic impact, try to slow down the RAM even more.

Heretic12 · 2024-11-20 18:44:59

Ran another ~4 hour run - no errors, and btw, I get the same IO error with and without XMP enabled, and after testing it multiple times I can probably say that there are not much (if any) difference - sometimes Stellaris crashes almost instantly without XMP, sometimes it is able to work for a minute or to with XMP

seth · 2024-11-20 20:52:23

Forget about whether stellaris "crashes", the more important question is whether that's also always linked to you losing the root device(s).
Have you tried to further cap the GPU then?

Heretic12 · 2024-11-20 23:43:53

Yes, dropped it down all the way to 1000 - with XMP disabled - the error persists. Actually, now I've found another error with powerdevil:

Nov 20 23:53:11 192.168.1.17 org_kde_powerdevil[1091]: Initializing libddcutil.  ddcutil version: 2.1.4, shared library: /usr/lib/libddcutil.so.5.1.2
Nov 20 23:53:11 192.168.1.17 org_kde_powerdevil[1091]: Options passed from client:
Nov 20 23:53:11 192.168.1.17 org_kde_powerdevil[1091]: Applying combined options:
Nov 20 23:53:12 192.168.1.17 wireplumber[980]: spa.bluez5: BlueZ system service is not available
Nov 20 23:53:12 192.168.1.17 org_kde_powerdevil[1091]: busno=2, sleep-multiplier =  2.00. Testing for supported feature 0x10 returned Error_Info[EIO in ddc_write_read_with_retry, causes: EIO]
Nov 20 23:53:12 192.168.1.17 org_kde_powerdevil[1091]: Library initialization complete.
Nov 20 23:53:12 192.168.1.17 org_kde_powerdevil[1091]: Watch thread started

And the usual

Nov 21 00:14:10 192.168.1.17 udisksd[917]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/Samsung_SSD_970_EVO_Plus_1TB_S4EWNMFN810703J: Error updating Health Information: No pr>
Nov 21 00:24:10 192.168.1.17 udisksd[917]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/Samsung_SSD_970_EVO_Plus_1TB_S4EWNMFN810703J: Error updating Health Information: No pr>
Nov 21 00:32:19 192.168.1.17 kernel: nvme nvme2: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Nov 21 00:32:19 192.168.1.17 kernel: nvme nvme2: Does your device have a faulty power saving mode enabled?
Nov 21 00:32:19 192.168.1.17 kernel: nvme nvme2: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug
Nov 21 00:32:19 192.168.1.17 kernel: nvme 0000:3f:00.0: enabling device (0000 -> 0002)
Nov 21 00:32:19 192.168.1.17 kernel: nvme nvme2: Disabling device after reset failure: -19
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs warning (device dm-1): ext4_end_bio:342: I/O error 10 writing to inode 96075877 starting block 20525824)
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on dev dm-1, logical block 5, lost async page write
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs warning (device dm-1): ext4_end_bio:342: I/O error 10 writing to inode 96075878 starting block 20539449)
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on device dm-1, logical block 20539449
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs warning (device dm-1): ext4_end_bio:342: I/O error 10 writing to inode 96075877 starting block 20534272)
Nov 21 00:32:19 192.168.1.17 kernel: Aborting journal on device dm-1-8.
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on dev dm-1, logical block 9627, lost async page write
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs warning (device dm-1): ext4_end_bio:342: I/O error 10 writing to inode 96075878 starting block 20539451)
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on dev dm-1, logical block 9961482, lost async page write
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs error (device dm-1) in ext4_reserve_inode_write:5813: Journal has aborted
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs warning (device dm-1): ext4_end_bio:342: I/O error 10 writing to inode 96075900 starting block 20527651)
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on device dm-1, logical block 20539451
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on dev dm-1, logical block 239632384, lost sync page write
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on dev dm-1, logical block 9961484, lost async page write
Nov 21 00:32:19 192.168.1.17 kernel: JBD2: I/O error when updating journal superblock for dm-1-8.
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs warning (device dm-1): ext4_end_bio:342: I/O error 10 writing to inode 96075878 starting block 20539498)
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on device dm-1, logical block 20527651
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on dev dm-1, logical block 9961486, lost async page write
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs error (device dm-1) in ext4_reserve_inode_write:5813: Journal has aborted
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs error (device dm-1): ext4_journal_check_start:84: comm kworker/u80:1: Detected aborted journal
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs error (device dm-1) in ext4_reserve_inode_write:5813: IO failure
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on device dm-1, logical block 20539498
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs error (device dm-1) in ext4_reserve_inode_write:5813: Journal has aborted
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs error (device dm-1): ext4_dirty_inode:6017: inode #96075878: comm HangWatcher: mark_inode_dirty error
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs warning (device dm-1): ext4_end_bio:342: I/O error 10 writing to inode 96075878 starting block 20539540)
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs warning (device dm-1): ext4_end_bio:342: I/O error 10 writing to inode 96075878 starting block 20539393)
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on device dm-1, logical block 20539540
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on device dm-1, logical block 20539393
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on dev dm-1, logical block 0, lost sync page write
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs warning (device dm-1): ext4_end_bio:342: I/O error 10 writing to inode 96075878 starting block 20539590)
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs warning (device dm-1): ext4_end_bio:342: I/O error 10 writing to inode 96075878 starting block 20539395)
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on device dm-1, logical block 20539590
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs (dm-1): I/O error while writing superblock
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on device dm-1, logical block 20539395
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs (dm-1): Remounting filesystem read-only
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on device dm-1, logical block 20539591
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on device dm-1, logical block 20525824
Nov 21 00:32:19 192.168.1.17 kernel: Buffer I/O error on dev dm-1, logical block 0, lost sync page write
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs (dm-1): I/O error while writing superblock

The full log's here: https://0x0.st/XnJ3.txt

seth · 2024-11-21 09:15:37

If it's not the nvme/APST, it's not the RAM and it's not the GPU (capping which should™ also substantially limit power draw and environmental temperatures?) we're looking at the CPU.
Can you trigger this by eg. building https://aur.archlinux.org/packages/linux-mainline ?

And to rule out some weird kernel/mdm/nvme bug, does this also happen w/ the LTS kernel

Two more things:

Nov 20 23:54:09 192.168.1.17 kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Nov 20 23:54:09 192.168.1.17 kernel: nvme nvme0: Does your device have a faulty power saving mode enabled?
Nov 20 23:54:09 192.168.1.17 kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug
Nov 20 23:54:09 192.168.1.17 udisksd[917]: Error probing device: NVMe Identify Controller command error: Interrupted system call (g-bd-nvme-error-quark, 1)
Nov 20 23:54:09 192.168.1.17 kernel: nvme 0000:02:00.0: enabling device (0000 -> 0002)
Nov 20 23:54:09 192.168.1.17 kernel: nvme nvme0: Disabling device after reset failure: -19
Nov 20 23:54:09 192.168.1.17 udisksd[917]: Error probing device: NVMe Identify Namespace command error: Input/output error (g-bd-nvme-error-quark, 1)
Nov 20 23:54:09 192.168.1.17 kernel: nvme nvme0: Identify namespace failed (-5)
…
Nov 21 00:14:10 192.168.1.17 udisksd[917]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/Samsung_SSD_970_EVO_Plus_1TB_S4EWNMFN810703J: Error updating Health Information: No probed controller info available (udisks-error-quark, 0)
Nov 21 00:24:10 192.168.1.17 udisksd[917]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/Samsung_SSD_970_EVO_Plus_1TB_S4EWNMFN810703J: Error updating Health Information: No probed controller info available (udisks-error-quark, 0)
Nov 21 00:32:19 192.168.1.17 kernel: nvme nvme2: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Nov 21 00:32:19 192.168.1.17 kernel: nvme nvme2: Does your device have a faulty power saving mode enabled?
Nov 21 00:32:19 192.168.1.17 kernel: nvme nvme2: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug
Nov 21 00:32:19 192.168.1.17 kernel: nvme 0000:3f:00.0: enabling device (0000 -> 0002)
Nov 21 00:32:19 192.168.1.17 kernel: nvme nvme2: Disabling device after reset failure: -19
Nov 21 00:32:19 192.168.1.17 kernel: EXT4-fs warning (device dm-1): ext4_end_bio:342: I/O error 10 writing to inode 96075877 starting block 20525824)

1. You don't have a static hostname. It would be super-weird if the hostname change is causing this, but please set one to avoifd it.
2. nvme0 gets checked but fails right away - was/is there a third nvme that gets completely ignored? Try to change the slots?

Heretic12 · 2024-11-21 20:47:40

So, building linux-mainline ended with IO Error - although it took ~2 hours before that happened. Using LTS kernel also didn't change anything.
Strangely enough - there are no I/O Error logs in the journal - https://0x0.st/Xnk9.txt
As for spare nvme - thing is, my mboard supports 3 m/2 slots, but my cpu doesn't have connectivity for all 3 of them - this slot supposed to work with the CPU from the next (11th) generation, so basically I have an SSD inside the non working slot. I doubt it has anything to do with the situation because it was always like that since I've assembled this PC and it didn't cause any problems other then the fact that I've spent extra money for SSD that can't work)

seth · 2024-11-21 20:59:04

BUILDING THE KERNEL TOOK TWO HOURS!!!???!!!?????

It probably ran only on a single core… fuck.
https://wiki.archlinux.org/title/Makepk … uild_times

But we *might* be getting somewhere if CPU stress causes this, can you try to constriain the CPU, resp. you're not overclocking the system right now, are you?
https://wiki.archlinux.org/title/CPU_fr … requencies

Heretic12 · 2024-11-21 22:22:34

No, didn't do any manual overclocks, XMP is disabled. Tweaked makepkg.conf to use all available threads and ran linux-mainline again - and caught IO Error again - https://0x0.st/XnnU.txt. Now lets tweak CPU clocks

Heretic12 · 2024-11-22 14:32:52

Ok, now I am legit confused... So, I've capped CPU clocks to 3 GHz, capped GPU clocks and turned off XMP. This allowed me to play Stellaris for a few hours yesterday (although inevitably ran into IO Error) and also it seems to be playable today. But I would still get IO Error while trying to build the kernel. Can try to build it with 1 GHz CPU clock though... But it looks like CPU IS the problem, at least a big part of it. Can it be due to some problems with intel-ucode package or is it just CPU decided to die on me?

seth · 2024-11-23 06:09:53

Nov 21 22:28:47 HereticPC kernel: microcode: updated early: 0xf8 -> 0xfc, date = 2024-02-01
Nov 21 22:28:47 HereticPC kernel: smpboot: CPU0: Intel(R) Core(TM) i9-10900K CPU @ 3.70GHz (family: 0x6, model: 0xa5, stepping: 0x5)

Is the system sufficiently cooled? How hot does the CPU get under unconstrained load?
Does it help to add "mitigations=off" to the https://wiki.archlinux.org/title/Kernel_parameters

But I would still get IO Error while trying to build the kernel. Can try to build it with 1 GHz CPU clock though...

Did you? Results?

If this was a raptor lake, it would be a clear candidate for that disaster but I'm not aware of similar reports for comet lakes.
Also the impact seems suspiciously specific in targetting your nvme

Heretic12 · 2024-11-23 19:39:11

Cooling is more then sufficient - a monoblock with custom loop, it was on 38 Celsius tops while on 3 GHz on full load.
Building kernel on 1 GHz ended with IO Error
Kernel parameter "mitigations=off" didn't help in any way...
https://0x0.st/X52y.txt
What is confusing - is how this error behaves - it almost feels like it is sentient and adapting) Thing is - after the first time I've capped CPU clocks - as I've said - it allowed me to run Stellaris for a few hours, but now - it works no longer - capping clocks to 3 GHz stopped helping and once again Stellaris crashes in a few minutes.
Tried switching hyperthreading off - no effect.

Last edited by Heretic12 (2024-11-24 21:44:34)

seth · 2024-11-25 08:28:48

The crashes are really just a follow up problem, the leading issue is still

Nov 23 20:32:52 HereticPC kernel: nvme nvme2: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Nov 23 20:32:52 HereticPC kernel: nvme nvme2: Does your device have a faulty power saving mode enabled?
Nov 23 20:32:52 HereticPC kernel: nvme nvme2: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug
Nov 23 20:32:52 HereticPC udisksd[876]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/Samsung_SSD_970_EVO_Plus_1TB_S4EWNMFN810722V: Error updating Health Information: NVMe Identify Controller command error: Interrupted system call (g-bd-nvme-error-quark, 1)
Nov 23 20:32:52 HereticPC udisksd[876]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/Samsung_SSD_970_EVO_Plus_1TB_S4EWNMFN810703J: Error updating Health Information: No probed controller info available (udisks-error-quark, 0)
Nov 23 20:32:52 HereticPC kernel: nvme 0000:3f:00.0: enabling device (0000 -> 0002)
Nov 23 20:32:52 HereticPC kernel: nvme nvme2: Disabling device after reset failure: -19

and I don't like that there's

Nov 23 20:12:49 HereticPC kernel: nvme nvme0: controller is down; will reset: CSTS=0xffffffff, PCI_STATUS=0x10
Nov 23 20:12:49 HereticPC kernel: nvme nvme0: Does your device have a faulty power saving mode enabled?
Nov 23 20:12:49 HereticPC kernel: nvme nvme0: Try "nvme_core.default_ps_max_latency_us=0 pcie_aspm=off pcie_port_pm=off" and report a bug
Nov 23 20:12:49 HereticPC udisksd[876]: Error probing device: NVMe Identify Controller command error: Interrupted system call (g-bd-nvme-error-quark, 1)
Nov 23 20:12:49 HereticPC kernel: nvme 0000:02:00.0: enabling device (0000 -> 0002)
Nov 23 20:12:49 HereticPC kernel: nvme nvme0: Disabling device after reset failure: -19
Nov 23 20:12:49 HereticPC udisksd[876]: Error probing device: NVMe Identify Namespace command error: Input/output error (g-bd-nvme-error-quark, 1)

As for spare nvme - thing is, my mboard supports 3 m/2 slots, but my cpu doesn't have connectivity for all 3 of them - this slot supposed to work with the CPU from the next (11th) generation, so basically I have an SSD inside the non working slot.

To be clear, there still /is/ an inccessible device slotted in nvme0?

I doubt it has anything to do with the situation because it was always like that since I've assembled this PC and it didn't cause any problems

So the problem started somewhat like a week ago. Around that time I did a few things:

You could try to downgrade the system to the status quo ante, https://wiki.archlinux.org/title/Downgrading_packages
In doubt, a kernel downgrade is (unlike other packages relatively save) and probably sufficient.

Other than that, I'd yank the dead device out of there and see what happens…

Heretic12 · 2024-11-25 17:51:13

Removing unused nvme did not help - https://0x0.st/X5U2.txt, although now I can't see any EXT4 IO Errors...

UPD
Tried to build linux-mainline kernel, whick failed, but it was not doe to IO Error:

perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
sphinx-build didn't return its version at ./scripts/sphinx-pre-install line 303.
make[2]: *** [Documentation/Makefile:121: htmldocs] Error 1
make[1]: *** [/home/Heretic/.cache/yay/linux-mainline/src/linux-mainline/Makefile:1720: htmldocs] Error 2
make: *** [Makefile:224: __sub-make] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: linux-mainline-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
linux-mainline - exit status 4
linux-mainline-headers - exit status 4

UPD 2

The same result with XMP on and no CPU caps:

perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
sphinx-build didn't return its version at ./scripts/sphinx-pre-install line 303.
make[2]: *** [Documentation/Makefile:121: htmldocs] Error 1
make[1]: *** [/home/Heretic/.cache/yay/linux-mainline/src/linux-mainline/Makefile:1720: htmldocs] Error 2
make: *** [Makefile:224: __sub-make] Error 2
==> ERROR: A failure occurred in build().
    Aborting...
 -> error making: linux-mainline-exit status 4
 -> Failed to install the following packages. Manual intervention is required:
linux-mainline - exit status 4
linux-mainline-headers - exit status 4

And the journal: https://0x0.st/X5Gr.txt

Last edited by Heretic12 (2024-11-25 20:19:55)

seth · 2024-11-25 20:27:34

There're no nvme related errors in that journal.
The kernel build fails during the documentation - you could comment the entire htmldocs stuff in the PKGBUILD but that's not related to the OP.
As for stellaris

Nov 25 18:43:15 HereticPC drkonqi-coredump-processor[1063]: "/home/Heretic/.local/share/Steam/steamapps/common/Stellaris/stellaris" 3327 "/var/lib/systemd/coredump/core.stellaris.1000.39f40c9e5f2b4c1399f7b3336e05b2ca.3327.1732288842000000.zst"

https://wiki.archlinux.org/title/Core_d … _core_dump

Heretic12 · 2024-11-25 21:07:48

Cought it again with Stellaris - https://0x0.st/X5GG.txt. For some reason, I can't find it in the journal here, but I swear that after the game crashed any command in the terminal was giving me

Input/Output Error

OK, this is an interesting thing, so several of previous boots were written into 1 journal - https://0x0.st/X5GC.txt
A lot of cases of the good-old I/O Error

Last edited by Heretic12 (2024-11-25 21:30:28)

seth · 2024-11-26 08:10:36

https://0x0.st/X5GC.txt is a 38MB file and contains the journals of > 2000 boots.
https://0x0.st/X5GG.txt doesn't have any nvme errors.
Maybe the nvme errors have been red-herrings wrt stellaris all along and "just" degraded your LVM array.

As mentioned, stellaris seems to leave some coredumps behind, please have a look at them.

Heretic12 · 2024-11-26 15:44:36

OK, so I ran Stellaris right now, crashed and got this core dump:

           PID: 3196 (stellaris)
           UID: 1000 (Heretic)
           GID: 984 (users)
        Signal: 7 (BUS)
     Timestamp: Tue 2024-11-19 00:49:09 CET (1 week 0 days ago)
  Command Line: ./stellaris --pdx-launcher-session-token ab41d55f-fed1-4a08-923e-ea540fae5957 --paradox-account-userid dccce280-801f-45f8>
    Executable: /home/Heretic/.local/share/Steam/steamapps/common/Stellaris/stellaris
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-steam@2d4ec7710b0f4fe9900d1e6ccc25b2d1.service
          Unit: user@1000.service
     User Unit: app-steam@2d4ec7710b0f4fe9900d1e6ccc25b2d1.service
         Slice: user-1000.slice
     Owner UID: 1000 (Heretic)
       Boot ID: ba52bc2ff283450a842b4009102f7c20
    Machine ID: 1bb617050641491aa10de18c321e6593
      Hostname: 192.168.1.17
       Storage: /var/lib/systemd/coredump/core.stellaris.1000.ba52bc2ff283450a842b4009102f7c20.3196.1731973749000000.zst (missing)
       Message: Process 3196 (stellaris) of user 1000 dumped core.
                
                Stack trace of thread 3196:
                #0  0x000079205cae3d58 n/a (/run/host/usr/lib/libgcc_s.so.1 + 0x25d58)
                #1  0x000079205cadeff3 n/a (/run/host/usr/lib/libgcc_s.so.1 + 0x20ff3)
                #2  0x000079205cae133e n/a (/run/host/usr/lib/libgcc_s.so.1 + 0x2333e)
                #3  0x000079205af339a1 n/a (/run/host/usr/lib/libc.so.6 + 0x1249a1)
                #4  0x00000000035022e8 n/a (/home/Heretic/.local/share/Steam/steamapps/common/Stellaris/stellaris + 0x31022e8)
                ELF object binary architecture: AMD x86-64

And the previous run gave me similar one:

           PID: 3057 (stellaris)
           UID: 1000 (Heretic)
           GID: 984 (users)
        Signal: 7 (BUS)
     Timestamp: Mon 2024-11-25 21:43:58 CET (18h ago)
  Command Line: ./stellaris --pdx-launcher-session-token 45b64221-5913-4d72-8958-43f8a4daa5cb --paradox-account-userid dccce280-801f-45f8-be8c-64869032d99d --continuelastsave --no-sandbox -gdpr-compliant
    Executable: /home/Heretic/.local/share/Steam/steamapps/common/Stellaris/stellaris
 Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-steam@4b6c501cca654ee69eccc6c398acb182.service
          Unit: user@1000.service
     User Unit: app-steam@4b6c501cca654ee69eccc6c398acb182.service
         Slice: user-1000.slice
     Owner UID: 1000 (Heretic)
       Boot ID: b8c6899510f4424797b99e05363e280d
    Machine ID: 1bb617050641491aa10de18c321e6593
      Hostname: HereticPC
       Storage: /var/lib/systemd/coredump/core.stellaris.1000.b8c6899510f4424797b99e05363e280d.3057.1732567438000000.zst (present)
  Size on Disk: 679M
       Message: Process 3057 (stellaris) of user 1000 dumped core.
                
                Stack trace of thread 3057:
                #0  0x00007dafaad22d58 n/a (/run/host/usr/lib/libgcc_s.so.1 + 0x25d58)
                #1  0x00007dafaad1dff3 n/a (/run/host/usr/lib/libgcc_s.so.1 + 0x20ff3)
                #2  0x00007dafaad2033e n/a (/run/host/usr/lib/libgcc_s.so.1 + 0x2333e)
                #3  0x00007dafa91339a1 n/a (/run/host/usr/lib/libc.so.6 + 0x1249a1)
                #4  0x00000000035022e8 n/a (/home/Heretic/.local/share/Steam/steamapps/common/Stellaris/stellaris + 0x31022e8)
                ELF object binary architecture: AMD x86-64

seth · 2024-11-26 18:16:02

This is flatschpak steam?
How does the repo version behave?

Heretic12 · 2024-11-26 19:01:51

No, it's from pacman/multilib

seth · 2024-11-26 19:06:33

https://archlinux.org/packages/multilib … e-runtime/ ?
https://wiki.archlinux.org/title/Steam/ … ve_runtime (try not using that)

Otherwise/in general does "steam -no-cef-sandbox" help?

Heretic12 · 2024-11-26 19:37:17

No, this one:

[Heretic@HereticPC ~]$ pacman -Qii steam
Name            : steam
Version         : 1.0.0.81-2
Description     : Valve's digital software delivery system
Architecture    : x86_64
URL             : https://steampowered.com/
Licenses        : custom
Groups          : None
Provides        : None
Depends On      : bash  desktop-file-utils  diffutils  hicolor-icon-theme  curl  dbus  freetype2  gdk-pixbuf2  ttf-font  zenity  lsb-release  nss  usbutils  xorg-xrandr
                  vulkan-driver  vulkan-icd-loader  lsof  python  xdg-user-dirs  glibc  libxcrypt  libxcrypt-compat  gcc-libs  lib32-glibc  lib32-libxcrypt
                  lib32-libxcrypt-compat  lib32-libgl  lib32-gcc-libs  lib32-libx11  lib32-libxss  lib32-alsa-plugins  lib32-libgpg-error  lib32-nss
                  lib32-vulkan-driver  lib32-vulkan-icd-loader
Optional Deps   : steam-native-runtime: steam native runtime support
Required By     : None
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 4.02 MiB
Packager        : Giancarlo Razzolini <grazzolini@archlinux.org>
Build Date      : Thu Aug 22 11:52:39 2024
Install Date    : Mon Nov 18 22:55:30 2024
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature
Backup Files    : None
Extended Data   : pkgtype=pkg

seth · 2024-11-26 19:46:25

seth wrote:

does "steam -no-cef-sandbox" help?

Heretic12 · 2024-11-26 19:56:40

No

(process:10167): GLib-GObject-CRITICAL **: 20:55:02.384: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
reaping pid: 10167 -- gameoverlayui
Game Recording - game stopped [gameid=281990]

Heretic12 · 2024-11-26 20:00:03

No

seth · 2024-11-26 20:01:52

I don't get why you're getting SIGBUS when gtk aborts.
Do you have a coredump for process 10167 ?

Arch Linux

#26 2024-11-19 22:27:56

Re: Constant Input/Output Error

#27 2024-11-20 18:44:59

Re: Constant Input/Output Error

#28 2024-11-20 20:52:23

Re: Constant Input/Output Error

#29 2024-11-20 23:43:53

Re: Constant Input/Output Error

#30 2024-11-21 09:15:37

Re: Constant Input/Output Error

#31 2024-11-21 20:47:40

Re: Constant Input/Output Error

#32 2024-11-21 20:59:04

Re: Constant Input/Output Error

#33 2024-11-21 22:22:34

Re: Constant Input/Output Error

#34 2024-11-22 14:32:52

Re: Constant Input/Output Error

#35 2024-11-23 06:09:53

Re: Constant Input/Output Error

#36 2024-11-23 19:39:11

Re: Constant Input/Output Error

#37 2024-11-25 08:28:48

Re: Constant Input/Output Error

#38 2024-11-25 17:51:13

Re: Constant Input/Output Error

#39 2024-11-25 20:27:34

Re: Constant Input/Output Error

#40 2024-11-25 21:07:48

Re: Constant Input/Output Error

#41 2024-11-26 08:10:36

Re: Constant Input/Output Error

#42 2024-11-26 15:44:36

Re: Constant Input/Output Error

#43 2024-11-26 18:16:02

Re: Constant Input/Output Error

#44 2024-11-26 19:01:51

Re: Constant Input/Output Error

#45 2024-11-26 19:06:33

Re: Constant Input/Output Error

#46 2024-11-26 19:37:17

Re: Constant Input/Output Error

#47 2024-11-26 19:46:25

Re: Constant Input/Output Error

#48 2024-11-26 19:56:40

Re: Constant Input/Output Error

#49 2024-11-26 20:00:03

Re: Constant Input/Output Error

#50 2024-11-26 20:01:52

Re: Constant Input/Output Error

Board footer