[SOLVED] Box is freezing after period of idleness

Having a bit of an issue that I can’t figure out:

One of our PCs, when it sits idle for a while, freezes up completely except the mouse – it still moves. However, nothing it clicks on responds in any way, nor does the keyboard work. A rebbot fixes it, for a while.

Sometimes, however, the boot hangs while the motherboard searches the web for some file about PXE. When this happens I have to boot from a LiveUSB first, and then a reboot to the hard drive will work.

Almost as if it is forgetting that the hard drive is there.

I have run the Intel Proceesor tool, IPCT, and the CPU passed.
Memtest86+ - 3 passes – passed
smartctl - the disk passed

I have also wiped the disk partitions, re-partitioned and formatted, and completely reinstalled. Everything seems to be fine as long as it doesn’t sit idle. Not yet sure how long it takes yet, though.

Info about the box:

@Otherbox ~ $ inxi -Fxz

System: Host: Otherbox Kernel: 4.13.0-45-generic x86_64 (64 bit gcc: 5.4.0)
Desktop: Cinnamon 3.6.6 (Gtk 3.18.9-1ubuntu3.3)
Distro: Linux Mint 18.3 Sylvia
Machine: Mobo: Intel model: DH57DD v: AAE82022-204
Bios: Intel v: JGIBX10J.86A.0663.2011.1019.0408 date: 10/19/2011
CPU: Dual core Intel Core i5 650 (-HT-MCP-) cache: 4096 KB
flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 12800
clock speeds: max: 3200 MHz 1: 1404 MHz 2: 1417 MHz 3: 1409 MHz
4: 1322 MHz
Graphics: Card: Intel Core Processor Integrated Graphics Controller
bus-ID: 00:02.0
Display Server: X.Org 1.18.4 drivers: intel (unloaded: fbdev,vesa)
Resolution: 1360x768@59.95hz
GLX Renderer: Mesa DRI Intel Ironlake Desktop
GLX Version: 2.1 Mesa 17.0.7 Direct Rendering: Yes
Audio: Card Intel 5 Series/3400 Series High Definition Audio
driver: snd_hda_intel bus-ID: 00:1b.0
Sound: Advanced Linux Sound Architecture v: k4.13.0-45-generic
Network: Card: Intel 82578DC Gigabit Network Connection
driver: e1000e v: 3.2.6-k port: 2020 bus-ID: 00:19.0
IF: enp0s25 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives: HDD Total Size: 1000.2GB (9.3% used)
ID-1: /dev/sda model: ST1000DL002 size: 1000.2GB
Partition: ID-1: / size: 99G used: 9.1G (10%) fs: ext4 dev: /dev/sda1
ID-2: /home size: 405G used: 71G (19%) fs: ext4 dev: /dev/sda3
ID-3: swap-1 size: 8.59GB used: 0.00GB (0%) fs: swap dev: /dev/sda2
RAID: No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors: System Temperatures: cpu: 44.0C mobo: N/A
Fan Speeds (in rpm): cpu: N/A
Info: Processes: 208 Uptime: 3 min Memory: 856.9/7775.3MB
Init: systemd runlevel: 5 Gcc sys: 5.4.0
Client: Shell (bash 4.3.481) inxi: 2.2.35

What other info can I supply to all you wonderful people?

Your disk stuff is unclear. I would suspect allocation or drive problems. There's also the possibility it is moving to standby, hibernate or even suspend. Does suspend/hibernate work?

I know it might sound a little funny, but I had similar-ish problem, in that: there was nothing that was clearly wrong other than something related to ACPI and/or interrupts.

To cut a long story short: it wasn't until I physically removed one of the drives, that I finally realized the root cause, which was ACPI interrupt routing failures. From what you've said, it does have at least some similarities with the issues I had. It was a dodgy hard drive that was the cause of my problems.

If it does go into hibernation; does it freeze up completely when it comes out of it? Does it come straight back out of it without you bringing it out of hibernation yourself?

Have you tried swapping any drives out?

Is there any possible clues in your kernel log?

If not, try that. Verify your machines hardware is in good working order and go from there.

Originally Posted by dustpuppy Sometimes, however, the boot hangs while the motherboard searches the web for some file about PXE.

you should switch off pxe booting in bios.

for the other issue:
open a terminal window, type 'top' or 'htop' (fancier), and figure out what the information means.
leave it running.
then, when the freeze occurs, with a bit of luck, you can see what's eating your resources.

Thanks, everyone.

I've replaced the disk, and already the difference is noticeable.
And I installed from scratch, and all looks good.
I couldn't find any mention of "PXE" in the BIOS,but now the issue has disappeared.
And I've got "top" running in another workspace.

Looking good...


UPDATE: next day running fine - thanks again

Originally Posted by dustpuppy I couldn't find any mention of "PXE" in the BIOS

it's some sort of network booting. might find these keywords in bios.

PXE is a boot method used for a system when you want to install automatically and there's nothing on the box. It's used via network. If you're not doing this it can be fairly safely ignored.

...and the OP seems to have solved their problem by replacing their drive. Which it was suggested in posts #2 and #3 that, it was a faulty drive that could be the problem here - and AFAICS it looks like it was indeed the problem.

well personally i still think it's advisable to disable network booting when you're not using it, even if the system is working fine otherwise, for, you know, safety reasons.