Ubuntu 14.04 restarting after the same amount of time

Colonel_Panic

Limp Gawd
Joined
Oct 5, 2009
Messages
328
I'm getting started with embedded systems and have Ubuntu server installed on a Mini ITX board for portability. It has 4GB of RAM and a 1.1GHz Celeron chip. I've since found that it reboots randomly, but often within a consistent timeframe. Just look at these uptime records from uptimed.

Code:
     #               Uptime | System                                     Boot up
----------------------------+---------------------------------------------------
     1     0 days, 00:20:19 | Linux 3.13.0-24-generic   Thu Aug 21 22:11:43 2014
     2     0 days, 00:20:18 | Linux 3.13.0-24-generic   Thu Jul 31 20:45:56 2014
     3     0 days, 00:20:18 | Linux 3.13.0-24-generic   Thu Jul 31 20:02:40 2014

I don't believe temperature to be an issue, as lm-sensors says the system is mostly 48C. I removed 1 RAM chip at a time but the problem persists. Additionally, I can't get into MemTest86 by booting Ubuntu or a live disk before the system reboots on its own.

I'm going to try keeping the system in the BIOS and see if it reboots. This might tell if the problem is Ubuntu based or something with hardware.
 

B00nie

[H]F Junkie
Joined
Nov 1, 2012
Messages
8,986
If you can't get into memtest even, your hardware is broken. Ubuntu is out of the equation at that point.
 

game14

[H]ard|Gawd
Joined
Nov 8, 2006
Messages
1,441
sounds like a hardware problem...check the switches and jumpers or other possibilities for shortcuts
 

jwcalla

2[H]4U
Joined
Jan 19, 2011
Messages
3,628
Do any of the log files indicate that a shutdown was initiated or do they just stop dead?
 

Colonel_Panic

Limp Gawd
Joined
Oct 5, 2009
Messages
328
Thanks for the info, everyone. I've checked /var/log/kern.log for some indication of the shutdown/boot process, but do not see anything interesting. I suspect hardware so I'm going to check with Biostar to see what they can do, but in the meantime I've looked deeper in the logs and have found more unusual things.


Code:
reboot   system boot  3.13.0-24-generi Sat Aug 23 21:59 - 22:09  (00:09)
reboot   system boot  3.13.0-24-generi Fri Aug 22 23:39 - 00:25  (00:45)
reboot   system boot  3.13.0-24-generi Fri Aug 22 18:01 - 00:25  (06:24)
reboot   system boot  3.13.0-24-generi Thu Aug 21 23:28 - 23:42  (00:14)
reboot   system boot  3.13.0-24-generi Thu Aug 21 23:15 - 23:42  (00:26)
reboot   system boot  3.13.0-24-generi Thu Aug 21 22:37 - 23:42  (01:04)
reboot   system boot  3.13.0-24-generi Thu Aug 21 22:12 - 23:42  (01:29)
reboot   system boot  3.13.0-24-generi Thu Jul 31 21:32 - 21:35  (00:02)
reboot   system boot  3.13.0-24-generi Thu Jul 31 21:14 - 21:35  (00:21)
reboot   system boot  3.13.0-24-generi Thu Jul 31 20:46 - 21:35  (00:49)
reboot   system boot  3.13.0-24-generi Thu Jul 31 20:30 - 21:35  (01:05)
reboot   system boot  3.13.0-24-generi Thu Jul 31 20:02 - 21:35  (01:32)
reboot   system boot  3.13.0-24-generi Thu Jul 31 19:49 - 20:02  (00:12)
reboot   system boot  3.13.0-24-generi Thu Jul 31 19:47 - 19:49  (00:01)
reboot   system boot  3.13.0-24-generi Thu Jul 31 19:44 - 19:46  (00:02)
reboot   system boot  3.13.0-24-generi Thu Jul 31 19:41 - 19:43  (00:02)
reboot   system boot  3.13.0-24-generi Thu Jul 31 19:31 - 19:40  (00:08)
reboot   system boot  3.13.0-24-generi Thu Jul 31 19:27 - 19:31  (00:03)
reboot   system boot  3.13.0-24-generi Thu Jul 31 19:25 - 19:27  (00:01)
reboot   system boot  3.13.0-24-generi Thu Jul 31 19:06 - 19:06  (00:00)
reboot   system boot  3.13.0-24-generi Thu Jul 31 18:52 - 19:06  (00:14)
reboot   system boot  3.13.0-24-generi Thu Jul 31 18:50 - 18:50  (00:00)
reboot   system boot  3.13.0-24-generi Thu Jul 31 14:26 - 18:34  (04:08)
reboot   system boot  3.13.0-24-generi Thu Jul 31 18:23 - 18:23  (00:00)
reboot   system boot  3.13.0-24-generi Thu Jul 31 18:22 - 18:22  (00:00)
reboot   system boot  3.13.0-24-generi Thu Jul 31 18:20 - 18:21  (00:00)
reboot   system boot  3.13.0-24-generi Thu Jul 31 18:14 - 18:19  (00:04)
reboot   system boot  3.13.0-24-generi Thu Jul 31 18:11 - 18:19  (00:07)
reboot   system boot  3.13.0-24-generi Thu Jul 31 18:10 - 18:11  (00:00)
reboot   system boot  3.13.0-24-generi Thu Jul 31 18:00 - 18:11  (00:10)
reboot   system boot  3.13.0-24-generi Thu Jul 31 17:55 - 17:59  (00:04)
reboot   system boot  3.13.0-24-generi Thu Jul 31 17:51 - 17:59  (00:07)
reboot   system boot  3.13.0-24-generi Thu Jul 31 17:46 - 17:51  (00:04)
reboot   system boot  3.13.0-24-generi Thu Jul 31 17:33 - 17:45  (00:11)
reboot   system boot  3.13.0-24-generi Wed Jul 30 22:53 - 23:05  (00:12)
reboot   system boot  3.13.0-24-generi Wed Jul 30 22:47 - 22:52  (00:05)
reboot   system boot  3.13.0-24-generi Wed Jul 30 22:39 - 22:52  (00:13)
reboot   system boot  3.13.0-24-generi Wed Jul 30 22:30 - 22:38  (00:07)
reboot   system boot  3.13.0-24-generi Wed Jul 30 22:27 - 22:38  (00:11)
reboot   system boot  3.13.0-24-generi Wed Jul 30 21:37 - 22:26  (00:48)
reboot   system boot  3.13.0-24-generi Tue Jul 29 19:58 - 00:34  (04:36)
reboot   system boot  3.13.0-24-generi Mon Jul 28 23:10 - 23:12  (00:02)
reboot   system boot  3.13.0-24-generi Mon Jul 28 22:28 - 23:08  (00:40)
reboot   system boot  3.13.0-24-generi Mon Jul 28 22:00 - 23:08  (01:08)

