Solved Sudden shutdown

dark.initr0

dark.initr0

Hello!
Over a year I experience a problem with my 10y old computer - sudden shutdown (not reboot - just power turns off in 1 second).
I have FreeBSD 13.2-STABLE + Xorg + XFCE4 on my home computer.

I'm guessing this problem related with overhitting, but I'm not sure.
I don't load my CPU with any heavy usage CPU programs. Mostly I just read web.

Could you recommend me a soft / steps to find root on this problem?
thnx!
 
Is it a Thinkpad? Some of them are prone to do this when the wlan card develops electrical problems. Remove it, carefully clean the contacts (You do have ESD gear, yes?) and refit. That helped my x230, but I need to do it again soon.
 
Crivens said:
Is it a Thinkpad? Some of them are prone to do this when the wlan card develops electrical problems. Remove it, carefully clean the contacts (You do have ESD gear, yes?) and refit. That helped my x230, but I need to do it again soon.
Click to expand...
This is not a laptop.
 
dark.initr0 said:
"13.2-STABLE" I see in my "uname -a"
Click to expand...

Full output of `uname -a`, please, if you can. Bear in mind, it's outdated (snapshots of 13-2-STABLE are no longer offered, and so on).


For comparison:

Code: 
% fetch -o /tmp/revision.txt -q https://download.freebsd.org/snapshots/amd64/13.3-STABLE/REVISION && cat /tmp/revision.txt
54030e8a5df5
%

– that is, <{link removed}> (a range ending four days ago).
 
Last edited:
Looks like a hardware problem. How often does this happen? Does the problem still occur on one stick of RAM?
If not RAM, then the power supply. And if it's not the memory and the power supply, I would restore the BIOS to factory defaults and take the computer to a service center.
 
Aminavy said:
note: there is not 13.2-STABLE. we have 13-STABLE and 13.2-RELEASE (or 13.3)
Click to expand...
It's 13.3-STABLE at this time, 13.2-STABLE is entirely possible if stable/13 was built before releng/13.3 was branched off.
Code: 
TYPE="FreeBSD"
REVISION="13.3"
BRANCH="STABLE"

newvers.sh « conf « sys - src - FreeBSD source tree

cgit.freebsd.org cgit.freebsd.org

The version changes from 13.2-STABLE to 13.3-PRERELEASE to 13.3-STABLE.

src - FreeBSD source tree

cgit.freebsd.org cgit.freebsd.org

src - FreeBSD source tree

cgit.freebsd.org cgit.freebsd.org
 
nxjoseph said:
This might need coretemp or amdtemp to be loaded if it isn't already loaded. coretemp is for intel CPUs and amdtemp is for amd CPUs.
Click to expand...
thanks! I have loaded this AMD module and have now such picture (from sysctl):
dev.cpu.5.temperature: 57.0C
dev.cpu.4.temperature: 57.0C
dev.cpu.3.temperature: 57.0C
dev.cpu.2.temperature: 57.0C
dev.cpu.1.temperature: 57.0C
dev.cpu.0.temperature: 57.0C
Click to expand...

I will try to make a cron script to log every minute temperature and will analyze results when have a problem next time.
 
Maybe you have some script that updates large git repos? Some time ago I owned the x220T and it could handle almost everything, except cloning src and ports, it overheated and rebooted.
 
dark.initr0 By any chance were you doing any new installations or fiddling with settings?

I posted here a while back about random shutdowns myself. This wasn't too long after doing some things with the linuxulator. I didn't get to finish what I was doing but those settings and some things I installed are still there which makes me wonder if that started the problem.
 
For what it's worth, my x230 does this also while running other OSes. This can be a hardware thing.
 
drhowarddrfine said:
dark.initr0 By any chance were you doing any new installations or fiddling with settings?

I posted here a while back about random shutdowns myself. This wasn't too long after doing some things with the linuxulator. I didn't get to finish what I was doing but those settings and some things I installed are still there which makes me wonder if that started the problem.
Click to expand...
I have compiled kernel (just commented some lines). I don't use linuxulator.
 
I want to thank everyone for suggestions.
I have solved problem. Problem was in... much dust in my CPU cooler)
For the first time I was in such funny situation, I have tried to check everything in system, packages ... and cooler was last thing I have checked)

To gather temperature of CPU I have loaded kernel module admtemp at startup
Code: 
sysrc kld_list+=amdtemp

Also I have written small script to log temperature to my log file.

Bash: 
#!/usr/local/bin/bash

logfile="$HOME/scripts/logs/temperature.txt"
echo "$(date) : $(sysctl -n dev.cpu.0.temperature)" >> "$logfile"

All this gave me a conclusion about overheating.

Later I have found another way to online monitor temperature in htop (needs to turn on option "Show CPU temperature")
 
dark.initr0 said:
I have solved problem. Problem was in... much dust in my CPU cooler)
Click to expand...
Thank you for reminding me. A few days ago, I had to power-cycle my FreeBSD server at home (it usually runs 24x365). When it came up, I noticed that the fans make sad noises. Not funny noises, sad noises. I think I need to shut it down, remove it from the bookshelf, clean it with compressed air, and then power it up once on the bench to see that all the fans are spinning happily.

Obviously, I don't monitor the temperatures, nor the fan speeds ... because I'm lazy, old, weak, and stupid. A few of those I can change.
 
You must log in or register to reply here.
Back
Top