Arch Linux

workdowg

Member

Registered: 2010-12-31

Posts: 69

How to diagnose laptop resume from suspend to ram issues

I'm going to start this thread very obscurely and edit it as the community gives their input...

So I've been avoiding putting my laptop to sleep because it wakes back up to a  frozen desktop about every other time now. None of the log files have given me any clues.
So my question is... Which files and logs are needed to narrow down why it will not resume consistently? Is there an application that would help diagnose it?

Thing to try first:
1) Let's rule out the discrete GPU problem: try switching off Nvidia card in BIOS/UEFI and using only Intel IGP. Test only, of course, not permanently.

Files needed to diagnose:
Will list names here

Programs to help diagnose:
Will list names here

My current system:
Asus - Q551LNB - laptop
Processor    - 4x Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
Memory - 8078MB
Intel(R) HD Graphics 5500 (Broadwell GT2)
3D controller - NVIDIA Corporation GM108M [GeForce 840M]
Memory - 8078MB (1370MB used)
1 SSD - (ext4          defaults,noatime,discard    0 1)
Kernel - Linux 4.2.2-1-ARCH (x86_64)
Window Manager: GNOME Shell 3.18

ATTN MODS: I posted a similar thread but got no answers so I am rephrasing the question to make it more helpful for others searching by Google... Feel free to remove the other one.

Thank you.

Last edited by workdowg (2015-10-17 12:28:33)

Xabre

Member

From: Serbia

Registered: 2009-03-19

Posts: 757

Re: How to diagnose laptop resume from suspend to ram issues

First, you said suspend, but not which type of suspend. Suspend to RAM (sleep) or suspend to disk (hibernate)?

From my experience, graphics stack is the most common cause of the problem, especially on laptops with hybrid graphics.

Let's rule out the discrete GPU problem: try switching off Nvidia card in BIOS/UEFI and using only Intel IGP. Test only, ofcourse, not permanently. If suspending works like that, that will narrow down the problem.

workdowg

Member

Registered: 2010-12-31

Posts: 69

Re: How to diagnose laptop resume from suspend to ram issues

First, you said suspend, but not which type of suspend. Suspend to RAM (sleep) or suspend to disk (hibernate)?

From my experience, graphics stack is the most common cause of the problem, especially on laptops with hybrid graphics.

Let's rule out the discrete GPU problem: try switching off Nvidia card in BIOS/UEFI and using only Intel IGP. Test only, ofcourse, not permanently. If suspending works like that, that will narrow down the problem.

Thank you.

Post renamed to "How to diagnose laptop resume from suspend to ram issues"

Adding - Disable discrete/hybrid graphics (I will do that right now!)

Adding - SSD - setting - ext4          defaults,noatime,discard    0 1

Edit: unfortunately I can't disable it in the bios... no setting for it. I am using Bumblebee now but it was doing it before I started using it.

Last edited by workdowg (2015-10-17 12:27:44)

frank604

Member

From: BC, Canada

Registered: 2011-04-20

Posts: 1,219

Re: How to diagnose laptop resume from suspend to ram issues

None of the log files have given me any clues.

Show the log files.  The journal output for the boot in which you crash could reveal something.

workdowg

Member

Registered: 2010-12-31

Posts: 69

Re: How to diagnose laptop resume from suspend to ram issues

None of the log files have given me any clues.

Show the log files.  The journal output for the boot in which you crash could reveal something.

Which ones exactly are needed? And what parameters? Journalctl -b 1 also? I'll have to wait until it happens. I'll try to make it do it...

workdowg

Member

Registered: 2010-12-31

Posts: 69

Re: How to diagnose laptop resume from suspend to ram issues

This thread got a little response but today I may have found a clue to the problem.
I found in the journalctl a reference to tlp which I had installed a long time ago and removed. But it still had a service file running... It wouldn't disable (tlp was not installed) so I installed it removed the service file and removed it. I was able to suspend to ram about 10 times after that.
However this morning when I woke it up I got my first error message!! Yay?

mei_me 0000:00:16.0: hbm: properties response: wrong status = 1 CLIENT_NOT_FOUND
mei_me 0000:00:16.0: mei_irq_read_handler ret = -71.