2

I am still using 14.04 (which still seems to be maintained, to my surprise).

Last week, it upgraded my kernel to Linux 3.13.0-149-generic. Since then I have the following problem:

I normally Suspend when not using the machine, with a request to de-suspend at 0400 each morning to do various housekeeping tasks. Since that upgrade, the de-suspension fails with a message

general protection fault: 0000 [#1] SMP

followed usually by various tracebacks and attempts to fix, most of which has disappeared off the top of the screen before it can be read. The keyboard and mouse are then completely dead, so I have to reboot, after which it informs me there has been a System Failure and do I want to report it (which I do, though my modem does not show much activity to indicate any report is actually being sent).

My hardware is i386 32bit using a Gigabyte Motherboard.

Once rebooted, the system works fine, with no evidence if hardware failure.

  • I understand what you're talking about but "wake" and "resume" are the common-use terms for what you're talking about when you say "de-suspend". They'll net you better results when searching. – Oli Jun 6 '18 at 12:11
  • 1
    And here's a pile of other people, seemingly with your problem: bugs.launchpad.net/ubuntu/+source/linux/+bug/1774150 – Oli Jun 6 '18 at 12:12
  • And: askubuntu.com/questions/1040169/… – Oli Jun 6 '18 at 12:13
  • 1
    Yes, the bug is now visible on launchpad, but no attempts to fix it thus far. – Charles Lindsey Jun 14 '18 at 11:01
  • 1
    The de-suspension was done by rtcwake(8). Also, I have now established that, if suspended by pm-hibernate (as opposed to pm-suspend), or if completely shut-down, rtcwake still brings it up at the appointed time. – Charles Lindsey Jun 14 '18 at 11:10

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.