Hi, from the systems point of view 'obsdfreqd' is just a service. Seeing it being stopped on shutdown is expected and normal.
As for apmd, my system prints while booting: starting local daemons: apmd cron. While halting, no message of stopping local daemons is printed. Not seeing that message seems to be expected behavior on your system. Regarding crashes, have you tried renewing the heatsink compound on your CPU? Have you checked the RAM? > Apologies, i am realising the ofreqbsd message is because it is the > only pkg daemon that needs shutting down? i think this is because of a > hardware problem with the charging port, is there any ways i can run > diagnostics on this? > Cheers, > Freddie > > On Sun, 11 Feb 2024 13:31:11 +0000 > freddie bubble <freddiebub...@countermail.com> wrote: > > > Hi! > > I have a thinkpad x230 running openbsd 7.4 and recently have been > > having more frequent crashes, there is nothing consistent about > > the crashes other than maybe the laptop is plugged into power as it > > is most of the time. looking around online this seems to be to do > > with the interaction between apmd and ofreqbsd. apmd has the -L > > flag set and ofreqbsd has -T 75,55. When my computer turns off the > > only message i can see before the shutdown sequence starts is that > > it is or has stopped obsdfreqd. I wonder if it is because apmd is > > starting after ofreqbsd? i can only see ofreqbsd when i 'rcctl > > order.' Really sorry if this is not enough information for any > > help as this is my first post here in years. Hope you are all well > > :)) > > > > Cheers, > > Freddie > -- greetings, Florian Viehweger
