Linux Mint 14 new install hangs on restart after resume

[MrBob22]

Was running Mint 12. Did a new install with Mint 14 but now whenever I select Suspend, the pc will shut down but freezes upon restart (using the power button or other keys)
A search of the forum shows lots of issues with restart but these seemed all related to laptops and proprietary drivers (I am using a desktop with only standard drivers.)
Here is what the first few lines of Crash report showed:
ProblemType: KernelOops
Annotation: This occured during a previous suspend and prevented it from resuming properly.
Architecture: amd64
Date: Sat Feb 9 11:44:30 2013
DistroRelease: LinuxMint 14
ExecutablePath: /usr/share/apport/apportcheckresume
ExecutableTimestamp: 1358451126
Failure: suspend/resume
InterpreterPath: /usr/bin/python3.2mu
Package: linux-image-3.5.0-17-generic
ProcCmdline: /usr/bin/python3 /usr/share/apport/apportcheckresume
ProcCwd: /
ProcEnviron:
TERM=linux
PATH=(custom, no user)

Further down in the file, there was this possibly notable line:

/etc/pm/sleep.d/10_unattended-upgrades-hibernate suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend:
Having NetworkManager put all interaces to sleep...Failed.

/usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend:
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory

/usr/lib/pm-utils/sleep.d/60_wpa_supplicant suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend:

/usr/lib/pm-utils/sleep.d/75modules suspend suspend: not applicable.
Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:

/usr/lib/pm-utils/sleep.d/90clock suspend suspend: not applicable.
Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:

/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/95anacron suspend suspend:
stop: Unknown instance:

I am at a loss to get this resolved. Any help would be appreciated! MrBob22
Here is something about my hardware:
-Computer-
Processor : 4x Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz
Memory : 3927MB (663MB used)
Operating System : Linux Mint 14 Nadia
User Name : bob (bob)
Date/Time : Sat 09 Feb 2013 12:30:32 PM EST
-Display-
Resolution : 1920x1080 pixels
OpenGL Renderer : Mesa DRI Intel(R) Sandybridge Desktop
X11 Vendor : The X.Org Foundation
-Multimedia-
Audio Adapter : HDA-Intel - HDA Intel PCH
-Input Devices-
Power Button
Microsoft Comfort Curve Keyboard 2000
USB Optical Mouse
HDA Intel PCH HDMI/DP,pcm : 3=
HDA Intel PCH Line
HDA Intel PCH Front Mic
HDA Intel PCH Rear Mic
HDA Intel PCH Front Headphone
HDA Intel PCH Line Out Side
HDA Intel PCH Line Out CLFE
HDA Intel PCH Line Out Surround
HDA Intel PCH Line Out Front
-Printers (CUPS)-
Canon-PIXMA-MX890
Stylus-Photo-1400 : <i>Default</i>
-SCSI Disks-
ATA WDC WD10EALS-002
ATA WDC WD10EZEX-00R
_NEC DVD_RW ND-3500AG

[MrBob22]

