Hello! Im using fedora 34 gnome edition. I have a problem. When i use my laptop (hp envy with ryzen 2500u, vega 8, 12gb ram) it work for a while perfectly, but later it chush and freeze. i think what problem is oom killer. I install earlyoom and try start GTA 5 and it work, but later i see black screen and working control (i can close gta5).
Are you seeing this in the system log? Or, other error messages?
1 Like
No, i dont see logs or error messages, but i noticed that the computer freezes when the RAM overflows. And if you turn on the oom killer, then there are two options either also freezes or (as in the case of GTA5) a black screen and working control. Can you told me how i can see logs and error messages?
How are you determining that RAM overflows? Can you explain “blank screen and working control” in a little more detail? Not trying to be difficult, just more detail will help us help you. Is the “oom killer” in question systemd-oomd or do you mean you’ve configured the kernel OOM killer in some specific way?
See Viewing logs in Fedora :: Fedora Docs for a quick guide to seeing system logs.
In the systemd-oomd case:
$ journalctl -n100 -u systemd-oomd
will give you the last 100 log messages from systemd-oomd. (-n100 could be replaced with -b or some other thing, or just left off to get the default, which I think is 1000 lines. And -u filters by the “systemd unit”, which is generally the service name.)
For the kernel OOM killer:
$ journalctl -k -g OOM
where -k means look for kernel messages and -g OOM “greps” for the string OOM and shows you only the lines that match.
But are you sure this isn’t a graphics driver problem? GTA 5 is Grand Theft Auto V, right? Are you running that through Steam / Proton? That can be kind of intense and expose driver bugs, cross-platform quirks, or even hardware problems.
[Danila_Filippov@fedora ~]$ journalctl -n100 -u systemd-oomd
– Journal begins at Sun 2021-10-17 15:48:20 MSK, ends at Mon 2021-11-01 21:41:>
окт 26 08:22:36 fedora systemd[1]: Stopped Userspace Out-Of-Memory (OOM) Killer.
окт 26 08:22:36 fedora systemd[1]: systemd-oomd.service: Consumed 1min 3.490s C>
– Boot 55d1c56c8dcc4a6188d045c4bffd2945 –
окт 26 08:22:54 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 26 08:22:54 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
окт 26 08:33:20 fedora systemd[1]: Stopping Userspace Out-Of-Memory (OOM) Kille>
окт 26 08:33:20 fedora systemd[1]: systemd-oomd.service: Deactivated successful>
окт 26 08:33:20 fedora systemd[1]: Stopped Userspace Out-Of-Memory (OOM) Killer.
– Boot 2335423288014387bb088463dec74d8f –
окт 26 08:33:42 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 26 08:33:42 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
окт 26 09:46:35 fedora systemd[1]: Stopping Userspace Out-Of-Memory (OOM) Kille>
окт 26 09:46:35 fedora systemd[1]: systemd-oomd.service: Deactivated successful>
окт 26 09:46:35 fedora systemd[1]: Stopped Userspace Out-Of-Memory (OOM) Killer.
окт 26 09:46:35 fedora systemd[1]: systemd-oomd.service: Consumed 4.632s CPU ti>
– Boot c075b51457df46fab25b8ee5f53855fa –
окт 26 09:46:52 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 26 09:46:52 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
more...
– Boot a55e9201650e498dab90cf6733bfa7db –
окт 26 10:34:02 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 26 10:34:02 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 059c18782ced46fb8a849d1c2f109d8d –
окт 26 11:01:52 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 26 11:01:52 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
окт 26 11:03:34 fedora systemd[1]: Stopping Userspace Out-Of-Memory (OOM) Kille>
окт 26 11:03:34 fedora systemd[1]: systemd-oomd.service: Deactivated successful>
окт 26 11:03:34 fedora systemd[1]: Stopped Userspace Out-Of-Memory (OOM) Killer.
– Boot 41ee5e97246d4fd093f6e9f602ee166e –
окт 26 11:04:08 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 26 11:04:08 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot bfc2e0aa66cc4bda8e304ae36d02d042 –
окт 26 17:13:07 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 26 17:13:07 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot da0f02fd89e34c8783ed56b9628c222a –
окт 27 07:28:05 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 27 07:28:05 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot f2c37609fcfc4a9ea846cdf009757596 –
окт 27 11:39:28 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 27 11:39:28 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot be756cc84cbc40d68bee649e69a66eee –
окт 27 17:46:07 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 27 17:46:07 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot ec16ff5f5eeb4df2b8ecff2ed9cdccfb –
окт 28 08:43:36 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 28 08:43:36 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
окт 28 12:05:16 fedora systemd[1]: Stopping Userspace Out-Of-Memory (OOM) Kille>
окт 28 12:05:16 fedora systemd[1]: systemd-oomd.service: Deactivated successful>
окт 28 12:05:16 fedora systemd[1]: Stopped Userspace Out-Of-Memory (OOM) Killer.
окт 28 12:05:16 fedora systemd[1]: systemd-oomd.service: Consumed 7.955s CPU ti>
– Boot 30f42db8984a42aa9840ec5837dd938d –
окт 28 12:07:08 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 28 12:07:08 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 66850565f945456a9e2e57bfc938239a –
окт 28 12:28:59 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 28 12:28:59 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 57eb6c1baa8548c1bd38375ded670972 –
окт 28 12:47:34 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 28 12:47:34 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 035f473a488043d5bf02aaea6587507f –
окт 29 13:46:28 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 29 13:46:28 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
окт 29 13:57:10 fedora systemd[1]: Stopping Userspace Out-Of-Memory (OOM) Kille>
окт 29 13:57:10 fedora systemd[1]: systemd-oomd.service: Deactivated successful>
окт 29 13:57:10 fedora systemd[1]: Stopped Userspace Out-Of-Memory (OOM) Killer.
– Boot ed1181641e4c49d19da43a5bbb2cc226 –
окт 29 13:57:29 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 29 13:57:29 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 352529c998fb4a8eba3d910aac3ef4f2 –
окт 29 15:58:20 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 29 15:58:20 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 9203528e62584f57b3fe579a434206be –
окт 29 16:16:26 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 29 16:16:26 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 53d0fcb1fe094f118f47e7cf93308f94 –
окт 29 20:10:52 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 29 20:10:52 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 4d8fbd09559e407db937b94f6dcf7e49 –
окт 29 20:18:34 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 29 20:18:35 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot dbefbfd6402f4f5cad3a8bc3a0de2420 –
окт 30 17:32:59 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 30 17:32:59 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot e9a4c79c520b41db8474e6a40e1ff16a –
окт 30 19:14:17 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 30 19:14:18 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 38c95706517144af92164b0f7377afd3 –
окт 30 21:01:33 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 30 21:01:33 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 0f39f65b53284f6d9b7df22cfca1486d –
окт 31 08:02:04 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 31 08:02:05 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 2d991a046fae4d07b58805eabb13b885 –
окт 31 08:32:33 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 31 08:32:33 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot ffb65b71a1db422a9eb159cdbbc3537d –
окт 31 08:42:52 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
окт 31 08:42:52 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot d49b75d7726a41fea08e249c159d025e –
ноя 01 08:55:56 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
ноя 01 08:55:56 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot e633a7972621496f86d7ab66164a643f –
ноя 01 10:01:11 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
ноя 01 10:01:11 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 862d6ee10dfc4907943a8c1cac4b4cec –
ноя 01 14:52:12 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
ноя 01 14:52:12 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot f087e8fe7eae4d2ba6514bd56d12b2c0 –
ноя 01 15:15:55 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
ноя 01 15:15:55 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 05cb6d1063ac4f2099406356236aba75 –
ноя 01 15:30:03 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
ноя 01 15:30:03 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
ноя 01 15:32:45 fedora systemd[1]: Stopping Userspace Out-Of-Memory (OOM) Kille>
ноя 01 15:32:45 fedora systemd[1]: systemd-oomd.service: Deactivated successful>
ноя 01 15:32:45 fedora systemd[1]: Stopped Userspace Out-Of-Memory (OOM) Killer.
– Boot e6e50e91ff70495b975694edb8be28f9 –
ноя 01 15:34:49 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
ноя 01 15:34:49 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 4880e85209694580b05e59656bd8f4b8 –
ноя 01 15:38:46 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
ноя 01 15:38:46 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot f4615c321caf4cddb025f7b700a15d31 –
ноя 01 15:49:22 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
ноя 01 15:49:22 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot b88cb509515947cdab8ede50f2cbd021 –
ноя 01 16:19:30 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
ноя 01 16:19:30 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 837f984d0b8f47328f35a6090592ab65 –
ноя 01 18:01:34 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
ноя 01 18:01:34 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 784c53eb8ccd4c778145e1e57a162c0c –
ноя 01 19:09:40 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
ноя 01 19:09:40 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 4636dbc24e5f4755a3396e034637b1ab –
ноя 01 19:49:36 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
ноя 01 19:49:36 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
– Boot 6b13a04d196449f7bade9a950d98dd19 –
ноя 01 20:11:39 fedora systemd[1]: Starting Userspace Out-Of-Memory (OOM) Kille>
ноя 01 20:11:39 fedora systemd[1]: Started Userspace Out-Of-Memory (OOM) Killer.
[Danila_Filippov@fedora ~]$ journalctl -k -g OOM
– Journal begins at Sun 2021-10-17 15:48:20 MSK, ends at Mon 2021-11-01 21:41:>
– No entries –
Im using earlyoom. My problem may stink during normal browser or document work. My laptop freeze and cant work without reboot
Thanks! I edited your post with a “details” block because it’s just repeating anyway. As you can see from that, all it’s doing is starting and stopping… it’s not logging that it’s killing anything. So that’s definitely not it.
Let’s try something else. First, use journalctl --list-boots to get a list of the logged entries for last system boots. That will give you output something like this:
-7 837687a2ab0c4e6ea9e21f3f7d106a2c Thu 2021-10-14 14:20:57 EDT—Fri 2021-10-15 21:32:46 EDT
-6 81c235bc2b9d45ceb0a7e7ed40250203 Fri 2021-10-15 21:33:36 EDT—Mon 2021-10-18 15:28:00 EDT
-5 ecc103cc664945d3b8df3507d728180e Mon 2021-10-18 15:28:43 EDT—Mon 2021-10-18 15:31:51 EDT
-4 9109adfb1b65440d958b7d01a5951aa2 Mon 2021-10-18 15:32:35 EDT—Mon 2021-10-25 09:47:43 EDT
-3 67d062729db64afb8198d875ab4e65f7 Mon 2021-10-25 09:48:29 EDT—Mon 2021-10-25 09:50:43 EDT
-2 05ec6c880aab4bd2ba33dab05575f1e1 Mon 2021-10-25 09:51:27 EDT—Sat 2021-10-30 10:32:30 EDT
-1 f2e9b33b734e4386bd72f95b291a76ed Sat 2021-10-30 10:33:15 EDT—Sat 2021-10-30 10:36:39 EDT
0 7832de8b011d49e283fb23084d2ad28f Sat 2021-10-30 10:37:23 EDT—Mon 2021-11-01 15:28:40 EDT
Now, you can use those numbers to get log entries _only from that boot. (That is, from when the computer started to the next time it starts.) Can you identify a time when the system crashed? If not now, next time it happens, it’ll be -1 — that is, the previous boot.
Then, you can run
journalctl -b-1 -k -p error
or, long form, same thing:
journalctl --boot=-1 --dmesg --priority=error
… either case, replacing -1 with the proper boot identifier, either the number or the long hex identifier, like 6b13a04d196449f7bade9a950d98dd19 for the most recent boot in the log you posted (now at the bottom of the “more…” section after my edit).
This should show you any and all kernel errors logged during that boot. Since you are seeing freezes, the error is almost certainly at that level, and this will help us identify where exactly.
1 Like