[SOLVED] Fail to resume after suspend using lid and other issues

[stevef]

I don't think the "no IRQ handler for vector" is the root of the problem with resuming from suspend.

I have an Acer Aspire One 722 running LL 7.0 with 4GByte RAM.
This unit displays this message for a few seconds on each boot and each shutdown but it is not something that causes any issue.

I put the Aspire into suspend mode and then attempted to resume.
As the unit goes into suspend and resumes, there are very brief (less half a second) views of a screen showing 3-4 instances of a message which could be the same message but the unit suspends and resumes as expected.

Can you confirm how much RAM your Aspire has ?
Open a terminal (press Ctrl, Alt and T together) and run this command

Code:

inxi

to show basic system information

When you get the blank screen after attempting to resume from suspend is the Aspire completely unresponsive ?

Are there any signs of activity at all - e.g.
Can you ping the IP address from another system.
Are the system LEDs active ?
If you attach a full size keyboard, do the Caps Lock and Number Lock indicators toggle ?
If you attach an external optical mouse, does the LED underneath light ?
If you press 'Alt' 'Ctrl' and 'F2' together does anything happen ?

At the blank screen, how do you restore operation ?

Next time you go through the process of suspend, attempt to resume and recovery, make a careful note of
a) the time you initiate the suspend
b) the time you initiate the resume
c) the time you begin to recover the system

When you get back into the system (by whatever means) run this command replacing hh:mm with the times you attempted the resume (b) and forced the recovery c.

Code:

journalctl --since hh:mm --until hh:mm

Press Q at the end
This will display any messages the system was able to log while resuming which may give a clue.

If there is anything of interest, you can pipe the output to a text file

Code:

journalctl --since hh:mm --until hh:mm | tee ~/aspireresumelog.txt

You can review the text file to remove any sensitive information and post the contents back here for review giving us a bit of context.

If there's nothing in the resume log you can check the logs made during the suspend operation (using the 'a' and 'b' times).  This will show what the system was able to log while suspending.
Again this may contain significant information and can be piped to a text file in a similar way.