Unable to Resume from Suspend/Hibernate: XFCE / Radeon 6900 / openSUSE 13.1

English Install/Boot/Login
1

So, I had this issue awhile back and didn’t really dig too deep into it. I am running openSUSE 13.1 with XFCE and a Radeon 6900 with the proprietary drivers. I had KDE installed and was able to resume and suspend without issue. The only other relevant change is that I’m now running Windows on the first partition. This is a relatively minor issue but I really love using suspend and hibernate. So far I’ve Googled for 3-4 hours and tried a number of things with no success. I’d love to get to the bottom of this, so where should I start in figuring this issue out?

So to summarize, the problem is that when I resume from suspend my system seems to restore but I have absolutely no video and the USB keyboard is totally not responsive (but the USB mouse seems to working still working insofar as its LED lights are still going). What logs / information might you need so I can start working towards debugging this?

  • Greg
2

Somehow I forgot that I had posted about this before, sorry for the double post. I will try: "I changed from the kernel-desktop to kernel-default which solved the problem. " when I get back and report my findings.

3

So changing the kernel did not resolve the issue. This is still an open issue for me. I would be extremely grateful if anyone had any suggestions.

4

On 2014-10-14 15:46, gregORe wrote:

> What logs /
> information might you need so I can start working towards debugging
> this?

You need to look at /var/log/messages and /var/log/pm-suspend.log.
Hopefully you can reboot the machine without pulling power, either with
a brief touch on the power button, or via ssh from another machine.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

5

I have to hit the hard reset in order to get back in, sadly. There’s no indication of anything failing in the suspend log and the messages log is massive and filled with things I don’t really understand. Is there something I should be looking for in there? It doesn’t seem like anything is failing related to resuming.

  • Greg
6

gregORe wrote:

>
> So changing the kernel did not resolve the issue. This is still an
> open issue for me. I would be extremely grateful if anyone had any
> suggestions.
>
>

Are you overclocking? My system fails to resume from suspend, with
symptoms like yours, at 4.2 GHz. At 4.1, everything is ok. No other
problems are in evidence at 4.2.

*********** To reply by e-mail, make w single in address **************

7

On 2014-10-14 21:36, gregORe wrote:

> I have to hit the hard reset in order to get back in, sadly.

Well, at least allow for a minute for things to settle and been written to disk.

> There’s no
> indication of anything failing in the suspend log and the messages log
> is massive and filled with things I don’t really understand. Is there
> something I should be looking for in there? It doesn’t seem like
> anything is failing related to resuming.

I don’t know exactly what to look for till I see it :slight_smile:

The thing is to seek for the hour and minute when you hibernated the machine, and start reading.
Then there is a line when the machine starts booting again, this is not interesting.

This is the starting log of my system booting:


<3.6> 2014-10-01 22:22:35 Telcontar systemd 1 - -  Starting Dispatch Password Requests to Console Directory Watch.
<5.6> 2014-10-01 22:22:35 Telcontar rsyslogd - - -  [origin software="rsyslogd" swVersion="7.4.7" x-pid="1097" x-info="http://www.rsyslog.com"] start
<3.6> 2014-10-01 22:22:35 Telcontar systemd 1 - -  Started Dispatch Password Requests to Console Directory Watch.
<0.6> 2014-10-01 22:22:35 Telcontar kernel - - -     0.000000] Initializing cgroup subsys cpuset
<3.6> 2014-10-01 22:22:35 Telcontar systemd 1 - -  Mounting Debug File System...
<0.6> 2014-10-01 22:22:35 Telcontar kernel - - -     0.000000] Initializing cgroup subsys cpu
<0.6> 2014-10-01 22:22:35 Telcontar kernel - - -     0.000000] Initializing cgroup subsys cpuacct

If you don’t find anything, upload that section of the log to susepaste.org for a sensible time, like two weeks, and post here the link, so we’ll have a look.

Note: I mean the section from the start of hibernation or a bit before, till the start of the next booting; the booting itself is pointless.

–
Cheers / Saludos,

Carlos E. R.
(from 13.1 x86_64 “Bottle” at Telcontar)

8

I had the same problem on an old Toshiba laptop with an SUMO APU. Added acpi_sleep=s3_bios,s3_mode to the kernel boot and then added a wake up script calling vbetool IIRC on resume. The info was on the Arch Wiki site, sorry don’t have the link.

Fixed it with kernel 3.14 and above in my case.

9

I know the thread is old, but… Can you please tell me how you did it?