Mouse and display not recognised after turning off computer when frozen

[luchino_prince]

Hello to everyone!

I have noted a consistent pattern on my machine after it freezes, and I wanted to gain a better understanding of what could be happening.

I have had this machine for a couple of years, and it has frozen basically only for two types of errors, ether a Cuda ERROR or just swamping the RAM. When this happens the only way out I know (if you know safer ones let me know!) is to turn on off manually the machine. If I do so though, and I just turn on the machine again, all the lights turn on and the machine seems to work, but it cannot find the keyboard, display and mouse. If though I turn off the machine and wait for some time, like lets say one hour, then I turn on the machine, everything seems fine, and I can use seamlessly after that. I guess this at least tells me there is no terminal damage to any hardware component of my machine, also I had the machine checked some six months ago and they said the hardware looked good.

Could anyone hint me why once frozen, I need to wait some time before the machine can be turned back on and used? Are there any suggestions on other procedures other than a hard physical turn-off of the machine when in freezes? Also if anyone thinks that this pattern likely signals to a potential problem with any specific hardware component let me know!

Best,
Luca

[BG405]

Welcome to the Community!

I’m afraid you win the Gold Medal for the least amount of information ever provided. I didn’t think a zero-content post was even possible on this Forum!

Could you at least tell us what type of machine it is?

Can you boot from a Manjaro Live .ISO? Such as the one you used to install the system.

Any unusual noises from the hard disk, assuming it’s a spinning disk? Indicator lights?

… If a Manjaro Live session boots, we can go from there.

Cheers!

ETA:

@luchino_prince

Could anyone hint me why once frozen, I need to wait some time before the machine can be turned back on and used? Are there any suggestions on other procedures other than a hard physical turn-off of the machine when in freezes? Also if anyone thinks that this pattern likely signals to a potential problem with any specific hardware component let me know!

Thanks for providing this info.

It does suggest a thermal issue from what you describe i.e. having to wait some time presumably to cool down. Blocked fans/airways, or degraded thermal paste maybe?

We could do with some more system info now we know the machine can run, at least for a time. e.g. open a Terminal and enter:

inxi -zv8

Copy the output here, highlight it and click the </> buton above the reply window. If you need further help on how to do this, feel free to ask.

This information may reveal if the memory issues are the result of e.g. no swap etc.

[Nachlese]

@luchino_prince

Could anyone hint me why once frozen, I need to wait some time before the machine can be turned back on and used?

Depends on HOW you shut it down.
It needs to shut down fully - which can take some time (a couple of seconds)
before it can be started up again.

If you shut it down hard (essentially just cut power)
the file system will need to be repaired - which takes some time, before the normal boot process can then continue.

[BG405]

I forgot to mention lm-sensors.

Useful to have a Terminal window open with e.g. watch -n30 sensors

Might need to install (and configure) it first. It’s in extra repo.

sudo pacman -Syu lm-sensors

[dmt]

If you don’t have swap then create some, that should help prevent you running out of RAM.

https://wiki.archlinux.org/title/Swap

@luchino_prince

the only way out I know (if you know safer ones let me know!) is to turn on off manually the machine

Enable the magic sys req key, and use REISUB.

[HowTo] reboot / turn off your frozen computer: REISUB/REISUO

Difficulty: ★★☆☆☆ This tutorial was created because people are using a hard power off during freezes, so this will teach you how to turn off your computer when everything is frozen using softer means. So whenever you see someone saying they had to “Power Off” or “Hard Reset” their system without doing a REISUB, please send them here! If you’re reading this in response to a question, please click the green link above this text to bring you to the full unabridged text of the tutorial…

[luchino_prince]

Thanks for the information and the patience. I did not provide the system information just because I inserted when creating my account, so I thought users could just see that. Hence some general information regarding my machine.

1. Manjaro version: 6.6.30-2
2. BOOTLOADER: GRUB 2.12~3~manjaro
3. Motherboard: PRO Z690-A WIFI DDR4(MS-7D25)
4. CPU: 13th Gen Intel(R) Core™ i9-13900K
5. RAM: 62Gi, Swap: 8.8Gi
6. Cuda Version 12.4
7. Nvidia-drivers Version 550.78
8. GPU: NVIDIA GeForce RTX 3090

Here is the output of inxi -zv8

System:
  Kernel: 6.6.30-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=f3e4fb05-d671-44e9-a80f-46419019c5e3 rw quiet splash apparmor=1
    security=apparmor resume=UUID=a093d245-e462-4932-80ba-24d675e7fd3c
    udev.log_priority=3
  Desktop: GNOME v: 46.1 tk: GTK v: 3.24.41 wm: gnome-shell
    tools: gsd-screensaver-proxy dm: GDM v: 46.0 Distro: Manjaro
    base: Arch Linux
Machine:
  Type: Desktop System: Micro-Star product: MS-7D25 v: 1.0
    serial: <superuser required>
  Mobo: Micro-Star model: PRO Z690-A WIFI DDR4(MS-7D25) v: 1.0
    serial: <superuser required> uuid: <superuser required> UEFI: American
    Megatrends LLC. v: 1.90 date: 11/08/2022
Battery:
  Device-1: hidpp_battery_0 model: Logitech MX Keys Wireless Keyboard
    serial: <filter> charge: 100% (should be ignored) rechargeable: yes
    status: discharging
