You are not logged in.

#26 2023-10-03 18:15:51

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,330

Re: [SOLVED] Green screen crash

The screensaver timeout is at exactly 10 minutes …

xset s off

Offline

#27 2023-10-11 18:02:59

blinkingbit
Member
Registered: 2023-02-03
Posts: 59

Re: [SOLVED] Green screen crash

It happened again sad Xorg log
This time only the main monitor connected with brand new cable in a completely different DP port to the previous ones and no sleeping/screensaver this time.

xset -q

Keyboard Control:
  auto repeat:  on    key click percent:  0    LED mask:  00000000
  XKB indicators:
    00: Caps Lock:   off    01: Num Lock:    off    02: Scroll Lock: off
    03: Compose:     off    04: Kana:        off    05: Sleep:       off
    06: Suspend:     off    07: Mute:        off    08: Misc:        off
    09: Mail:        off    10: Charging:    off    11: Shift Lock:  off
    12: Group 2:     off    13: Mouse Keys:  off
  auto repeat delay:  660    repeat rate:  25
  auto repeating keys:  00ffffffdffffbbf
                        fadfffefffedffff
                        9fffffffffffffff
                        fff7ffffffffffff
  bell percent:  50    bell pitch:  400    bell duration:  100
Pointer Control:
  acceleration:  2/1    threshold:  4
Screen Saver:
  prefer blanking:  yes    allow exposures:  yes
  timeout:  0    cycle:  600
Colors:
  default colormap:  0x20    BlackPixel:  0x0    WhitePixel:  0xffffff
Font Path:
  built-ins
DPMS (Display Power Management Signaling):
  Server does not have the DPMS Extension

While looking for solutions I have found that lspci -v outputs only my gpu controller for VGA even though I'm only using DisplayPort and HDMI(It says "VGA compatible" but it doesn't mention DP or HDMI but they are mentioned as audio controllers):

00:00.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14d8
	Subsystem: ASUSTeK Computer Inc. Device 8877
	Flags: fast devsel

00:00.2 IOMMU: Advanced Micro Devices, Inc. [AMD] Device 14d9
	Subsystem: ASUSTeK Computer Inc. Device 8877
	Flags: bus master, fast devsel, latency 0, IRQ 26
	Capabilities: <access denied>

00:01.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14da
	Flags: fast devsel, IOMMU group 0

