Bug ID 935086
Summary System hangs on resume from hibernation
Classification openSUSE
Product openSUSE Distribution
Version 13.2
Hardware Other
OS openSUSE 13.2
Status NEW
Severity Normal
Priority P5 - None
Component Basesystem
Assignee bnc-team-screening@forge.provo.novell.com
Reporter novell-ugeuder@sneakemail.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Created attachment 638210 [details]
screen image when resume from hibernate hangs

During resuming from hibernation to disk my system hangs.
I just installed the new dracut (patch openSUSE-2015-427) but the problem
persists.

I am aware that there are a couple of similar bug reports already, e.g. 
https://bugzilla.opensuse.org/show_bug.cgi?id=917221 but I'm not sure this is
the same issue. My hang has been 100% repeatable since 13.2 came out. (Actually
system has been reinstalled once since then, problem exactly the same)

When I started to debug the problem and added splash=0 rd.break=pre-mount
to the kernel command line the problem went away.

- With default kernel args: every resume hangs
- With additional splash=0: every resume hangs
- With additional splash=0 rd.break=pre-mount: every resume succeeds

So my guess is this could be a timing issue. Entering the rd shell and waiting
until I press Crtl-D makes the system slow enough that it works.

The last console message before hanging is (see attached screen image)

   [ OK ] Reached target Remote File Systems

The problem must be somewhere after that. But when trying to debug where it is
the problem went away.

splash=0 rd.break=pre-mount is kind of acceptable for me, but still that's not
the way things should work.

My setup:

/boot is ext2
rest of the disk is LUKS encrypted, LVM, rootfs is btrfs, /home is xfs

Some other report mentions that encrypted disks don't work, soem problem with
crypttab. However, this has never been my problem. The disk password is always
asked an opening the encryption seems to succeed. The hand occurs somewhat
later.

I guess the problem is difficult to understand/fix from the information
provided. So all hints to debug it further / provide more info are welcome.


You are receiving this mail because: