SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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)
[ 101.167822] acpi device:4d: registered as cooling_device9
[ 101.167875] input: Video Bus as /devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input7
[ 101.167920] [drm] Initialized i915 1.6.0 20151010 for 0000:00:02.0 on minor 0
[ 101.173301] usb 1-1: new high-speed USB device number 2 using ehci-pci
[ 101.190418] fbcon: inteldrmfb (fb0) is primary device
[ 101.200302] usb 2-1: new high-speed USB device number 2 using ehci-pci
[ 101.232116] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* uncleared pch fifo underrun on pch transcoder A
[ 101.232145] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH transcoder A FIFO underrun
[ 101.261887] Console: switching to colour frame buffer device 160x45
[ 101.262584] i915 0000:00:02.0: fb0: inteldrmfb frame buffer device
[ 101.287604] usb 1-1: New USB device found, idVendor=8087, idProduct=0024
[ 101.287618] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 101.287882] hub 1-1:1.0: USB hub found
[ 101.287974] hub 1-1:1.0: 4 ports detected
[ 101.314600] usb 2-1: New USB device found, idVendor=8087, idProduct=0024
[ 101.314613] usb 2-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[ 101.314745] hub 2-1:1.0: USB hub found
[ 101.314847] hub 2-1:1.0: 6 ports detected
[ 101.588307] usb 2-1.6: new low-speed USB device number 3 using ehci-pci
[ 101.677613] usb 2-1.6: New USB device found, idVendor=093a, idProduct=2510
[ 101.677645] usb 2-1.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 101.677659] usb 2-1.6: Product: USB Optical Mouse
[ 101.677670] usb 2-1.6: Manufacturer: PixArt
[ 102.612438] intel_rapl: Found RAPL domain package
[ 102.612454] intel_rapl: Found RAPL domain core
[ 102.613053] intel_rapl: Found RAPL domain uncore
[ 102.991144] i2c /dev entries driver
[ 103.634983] hidraw: raw HID events driver (C) Jiri Kosina
[ 103.647245] usbcore: registered new interface driver usbhid
[ 103.647925] usbhid: USB HID core driver
[ 103.649866] input: PixArt USB Optical Mouse as /devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.6/2-1.6:1.0/0003:093A:2510.0001/input/input8
[ 103.650964] hid-generic 0003:093A:2510.0001: input,hidraw0: USB HID v1.11 Mouse [PixArt USB Optical Mouse] on usb-0000:00:1d.0-1.6/input0
[ 103.679219] [drm] GMBUS [i915 gmbus ssc] timed out, falling back to bit banging on pin 1
[ 103.738221] [drm] GMBUS [i915 gmbus dpc] timed out, falling back to bit banging on pin 4
[ 103.797220] [drm] GMBUS [i915 gmbus dpd] timed out, falling back to bit banging on pin 6
[ 103.856217] [drm] GMBUS [i915 gmbus panel] timed out, falling back to bit banging on pin 3
[ 103.915204] [drm] GMBUS [i915 gmbus dpb] timed out, falling back to bit banging on pin 5
[ 104.513520] Adding 5242876k swap on /dev/mapper/slack-swap. Priority:-1 extents:1 across:5242876k
[ 104.683604] fuse init (API version 7.23)
[ 104.941468] EXT4-fs (dm-2): re-mounted. Opts: (null)
[ 109.358589] SGI XFS with ACLs, security attributes, no debug enabled
[ 109.399630] XFS (dm-3): Mounting V5 Filesystem
[ 109.658368] XFS (dm-3): Starting recovery (logdev: internal)
[ 109.809527] XFS (dm-3): Ending recovery (logdev: internal)
[ 111.370929] udevd[931]: could not read from '/sys/module/pcc_cpufreq/initstate': No such device
[ 115.603857] r8169 0000:02:00.0 eth0: link down
[ 115.603860] r8169 0000:02:00.0 eth0: link down
[ 116.561891] NET: Registered protocol family 10
[ 116.562262] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 117.206612] r8169 0000:02:00.0 eth0: link up
[ 117.206622] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[ 122.802544] vboxdrv: Found 4 processor cores
[ 122.818676] vboxdrv: TSC mode is Invariant, tentative frequency 2993199910 Hz
[ 122.818687] vboxdrv: Successfully loaded version 5.1.6 (interface 0x00260000)
[ 123.138284] VBoxNetFlt: Successfully started.
[ 123.180965] VBoxNetAdp: Successfully started.
[ 123.195327] VBoxPciLinuxInit
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?
Yes, the machine shuts off so as not to give any signal. Just for everything and I can only turn it on again if you remove the power cord and reconnect.
If the RAM, CPU, and motherboard are okay maybe you have a bad power supply? A short somewhere on your motherboard?
I made sure I did not have a short. I checked, I isolated the components in order to avoid this problem.
I will test with another power source to see if the problem occurs.
I made sure I did not have a short. I checked, I isolated the components in order to avoid this problem.
I will test with another power source to see if the problem occurs.
This sounds like a power supply issue, just by guessing. Or a mobo safety feature.
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?
Hourly likely wouldn't catch the peak before a shutdown unless the timing was just right... even ten minutes might not be frequently enough. But, as soon as the system is shut down, OP should be able to go into the BIOS and see the actual temperature. It might've cooled off a few degrees, but not enough that you wouldn't still get a ballpark of where it was.
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:
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:
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.
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.
40C+ is normal idle for i5s? My computers usually sit in the low 30s for idle. I'll get to mid-40s if I'm doing something on it. Granted, I run predominantly AMD, so I'm not terribly familiar with Intel's cooling properties.
Not that I'm saying the temps are the problem, but that does seem on the high side if it is idle temps.
40C+ is normal idle for i5s? My computers usually sit in the low 30s for idle. I'll get to mid-40s if I'm doing something on it. Granted, I run predominantly AMD, so I'm not terribly familiar with Intel's cooling properties.
Not that I'm saying the temps are the problem, but that does seem on the high side if it is idle temps.
On a stock, cooler, yeah I think temp in the 40s is normal. Depends on ambient temperature as well, obviously.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
