Monitor wouldn't wake up this morning until I rebooted - How to troubleshoot?

[glitchathon]

This morning, I could not wake up my monitor from sleep (My power settings have monitor going to sleep after 1 hour). Changing mouses/USB ports, etc didn't work. I also swapped monitors and that didn't work. This is a desktop with external monitor connected via HDMI.

I then rebooted the machine from an ssh session and everything is working again. Before rebooting, I did try to wake the monitor from the ssh session with xset dpms force off/on and other ideas I saw on forums, but nothing was working. I also tried xrandr and it couldn't find any displays. I also tried doing Ctrl-Alt-F2 to go to TTY and Ctrl-Alt-F3 to go back to the X session, but that didn't work either. Only a reboot worked.

I am on the 6.1 kernel and I did update to 6.1.0-1007-oem when it was available (a couple days ago?) and this is the first time this ever happened. So maybe it's the latest kernel update.

I restarted into the previous kernel (6.1.0-1006-oem) and uninstalled the 1007 kernel for now. Hoping this is the problem. However, is there any other way I can troubleshoot to see what happened and how to prevent it from happening?

Thank you so much!

Here is my system info:

Code: Select all

System:
  Kernel: 6.1.0-1006-oem x86_64 bits: 64 compiler: N/A Desktop: MATE 1.26.0 wm: marco dm: LightDM
    Distro: Linux Mint 21.1 Vera base: Ubuntu 22.04 jammy
Machine:
  Type: Desktop Mobo: Micro-Star model: PRO B760M-A WIFI DDR4 (MS-7D99) v: 1.0
    serial: <superuser required> UEFI: American Megatrends LLC. v: 1.20 date: 01/06/2023
