I have had the same problem with intel nuc 6 since 1 month ago,
the problem is solved with kernel 4.19 LTS, every time I update to kernel 5.x LTS, the problem is accrued again
Please try to downgrade the kernel to 4.19 and test again.
]]>If I may add one thing that may or may not help the OP.
Try a different kernel, since I am using 4.19 the panic did not occur.
Rickrock; you are definitely encountering a kernel panic. https://wiki.archlinux.org/index.php/Ge … nel_panics
herOldMan: You may not have a kernel panic. Can you ping the box when it is in this state?
This appears to be an abandoned thread. We don't know much about the OP's problem. Rickrock and herOldMan don't have the exact same problem. I shall leave this thread open for now, but may end up closing it in the near future unless we hear from Travares. Should I close it, I invite both of you to start your own threads. If you feel this thread is relevant, you can always link back to it.
]]>Light blinks and there is nothing I can do but a hard reboot.
My laptop has an Intel cpu, and intel video.
I had the same issue while running Manjaro on it.
]]>I am also using a Ryzen 7 and I am also having intermittant freezes, sometimes once a week, other times twice a day. The system was built ~ 2 years ago and I did not see the problem until early/mid December (the intermittant nature of the freeze makes it very difficult to associate it with updates).
There is no relevant information in the journal nor Xorg logs.
The problem occurs under all loads from idle to heavy use. Neither heavy use nor an extended idle state will induce the problem.
Switching to the lts kernel did not solve the problem.
When it freezes it is truely frozen: it no longer appears on the network and is unavailable via ssh. Using a wired usb keyboard: CTRL+ALT+F2/F3/etc is not functional, there are no blinking LEDs, and SysRq is not responsive. The only resort is the reset button.
Memtest and SMART tests show all is well. The machine responds very well to stress tests.
Updating my BIOs (Crosshair VI) did not help.
]]>My Hardware:
Gigabyte B450 Auros Pro
Ryzen 5 3600
Nvidia 1660 Super
16G Ram
Usually it freezes in Chromium and last it showed the below in the logs:
Jan 04 02:16:10 loki slim[27178]: [27178:27206:0104/021610.340498:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.ScreenSaver.Inhibit: object_path= /org/freedesktop/Scree>
Jan 04 02:16:10 loki slim[27178]: [27178:27206:0104/021610.340519:ERROR:power_save_blocker_x11.cc(330)] No response to Inhibit() request!
Jan 04 02:16:14 loki kernel: NVRM: GPU at PCI:0000:09:00: GPU-4b1bbee0-8968-af05-2a72-b0aff8bf67a0
Jan 04 02:16:14 loki kernel: NVRM: GPU Board Serial Number:
Jan 04 02:16:14 loki kernel: NVRM: Xid (PCI:0000:09:00): 61, pid=593, 0cec(3098) 00000000 00000000
Jan 04 02:16:23 loki slim[27178]: [27178:27206:0104/021623.616920:ERROR:object_proxy.cc(632)] Failed to call method: org.freedesktop.ScreenSaver.UnInhibit: object_path= /org/freedesktop/Scr>
Jan 04 02:16:23 loki slim[27178]: [27178:27206:0104/021623.616940:ERROR:power_save_blocker_x11.cc(403)] No response to Uninhibit() request!
Jan 04 02:16:43 loki slim[593]: (EE) client bug: timer event5 debounce: offset negative (-905ms)
Jan 04 02:16:43 loki slim[593]: (EE) client bug: timer event5 debounce short: offset negative (-918ms)
Jan 04 02:16:46 loki slim[593]: (EE) client bug: timer event5 debounce: offset negative (-473ms)
Jan 04 02:16:46 loki slim[593]: (EE) client bug: timer event5 debounce: offset negative (-353ms)
Jan 04 02:16:46 loki slim[593]: (EE) client bug: timer event5 debounce short: offset negative (-366ms)
Jan 04 02:16:49 loki slim[593]: (EE) client bug: timer event5 debounce: offset negative (-252ms)
Jan 04 02:16:49 loki slim[593]: (EE) client bug: timer event5 debounce: offset negative (-148ms)
Jan 04 02:16:49 loki slim[593]: (EE) client bug: timer event5 debounce short: offset negative (-161ms)
Jan 04 02:16:49 loki slim[593]: (EE) client bug: timer event5 debounce: offset negative (-36ms)
Jan 04 02:16:50 loki slim[593]: (EE) client bug: timer event5 debounce: offset negative (-451ms)
Jan 04 02:16:50 loki slim[593]: (EE) client bug: timer event5 debounce short: offset negative (-464ms)
Jan 04 02:16:57 loki slim[593]: (EE) client bug: timer event5 debounce: offset negative (-403ms)
Jan 04 02:16:57 loki slim[593]: (EE) client bug: timer event5 debounce: offset negative (-323ms)
Jan 04 02:16:57 loki slim[593]: (EE) client bug: timer event5 debounce short: offset negative (-336ms)
Jan 04 02:17:16 loki kernel: nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
Jan 04 02:17:36 loki kernel: nvidia-modeset: WARNING: GPU:0: Lost display notification (0:0x00000000); continuing.
Jan 04 02:17:43 loki acpid[533]: client 593[0:0] has disconnected
Full log can be get from: https://www.dropbox.com/s/x7pw2wppivnah … -file?dl=1
Hope this helps.
]]>The only thing I can do is to hold down the power button and reboot it.
The question is: what things have you tried? How have you determined it has actually frozen?
What others have suggested (ping, ssh etc.) are good suggestions. Whenever I face a freeze, my goto procedure is (at least roughly) this:
1. CTRL+ALT+F2 (change to another VC from GUI). Sometimes it's just the X.org session which goes hayward.
2. if no response, SysRQ + forced sync. If HDD light blinks, I know the Kernel is not completely hung.
3. Depending on situation, I might SSH into the computer (if Kernel is not completely dead) or
4. a) If it seems just the display driver has hung (up to a point when VCs just don't display but still work underneath), CTRL+ALT+F2 and then CTRL+ALT+DEL should cause a soft reboot!
4. b) If I can not SSH (or feeling lazy and CTRL+ALT+DEL does not work) I'll do a SysRq + REISUB.
If all of the above and SysRq does not work, it is indeed a hard hung up. It is still worthwhile to try do a forced sync and mount-readonly (just in case Kernel is alive, but at this point it is already done) and then use the power button. But it is very rare to get to a point where using power button is actually needed (save for starting from poweroff), however it can happen.
Indeed check the logs afterwards in any case. Hanging can be caused by just about anything.
(Try journalctl -b -1 and then paste the log somewhere; if the session has been long, you could do journalctl --since '10 minutes ago' to get a bit shorter / manageable log size, but of course change the timespan accordingly to a long enough timespan to actually get the relevant log entries).
EDIT: A few clarifications
]]>Tavares
]]>I have an issue and I can't figure it out. My Arch Linux keeps freezing on me. Sometimes it takes 2min after boot and sometimes it's after 30min. It completely freezes and doesn't respond to anything no matter how long I wait. The only thing I can do is to hold down the power button and reboot it.
My hardware:
Gigabyte X570 Gaming X motherboard
Ryzen 7 3700x CPU
Nvidia Geforce 2070 RTX
16G Ram
On my mother board I have two M.2 SSDs, one from Samsung and the other from HP
On my Samsung M.2 I have Windows 10 installed. (gpt disk, UEFI boot)
On my HP M.2 I have Arch Linux installed. (also gpt UEFI boot)
My Windows 10 never freezes no matter how much work I'm doing. I could be running 10 programs and playing Red Dead at the same time on Ultra graphic settings without a problem.
My Arch sometimes freezes with just one terminal opened doing nothing. I have a Conky script that shows me that my Ram is at less than 10% used and CPU at 2% at the moment it freezes. I can't seem to reproduce the issue to figure out if there's a specific action that makes it freeze, it seems to just happen randomly.
I have a Thinkpad X1 carbon gen 2 (old one) with only Arch installed (Legacy) and I've never had this problem on my thinkpad even though my hardware is 10% the power of my desktop PC.
Please guys I'd love your help and opinions. My arch freezing makes it almost unusable! PLEASE HELP!!
Thank you for your time,
Tavares