Second monitor stuck in power on/off loop

Problem

With a 2 monitor setup, secondary monitor will cycle through powering on, flashing the current screen, powering off. This happens indefinitely. Through rebooting occassionally the second monitor will stay on, this happens about 1 in 30 reboots.

Please see attached video example of the problem:

Cause

Possibly driver issues or hardware issues.

I noticed that this started occurring on Fedora 37, however, at the time it was about a 50/50 to happen when rebooting and so I just ignored the issue. I then leapfrogged to Fedora 40 and the issue is much more frequent now to where I’m seeking to fix it.

Related Issues

Bugzilla report: #NNNN

^ In reference to the above, when I tried to go about starting a tracker it required me to select a package however at the moment I dont even know how to assess which package (if any) may be causing the issue.

Workarounds

None yet.

From Proposed Common Issues to Ask Fedora

F37 is EOL, can you update to either f39 or f40 that are supported and may have fixed the issue you see?

Personally I always update 1 version at a time, but you could do f37 to f39 then f39 to f40.

Hi Barry,

Yes, sorry I am on Fedora 40. I meant to say that I was experiencing the issue while using Fedora 37, then recently updated to Fedora 40 (by going from 38, then 39, then 40). Since upgrading to 40 (which has been lovely by the way) the issue has gone from being a minor occurrence to being very prevalent. I referenced that it started on 37 incase that information may somehow be useful but perhaps not.

I hope that makes sense.

Cheers,
Andrew

Added f40 and removed f37

As this may be a hardware related issue here is the output of

neofetch

We prefer hardware info from inxi -Fzxx and post as pre-formatted text not an image please, using the </>.

Have you checked sudo dmesg and system and user journals for error messages when this happens?

Hi @kovachia. I’m trying to make sure people understand where to best file new topics. When you created a new topic in Proposed Common Issues , there was this pre-populated template present:

This is NOT a place to report bugs. If you want to discuss a problem, use the Ask category instead:
https://discussion.fedoraproject.org/c/ask

Why have you decided to still create it in Proposed Common Issues instead of the suggested Ask Fedora category? Please help me understand your thought process, in order to better phrase the template. Thanks!

Hi Kamil :slight_smile:

I played around this morning and I think I was able to re-create what happened[1]. I think what happened was I selected “New post” and then saw your warning. I followed the link to the /c/ask url. (Without thinking much) I suspect that I just pressed the “Open draft” button and continued typing. I saw your warning again but as I was in /c/ask in my url bar I assumed that I was now in the correct location and posted. I don’t think it occurred to me that there was the drop down bar on the post which needed to be changed. I think in my head I was treating the functionality as something like stack-exchange where there are various separate stacks that have their own unique url’s and so by going to a different web-page I was posting to a different thread.

My appologies, I know how hard it can be to get users to use a design the way its intended, and the frustration at all the new ways the find to get around your well written explanations, haha.

Cheers,
Andrew


  1. An additional step is that you must be exhausted from a 6 hour car drive ↩︎

Hi Barry,

Thank you :slight_smile: Here is the hardware info


andrew@fedora:~$ inxi -Fzxx
System:
  Kernel: 6.9.4-200.fc40.x86_64 arch: x86_64 bits: 64 compiler: gcc
    v: 2.41-37.fc40
  Desktop: GNOME v: 46.2 tk: GTK v: 3.24.42 wm: gnome-shell dm: GDM
    Distro: Fedora Linux 40 (Workstation Edition)
Machine:
  Type: Desktop Mobo: ASRock model: B550 Phantom Gaming 4
    serial: <superuser required> UEFI: American Megatrends LLC. v: P2.20
    date: 02/24/2022