i tried some of the Ubuntu fixes - like changes to the GRUB to enable pci devices (the theory being that these devices might need to be enabled for wakeup. None of that seemed to help.

Another idea was to get a more advanced version of the Linux Kernel. So I upgraded to 3.7.5-030705-generic. This booted ok and upon trying the suspend option, and resuming, it seemed to not hang. Sadly, a few mouse later, the system froze again.

Log still shows these errors:

/usr/lib/pm-utils/sleep.d/75modules resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/60_wpa_supplicant resume suspend:
Failed to connect to wpa_supplicant - wpa_ctrl_open: No such file or directory

/usr/lib/pm-utils/sleep.d/60_wpa_supplicant resume suspend: success.
Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend:
Having NetworkManager wake interfaces back up...Failed


I cannot say why the system keeps freezing.

[pgmer6809]

see next post. this one was duplicate

pgmer6809

[pgmer6809]

I am having a similar problem.
I am running Mate 14, 64 bit on a somewhat older MOBO (Asus K8V-SE) with an amd64 athlone chip.

I have narrowed the problem down to something to do with USB.

My monitor has a USB hub included, and I had that hub connected to the box, and my kbd and mouse plugged into the usb ports on the monitor.
In that configuration the screen would never come back. On resume the desktop would show briefly and then the monitor would go to pwr saving mode and I could never wake it up.

I unplugged the monitor USB hub, and connected a ps-2 mouse and ps2 kbd.

Now resume works just fine. (provided I booted with ps-2 stuff. Switching to ps2 after boot, while the mouse and kbd wil work the resume does not.

Next test is to use the usb kbd and mouse in a 'native' mobo usb port and not use the monitor usb hub.

That works. SO the problem seems to be if I am using the usb hub on the monitor.I can live with that but it is annoying and less convenient.

Anyone have any ideas about why this is?

pgmer6809

[MrBob22]

Hey thanks for the reply, pgmer6809~!
I dont have a hub connected, but I do have a KVM switch. I guess I could check that issue out by unplugging the switch and trying suspend without it. Why do you suspect USB? I think the bug pops up after the resume happens but just after the computer reconnects to the internet (wired or wireless).

I was looking at Ubuntu forums and there is a bug report on suspend not working properly after the new update in Ubuntu 12.04 (but it was reported on laptops, not on desktops) but I am betting something in the kernel update has caused the hang up. Bugs like this take awhile to get squashed.....

[pgmer6809]

It may have something to do with my mobo.
BUt I had the something of the same problem when I was running vers 11 or so of UBUNTU.
If I left a USB stick plugged into the computer when I tried to resume, it would just hang.
But if I removed the USB stick (either before or after the suspend i forget which) then it would work.

There seems to be something about UDEV that gets itself in a knot when it resumes.

I looked at the file /var/log/pm-suspend.log for messges, but I did not see anything there.
There is a bunch of stuff about the network not being able to put the ethernet cards to sleep etc.
but that does not seem to matter.
IF you are viewing the log with less, you can try searching for the string 'awake'
in the log this hapens right after all the suspend msgs, and is the beginning of the resume msgs.
but I did not see much there that helped me.
pgmer6809

[catweazel]

It may have something to do with my mobo.

Code: Select all

gksu pluma /etc/default/grub

Change this line:

Code: Select all

GRUB_CMDLINE_LINUX=""

To this:

Code: Select all

GRUB_CMDLINE_LINUX="acpi_sleep=nonvs"

Then do this:

Code: Select all

sudo update-grub

Finally, reboot and try suspending again.

[MrBob22]

Hey Thanks TechGhodTrole for the reply!

I loaded Grub file, patched in the change, updated grub, but sadly, the resume still results in a frozen screen. This is a shame, because I have two desktops next to each other, sharing nice new 27 inch monitor. I was switching between the two machines, put one to suspend and then using the other. Now I have to power down my Linux Mint box. Its sorta of weird box - has a miniITX board, a nice Intel I-3 2100, that Linux treats much like a quad core, but its loaded into a cast-off very large tower case that was a smoking gamer machine in a previous life. But I digress. Mint 12 work fine with this hardware. Only since I "upgraded" to Mint 14 has this popped up. MrBob22

[MrBob22]

I tried this bit of code from a Ubuntu forum:

Code: Select all

sudo sh -c 'echo "#!/bin/sh\ndbus-send --print-reply --system --dest=org.freedesktop.UPower /org/freedesktop/UPower org.freedesktop.UPower.Suspend" >/usr/local/bin/suspend;chmod +x /usr/local/bin/suspend'

Code: Select all

It did not solve the resume problems, but happily (by this fix or serendipity), I can now at least use hybernate. Your mileage may vary.
I dont plan to post further since I presume at some point this bug will be fixed upstream.