Different problems with suspend / resume on two systems

English Install/Boot/Login
1

Hello

I have installed openSUSE 13.2 on two systems.
An ASUS desktop PC and a Toshiba Notebook (NB 10).

The desktop PC sometimes freezes completely, after selecting “suspend” (to RAM, Ruhezustand) from the menu.
I need to press the power button for some time (hard way) in this situation.

The Notebook does suspend reliably, but after resuming, sometimes the keyboard and touchpad are “locked”.
I need to press the power button too, but the system then shuts down normally.

I have almost a default 64 bit installation on both systems with btrfs on SSD.

Will there be some update to fix these problems?

Thank you!

Linux 3.16.6-2-desktop
openSUSE 13.2 (Harlequin) (x86_64)
KDE 4.14.3

2

Only if you report them

You need to list the hardware in detail ie CPU memory video drivers etc and an exact detailed description of the problem

Report on bugzilla

https://en.opensuse.org/Bugzilla. Same log on as here

3

Thank you.
I would like to wait for some time and see if other people have similar problems, or if I am an extremely unlucky person having problems in this area on two completely different machines.

4

Suspend/Hibernate problems are fairly common. In Windows it is often cured with drivers from the motherboard maker. Unfortunately they don’t bother with Linux. An any case You can do a search in Bugzilla and add a comment to an exiting bug. More comments often help get a fix.

Become the squeak in the wheel

5

On 2014-12-02 13:46, theo222 wrote:

> Will there be some update to fix these problems?

Not unless they are reported (no, forum posts are not reports in this
context), and somebody finds out why you have a problem. From your post
there is very little information to make a diagnostic, sorry; neither do
I have a suggestion to try out. Suspend problems are difficult to diagnose.

–
Cheers / Saludos,

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

6

Thank you.

I haven’t attached any system information, because there are issues on two completely different systems, and I wanted to find out if this is an general known problem with this OpenSUSE Version.

One my desktop computer, I was using OpenSuSE 12.2 before and I had no problems with suspend-to-RAM.

I am going to write some bug reports later.

Can you tell me which informations are most helpful for creating a bug report?

/var/log/Xorg.0.log?
the output of dmidecode?

Thank you!

7

Well outlines are on the page I directed you to but in general also tell the hardware involved that is germane to the problem and what happens and how to reproduce it. You should always first do a check to see if others have reported and if it is close to your problem add a comment again with as much resolvable info concerning the environment and keep your descriptions short and to the point. Don’t need stories just facts

8

On 2014-12-03 21:06, theo222 wrote:
>
> Thank you.
>
> I haven’t attached any system information, because there are issues on
> two completely different systems, and I wanted to find out if this is an
> general known problem with this OpenSUSE Version.

Well, as gogalthorp suggest, a search in Bugzilla (true, not easy to do)
is a good thing.

I have no personal experience with 13.2, i just have a virtual install.
I can tell you my tricks with previous versions, and I don’t know for
sure if they are valid on 13.2.

I edit “/etc/suspend.conf” and disable the “splash” (splash = n). I also
increase verbosity (suspend loglevel = 255).

I have a note that says « use ‘no_console_suspend’ boot option for more
messages.»

This should allow you to see some messages, and perhaps you get to see
one with a clue.

The “/var/log/pm-suspend.log” is important. However, if it crashes, logs
are not written.

Once I had to add printk calls (I think that was the function) to the
kernel code itself to let it print debugging messages to the display, so
that I could know where it stopped or crashed. Maybe take videos,
because log to disk fails. Log to serial port is a possibility.

Then… the devs were replacing pm-utils with systemd things. I’m not
sure how far they went, but I expect problems.

You can try pm-… calls directly. I use pm-hibernate as root in a
terminal. There is another one for suspend.

I don’t know how exactly to browse logs info in 13.2, because it uses
systemd ways. You might prefer to install syslog and obtain traditional
text logs.

If your problem is that the keyboard blocks, try switching to text mode
before suspend, and suspend from terminal.

–
Cheers / Saludos,

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

9

Thank you for all the hints.

I have found something new.

I will concentrate on the notebook problem first, because it happens more frequently.

In case the keyboard and touchpad are locked after resuming, I can still use an external USB mouse!
I can then suspend again, using the external mouse.
After that, a key press starts “resume” and everything works again.

I doubt that anything is being logged in this case. I looks like some timing problem. It happens in about 20% of the cases.

These reports may have to do with my problem:
https://bugzilla.opensuse.org/show_bug.cgi?id=906026

More general:
https://bugzilla.opensuse.org/show_bug.cgi?id=904828
https://bugzilla.opensuse.org/show_bug.cgi?id=890012

10

On 2014-12-04 11:46, theo222 wrote:

> In case the keyboard and touchpad are locked after resuming, I can still
> use an external USB mouse!
> I can then suspend again, using the external mouse.
> After that, a key press starts “resume” and everything works again.

Curious.

Maybe it needs restarting the usb interfaces.

> I doubt that anything is being logged in this case. I looks like some
> timing problem. It happens in about 20% of the cases.

As it doesn’t crash, there will be logs. Whether they tell something
interesting or not, that’s different :slight_smile:

> These reports may have to do with my problem:
> https://bugzilla.opensuse.org/show_bug.cgi?id=906026
>
> More general:
> https://bugzilla.opensuse.org/show_bug.cgi?id=904828
> https://bugzilla.opensuse.org/show_bug.cgi?id=890012

Well, check which one looks the same as yours, and add your comments
there. If they have posted solutions, try them.

If none is your problem, create a new report.

Sorry, I can’t look at them this instant…

–
Cheers / Saludos,

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

11

Thank you.

I don’t know exactly. It seems that some code to wake up the keyboard and touchpad is no being executed or at the wrong moment.
The internal kbd and touchpad of a notebook is not connected via USB, right?

12

On 2014-12-05 13:16, theo222 wrote:

> The internal kbd and touchpad of a notebook is not connected via USB,
> right?

I’m unsure, but I think they are. Why not? The interface exists, and
keyboards need “something” to connect to the computer. Why use an
specific interface instead? It is rare to find keyboards with ps/2
cables, anyway, which is the other standard.

–
Cheers / Saludos,

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

13

There was an update today in this area:

https://bugzilla.opensuse.org/show_bug.cgi?id=904828

I have no idea if this is related, I’ll see later.

Thank you.