00:01.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14db (prog-if 00 [Normal decode])
	Subsystem: ASUSTeK Computer Inc. Device 8877
	Flags: bus master, fast devsel, latency 0, IRQ 27, IOMMU group 1
	Bus: primary=00, secondary=01, subordinate=03, sec-latency=0
	I/O behind bridge: f000-ffff [size=4K] [16-bit]
	Memory behind bridge: fcb00000-fcdfffff [size=3M] [32-bit]
	Prefetchable memory behind bridge: fa00000000-fc0fffffff [size=8448M] [32-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:01.2 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14db (prog-if 00 [Normal decode])
	Subsystem: ASUSTeK Computer Inc. Device 8877
	Flags: bus master, fast devsel, latency 0, IRQ 28, IOMMU group 2
	Bus: primary=00, secondary=04, subordinate=04, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: fcf00000-fcffffff [size=1M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:02.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14da
	Flags: fast devsel, IOMMU group 3

00:02.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14db (prog-if 00 [Normal decode])
	Subsystem: ASUSTeK Computer Inc. Device 8877
	Flags: bus master, fast devsel, latency 0, IRQ 29, IOMMU group 4
	Bus: primary=00, secondary=05, subordinate=13, sec-latency=0
	I/O behind bridge: e000-efff [size=4K] [16-bit]
	Memory behind bridge: fc100000-fc6fffff [size=6M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:03.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14da
	Flags: fast devsel, IOMMU group 5

00:04.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14da
	Flags: fast devsel, IOMMU group 6

00:08.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14da
	Flags: fast devsel, IOMMU group 7

00:08.1 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14dd (prog-if 00 [Normal decode])
	Subsystem: ASUSTeK Computer Inc. Device 8877
	Flags: bus master, fast devsel, latency 0, IRQ 30, IOMMU group 8
	Bus: primary=00, secondary=14, subordinate=14, sec-latency=0
	I/O behind bridge: d000-dfff [size=4K] [16-bit]
	Memory behind bridge: fc700000-fcafffff [size=4M] [32-bit]
	Prefetchable memory behind bridge: fc20000000-fc301fffff [size=258M] [32-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:08.3 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 14dd (prog-if 00 [Normal decode])
	Subsystem: ASUSTeK Computer Inc. Device 8877
	Flags: bus master, fast devsel, latency 0, IRQ 31, IOMMU group 9
	Bus: primary=00, secondary=15, subordinate=15, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: fce00000-fcefffff [size=1M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

00:14.0 SMBus: Advanced Micro Devices, Inc. [AMD] FCH SMBus Controller (rev 71)
	Subsystem: ASUSTeK Computer Inc. FCH SMBus Controller
	Flags: 66MHz, medium devsel, IOMMU group 10
	Kernel driver in use: piix4_smbus
	Kernel modules: i2c_piix4, sp5100_tco

00:14.3 ISA bridge: Advanced Micro Devices, Inc. [AMD] FCH LPC Bridge (rev 51)
	Subsystem: ASUSTeK Computer Inc. FCH LPC Bridge
	Flags: bus master, 66MHz, medium devsel, latency 0, IOMMU group 10

00:18.0 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e0
	Flags: fast devsel, IOMMU group 11

00:18.1 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e1
	Flags: fast devsel, IOMMU group 11

00:18.2 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e2
	Flags: fast devsel, IOMMU group 11

00:18.3 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e3
	Flags: fast devsel, IOMMU group 11
	Kernel driver in use: k10temp
	Kernel modules: k10temp

00:18.4 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e4
	Flags: fast devsel, IOMMU group 11

00:18.5 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e5
	Flags: fast devsel, IOMMU group 11

00:18.6 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e6
	Flags: fast devsel, IOMMU group 11

00:18.7 Host bridge: Advanced Micro Devices, Inc. [AMD] Device 14e7
	Flags: fast devsel, IOMMU group 11

01:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Upstream Port of PCI Express Switch (rev c1) (prog-if 00 [Normal decode])
	Flags: bus master, fast devsel, latency 0, IRQ 32, IOMMU group 12
	Memory at fcd00000 (32-bit, non-prefetchable) [size=16K]
	Bus: primary=01, secondary=02, subordinate=03, sec-latency=0
	I/O behind bridge: f000-ffff [size=4K] [16-bit]
	Memory behind bridge: fcb00000-fccfffff [size=2M] [32-bit]
	Prefetchable memory behind bridge: fa00000000-fc0fffffff [size=8448M] [32-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

02:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch (prog-if 00 [Normal decode])
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 XL Downstream Port of PCI Express Switch
	Flags: bus master, fast devsel, latency 0, IRQ 33, IOMMU group 13
	Bus: primary=02, secondary=03, subordinate=03, sec-latency=0
	I/O behind bridge: f000-ffff [size=4K] [16-bit]
	Memory behind bridge: fcb00000-fccfffff [size=2M] [32-bit]
	Prefetchable memory behind bridge: fa00000000-fc0fffffff [size=8448M] [32-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

03:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Navi 23 [Radeon RX 6650 XT / 6700S / 6800S] (rev c1) (prog-if 00 [VGA controller])
	Subsystem: Micro-Star International Co., Ltd. [MSI] Navi 23 [Radeon RX 6650 XT / 6700S / 6800S]
	Flags: bus master, fast devsel, latency 0, IRQ 103, IOMMU group 14
	Memory at fa00000000 (64-bit, prefetchable) [size=8G]
	Memory at fc00000000 (64-bit, prefetchable) [size=256M]
	I/O ports at f000 [size=256]
	Memory at fcb00000 (32-bit, non-prefetchable) [size=1M]
	Expansion ROM at fcc00000 [disabled] [size=128K]
	Capabilities: <access denied>
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

03:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Navi 21/23 HDMI/DP Audio Controller
	Flags: bus master, fast devsel, latency 0, IRQ 124, IOMMU group 15
	Memory at fcc20000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

04:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 (prog-if 02 [NVM Express])
	Subsystem: Samsung Electronics Co Ltd SSD 970 EVO
	Flags: bus master, fast devsel, latency 0, IRQ 47, NUMA node 0, IOMMU group 16
	Memory at fcf00000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: nvme
	Kernel modules: nvme

05:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43f4 (rev 01) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3328
	Flags: bus master, fast devsel, latency 0, IRQ 24, IOMMU group 17
	Bus: primary=05, secondary=06, subordinate=13, sec-latency=0
	I/O behind bridge: e000-efff [size=4K] [16-bit]
	Memory behind bridge: fc100000-fc6fffff [size=6M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

06:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43f5 (rev 01) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3328
	Flags: bus master, fast devsel, latency 0, IRQ 34, IOMMU group 18
	Bus: primary=06, secondary=07, subordinate=07, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: [disabled] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

06:06.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43f5 (rev 01) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3328
	Flags: bus master, fast devsel, latency 0, IRQ 36, IOMMU group 19
	Bus: primary=06, secondary=08, subordinate=08, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: [disabled] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

06:07.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43f5 (rev 01) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3328
	Flags: bus master, fast devsel, latency 0, IRQ 38, IOMMU group 20
	Bus: primary=06, secondary=09, subordinate=09, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: fc600000-fc6fffff [size=1M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

06:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43f5 (rev 01) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3328
	Flags: bus master, fast devsel, latency 0, IRQ 39, IOMMU group 21
	Bus: primary=06, secondary=0a, subordinate=11, sec-latency=0
	I/O behind bridge: e000-efff [size=4K] [16-bit]
	Memory behind bridge: fc100000-fc3fffff [size=3M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

06:0c.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43f5 (rev 01) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3328
	Flags: bus master, fast devsel, latency 0, IRQ 24, IOMMU group 22
	Bus: primary=06, secondary=12, subordinate=12, sec-latency=0
	I/O behind bridge: [disabled] [16-bit]
	Memory behind bridge: fc500000-fc5fffff [size=1M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

06:0d.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43f5 (rev 01) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3328
	Flags: bus master, fast devsel, latency 0, IRQ 40, IOMMU group 23
	Bus: primary=06, secondary=13, subordinate=13, sec-latency=0
	I/O behind bridge: [disabled] [16-bit]
	Memory behind bridge: fc400000-fc4fffff [size=1M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

09:00.0 Network controller: Intel Corporation Wi-Fi 6 AX200 (rev 1a)
	Subsystem: Intel Corporation Wi-Fi 6 AX200NGW
	Flags: bus master, fast devsel, latency 0, IRQ 37, IOMMU group 20
	Memory at fc600000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: iwlwifi
	Kernel modules: iwlwifi

0a:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43f4 (rev 01) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3328
	Flags: bus master, fast devsel, latency 0, IRQ 24, IOMMU group 21
	Bus: primary=0a, secondary=0b, subordinate=11, sec-latency=0
	I/O behind bridge: e000-efff [size=4K] [16-bit]
	Memory behind bridge: fc100000-fc3fffff [size=3M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

0b:00.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43f5 (rev 01) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3328
	Flags: bus master, fast devsel, latency 0, IRQ 41, IOMMU group 21
	Bus: primary=0b, secondary=0c, subordinate=0c, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: [disabled] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

0b:04.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43f5 (rev 01) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3328
	Flags: bus master, fast devsel, latency 0, IRQ 42, IOMMU group 21
	Bus: primary=0b, secondary=0d, subordinate=0d, sec-latency=0
	I/O behind bridge: e000-efff [size=4K] [16-bit]
	Memory behind bridge: fc300000-fc3fffff [size=1M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

0b:05.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43f5 (rev 01) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3328
	Flags: bus master, fast devsel, latency 0, IRQ 43, IOMMU group 21
	Bus: primary=0b, secondary=0e, subordinate=0e, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: [disabled] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

0b:08.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43f5 (rev 01) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3328
	Flags: bus master, fast devsel, latency 0, IRQ 44, IOMMU group 21
	Bus: primary=0b, secondary=0f, subordinate=0f, sec-latency=0
	I/O behind bridge: [disabled] [32-bit]
	Memory behind bridge: [disabled] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

0b:0c.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43f5 (rev 01) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3328
	Flags: bus master, fast devsel, latency 0, IRQ 24, IOMMU group 21
	Bus: primary=0b, secondary=10, subordinate=10, sec-latency=0
	I/O behind bridge: [disabled] [16-bit]
	Memory behind bridge: fc200000-fc2fffff [size=1M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

0b:0d.0 PCI bridge: Advanced Micro Devices, Inc. [AMD] Device 43f5 (rev 01) (prog-if 00 [Normal decode])
	Subsystem: ASMedia Technology Inc. Device 3328
	Flags: bus master, fast devsel, latency 0, IRQ 40, IOMMU group 21
	Bus: primary=0b, secondary=11, subordinate=11, sec-latency=0
	I/O behind bridge: [disabled] [16-bit]
	Memory behind bridge: fc100000-fc1fffff [size=1M] [32-bit]
	Prefetchable memory behind bridge: [disabled] [64-bit]
	Capabilities: <access denied>
	Kernel driver in use: pcieport

0d:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8125 2.5GbE Controller (rev 05)
	DeviceName: Realtek RTL8125BG LAN
	Subsystem: ASUSTeK Computer Inc. RTL8125 2.5GbE Controller
	Flags: bus master, fast devsel, latency 0, IRQ 24, IOMMU group 21
	I/O ports at e000 [size=256]
	Memory at fc300000 (64-bit, non-prefetchable) [size=64K]
	Memory at fc310000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: r8169
	Kernel modules: r8169

10:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43f7 (rev 01) (prog-if 30 [XHCI])
	Subsystem: ASMedia Technology Inc. Device 1142
	Flags: bus master, fast devsel, latency 0, IRQ 24, IOMMU group 21
	Memory at fc200000 (64-bit, non-prefetchable) [size=32K]
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

11:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43f6 (rev 01) (prog-if 01 [AHCI 1.0])
	Subsystem: ASMedia Technology Inc. Device 1062
	Flags: bus master, fast devsel, latency 0, IRQ 45, IOMMU group 21
	Memory at fc180000 (32-bit, non-prefetchable) [size=1K]
	Expansion ROM at fc100000 [disabled] [size=512K]
	Capabilities: <access denied>
	Kernel driver in use: ahci

12:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 43f7 (rev 01) (prog-if 30 [XHCI])
	Subsystem: ASMedia Technology Inc. Device 1142
	Flags: bus master, fast devsel, latency 0, IRQ 24, IOMMU group 22
	Memory at fc500000 (64-bit, non-prefetchable) [size=32K]
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

13:00.0 SATA controller: Advanced Micro Devices, Inc. [AMD] Device 43f6 (rev 01) (prog-if 01 [AHCI 1.0])
	Subsystem: ASMedia Technology Inc. Device 1062
	Flags: bus master, fast devsel, latency 0, IRQ 46, IOMMU group 23
	Memory at fc480000 (32-bit, non-prefetchable) [size=1K]
	Expansion ROM at fc400000 [disabled] [size=512K]
	Capabilities: <access denied>
	Kernel driver in use: ahci

14:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Raphael (rev c7) (prog-if 00 [VGA controller])
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Raphael
	Flags: bus master, fast devsel, latency 0, IRQ 86, IOMMU group 24
	Memory at fc20000000 (64-bit, prefetchable) [size=256M]
	Memory at fc30000000 (64-bit, prefetchable) [size=2M]
	I/O ports at d000 [size=256]
	Memory at fca00000 (32-bit, non-prefetchable) [size=512K]
	Capabilities: <access denied>
	Kernel driver in use: amdgpu
	Kernel modules: amdgpu

14:00.1 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller
	Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Rembrandt Radeon High Definition Audio Controller
	Flags: bus master, fast devsel, latency 0, IRQ 126, IOMMU group 25
	Memory at fca88000 (32-bit, non-prefetchable) [size=16K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

14:00.2 Encryption controller: Advanced Micro Devices, Inc. [AMD] VanGogh PSP/CCP
	Subsystem: ASUSTeK Computer Inc. VanGogh PSP/CCP
	Flags: bus master, fast devsel, latency 0, IRQ 105, IOMMU group 26
	Memory at fc900000 (32-bit, non-prefetchable) [size=1M]
	Memory at fca8c000 (32-bit, non-prefetchable) [size=8K]
	Capabilities: <access denied>
	Kernel driver in use: ccp
	Kernel modules: ccp

14:00.3 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15b6 (prog-if 30 [XHCI])
	Subsystem: ASUSTeK Computer Inc. Device 8877
	Flags: fast devsel, IRQ 77, IOMMU group 27
	Memory at fc800000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

14:00.4 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15b7 (prog-if 30 [XHCI])
	Subsystem: ASUSTeK Computer Inc. Device 8877
	Flags: fast devsel, IRQ 86, IOMMU group 28
	Memory at fc700000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

14:00.6 Audio device: Advanced Micro Devices, Inc. [AMD] Family 17h/19h HD Audio Controller
	DeviceName: Realtek ALC897 Audio
	Subsystem: ASUSTeK Computer Inc. Family 17h/19h HD Audio Controller
	Flags: bus master, fast devsel, latency 0, IRQ 127, IOMMU group 29
	Memory at fca80000 (32-bit, non-prefetchable) [size=32K]
	Capabilities: <access denied>
	Kernel driver in use: snd_hda_intel
	Kernel modules: snd_hda_intel

15:00.0 USB controller: Advanced Micro Devices, Inc. [AMD] Device 15b8 (prog-if 30 [XHCI])
	Subsystem: ASUSTeK Computer Inc. Device 8877
	Flags: fast devsel, IRQ 24, IOMMU group 30
	Memory at fce00000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: <access denied>
	Kernel driver in use: xhci_hcd
	Kernel modules: xhci_pci

I'm thinking on buying an UPS (I've seen APC ones recommended for linux) to ensure energy supply. Besides that I don't know what I could try to trace down the issue. I'm changing to xstart -logverbose 6 to see if I can see anything more in the logfiles, tell me if you know any other log I should increase it's verbosity to track this issue in more depth.

Offline

#28 2023-10-11 21:23:57

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,330

Re: [SOLVED] Green screen crash

lspci -v outputs only my gpu controller for VGA even though

That'd normal and doesn't refer to a VGA connector, https://en.wikipedia.org/wiki/Video_Graphics_Array

I'd first and foremost test the behavior on some live distro like eg. knoppix to see whether the issue exists on different SW stacks.
Not saying a UPS is bad, but unless you're living in a location w/ frequent power fluctuations, I don't see how that could help here.

Offline

#29 2023-10-16 16:27:36

blinkingbit
Member
Registered: 2023-02-03
Posts: 59

Re: [SOLVED] Green screen crash

I have tried with linux mint and tailsOS:

Mint does show the same repeated pooling although I couldn't reproduce the crash or any artifacts on it yet.
I tried tailsOS (I was curious about the OS, that's the real reason) just in case using wayland could be possible to discover anything new or a hint of a hardware problem but I didn't find anything relevant nor reproduce the problem there.

I also tried to boot knoppix but it seems that ventoy doesn't like that distro, I hope mint is good enough in this case.

Offline

#30 2023-10-16 18:54:57

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,330

Re: [SOLVED] Green screen crash

Qick recap: did you manage to reproduce this w/ a "naked" X11 server on arch (eg. "startx xterm" for just an xterm)
If not, and since we're likely looking for some timer-triggered event, do you run sth. like xautolock or xscreensaver?
Can you reproduce it w/o conky or polybar?

Offline

#31 2023-10-17 20:24:51

blinkingbit
Member
Registered: 2023-02-03
Posts: 59

Re: [SOLVED] Green screen crash

Nope I have not reproduce it on a "naked" X11 server.
It's fair to assume that I'm running all xthings that come activated by default. I didn't even know about xscreensaver until we talked about it here (before that I thought it was somehow managed by my monitor). I have the ssh daemon running but I doubt it could have any impact on this, should I be monitoring systemd services?

I don't really have that much programs running at once (configured by hand I would say that i3, polybar, picom, pulseaudio and conky). I'm not very proud of my sound configuration but I haven't found any correlation with it neither (I tried not connecting my bluetooth headset for a while with no impact and killing pulseaudio when the flickering starts didn't solved it either).

Just to be sure, the output of yay -Qe:

alacritty 0.12.3-1
alsa-utils 1.2.10-1
alvr 20.4.0-1
amd-ucode 20230804.7be2766d-2
anki 2.1.66-1
autoconf 2.71-4
autofirma-bin 1.8.2-1
automake 1.16.5-2
autorandr 1.14-1
base 3-2
bear 3.1.3-3
bison 3.8.2-6
blender 17:3.6.4-2
bluez-utils 5.70-1
clang 16.0.6-1
cmake 3.27.7-1
configuradorfnmt 1.0.1-2
conky 1.18.1-2
cups 1:2.4.7-2
debugedit 5.0-5
dhcpcd 10.0.2-1
discord 0.0.31-1
dkms 3.0.11-1
dxvk-bin 2.3-1
efibootmgr 18-2
exfat-utils 1.4.0-2
fakeroot 1.32.1-1
fcitx5 5.1.1-1
fcitx5-gtk 5.1.0-1
fcitx5-mozc 2.26.4632.102.g4d2e3bd-2
fcitx5-qt 5.1.1-3
fd 8.7.0-2
feh 3.10.1-2
filezilla 3.65.0-2
firefox 118.0.2-1
flex 2.6.4-5
gcc 13.2.1-3
gdb 13.2-1
geckodriver 0.33.0-1
git 2.42.0-1
grub 2:2.12rc1-5
heroic-games-launcher-bin 2.9.2-2
hplip 1:3.23.8-1
i3-wm 4.22-4
irssi 1.4.5-1
kdenlive 23.08.2-1
khal 0.11.2-2
khard 0.18.0-2
krita 5.2.0-2
lib32-libpulse 16.1-6
lib32-mesa 1:23.2.1-2
lib32-systemd 254.5-1
lib32-vkd3d 1.9-1
lib32-vulkan-radeon 1:23.2.1-2
libva-mesa-driver 1:23.2.1-2
linux 6.5.7.arch1-1
linux-firmware 20230804.7be2766d-2
linux-headers 6.5.7.arch1-1
lua-language-server 3.7.0-1
luarocks 3.9.2-1
lutris 0.5.13-6
m4 1.4.19-3
maim 5.7.4-6
man-db 2.12.0-1
man-pages 6.05.01-1
mesa-vdpau 1:23.2.1-2
mpv 1:0.36.0-1
neovim 0.9.4-2
net-tools 2.10-2
npm 10.2.0-1
ntfs-3g 2022.10.3-1
nvme-cli 2.6-1
openssh 9.5p1-1
otf-ipaexfont 004.01-3
p7zip 1:17.05-1
picom 10.2-1
pkgconf 1.8.1-1
polybar 3.6.3-3
pulseaudio 16.1-6
pulseaudio-alsa 1:1.2.7.1-2
pulseaudio-bluetooth 16.1-6
pulsemixer 1.5.1-4
python 3.11.5-2
python-lsp-server 1.8.0-1
python-pip 23.2.1-1
rclone 1.64.0-1
ripgrep 13.0.0-3
rofi 1.7.5-2
rsync 3.2.7-6
sane 1.2.1-5
sidequest-bin 0.10.38-1
steam 1.0.0.78-2
stylua 0.18.2-1
sudo 1.9.14.p3-1
texinfo 7.0.3-1
texlab 5.6.0-1
texlive-basic 2023.66594-19
texlive-bibtexextra 2023.66594-19
texlive-fontsextra 2023.66594-19
texlive-formatsextra 2023.66594-19
texlive-games 2023.66594-19
texlive-humanities 2023.66594-19
texlive-latexextra 2023.66594-19
texlive-mathscience 2023.66594-19
texlive-music 2023.66594-19
texlive-pictures 2023.66594-19
texlive-pstricks 2023.66594-19
texlive-publishers 2023.66594-19
thunderbird 115.3.2-1
todoman 4.3.2-1
transmission-qt 4.0.4-1
tree 2.1.1-1
ttf-hack 3.003-6
unrar 1:6.2.12-1
unzip 6.0-20
ventoy-bin 1.0.95-1
vulkan-radeon 1:23.2.1-2
which 2.21-6
wine 8.18-1
xclip 0.13-4
xorg-server 21.1.8-2
xorg-xinit 1.4.2-1
xorg-xinput 1.6.4-1
xpadneo-dkms 0.9.5-3
yay-git 12.1.3.r0.ge60ccdf-1
youtube-dl 2021.12.17-2
zk 0.14.0-1

I can try to disable polybar and conky for a while and see if the problem appears. This problem   is frequent enough to be annoying but rare enough to not being easily triggered hmm

Offline

#32 2023-10-24 20:01:33

blinkingbit
Member
Registered: 2023-02-03
Posts: 59

Re: [SOLVED] Green screen crash

It crashed today without conky nor polybar running. xorg log

I was running unreal engine and compiling code for some time. I took a break to play a game on steam, and after some time playing it crashed (last xorg timestamp is almost exactly when it happened). I could continue playing without problems after rebooting.

Another thing I want to point out is that if it is a timer-triggered event, is not related to boot time as I had this kind of crashes seconds after booting in some sessions and it happened hours after too in others.

I don't know how to reproduce it easily with a clean X server. It usually crash with multiple applications running. I will try to run as few as necessary although it will take some time to crash it with this setup.

Offline

#33 2023-10-27 19:58:09

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,330

Re: [SOLVED] Green screen crash

and after some time playing it crashed

Doesn't suggest it's related to any screensaver/dpms - the outputs got polled quite a lot during the last 128 seconds - cable or plugs?
Did you reboot "cleanly" and do you have a system journal for that boot?

Offline

#34 2023-11-02 18:35:14

blinkingbit
Member
Registered: 2023-02-03
Posts: 59

Re: [SOLVED] Green screen crash

cable or plugs?

I doubt the cables have any issue, I have tested with multiple ones and bought new ones but the polling always happens.

It could be related to a plug but I have tested all gpu and monitor plugs and the problem always happens. The weird thing is that, in my experience, hardware problems tend to worsen over time but in this case, it seems completely random it could happen 3 times in a row and run well for a week until the next crash.

Did you reboot "cleanly" and do you have a system journal for that boot?

Maybe I misused the term "reboot" here. The crash ended with my PC completely turned off so I just booted. I don't think of it as a "clean" boot as it spent extra time checking all the storage devices.

I don't have a log of that boot but I remember checking it and the outputs were polled a lot too. There were a lot of instances where that output was polled without crashing or producing artifacts. For example in my current boot, the following line appears 80~ times in a single second:

[  1975.133] (II) modeset(0): EDID vendor "ACI", prod id 8957

Another thing that could be happening is that my processor not having integrated graphics makes the system panic if there is no GPU unit detected.

Offline

#35 2023-11-02 20:41:29

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,330

Re: [SOLVED] Green screen crash

The crash ended with my PC completely turned off so I just booted.

That's a hardware issue - software would maybe lead to complete freezes, but not a power loss.
On a stretch, the system gets live-locked, overheats (fan action?) and emergency powers down.

Did you see https://wiki.archlinux.org/title/Ryzen#Troubleshooting ?

makes the system panic if there is no GPU unit detected

Does this relate to incidents other than the output polling? (The output polling involves your GPU, that's there at the time)

Offline

#36 2023-11-02 21:21:09

blinkingbit
Member
Registered: 2023-02-03
Posts: 59

Re: [SOLVED] Green screen crash

the system gets live-locked, overheats (fan action?), and emergency powers down.

I think this is the current situation because when the crash happens, the system is still running (I can connect through SSH and run commands and programs) but the screen is completely green and after about 30 seconds it somehow ends up powering off. I'm not completely sure what kind of mechanism is using but is not like a power loss, it doesn't occur in an instant, and it takes some time (for logging purposes or trying to recover from it I guess).

Does the OS override or take control with priority over the bios configuration? In theory, the gpu is configured to spin a lot faster if the temperature rises. I mean a lot as in hearing a loud noise when it happens. When the crash happens, the fans are spinning like the temperature is completely under control. I have always assumed that the bios should take care of that but maybe that assumption is wrong.

Does this relate to incidents other than the output polling?

I don't really know. The output polling is the most obvious hint to this problem because it keeps happening all the time whether the system ends up crashing or not.

I will try the troubleshooting suggestions of that wiki page and check the Gentoo one too. Both gpu and cpu are recent ones, so it could be that both are still unstable under linux. I thought I was safe when picking amd lol

Offline

#37 2023-11-05 16:16:12

blinkingbit
Member
Registered: 2023-02-03
Posts: 59

Re: [SOLVED] Green screen crash

Update:

Today my pc was capable of "recover" from the artifacts & greenscreen. I opened firefox, steam and Counter Strike. Just after the game initialize, the artifacts started appearing and the screen was completely green from time to time. Thanks that it was a recent boot, I was able to close the game window and after that all artifacts disappeared.

There are a lot of messages (journalctl -k of my current boot) saying:

[drm] Skip scheduling IBs!

Also it seems that there are some logs lost when this happens (?):

Nov 05 17:02:29.049517 PC systemd-journald[343]: /dev/kmsg buffer overrun, some messages lost.

The "almost crash" (I'm pretty confident that if let alone, that could have ended in a forced shutdown or reboot as it usually does) happened at 17:02 xorg log.

** Edit **

Possible related kernel/driver bug
It seems pretty similar to me but I'm not that confident in opening bug reports for it (it's not clear which program should be responsible to handle this issue sad). There are some related discussions in mesa and amd bugtrackers.
Looking carefully around the "IBs!" prints there is a drm:amdgpu_job_timedout error that matches the bug report. It happened 20 minutes before the artifacts appeared but seems related anyway as a similar output it's displayed when the problem appeared (around 17:02).
Journal of that boot

Last edited by blinkingbit (2023-11-05 19:23:57)

Offline

#38 2023-11-05 21:33:26

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,330

Re: [SOLVED] Green screen crash

Stop, disable, kill and remove autorandr.

Edit: unrelated, but you've systemd-networkd and dhcpcd enabled - pick one, disable the other.

Last edited by seth (2023-11-05 21:34:53)

Offline

#39 2023-11-28 16:42:54

blinkingbit
Member
Registered: 2023-02-03
Posts: 59

Re: [SOLVED] Green screen crash

It's been a while since last crash. I haven't experience another one yet although the green screen flickering happens sometimes.

In my current session there is a way to reproduce it by moving the cursor between background previews inside steam pointshop but only with steam running in fullscreen ($mod+f in i3wm). I've spent quite a long time triggering it, stopping and re-triggering it trying to figure if it's hardware or software related. It seems like a software issue at least this particular case, as it was only triggering with a particular way of drawing to the screen. While in floating window mode, the issue did not trigger even after trying several times. I have to check in my next boot if I can reproduce it in every boot. Also I have found no messages in the journal this time.

I have been trying to follow this gentoo troubleshooting guide. And I have discovered that my gpu spec doesn't match with sysfs configuration (I don't really know what to do from here yet).

$cat pp_od_clk_voltage
OD_SCLK:
0:        400Mhz
1:       2200Mhz
OD_RANGE:
SCLK:     400Mhz       2200Mhz

$cat pp_dpm_mclk
0: 2400Mhz *

$cat pp_dpm_sclk
0: 400Mhz
1: 600Mhz *
2: 2200Mhz

I couldn't follow all the calculations but the memory clock already seem too much.

     | Base clock | Game clock | Boost clock | memory clock | vram bus | bandwith
---------------------------------------------------------------------------------
Spec |  2106 MHz  | 2447 MHz   | 2669 MHz    | 2190MHz(17.5)|  128     | 280.3GB/s 
sysfs|     -      | 2200 MHz   | --------    | 2400MHz      |

I'm also looking into "Prime Synchronization" trying to see if solutions to my problem (flickering) could be solved by fixing another thing like screen tearing in x11 with amdgpu or modesetting.

Offline

#40 2023-11-29 20:40:15

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,330

Re: [SOLVED] Green screen crash

While in floating window mode, the issue did not trigger even after trying several times.

Compositor? Unredirected fullscreen? Some sort of overlay key (ie. the content should get rendered there but isn't and you see the "greenscreen")?

Offline

#41 2023-11-30 06:12:33

blinkingbit
Member
Registered: 2023-02-03
Posts: 59

Re: [SOLVED] Green screen crash

I use picom as my compositor with the following config file.

The problem didn't happen on the next boot but maybe there is something wrong with my config.

I don't understand what fullscreen redirection really is. I have found this and I'm going to try to make some sort of rule to set it for steam but I have experience the same flicker with firefox in a normal window so it won't solve the whole issue.

Offline

#42 2023-11-30 07:23:40

seth
Member
From: Don't DM me only for attention
Registered: 2012-09-03
Posts: 74,330

Re: [SOLVED] Green screen crash

Compositors capture the output of a window and pipe it through themselves to paint the final screen with transparency and shadows etc.
Since this is usually pointless for opaque fullscreen windows they tend to sit those out and just let them paint directly.

You could kill picom and try your testcase windowed to see whether you're now getting the same effect you're getting for the fullscreen window.

Offline

#43 2023-12-13 17:19:47

blinkingbit
Member
Registered: 2023-02-03
Posts: 59

Re: [SOLVED] Green screen crash

Quick update regarding the compositor.
Today the flicker started so I tried to kill picom just in case fullscreen redirection was producing it. The issue persisted and a couple hours after, greenscreen and crashed as always.

Journal log.

I have increased verbosity level trying to figure out the root of the problem but still the issue does not reach the journal or I'm looking at the wrong place.

Offline

#44 2024-03-08 16:26:42

blinkingbit
Member
Registered: 2023-02-03
Posts: 59

Re: [SOLVED] Green screen crash

Final update about the topic:

Some days ago my system refused to make the graphics card work on boot. The problem solved itself a couple times but I have finally decided to give up on this as all points towards a defect in the gpu.
I have returned the card without a problem (maybe it's a known defect and I have been chasing a red herring the whole time). In the mean time I have tested the system with both a gtx 1050 Ti and a RTX 7800.

Both AMD and NVidia works without weird artifacts.

Thank you for the help. I will marked this as solved and a TL;DR edit to save people time.

Offline

Board footer

Powered by FluxBB