Slackware shutting down - Is there log to read?
Hello, I'm running a slackware 14.2 running on a core machine i5 | 8gb ddr3 and 2x hds 1tb.
The problem is that the machine insists on turning itself off, and after a few seconds it is enough to take the power cord, reconnect and turn it on until the next shutdown. Detail, when turning off the led numlock stays on, sometimes it starts to start and stops. Tests done on motherboard: Ok Tests done in cpu: ok Testing memories: ok Last lines dmesg: Code:
101.167642] ACPI: Video Device [GFX0] (multi-head: yes rom: no post: no) |
Edit: duplicate post.
|
How and when does the machine turn off? Does the power cut off abruptly, or is it a normal shutdown with "going to init 0" type messages?
I understand that you can't turn the computer on again with the button, after it has shut down? Is that correct? |
If the RAM, CPU, and motherboard are okay maybe you have a bad power supply? A short somewhere on your motherboard?
|
Quote:
|
Quote:
I will test with another power source to see if the problem occurs. |
Quote:
This may sound odd, but has happened to me: have you checked the grounding at the outlet? |
I had a previous computer that when the temperature got too high, it would try and trigger a shutdown, although, I'm not sure exactly how it did it, because in kodi, it would only pop up the shutdown dialog without actually shutting anything down. I never ran into the issue outside of kodi, because I normally wouldn't operate the computer without running kodi.
So, your computer may take that to the extreme and actually shut off the computer when the temperature gets too high. So I would see if you can find the temperature of your processor when the shutdowns occur and, if they are high, see if there's a setting to change it in the BIOS and/or clean out the heatsink for the processor. |
bassmadrigal kind of something like output of sensors sent to log file run through hourly cron job?
|
Quote:
|
I agree with bassmadrigal. Overheating is the most common cause of unexpected shutdowns and the most common cause of overheating is dust build-up inside the machine and in the air vents.
Make sure the air vents are all clear and that there's no dust build-up inside the machine. If this is a desktop, open it up and inspect the heat sink over the CPU. Use a can of compressed air to blow away any dust. |
bassmadrigal
frankbell glorsplitz Yes, one of the first factors I investigated was the overheating of the components, even after using the computer for a long time because it is raining the climate is calmer, so the components remain at acceptable temperature. After the last reboot that was 30 minutes before the post I checked everything; Motherboard, cpu, power cables, usb connection cables, verified sources, replaced sata cables. The components are very clean, there is no dust or anything that prevents good ventilation. After doing a checkup, I set up the machine and from the moment of the post until now it is not turning off, including the first thing I did when the link was posting ... Is there any way to reliably stress components? time online: Code:
bash-4.3# uptime sensors output: Code:
bash-4.3# sensors |
Quote:
If you pass 15-30 minutes of that without anything bad happening, it's a very good indication your CPU and RAM are good to go. Note that this might be dangerous if you have a serious hardware problem going on in there. Your idle temps are normal. Do you have easy access to another PSU? I know it's a pain to replace the PSU, but that's often been the culprit with this sort of thing IME. |
Quote:
Not that I'm saying the temps are the problem, but that does seem on the high side if it is idle temps. |
Quote:
I personally use an i7, and it runs in the low 30s, but then again, I put a huge Noctua cooler on it, so that helps a great deal. At any rate, if there is a problem related to temperature, prime95 should reveal that very quickly. |
All times are GMT -5. The time now is 12:29 PM. |