Hi Terry,
> I have posted the output of journalctl at
> https://hadrian-way.co.uk/Misc/journal.txt.
I see the kernel version has changed over time. Does one of these match
when problems started?
Oct 09 06:27:45 Linux version 6.2.0-34-generic
Oct 21 06:49:29 Linux version 6.2.0-35-generic
Oct 31 06:45:38 Linux version 6.2.0-36-generic
Nov 03 07:10:43 Linux version 6.5.0-10-generic
> 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 see a couple of recent ‘-- Boot’ which aren't preceded by an orderly
shutdown.
The first suggests attempts to reduce power consumption.
Nov 13 10:09:05 OptiPlex kded5[2241]: window match: "Bing — Konqueror" :OK
Nov 13 10:09:05 OptiPlex kded5[2241]: window match: "Bing — Konqueror" :OK
Nov 13 10:09:35 OptiPlex kernel: intel_rapl_common:
package-0:package:long_term locked by BIOS
Nov 13 10:09:35 OptiPlex kernel: intel_rapl_common:
package-0:package:long_term locked by BIOS
Nov 13 10:09:35 OptiPlex kernel: intel_rapl_common:
package-0:package:long_term locked by BIOS
Nov 13 10:09:39 OptiPlex kernel: intel_powerclamp: Start idle injection to
reduce power
Nov 13 10:09:40 OptiPlex kernel: intel_powerclamp: Stop forced idle
injection
Nov 13 10:09:41 OptiPlex kernel: intel_powerclamp: Start idle injection to
reduce power
Nov 13 10:09:43 OptiPlex kernel: intel_powerclamp: Stop forced idle
injection
Nov 13 10:09:44 OptiPlex kernel: intel_powerclamp: Start idle injection to
reduce power
Nov 13 10:09:46 OptiPlex kernel: intel_powerclamp: Stop forced idle
injection
Nov 13 10:09:47 OptiPlex kernel: intel_powerclamp: Start idle injection to
reduce power
Nov 13 10:09:49 OptiPlex kernel: intel_powerclamp: Stop forced idle
injection
Nov 13 10:09:50 OptiPlex kernel: intel_powerclamp: Start idle injection to
reduce power
Nov 13 10:09:52 OptiPlex kernel: intel_powerclamp: Stop forced idle
injection
Nov 13 10:09:53 OptiPlex kernel: intel_powerclamp: Start idle injection to
reduce power
Nov 13 10:09:54 OptiPlex kernel: perf: interrupt took too long (3163 >
3157), lowering kernel.perf_event_max_sample_rate to 63000
-- Boot ca7b1b0ebca14ef593ca63664a8ef61c --
Nov 13 10:11:30 OptiPlex kernel: microcode: updated early: 0x23 -> 0x2f,
date = 2019-02-17
The second just cuts off mid journalling.
Nov 14 06:56:28 OptiPlex systemd[1]: Starting
update-notifier-download.service - Download data for packages that failed at
package install time...
-- Boot 28f4f4d1397f4835a7c248aa9505aba1 --
Nov 14 06:57:30 OptiPlex kernel: microcode: updated early: 0x23 -> 0x2f,
date = 2019-02-17
Is the PSU in your desktop capable of supplying the whole machine at
full pelt, including all the peripherals? It might explain the
unexpected shutdown when the machine was highly loaded for a while.
Though of course what you really want is to stop the runaway load.
--
Cheers, Ralph.
--
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