CPU:
  Info: 14-core (6-mt/8-st) model: 13th Gen Intel Core i5-13600K bits: 64 type: MST AMCP arch: N/A
    rev: 1 cache: L1: 1.2 MiB L2: 20 MiB L3: 24 MiB
  Speed (MHz): avg: 4005 high: 5102 min/max: 800/5100:3900 cores: 1: 5102 2: 5102 3: 3500
    4: 3500 5: 5100 6: 3500 7: 5100 8: 3500 9: 5100 10: 5101 11: 3500 12: 3500 13: 3500 14: 3711
    15: 3500 16: 3500 17: 3500 18: 3500 19: 3788 20: 3500 bogomips: 139776
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
  Device-1: Intel vendor: Micro-Star MSI driver: i915 v: kernel ports: active: HDMI-A-2
    empty: DP-1, DP-2, HDMI-A-1, HDMI-A-3, HDMI-A-4 bus-ID: 00:02.0 chip-ID: 8086:a780
  Display: x11 server: X.Org v: 1.21.1.3 compositor: marco v: 1.26.0 driver: X:
    loaded: modesetting unloaded: fbdev,vesa gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96
  Monitor-1: HDMI-2 mapped: HDMI-A-2 model: Asus PB258 res: 2560x1440 dpi: 118 diag: 634mm (25")
  OpenGL: renderer: Mesa Intel Graphics (RPL-S) v: 4.6 Mesa 22.2.5 direct render: Yes
Audio:
  Device-1: Intel vendor: Micro-Star MSI driver: snd_hda_intel v: kernel bus-ID: 00:1f.3
    chip-ID: 8086:7a50
  Sound Server-1: ALSA v: k6.1.0-1006-oem 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: Intel driver: iwlwifi v: kernel port: N/A bus-ID: 00:14.3 chip-ID: 8086:7a70
  IF: wlo1 state: down mac: <filter>
  Device-2: Realtek RTL8125 2.5GbE vendor: Micro-Star MSI driver: r8169 v: kernel pcie:
    speed: 5 GT/s lanes: 1 port: 3000 bus-ID: 04:00.0 chip-ID: 10ec:8125
  IF: enp4s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Bluetooth:
  Device-1: Intel type: USB driver: btusb v: 0.8 bus-ID: 1-14:8 chip-ID: 8087:0033
  Report: hciconfig ID: hci0 rfk-id: 0 state: down bt-service: enabled,running rfk-block:
    hardware: no software: yes address: <filter>
Drives:
  Local Storage: total: 6.37 TiB used: 3.17 TiB (49.7%)
  ID-1: /dev/nvme0n1 vendor: Crucial model: CT1000P5PSSD8 size: 931.51 GiB speed: 63.2 Gb/s
    lanes: 4 serial: <filter> temp: 38.9 C
  ID-2: /dev/nvme1n1 vendor: Western Digital model: WD Blue SN570 2TB size: 1.82 TiB
    speed: 31.6 Gb/s lanes: 4 serial: <filter> temp: 34.9 C
  ID-3: /dev/sda vendor: HGST (Hitachi) model: HMS5C4040BLE640 size: 3.64 TiB speed: 6.0 Gb/s
    serial: <filter>
Partition:
  ID-1: / size: 915.32 GiB used: 42.39 GiB (4.6%) fs: ext4 dev: /dev/nvme0n1p2
  ID-2: /boot/efi size: 511 MiB used: 6.1 MiB (1.2%) fs: vfat dev: /dev/nvme0n1p1
Swap:
  ID-1: swap-1 type: file size: 2 GiB used: 0 KiB (0.0%) priority: -2 file: /swapfile
USB:
  Hub-1: 1-0:1 info: Hi-speed hub with single TT ports: 16 rev: 2.0 speed: 480 Mb/s
    chip-ID: 1d6b:0002
  Hub-2: 1-4:2 info: Realtek RTS5411 Hub ports: 5 rev: 2.1 speed: 480 Mb/s chip-ID: 0bda:5411
  Device-1: 1-4.1:4 info: Pixart Imaging Optical Mouse type: Mouse driver: hid-generic,usbhid
    rev: 2.0 speed: 1.5 Mb/s chip-ID: 093a:2510
  Device-2: 1-4.2:6 info: Kinesis Advantage2 Keyboard type: Mouse,Keyboard,HID
    driver: hid-generic,usbhid rev: 2.0 speed: 12 Mb/s chip-ID: 29ea:0102
  Device-3: 1-9:3 info: Micro Star MYSTIC LIGHT type: HID driver: hid-generic,usbhid rev: 1.1
    speed: 12 Mb/s chip-ID: 1462:7d99
  Hub-3: 1-10:5 info: Genesys Logic Hub ports: 4 rev: 2.1 speed: 480 Mb/s chip-ID: 05e3:0610
  Hub-4: 1-11:7 info: Genesys Logic Hub ports: 4 rev: 2.0 speed: 480 Mb/s chip-ID: 05e3:0608
  Device-1: 1-14:8 info: Intel type: Bluetooth driver: btusb rev: 2.0 speed: 12 Mb/s
    chip-ID: 8087:0033
  Hub-5: 2-0:1 info: Super-speed hub ports: 10 rev: 3.1 speed: 20 Gb/s chip-ID: 1d6b:0003
  Hub-6: 2-4:2 info: Realtek Hub ports: 4 rev: 3.2 speed: 5 Gb/s chip-ID: 0bda:0411
  Hub-7: 2-10:3 info: Genesys Logic USB3.2 Hub ports: 4 rev: 3.2 speed: 5 Gb/s
    chip-ID: 05e3:0620
Sensors:
  System Temperatures: cpu: 27.8 C mobo: N/A
  Fan Speeds (RPM): N/A
Repos:
  Packages: 2626 apt: 2616 flatpak: 10
  No active apt repos in: /etc/apt/sources.list
  Active apt repos in: /etc/apt/sources.list.d/additional-repositories.list
    1: deb https: //cloud.r-project.org/bin/linux/ubuntu jammy-cran40/
    2: deb [signed-by=/usr/share/keyrings/gpg-pub-moritzbunkus.gpg] https: //mkvtoolnix.download/ubuntu/ jammy main
  Active apt repos in: /etc/apt/sources.list.d/element-io.list
    1: deb [signed-by=/usr/share/keyrings/element-io-archive-keyring.gpg] https: //packages.element.io/debian/ default main
  Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
    1: deb [arch=amd64] https: //dl.google.com/linux/chrome/deb/ stable main
  Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
    1: deb https: //mirrors.ocf.berkeley.edu/linuxmint-packages vera main upstream import backport
    2: deb http: //mirror.uoregon.edu/ubuntu jammy main restricted universe multiverse
    3: deb http: //mirror.uoregon.edu/ubuntu jammy-updates main restricted universe multiverse
    4: deb http: //mirror.uoregon.edu/ubuntu jammy-backports main restricted universe multiverse
    5: deb http: //security.ubuntu.com/ubuntu/ jammy-security main restricted universe multiverse
  No active apt repos in: /etc/apt/sources.list.d/plexmediaserver.list
  Active apt repos in: /etc/apt/sources.list.d/ufleisch-kid3-jammy.list
    1: deb [arch=amd64 signed-by=/etc/apt/keyrings/ufleisch-kid3-jammy.gpg] https: //ppa.launchpadcontent.net/ufleisch/kid3/ubuntu jammy main
Info:
  Processes: 413 Uptime: 15m Memory: 31.12 GiB used: 2.92 GiB (9.4%) Init: systemd v: 249
  runlevel: 5 Compilers: gcc: 11.3.0 alt: 11/12 Client: Unknown python3.10 client inxi: 3.3.13

[coffee412]

Is it just the monitor or is your computer actually freezing up? If its your computer freezing up then I might have a fix for you. I had the same problem with mine where it would lock up when not attended for a while. I had this problem ever since the 5.15.0-57-generic kernel upgrade. Check your syslog file for some errors.

I actually forgot what the errors were but they repeated in the syslog. Im sorry.

In your /etc/default/grub edit the below line and add the bold blue pci=nommconf . Then update grub.

GRUB_CMDLINE_LINUX_DEFAULT="pci=nommconf quiet splash"

After I did that I have no more issues. I am even up to kernel 5.15.0-60 now and all is fine. Not saying this will fix yours but your symptoms sound the same as mine. Any who - If you see repeatable errors in your syslog file copy and paste them here.

[glitchathon]

Is it just the monitor or is your computer actually freezing up? If its your computer freezing up then I might have a fix for you. I had the same problem with mine where it would lock up when not attended for a while. I had this problem ever since the 5.15.0-57-generic kernel upgrade. Check your syslog file for some errors.

Thanks for the reply!

So in my case, the PC was running just fine... I was able to ssh into it, and the memory and CPU usage was normal and idling just fine. Just the display stopped working until I rebooted.

I looked in syslog and didn't see anything weird, but I will keep a look on it to see what happens when the monitor turns off. And then see what it logs when I (hopefully) wake it up with mouse movement.

[coffee412]

Well, I just wanted to throw that out there because the way you described it, It sounded a bit like my issue. I guess I really cannot advise any further on this. Hopefully something shows up in the logs.

[glitchathon]

Well, I just wanted to throw that out there because the way you described it, It sounded a bit like my issue. I guess I really cannot advise any further on this. Hopefully something shows up in the logs.

Thanks, I appreciate it! I did make a note to explore that line GRUB_CMDLINE_LINUX_DEFAULT as well, in case the kernel downgrade doesn't help.

[SMG]

This morning, I could not wake up my monitor from sleep (My power settings have monitor going to sleep after 1 hour). Changing mouses/USB ports, etc didn't work. I also swapped monitors and that didn't work. This is a desktop with external monitor connected via HDMI.

You could check to see if there were any error messages related to the graphics driver.

If two boots back was the one with the problem, this will get graphics-related information about that boot. It might or might not show a problem depending upon what the problem was.

Code: Select all

journalctl -b -2 | grep -i "drm\|i915\|00:02.0"

You didn't supply the complete inxi output with xxx so I am guessing the bus ID, but usually that is what it is for an Intel GPU. You can verify that is correct by running inxi -Gxxx.

I used the below to decide a boot cycle. The command would need adjusted if that is not correct.
-2 = monitor did not wake.
-1 = reboot from SSH
0 = current boot with 6.1.0-1006-oem

Here is the linux-oem-6.1 (6.1.0-1007.7) Changelog.

Only a reboot worked.

Possibly restarting X Server might have worked, but that restarts the desktop session so you would also lose what is open by doing that.

[glitchathon]

@SMG,
Thank you very much for your reply!

Here is my output for inxi -Gxxx:

Code: Select all

Graphics:
  Device-1: Intel vendor: Micro-Star MSI driver: i915 v: kernel ports:
    active: HDMI-A-2 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-3, HDMI-A-4
    bus-ID: 00:02.0 chip-ID: 8086:a780 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.3 compositor: marco v: 1.26.0
    driver: X: loaded: modesetting unloaded: fbdev,vesa gpu: i915
    display-ID: :0 screens: 1
  Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.7x15.0")
    s-diag: 777mm (30.6")
  Monitor-1: HDMI-2 mapped: HDMI-A-2 model: Asus PB258 serial: FBLMTJ003484
    res: 2560x1440 hz: 60 dpi: 118 size: 553x311mm (21.8x12.2")
    diag: 634mm (25") modes: max: 2560x1440 min: 720x400
  OpenGL: renderer: Mesa Intel Graphics (RPL-S) v: 4.6 Mesa 22.2.5
    direct render: Yes

Was just looking for error messages during the time frame between about 12:30AM and 7:30AM when things stopped working, and I didn't see anything that looks different than messages before and after. I'll dig into this a little deeper when I get home tonight.

Thanks for helping me dig into this. I actually woke up the monitor successfully a few times today with the previous (1006) kernel version, so so far, it does seem like it is the 1007 update that caused it.

[SMG]

Graphics:
Device-1: Intel vendor: Micro-Star MSI driver: i915 v: kernel ports:
active: HDMI-A-2 empty: DP-1, DP-2, HDMI-A-1, HDMI-A-3, HDMI-A-4
bus-ID: 00:02.0 chip-ID: 8086:a780 class-ID: 0300

If I have the boot cycles correct, the command I recommended should work because it has the correct bus ID.

Was just looking for error messages during the time frame between about 12:30AM and 7:30AM when things stopped working, and I didn't see anything that looks different than messages before and after. I'll dig into this a little deeper when I get home tonight.

If there is a problem with the i915 driver, it may not show in the logs.

Thanks for helping me dig into this. I actually woke up the monitor successfully a few times today with the previous (1006) kernel version, so so far, it does seem like it is the 1007 update that caused it.

If it is the kernel, you may want to report a bug so they know it needs corrected.

[glitchathon]

Yep the command you recommended was the one I used. I forgot how many times I had to reboot to get to the grub menu , so tweaked the number a few times. Hopefully I can find some evidence of what happened, in which case I can make a bug report. Thanks!

[SMG]

Yep the command you recommended was the one I used. I forgot how many times I had to reboot to get to the grub menu , so tweaked the number a few times.

If you run

Code: Select all

journalctl --list-boots | tail -n 10

that will list the last 10 boot cycles with the start and stop dates/times. You would want to use the number in the far left column in the command.

[glitchathon]

So there is one error I found that is unique to the time period between the time I installed the 6.1.0-1007 kernel and the time the monitor stopped working:

Code: Select all

kernel: [32916.799507] Fence expiration time out i915-0000:00:02.0:Xorg[1168]:19a4a14!

This error happened a lot, despite the system running just fine throughout the day yesterday up until 4AM. I discovered the monitor unresponsive at 7:30AM this morning. After that, I haven't seen that error again.

I looked into the archived syslog's and did not see that error at any point in the recent past, other than a Fence expiration time out related to some transcoding I did.

[SMG]

So there is one error I found that is unique to the time period between the time I installed the 6.1.0-1007 kernel and the time the monitor stopped working:

Code: Select all

kernel: [32916.799507] Fence expiration time out i915-0000:00:02.0:Xorg[1168]:19a4a14!

The command I gave you pulled out messages related to the driver, good or bad. It was not a command to pull out only errors.

The fact the line recorded many times with no correlation to your issue likely means it is not related.

I looked into the archived syslog's and did not see that error at any point in the recent past, other than a Fence expiration time out related to some transcoding I did.

When I did a search on Fence expiration time out i915, bugs related to transcoding Plex servers came up. Here is one GPU hang when transcoding in plex.

[glitchathon]

This morning, the monitor woke up normally. It seems like a kernel issue, so far. I'll look into submitting a bug report, but without an error message, I'm not sure if it would be helpful?

[SMG]

This morning, the monitor woke up normally. It seems like a kernel issue, so far. I'll look into submitting a bug report, but without an error message, I'm not sure if it would be helpful?

I do not know what might be helpful, but usually, if you do not supply information which is helpful then there are prompts about what information to provide. There might be some type of debugging parameters which you could run, but the developers would be the ones to suggest those.

[glitchathon]

Well, it happened again this morning on the older 6.1.0-1006-oem kernel, so it might not have anything to do with the 1007-oem kernel. Hmm...

[SMG]

Well, it happened again this morning on the older 6.1.0-1006-oem kernel, so it might not have anything to do with the 1007-oem kernel. Hmm...

The 6.1.0-1008-oem is available and there is a huge list of updates for it including ones for i915. Maybe it will help.

Or maybe your cable is starting to be problematic.

[glitchathon]

Well, it happened again this morning on the older 6.1.0-1006-oem kernel, so it might not have anything to do with the 1007-oem kernel. Hmm...

The 6.1.0-1008-oem is available and there is a huge list of updates for it including ones for i915. Maybe it will help.

Or maybe your cable is starting to be problematic.

Oh nice, I will keep an eye out for that update then. I should still be looking at this package? linux-oem-22.04c

I see it is still at version 6.1.0-1007, and I assume I should just check and wait for when it shows the 1008 version? Since I uninstalled the 1007 version, update manager probably won't be prompting me for it.

My cable should be ok, since I did try a few others when it last happened and I still couldn't get the monitor to connect until I rebooted.

Thanks again!

[SMG]

Oh nice, I will keep an eye out for that update then. I should still be looking at this package? linux-oem-22.04c

Yes, that is the package. If Synaptic is not yet showing 1008, then it may not have been released to everyone yet.

I see it is still at version 6.1.0-1007, and I assume I should just check and wait for when it shows the 1008 version? Since I uninstalled the 1007 version, update manager probably won't be prompting me for it.

I think it depends on what you did with 1007. Did you just put a hold on that package or all future packages?

[glitchathon]

Oh nice, I will keep an eye out for that update then. I should still be looking at this package? linux-oem-22.04c

Yes, that is the package. If Synaptic is not yet showing 1008, then it may not have been released to everyone yet.

I see it is still at version 6.1.0-1007, and I assume I should just check and wait for when it shows the 1008 version? Since I uninstalled the 1007 version, update manager probably won't be prompting me for it.

I think it depends on what you did with 1007. Did you just put a hold on that package or all future packages?

So it appears that kernel removal is a bit different. Since I managed it from Update Manager (removal of kernel), I didn't do any blacklisting of versions or packages... This is the sequence of events that happened:

• Installed linux-oem-22.04c which was version 1006 at the time.
• Prompted by Update Manager a few weeks later to update to 1007, which I accepted.
• Had the monitor issue
• Rebooted into grub and selected 1006 kernel
• Removed 1007 kernel from Update Manager/Kernel section
• If you go into Synaptic now, you can look for linux-oem-22.04c and it does not show it as installed, despite having installed 1006 from it. I never explicitly removed the package, but I did remove 1007 kernel from the kernels section, which now shows linux-oem-22.04c as not installed.

It seems like apt no longer sees that package installed, despite the 1006 kernel being installed and loaded. So when 1008 comes out, I assume the Update Manager won't see it, but I can just install that package and I am back to having that package installed and monitored for future updates.

Hope that makes sense!

[SMG]

If you go into Synaptic now, you can look for linux-oem-22.04c and it does not show it as installed, despite having installed 1006 from it.

What is showing as the "latest version" for linux-oem-22.04c? Is it 1007 or 1008?

It seems like apt no longer sees that package installed, despite the 1006 kernel being installed and loaded.

That seems a bit odd considering that is how you installed it in the first place.

So when 1008 comes out, I assume the Update Manager won't see it, but I can just install that package and I am back to having that package installed and monitored for future updates.

I don't know. Maybe they changed something in Ubuntu 22.04.

I still have LM20.3 installed and I can go into Synaptic and see individual packages for the linux-oem-5.14 kernel (the last one released for Ubuntu 20.04) and there are version numbers of each individual release at the end of the packages. I would have expected you could see something similar for linux-oem-6.1, but it is possible that is not the case.