Memory:
  System RAM: total: 64 GiB available: 62.59 GiB used: 43.87 GiB (70.1%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Controller0-DIMMA1 type: no module installed
  Device-2: Controller0-DIMMA2 type: DDR4 detail: synchronous size: 32 GiB
    speed: 3200 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: A-DATA Technology part-no: N/A
    serial: <filter>
  Device-3: Controller1-DIMMB1 type: no module installed
  Device-4: Controller1-DIMMB2 type: DDR4 detail: synchronous size: 32 GiB
    speed: 3200 MT/s volts: note: check curr: 1 min: 1 max: 1 width (bits):
    data: 64 total: 64 manufacturer: A-DATA Technology part-no: N/A
    serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: 13th Gen Intel Core i9-13900K bits: 64 type: MST AMCP
    arch: Raptor Lake gen: core 13 level: v3 note: check built: 2022+
    process: Intel 7 (10nm) family: 6 model-id: 0xB7 (183) stepping: 1
    microcode: 0x122
  Topology: cpus: 1x cores: 24 mt: 8 tpc: 2 st: 16 threads: 32 smt: enabled
    cache: L1: 2.1 MiB desc: d-16x32 KiB, 8x48 KiB; i-8x32 KiB, 16x64 KiB
    L2: 32 MiB desc: 8x2 MiB, 4x4 MiB L3: 36 MiB desc: 1x36 MiB
  Speed (MHz): avg: 2730 high: 5276 min/max: 800/5500:5800:4300 scaling:
    driver: intel_pstate governor: powersave cores: 1: 5241 2: 5200 3: 5200
    4: 800 5: 800 6: 5200 7: 5276 8: 5200 9: 5243 10: 5200 11: 800 12: 5200
    13: 800 14: 5200 15: 5200 16: 800 17: 800 18: 800 19: 800 20: 4100 21: 800
    22: 4097 23: 4100 24: 800 25: 800 26: 800 27: 800 28: 800 29: 4117 30: 800
    31: 800 32: 800 bogomips: 191744
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_lbr arch_perfmon art avx avx2 avx_vnni bmi1 bmi2
    bts clflush clflushopt clwb cmov constant_tsc cpuid cpuid_fault cx16 cx8
    de ds_cpl dtes64 dtherm dts ept ept_ad erms est f16c flexpriority
    flush_l1d fma fpu fsgsbase fsrm fxsr gfni hfi ht hwp hwp_act_window
    hwp_epp hwp_notify hwp_pkg_req ibpb ibrs ibrs_enhanced ibt ida intel_pt
    invpcid lahf_lm lm mca mce md_clear mmx monitor movbe movdir64b movdiri
    msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pclmulqdq pconfig pdcm
    pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts rdpid rdrand rdseed
    rdtscp rep_good sdbg sep serialize sha_ni smap smep smx split_lock_detect
    ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tme tpr_shadow
    tsc tsc_adjust tsc_deadline_timer tsc_known_freq umip user_shstk vaes vme
    vmx vnmi vpclmulqdq vpid waitpkg x2apic xgetbv1 xsave xsavec xsaveopt
    xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling mitigation: Clear Register File
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB:
    conditional; RSB filling; PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected

Currently the machine works fine, and it displays no issues. It just seems that when people mention having to wait some time to restart the machine they are always in the order of seconds, while I have to wait potentially 30 mins-1hr, which seems a lot. The machine does not make any weird noise when turning on, all the lights turn on and also the fans turn on. It just fails to go to the login page.

Not sure about thermal issues as I did change the thermal paste in September, but I think only of the GPU.

Unfortunately I don’t know what a “Manjaro Live .ISO” is, so cannot answer that question.

Let me know if you spot any potential issues with the information provided, and thank you for the time again!

Best,
Luca

[luchino_prince]

@BG405

Can you boot from a Manjaro Live .ISO

And could the repairing take even 30 mins to your knowledge?

[dmt]

@luchino_prince

Unfortunately I don’t know what a “Manjaro Live .ISO” is, so cannot answer that question.

A .iso is a disk image. Manjaro makes several available to download, you download one and write it to a USB drive to produce a live USB (in this case described as a “live .ISO”), which can be used to install or fix Manjaro. It’s live because it’s a running OS not just an installer, which is why it can be used to fix a broken installation without reinstalling.

You should always have a live USB handy in case you run into trouble.

[Nachlese]

@luchino_prince

And could the repairing take even 30 mins to your knowledge?

It usually only takes a few seconds.
As always, it’s faster with solid state drives, slower with spinning disks.

[soundofthunder]

@luchino_prince

I did not provide the system information just because I inserted when creating my account, so I thought users could just see that.

@luchino_prince

Here is the output of inxi -zv8

For future reference when asked for system information we only need the inxi output. The other information you gave might only be useful if we wanted to buy a similar computer online.

@luchino_prince

When this happens the only way out I know (if you know safer ones let me know!) is to turn on off manually the machine.

Since you didn’t respond to the information given by @dmt to answer this question, I’ll paste the REISUB/REISUO link here again…

This is what you need to read and understand to avoid having to hard reset your machine:

[HowTo] reboot / turn off your frozen computer: REISUB/REISUO

Difficulty: ★★☆☆☆ This tutorial was created because people are using a hard power off during freezes, so this will teach you how to turn off your computer when everything is frozen using softer means. So whenever you see someone saying they had to “Power Off” or “Hard Reset” their system without doing a REISUB, please send them here! If you’re reading this in response to a question, please click the green link above this text to bring you to the full unabridged text of the tutorial…

Cheers.