How to get related crash logs and troubleshoot?

[MintGaming]

New Linux user here. How do you get a crash log after system shut down running a program? I am currently on 21.1 Vera with the 5.15.0-58 kernel. Playing non-steam games seems to be perfectly fine but it had crashed a few times when trying to record gameplay with OBS. Crashed once when using Blender. Steam gameing are impossible since it will always crash the computer whenever it renders a shader or whatever you call it. Even Steam itself will cause computer to shut down occasionally.
I think this is purely a software problem since I was on Manjaro back in mid November last year and I hadn't have any of the problems present today until the a kernel update. Should I switch to an older kernel to test? Only 5.15 kernels and one 5.19 kernel is available for me? How can I get an 5.10 kernel on 21.1 Vera?
Anyways, here is my system information.

Code: Select all

System:
  Kernel: 5.15.0-58-generic x86_64 bits: 64 compiler: gcc v: 11.3.0
    Desktop: Cinnamon 5.6.7 tk: GTK 3.24.33 wm: muffin vt: 7 dm: LightDM 1.30.0
    Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop System: Gigabyte product: H97-HD3 v: N/A
    serial: <superuser required> Chassis: type: 3 serial: <superuser required>
  Mobo: Gigabyte model: H97-HD3 serial: <superuser required>
    UEFI: American Megatrends v: F9c date: 03/03/2016
