On 15/11/2023 07:03, Terry Coles wrote:
You might find some indication of past problems with ‘sudo -i
journalctl’. It will place you in less(1). There's the date to go by
and you can search with ‘/’, e.g. ‘oom-killer’.
There was only one instance of oom-killer:
Nov 02 08:46:48 OptiPlex kernel: systemd invoked oom-killer:
gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0,
oom_score_adj=0
That is some time before all this happened.
I've just spent some time manually parsing the journalctl output for any
sign of a problem. There are several instances of chromium being
flagged prior to the big crash, which I think was sometime around 0724
(I honestly can't remember when it occurred, but the next reboot at 0726
stayed up until 0916, when I think I was trying to get my desktop back.
I can see nothing in that period that I can recognise as a problem,
but I probably would recognise it if I saw it.
I have posted the output of journalctl at
https://hadrian-way.co.uk/Misc/journal.txt. (it's a very large file,
but I thought it was worth putting all the recent history out there for
someone who might see when things started going wrong).
--
Terry Coles
--
Next meeting: Online, Jitsi, Tuesday, 2023-12-05 20:00
Check to whom you are replying
Meetings, mailing list, IRC, ... http://dorset.lug.org.uk
New thread, don't hijack: mailto:dorset@mailman.lug.org.uk