CPU:
  Info: 8-core model: AMD Ryzen 7 5800X bits: 64 type: MT MCP arch: Zen 3+
    rev: 0 cache: L1: 512 KiB L2: 4 MiB L3: 32 MiB
  Speed (MHz): avg: 2197 high: 2200 min/max: 2200/4850 boost: enabled cores:
    1: 2200 2: 2196 3: 2196 4: 2196 5: 2188 6: 2193 7: 2200 8: 2200 9: 2196
    10: 2200 11: 2200 12: 2200 13: 2196 14: 2196 15: 2200 16: 2200
    bogomips: 121382
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Graphics:
  Device-1: AMD Navi 23 [Radeon RX 6600/6600 XT/6600M] vendor: Tul /
    PowerColor Red Devil driver: amdgpu v: kernel arch: RDNA-2 pcie:
    speed: 16 GT/s lanes: 16 ports: active: DP-3,HDMI-A-1
    empty: DP-1,DP-2,Writeback-1 bus-ID: 07:00.0 chip-ID: 1002:73ff
  Device-2: Linux Foundation EEM Gadget driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-4:3 chip-ID: 1d6b:0102
  Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 24.1.0
    compositor: gnome-shell driver: X: loaded: amdgpu
    unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 4480x1440 s-dpi: 96
  Monitor-1: DP-3 mapped: DisplayPort-2 pos: primary,left
    model: LG (GoldStar) ULTRAGEAR res: 2560x1440 dpi: 93 diag: 800mm (31.5")
  Monitor-2: HDMI-A-1 mapped: HDMI-A-0 pos: right
    model: LG (GoldStar) 27MP35 res: 1920x1080 dpi: 82 diag: 686mm (27")
  API: OpenGL v: 4.6 vendor: amd mesa v: 24.1.1 glx-v: 1.4 es-v: 3.2
    direct-render: yes renderer: AMD Radeon RX 6600 XT (radeonsi navi23 LLVM
    18.1.6 DRM 3.57 6.9.4-200.fc40.x86_64) device-ID: 1002:73ff
  API: Vulkan v: 1.3.283 surfaces: xcb,xlib device: 0 type: discrete-gpu
    driver: N/A device-ID: 1002:73ff device: 1 type: cpu driver: N/A
    device-ID: 10005:0000
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
  Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie:
    speed: 16 GT/s lanes: 16 bus-ID: 07:00.1 chip-ID: 1002:ab28
  Device-2: AMD Starship/Matisse HD Audio vendor: ASRock
    driver: snd_hda_intel v: kernel pcie: speed: 16 GT/s lanes: 16
    bus-ID: 09:00.4 chip-ID: 1022:1487
  Device-3: Realtek USB2.0 Microphone
    driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 480 Mb/s
    lanes: 1 bus-ID: 1-2:13 chip-ID: 0bda:4937
  Device-4: Linux Foundation EEM Gadget driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 3-4:3 chip-ID: 1d6b:0102
  API: ALSA v: k6.9.4-200.fc40.x86_64 status: kernel-api
  Server-1: PipeWire v: 1.0.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    4: pw-jack type: plugin
Network:
  Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
    vendor: ASRock driver: r8169 v: kernel pcie: speed: 2.5 GT/s lanes: 1
    port: f000 bus-ID: 04:00.0 chip-ID: 10ec:8168
  IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:
  Local Storage: total: 894.25 GiB used: 804.33 GiB (89.9%)
  ID-1: /dev/nvme0n1 vendor: Western Digital model: WDS960G2G0C-00AJM0
    size: 894.25 GiB speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 26.9 C
Partition:
  ID-1: / size: 892.67 GiB used: 804 GiB (90.1%) fs: btrfs dev: /dev/nvme0n1p3
  ID-2: /boot size: 973.4 MiB used: 313.3 MiB (32.2%) fs: ext4
    dev: /dev/nvme0n1p2
  ID-3: /boot/efi size: 598.8 MiB used: 19 MiB (3.2%) fs: vfat
    dev: /dev/nvme0n1p1
  ID-4: /home size: 892.67 GiB used: 804 GiB (90.1%) fs: btrfs
    dev: /dev/nvme0n1p3
Swap:
  ID-1: swap-1 type: zram size: 8 GiB used: 1.46 GiB (18.3%) priority: 100
    dev: /dev/zram0
Sensors:
  System Temperatures: cpu: 43.5 C mobo: N/A gpu: amdgpu temp: 32.0 C
    mem: 30.0 C
  Fan Speeds (rpm): N/A gpu: amdgpu fan: 0
Info:
  Memory: total: 16 GiB available: 15.53 GiB used: 8.51 GiB (54.8%)
  Processes: 461 Power: uptime: 13h 58m wakeups: 1 Init: systemd v: 255
    target: graphical (5) default: graphical
  Packages: 32 pm: dpkg pkgs: 3 pm: flatpak pkgs: 29 Compilers: gcc: 14.1.1
    Shell: Bash v: 5.2.26 running-in: gnome-terminal inxi: 3.3.34

I’ll get the dmesg now if I can find it.

Cheers,
Andrew

Thanks, Andrew, your answer was very helpful! I didn’t realize that once you have a draft topic opened, even if you change the URL and open a “new” draft, it’s still the original one. I have replicated the steps right now. The Discourse UI is trying to be friendly, but it this case, it’s going completely against the intention.

I’ll try to rephrase the template to make it clearer and avoid this pitfall. Thanks a lot.

No problem Kamil! :slight_smile: I’m glad it was helpful. Hope you have a good day!

Cheers,
Andrew

Hi Barry,

There are no error messages but there are a few warning messages which I’m uncertain which are related or not. I’ll share all of the warnings now.

  1. General search for warnings
andrew@fedora:~$ sudo dmesg -L -l emerg,alert,crit,err,warn
[    0.081703] Speculative Return Stack Overflow: IBPB-extending microcode not applied!
[    0.081703] Speculative Return Stack Overflow: WARNING: See https://kernel.org/doc/html/latest/admin-guide/hw-vuln/srso.html for mitigation options.
[    0.595639] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[    9.822925] usb 3-4: Warning! Unlikely big volume range (=4608), cval->res is probably wrong.
[    9.822929] usb 3-4: [5] FU [Capture Input terminal Capture Volume] ch = 1, val = 512/5120/1
[   10.637737] block nvme0n1: No UUID available providing old NGUID
  1. Notices as well as warnings
andrew@fedora:~$ sudo dmesg -L -l emerg,alert,crit,err,warn,notice
[    0.000000] Linux version 6.9.4-200.fc40.x86_64 (mockbuild@d372fa1a67e347178b7bd422ead09b96) (gcc (GCC) 14.1.1 20240607 (Red Hat 14.1.1-5), GNU ld version 2.41-37.fc40) #1 SMP PREEMPT_DYNAMIC Wed Jun 12 13:33:34 UTC 2024
[    0.000000] random: crng init done
[    0.028505] Kernel command line: BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.9.4-200.fc40.x86_64 root=UUID=14f1f163-9839-401a-9851-1d653e5138ba ro rootflags=subvol=root rhgb quiet
[    0.028554] Unknown kernel command line parameters "rhgb BOOT_IMAGE=(hd0,gpt2)/vmlinuz-6.9.4-200.fc40.x86_64", will be passed to user space.
[    0.081703] Speculative Return Stack Overflow: IBPB-extending microcode not applied!
[    0.081703] Speculative Return Stack Overflow: WARNING: See https://kernel.org/doc/html/latest/admin-guide/hw-vuln/srso.html for mitigation options.
[    0.233469] audit: type=2000 audit(1718794990.157:1): state=initialized audit_enabled=0 res=1
[    0.250100] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored
[    0.277501] SCSI subsystem initialized
[    0.285183] VFS: Disk quotas dquot_6.6.0
[    0.318757] Initialise system trusted keyrings
[    0.318776] Key type blacklist registered
[    0.319243] integrity: Platform Keyring initialized
[    0.319247] integrity: Machine keyring initialized
[    0.326723] Key type asymmetric registered
[    0.326725] Asymmetric key parser 'x509' registered
[    0.595639] device-mapper: core: CONFIG_IMA_DISABLE_HTABLE is disabled. Duplicate IMA measurements will not be recorded in the IMA log.
[    0.604594] Loading compiled-in X.509 certificates
[    0.610076] Loaded X.509 cert 'Fedora kernel signing key: NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN'
[    0.614963] Key type .fscrypt registered
[    0.614964] Key type fscrypt-provisioning registered
[    0.615696] Key type big_key registered
[    0.615701] Key type trusted registered
[    0.631283] Key type encrypted registered
[    0.631394] Loading compiled-in module X.509 certificates
[    0.631752] Loaded X.509 cert 'Fedora kernel signing key: NNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNNN'
[    2.797564] ccp 0000:09:00.1: ccp: unable to access the device: you might be running a broken BIOS.
[    2.797588] ccp 0000:09:00.1: psp enabled
[    8.433920] audit: type=1404 audit(1718794998.336:2): enforcing=1 old_enforcing=0 auid=4294967295 ses=4294967295 enabled=1 old-enabled=1 lsm=selinux res=1
[    8.520964] audit: type=1403 audit(1718794998.423:3): auid=4294967295 ses=4294967295 lsm=selinux res=1
[    9.201317] audit: type=1130 audit(1718794999.104:4): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-journald comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    9.225251] audit: type=1130 audit(1718794999.127:5): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-random-seed comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    9.228857] audit: type=1130 audit(1718794999.131:6): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-sysctl comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    9.233670] audit: type=1334 audit(1718794999.136:7): prog-id=36 op=LOAD
[    9.233772] audit: type=1334 audit(1718794999.136:8): prog-id=37 op=LOAD
[    9.233803] audit: type=1334 audit(1718794999.136:9): prog-id=38 op=LOAD
[    9.255460] audit: type=1130 audit(1718794999.158:10): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=lvm2-monitor comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    9.255639] audit: type=1130 audit(1718794999.158:11): pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-userdbd comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
[    9.822925] usb 3-4: Warning! Unlikely big volume range (=4608), cval->res is probably wrong.
[    9.822929] usb 3-4: [5] FU [Capture Input terminal Capture Volume] ch = 1, val = 512/5120/1
[   10.637737] block nvme0n1: No UUID available providing old NGUID