This is the record of
Code:
last reboot
If you look at the start/end times, there are some anomalies that are quite strange.

There are multiple occasions where the system shuts down at the same time (there are 4 at 23:42 for example) but each have a different startup time. Some of the startup times actually show before the previous record has shown shutdown, which is weird also. I don't know what all that means, but it seems to show there is something even more unusual going on.
 

Colonel_Panic

Limp Gawd
Joined
Oct 5, 2009
Messages
328
Some updates, along with what I hope is a resolution:

I sent the motherboard to Biosstar through RMA, and after about 3 weeks it came back, as the technician noted that it ran for a 12 hour burn-in test without issue.

In the meantime I picked up a 160W PicoPSU and just now wired it up (had to solder the connectors). Thanks to whoever suggested a power supply issue, as I was able to get into Ubuntu's MemTest program, which suggests to me that the issue could be fixed. The test is running now and so far it looks good. Hopefully that's the end!
 

Colonel_Panic

Limp Gawd
Joined
Oct 5, 2009
Messages
328
Dammit I spoke too soon. Even though it got through the memory test fine, it's still doing a hard stop and reboot. Still working on this one.
 

B00nie

[H]F Junkie
Joined
Nov 1, 2012
Messages
8,986
Dammit I spoke too soon. Even though it got through the memory test fine, it's still doing a hard stop and reboot. Still working on this one.

So you suspect a PSU problem, then pick up a miniature PSU thats most likely going to choke and garantee problems? Why don't you get a proper PSU for petes sakes!

What sort of a PSU did you have if you thought this 160W miniature version was going to cut the mustard?
 

Colonel_Panic

Limp Gawd
Joined
Oct 5, 2009
Messages
328
So you suspect a PSU problem, then pick up a miniature PSU thats most likely going to choke and garantee problems? Why don't you get a proper PSU for petes sakes!

What sort of a PSU did you have if you thought this 160W miniature version was going to cut the mustard?

The case came with a 60W PSU built for Mini ITX boards. Seeing that the system isn't crashing when going to Memtest86, I don't think the PSU is the problem any longer and I wasn't interested in picking up a full sized spare (I use a separate hacked 350W for bench power in electronics projects). I've since held it in BIOS for about an hour without problem, so now I'm loading different Ubuntu live disks to see if there's a conflict with the Ubuntu kernel.

Somehow I tend to get these weird, random issues with new hardware but I'm slowly eliminating possible issues, and OS now one of the last to try.
 

Colonel_Panic

Limp Gawd
Joined
Oct 5, 2009
Messages
328
Went through the internet again and discovered other Linux users with similar issues. A solution seems to have made it through the different forums until I found it here. From what I gather it has something to do with the kernel's power saving modes and others have had success disabling it. After making the change I now have 01:38 hour uptime so crossing fingers that it might be tamed. Will confirm later after leaving it running overnight!
 

B00nie

[H]F Junkie
Joined
Nov 1, 2012
Messages
8,986
Went through the internet again and discovered other Linux users with similar issues. A solution seems to have made it through the different forums until I found it here. From what I gather it has something to do with the kernel's power saving modes and others have had success disabling it. After making the change I now have 01:38 hour uptime so crossing fingers that it might be tamed. Will confirm later after leaving it running overnight!

Even this problem might relate to the PSU if your PSU doesn't support the proper power saving modes and voltages. But I hope you got it solved.
 
Top