CPU:
  Info: quad core model: Intel Core i7-4771 bits: 64 type: MT MCP
    smt: enabled arch: Haswell rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 3752 high: 3791 min/max: 800/3900 cores: 1: 3784
    2: 3790 3: 3692 4: 3746 5: 3735 6: 3790 7: 3693 8: 3791 bogomips: 55871
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2080] vendor: Micro-Star MSI
    driver: nvidia v: 515.86.01 pcie: speed: 2.5 GT/s lanes: 16 ports:
    active: none off: HDMI-A-1 empty: DP-1, DP-2, DP-3, Unknown-1
    bus-ID: 01:00.0 chip-ID: 10de:1e82 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.3 driver: X: loaded: nvidia
    unloaded: fbdev,modesetting,nouveau,vesa gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 3840x2160 s-dpi: 162 s-size: 602x341mm (23.7x13.4")
    s-diag: 692mm (27.2")
  Monitor-1: HDMI-0 res: 3840x2160 hz: 60 dpi: 163
    size: 600x340mm (23.6x13.4") diag: 690mm (27.2")
  OpenGL: renderer: NVIDIA GeForce RTX 2080/PCIe/SSE2
    v: 4.6.0 NVIDIA 515.86.01 direct render: Yes
Audio:
  Device-1: Intel 9 Series Family HD Audio vendor: Gigabyte
    driver: snd_hda_intel v: kernel bus-ID: 00:1b.0 chip-ID: 8086:8ca0
    class-ID: 0403
  Device-2: NVIDIA TU104 HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: speed: 8 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:10f8 class-ID: 0403
  Device-3: Kingston HyperX 7.1 Audio type: USB
    driver: hid-generic,snd-usb-audio,usbhid bus-ID: 3-3:2 chip-ID: 0951:16a4
    class-ID: 0300 serial: <filter>
  Sound Server-1: ALSA v: k5.15.0-58-generic running: yes
  Sound Server-2: PulseAudio v: 15.99.1 running: yes
  Sound Server-3: PipeWire v: 0.3.48 running: yes
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Gigabyte driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
  IF-ID-1: virbr0 state: down mac: <filter>
Drives:
  Local Storage: total: 8.19 TiB used: 2.8 TiB (34.2%)
  ID-1: /dev/sda vendor: Western Digital model: WDS100T2B0A-00SM50
    size: 931.51 GiB speed: 6.0 Gb/s type: SSD serial: <filter> rev: 00WD
    scheme: GPT
  ID-2: /dev/sdb vendor: HGST (Hitachi) model: HUS726T4TALE6L4
    size: 3.64 TiB speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: W460 scheme: GPT
  ID-3: /dev/sdc vendor: HGST (Hitachi) model: HUS726T4TALE6L4
    size: 3.64 TiB speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: W40H scheme: GPT
Partition:
  ID-1: / size: 915.32 GiB used: 182.09 GiB (19.9%) fs: ext4 dev: /dev/sda2
  ID-2: /boot/efi size: 511 MiB used: 5.2 MiB (1.0%) fs: vfat
    dev: /dev/sda1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
Sensors:
  System Temperatures: cpu: 51.0 C mobo: 27.8 C gpu: nvidia temp: 42 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 23%
Repos:
  Packages: 3662 apt: 3653 flatpak: 9
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb https://mirror-hk.koddos.net/linuxmint/packages vera main upstream import backport
    2: deb http://mirror.as.kamatera.com/ubuntu jammy main restricted universe multiverse
    3: deb http://mirror.as.kamatera.com/ubuntu jammy-updates main restricted universe multiverse
    4: deb http://mirror.as.kamatera.com/ubuntu jammy-backports main restricted universe multiverse
    5: deb http://security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  Active apt repos in: /etc/apt/sources.list.d/protonvpn-stable.list
    1: deb [arch="all", signed-by=/usr/share/keyrings/protonvpn-stable-archive-keyring.gpg] https://repo.protonvpn.com/debian stable main
Info:
  Processes: 297 Uptime: 18m wakeups: 1 Memory: 15.55 GiB
  used: 2.93 GiB (18.8%) Init: systemd v: 249 runlevel: 5 Compilers:
  gcc: 11.3.0 alt: 11 Shell: Bash v: 5.1.16 running-in: gnome-terminal
  inxi: 3.3.13

[rene]

New Linux user here. How do you get a crash log after system shut down running a program?

Most often in fact simply "not" since said crash will also have kept anything useful from reaching a log -- but FWIW you with journalctl -b -1 or journalctl -rb -1 (for reverse-order) are presented the logs from the boot before this one, i.e., due to the -1. You are placed in the viewer less to view such by default; https://linuxize.com/post/less-command-in-linux/

[spamegg]

There is also the Logs application in your Menu.

[MintGaming]

It appears that even non-steam games are causing my computer to shut down. I tried "Shadow Tactics Blades of the Shogun Demo" from Gog.com and it crashed twice exactly when it finished up loading screen.
Here I've got 2 identical errors under Logs's "Important" section related with the graphics card 3 seconds apart.

Code: Select all

[drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership

[rene]

That would then likely be an Nvidia-specific matter. You may need/want to repost with an also Nvidia-specific topic title so as to attract someone that knows Nvidia issues (most longer-time Linux users don't use Nvidia due to the proprietary driver issues).

[MintGaming]

Thank you for the quick response but as I said on the original post, the system worked flawlessly previously on Manjaro 5.10 kernel back in November last year(could be wrong but it's the latest one before the 5.15 kernel update). I am not sure if the errors from the log is what caused the computer to shut down. I had also tried all the available Nvidia drivers. I believe this is a problem related to the kernel. I would like to know how to get 5.10 kernel to be installed on Mint 21.1 if you can teach me how to. It doesn't appear on the Update Manager list. Thanks!

[rene]

I'm not in fact on Linux Mint and was explicitly not commenting on that part of your post. IIRC 21.1 has or had indeed 5.15 alone and at least at minimum available in a "blessed" manner -- but allow for someone in fact on Mint 21.1 to know better.

What you can always do is grab a so-called mainline kernel from...

What you could always have done had Ubuntu not seemingly effed up the amd64 build is grab a mainline kernel from e.g. https://kernel.ubuntu.com/~kernel-ppa/m ... v5.10.165/ but that's out then as well at the moment. Sorry -- I've no better advise available.

[EDIT] Seems https://kernel.ubuntu.com/~kernel-ppa/m ... v5.10.130/ is the last successful amd64 build. You'd grab all amd64 .debs except the -lowlatency ones to e.g. ~/Downloads/5.0.10/ and from that directory use sudo dpkg -i *.deb. On reboot you'd likely have to pick that kernel explicitly from the Grub menu -- but I'd not worry about that for now since I doubt it'll fix your issue anyway.

[MiZoG]

It looks like a gpu-related problem. I see no valid reason to implicate kernel(s).
I haven't come across any indication that your gpu doesn't function properly under whichever kernel series.

Now for Shadow Tactics: Blades of the Shogun Demo
it is clearly mentioned that you need a bunch of 32bit libs. Did you install those?
That also reminds me to ask: have you installed 32bit opengl / vulkan libs into your system? Packages like libopengl0:i386, libnvidia-gl-518:i386, libvulkan1:i386?

Just happened and I skipped 515.x drivers on Mint. 470.x and 510.x drivers proved rock-solid for me on LM 20.3 and I don't face any stability problem so far on Vera (21.1) with 525.x drivers (available in Driver Manager).

Tip for worry-free operation of Steam Linux client: turn off hardware acceleration in app settings.
For specific Steam games (native or steam-proton) start separate threads.

OBS / Blender is another story. It can be a hit or miss with an otherwise most stable system. It might take a few efforts to find a specific version (PPA, flatpak or whatever) to work with specific driver versions and so on. However being on nvidia is an advantage in this case.

[SMG]

Here I've got 2 identical errors under Logs's "Important" section related with the graphics card 3 seconds apart.

Code: Select all

[drm:nv_drm_master_set [nvidia_drm]] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership

That's a common message which, so far, I've not seen related to any specific issues. I have seen it in a lot of logs and it's there for people who do not have any problems. It's entire possible those messages appeared during system start-up.

How do you get a crash log after system shut down running a program?

You should look for the specific logs of the application which shut down. Unless the operating system completely froze or shut down, then it is likely the issue is with the application itself.

OBS is an extremely resource-intensive application. OBS does have logs. I would presume the games do as well.

Steam gameing are impossible since it will always crash the computer whenever it renders a shader or whatever you call it. Even Steam itself will cause computer to shut down occasionally.

The computer physically turns off?

Everyone has a different definition of a crash, so it is best if you give more detail of what you see and hear happening when the computer "crashes".

How can I get an 5.10 kernel on 21.1 Vera?

Why are you asking about the 5.10 kernel? It was never an HWE kernel in Ubuntu although there was a 5.10-oem version.

[MintGaming]

Why are you asking about the 5.10 kernel? It was never an HWE kernel in Ubuntu although there was a 5.10-oem version.

I apologize about this first. Turns out I was on the 5.15.60-1-Manjaro kernel not 5.10 kernel. Here is the info got from my Manjaro USB drive which ran most of everything fine back then.

Code: Select all

System:
  Kernel: 5.15.60-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 12.1.1
    Desktop: Xfce v: 4.16.0 tk: Gtk v: 3.24.29 info: xfce4-panel wm: xfwm
    v: 4.16.1 vt: 7 dm: LightDM v: 1.32.0 Distro: Manjaro Linux
    base: Arch Linux
Machine:
  Type: Desktop System: Gigabyte product: H97-HD3 v: N/A
    serial: <superuser required> Chassis: type: 3 serial: <superuser required>
  Mobo: Gigabyte model: H97-HD3 serial: <superuser required>
    UEFI: American Megatrends v: F9c date: 03/03/2016
CPU:
  Info: quad core model: Intel Core i7-4771 bits: 64 type: MT MCP
    smt: enabled arch: Haswell rev: 3 cache: L1: 256 KiB L2: 1024 KiB L3: 8 MiB
  Speed (MHz): avg: 1197 high: 2501 min/max: 800/3900 cores: 1: 798 2: 1841
    3: 1223 4: 798 5: 799 6: 824 7: 2501 8: 799 bogomips: 55894
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: NVIDIA TU104 [GeForce RTX 2080] vendor: Micro-Star MSI
    driver: nvidia v: 515.65.01 arch: Turing pcie: speed: 2.5 GT/s lanes: 16
    bus-ID: 01:00.0 chip-ID: 10de:1e82 class-ID: 0300
  Display: x11 server: X.Org v: 21.1.4 compositor: xfwm v: 4.16.1 driver:
    X: loaded: nvidia gpu: nvidia display-ID: :0.0 screens: 1
  Screen-1: 0 s-res: 3840x2160 s-dpi: 162 s-size: 602x341mm (23.70x13.43")
    s-diag: 692mm (27.24")
  Monitor-1: HDMI-0 res: 3840x2160 hz: 60 dpi: 163
    size: 600x340mm (23.62x13.39") diag: 690mm (27.15") modes: N/A
  Message: Unable to show GL data. Required tool glxinfo missing.
Audio:
  Device-1: Intel 9 Series Family HD Audio vendor: Gigabyte
    driver: snd_hda_intel bus-ID: 3-3:2 v: kernel bus-ID: 00:1b.0
    chip-ID: 0951:16a4 chip-ID: 8086:8ca0 class-ID: 0300 serial: <filter>
    class-ID: 0403
  Device-2: NVIDIA TU104 HD Audio vendor: Micro-Star MSI
    driver: snd_hda_intel v: kernel pcie: speed: 2.5 GT/s lanes: 16
    bus-ID: 01:00.1 chip-ID: 10de:10f8 class-ID: 0403
  Device-3: Kingston HyperX 7.1 Audio type: USB
    driver: hid-generic,snd-usb-audio,usbhid
  Sound Server-1: ALSA v: k5.15.60-1-MANJARO running: yes
  Sound Server-2: JACK v: 1.9.21 running: no
  Sound Server-3: PulseAudio v: 16.1 running: yes
  Sound Server-4: PipeWire v: 0.3.56 running: no
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Gigabyte driver: r8169 v: kernel pcie: speed: Unknown lanes: 63
    port: d000 bus-ID: 03:00.0 chip-ID: 10ec:8168 class-ID: 0200
  IF: enp3s0 state: down mac: <filter>
Drives:
  Local Storage: total: 8.2 TiB used: 0 KiB (0.0%)
  ID-1: /dev/sda vendor: Western Digital model: WDS100T2B0A-00SM50
    size: 931.51 GiB speed: 6.0 Gb/s type: SSD serial: <filter> rev: 00WD
    scheme: GPT
  ID-2: /dev/sdb vendor: HGST (Hitachi) model: HUS726T4TALE6L4
    size: 3.64 TiB speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: W460 scheme: GPT
  ID-3: /dev/sdc vendor: HGST (Hitachi) model: HUS726T4TALE6L4
    size: 3.64 TiB speed: 6.0 Gb/s type: HDD rpm: 7200 serial: <filter>
    rev: W40H scheme: GPT
  ID-4: /dev/sdd type: USB model: SD MMC Card Reader size: 15.05 GiB
    type: SSD serial: <filter> rev: 1.00 scheme: MBR
Partition:
  Message: No partition data found.
Swap:
  Alert: No swap data was found.
Sensors:
  System Temperatures: cpu: 34.0 C mobo: N/A gpu: nvidia temp: 35 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 23%
Info:
  Processes: 222 Uptime: 16m wakeups: 1 Memory: 15.55 GiB used: 2.13 GiB
  (13.7%) Init: systemd v: 251 default: graphical Compilers: gcc: 12.1.1
  clang: 14.0.6 Shell: Bash v: 5.1.16 running-in: xfce4-terminal inxi: 3.3.20
  

The computer physically turns off? Everyone has a different definition of a crash, so it is best if you give more detail of what you see and hear happening when the computer "crashes"

Yes, it was always unforgiving, it will shut down the computer completely(power off) then reboot itself immediately.

You should look for the specific logs of the application which shut down. Unless the operating system completely froze or shut down, then it is likely the issue is with the application itself. OBS is an extremely resource-intensive application. OBS does have logs. I would presume the games do as well.

Skyrim is one of the many games that will cause my computer to shut down. I have set Storage=persistent on my /etc/systemd/journald.conf This is the log after the computer have shut down.

Code: Select all

Jan 28 20:05:05 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#15 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Jan 28 20:05:05 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#15 Sense Key : Not Ready [current] 
Jan 28 20:05:05 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#15 Add. Sense: Medium not present - tray closed
Jan 28 20:05:05 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#15 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Jan 28 20:05:05 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
Jan 28 20:05:05 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#16 unaligned transfer
Jan 28 20:05:05 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:05 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 0, async page read
Jan 28 20:05:05 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#17 unaligned transfer
Jan 28 20:05:05 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:05 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 1, async page read
Jan 28 20:05:05 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#18 unaligned transfer
Jan 28 20:05:05 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 2 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:05 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 2, async page read
Jan 28 20:05:05 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#19 unaligned transfer
Jan 28 20:05:05 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 3 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:05 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 3, async page read
Jan 28 20:05:05 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#20 unaligned transfer
Jan 28 20:05:05 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 4 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:05 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 4, async page read
Jan 28 20:05:05 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#21 unaligned transfer
Jan 28 20:05:05 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 5 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:05 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 5, async page read
Jan 28 20:05:05 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#22 unaligned transfer
Jan 28 20:05:05 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 6 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:05 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 6, async page read
Jan 28 20:05:05 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#23 unaligned transfer
Jan 28 20:05:05 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 7 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:05 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 7, async page read
Jan 28 20:05:09 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#2 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Jan 28 20:05:09 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#2 Sense Key : Not Ready [current] 
Jan 28 20:05:09 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#2 Add. Sense: Medium not present - tray closed
Jan 28 20:05:09 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#2 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Jan 28 20:05:09 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
Jan 28 20:05:09 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#3 unaligned transfer
Jan 28 20:05:09 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 0, async page read
Jan 28 20:05:09 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#4 unaligned transfer
Jan 28 20:05:09 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 1, async page read
Jan 28 20:05:09 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#5 unaligned transfer
Jan 28 20:05:09 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#6 unaligned transfer
Jan 28 20:05:09 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#7 unaligned transfer
Jan 28 20:05:09 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#8 unaligned transfer
Jan 28 20:05:09 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#9 unaligned transfer
Jan 28 20:05:09 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#10 unaligned transfer
Jan 28 20:05:22 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#21 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Jan 28 20:05:22 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#21 Sense Key : Not Ready [current] 
Jan 28 20:05:22 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#21 Add. Sense: Medium not present - tray closed
Jan 28 20:05:22 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#21 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Jan 28 20:05:22 cacluator-H97-HD3 kernel: print_req_error: 8 callbacks suppressed
Jan 28 20:05:22 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0
Jan 28 20:05:22 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#22 unaligned transfer
Jan 28 20:05:22 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:22 cacluator-H97-HD3 kernel: buffer_io_error: 6 callbacks suppressed
Jan 28 20:05:22 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 0, async page read
Jan 28 20:05:22 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#23 unaligned transfer
Jan 28 20:05:22 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:22 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 1, async page read
Jan 28 20:05:22 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#27 unaligned transfer
Jan 28 20:05:22 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 2 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:22 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 2, async page read
Jan 28 20:05:22 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#28 unaligned transfer
Jan 28 20:05:22 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 3 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:22 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 3, async page read
Jan 28 20:05:22 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#29 unaligned transfer
Jan 28 20:05:22 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 4 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:22 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 4, async page read
Jan 28 20:05:22 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#30 unaligned transfer
Jan 28 20:05:22 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 5 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:22 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 5, async page read
Jan 28 20:05:22 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#0 unaligned transfer
Jan 28 20:05:22 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 6 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:22 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 6, async page read
Jan 28 20:05:22 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#1 unaligned transfer
Jan 28 20:05:22 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 7 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:22 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 7, async page read
Jan 28 20:05:30 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#14 FAILED Result: hostbyte=DID_OK driverbyte=DRIVER_OK cmd_age=0s
Jan 28 20:05:30 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#14 Sense Key : Not Ready [current] 
Jan 28 20:05:30 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#14 Add. Sense: Medium not present - tray closed
Jan 28 20:05:30 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#14 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00
Jan 28 20:05:30 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
Jan 28 20:05:30 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#15 unaligned transfer
Jan 28 20:05:30 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:30 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 0, async page read
Jan 28 20:05:30 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#16 unaligned transfer
Jan 28 20:05:30 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 1 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:30 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 1, async page read
Jan 28 20:05:30 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#21 unaligned transfer
Jan 28 20:05:30 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 2 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:30 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 2, async page read
Jan 28 20:05:30 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#22 unaligned transfer
Jan 28 20:05:30 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 3 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:30 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 3, async page read
Jan 28 20:05:30 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#23 unaligned transfer
Jan 28 20:05:30 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 4 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:30 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 4, async page read
Jan 28 20:05:30 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#31 unaligned transfer
Jan 28 20:05:30 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 5 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:30 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 5, async page read
Jan 28 20:05:30 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#0 unaligned transfer
Jan 28 20:05:30 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 6 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:30 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 6, async page read
Jan 28 20:05:30 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#1 unaligned transfer
Jan 28 20:05:30 cacluator-H97-HD3 kernel: blk_update_request: I/O error, dev sr0, sector 7 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0
Jan 28 20:05:30 cacluator-H97-HD3 kernel: Buffer I/O error on dev sr0, logical block 7, async page read

-- Boot d4af8cc99f0d40028ed5f8cec15ecd60 --

Jan 28 20:06:27 cacluator-H97-HD3 kernel: microcode: microcode updated early to revision 0x28, date = 2019-11-12
Jan 28 20:06:27 cacluator-H97-HD3 kernel: Linux version 5.15.0-58-generic (buildd@lcy02-amd64-101) (gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld 

The following is the system logs of Steam(4077), Wine, Wineserver and Skyrim after the computer shut down.

Code: Select all

cacluator@cacluator-H97-HD3:~$ journalctl _PID=4077
Jan 24 16:56:18 cacluator-H97-HD3 sudo[4077]: cacluator : PWD=/home/cacluator ; USER=root ; COMMAND=/usr/bin/mint-refresh-cache
Jan 24 16:56:18 cacluator-H97-HD3 sudo[4077]: pam_unix(sudo:session): session opened for user root(uid=0) by (uid=1000)
Jan 24 16:56:26 cacluator-H97-HD3 sudo[4077]: pam_unix(sudo:session): session closed for user root
cacluator@cacluator-H97-HD3:~$ journalctl _PID=4082
-- No entries --
cacluator@cacluator-H97-HD3:~$ journalctl _PID=5235
-- No entries --
cacluator@cacluator-H97-HD3:~$ journalctl _PID=5167
-- No entries --
cacluator@cacluator-H97-HD3:~$ journalctl _PID=5169
-- No entries --
cacluator@cacluator-H97-HD3:~$ journalctl _PID=4084

As for OBS, it didn't gave me any useful information regarding computer crashes. And it's only really crash when it's recording a steam game or with steam app opened. Even opening up the steam app and browsing the game library can cause computer to shut down occasionally.

Now for Shadow Tactics: Blades of the Shogun Demo
it is clearly mentioned that you need a bunch of 32bit libs. Did you install those?
That also reminds me to ask: have you installed 32bit opengl / vulkan libs into your system? Packages like libopengl0:i386, libnvidia-gl-518:i386, libvulkan1:i386?
Tip for worry-free operation of Steam Linux client: turn off hardware acceleration in app settings.
For specific Steam games (native or steam-proton) start separate threads.

Even using the steam app itself will cause computer to shut down. I have tried the following, plays steam games with native linux support only, plays steam games with the latest version of proton, plays steam games with older version of proton, plays steam games with proton-GE. I believe it already had all the needed library installed on proton. All to no avail. Plus, Shadow Tactics: Blades of the Shogun Demo is available for linux natively. I also tried other older games such as Postal Classic Uncut, Shadow Warrior Classic, Beneath A Steel Sky and it had no problem running them. Playing Counter Strike 1.6 on steam while recording with OBS is also fine(tested playing for 20 minutes). I have also tried playing with hardware acceleration off. Didn't fix anything.

Here is a screenshot of Skyrim(Original) on the main menu. Does anything look unusual here? Loading the game saves, opening the map, entering a new area, object/npc appearing on screen will cause computer to shut down when playing.

[MintGaming]

Now for Shadow Tactics: Blades of the Shogun Demo
it is clearly mentioned that you need a bunch of 32bit libs. Did you install those?
That also reminds me to ask: have you installed 32bit opengl / vulkan libs into your system? Packages like libopengl0:i386, libnvidia-gl-518:i386, libvulkan1:i386?

Yes. I just checked. I had them all installed. Here is the log when I ran the game:

Code: Select all

Jan 28 23:51:30 cacluator-H97-HD3 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=6b7cd341-043d-4f3a-aa02-7881e006ebbb ro quiet splash iommu=1 intel_iommu=on
Jan 28 23:51:30 cacluator-H97-HD3 kernel: Linux version 5.15.0-58-generic (buildd@lcy02-amd64-101) (gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 (Ubuntu 5.15.0-58.64-generic 5.15.74)
Jan 28 23:51:30 cacluator-H97-HD3 kernel: microcode: microcode updated early to revision 0x28, date = 2019-11-12
-- Boot 209b10bfb34849ada92b05d795b4f986 --
Jan 28 23:49:38 cacluator-H97-HD3 kernel: process 'Gog_Games/Shadow Tactics Blades of the Shogun Demo/game/Shadow Tactics' started with executable stack
Jan 28 23:48:04 cacluator-H97-HD3 kernel: sr 4:0:0:0: [sr0] tag#22 unaligned transfer

It seems that there isn't any log related to the game itself other than that one line.

[SMG]

I apologize about this first. Turns out I was on the 5.15.60-1-Manjaro kernel not 5.10 kernel.

So basically what you are using in LM21.1. The 5.15.0-x kernel from Ubuntu backports fixes from later 5.15 kernel.

Yes, it was always unforgiving, it will shut down the computer completely(power off) then reboot itself immediately.

That sounds like a hardware issue, a failing or undersized PSU.

The operating system either reboots (warm boot where only the operating system restarts) or it shuts down. It does not restart after a shutdown.

Skyrim is one of the many games that will cause my computer to shut down. I have set Storage=persistent on my /etc/systemd/journald.conf This is the log after the computer have shut down.

I/O errors usually indicate a hardware issue. Could be the drive, a cable to the drive, or a connector.

If your system is not currently backed up, I suggest doing that now.

[MiZoG]

Somehow I have Blades of the Shogun in my GOG account. A giveaway I don't recall. This is how I at least got it in Epic store as well.
I have 2 nvidia-gpu-powered systems (LM 21.1 intel i5 7500, gtx 1050ti, 5.15.0-58, 525.78.x + LMDE5 Intel i5 6600T, gtx 750ti, 5.10.0-21, 470.161.x).
Full game (not demo) works fine on both.
Hard for me to believe the problem you face is driver/kernel related.
Those boot arguments of yours iommu=1 intel_iommu=on strike me as odd and unnecessary but I don't positively know if they affect your gpu under Linux.
Since you suffer from forced reboots, you should check n repair your filesystem, see here and there.
If the erratic behaviour you describe persists, you should look into your hardware. PSU? GPU dying?