My gut was saying I shouldn’t be sharing the Fedora kernel signing key so I have obscured it here. If this is somehow relevant I can add it back in.

I see nothing that seems to reference a monitor in anyway.

  1. I also tried searching the messages to references to HDMI or DPI but found nothing of interest

andrew@fedora:~$ sudo dmesg -L |grep HDMI
[    7.960984] [drm] DP-HDMI FRL PCON supported
[    9.774079] input: HDA ATI HDMI HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.1/0000:05:00.0/0000:06:00.0/0000:07:00.1/sound/card0/input12
[    9.774153] input: HDA ATI HDMI HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.1/0000:05:00.0/0000:06:00.0/0000:07:00.1/sound/card0/input13
[    9.774215] input: HDA ATI HDMI HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.1/0000:05:00.0/0000:06:00.0/0000:07:00.1/sound/card0/input14
[    9.774287] input: HDA ATI HDMI HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.1/0000:05:00.0/0000:06:00.0/0000:07:00.1/sound/card0/input15
[    9.774343] input: HDA ATI HDMI HDMI/DP,pcm=10 as /devices/pci0000:00/0000:00:03.1/0000:05:00.0/0000:06:00.0/0000:07:00.1/sound/card0/input16
andrew@fedora:~$ sudo dmesg -L |grep DPI
andrew@fedora:~$ sudo dmesg -L |grep dpi
andrew@fedora:~$ sudo dmesg -L |grep hdmi

Hardware look good, nothing stands out as odd.

Have you tried a different cable? Also possibly a different connector (HDMI instead of DP, etc)? And try a different port on the GPU, if possible.

I have seen similar issues where one of the monitors times out with “no signal”. Often this involved a cable with some converter, e.g., USBC to HDMI, or a KVM. Most recently it was a Dell monitor with built-in KVM. The problem went away with firmware updates to the host system and the KVM.

One big benefit journalctl over dmesgis that it allows you to examine messages for older boots so you can see differences between a boot that worked (maybe using an older or recovery kernel) with one that exhibited the problem.