Comment # 20 on bug 957547 from Markos Chandras

(In reply to Takashi Iwai from comment #19)
> (In reply to Markos Chandras from comment #18)
> > (In reply to Takashi Iwai from comment #17)
> > > Also, another thing to be helpful is to check whether the direct S4 also
> > > shows the same problem.  Try like
> > >   echo -n disk > /sys/power/state
> > > 
> > > This will trigger S4 but without systemd hooks.  Then you'll have to choose
> > > the right kernel in GRUB at resuming, instead of the automatic boot.
> > > 
> > > I guess this should still show the problem, but just to be sure.
> > > 
> > > Once when this is confirmed, you can try the test method in pm_test.  For
> > > example,
> > >   echo -n freezer > /sys/power/pm_test
> > > will test only the freezer and resumes.  You can see the available test
> > > methods by "cat /sys/power/pm_test".  More detailed instruction is found in
> > > /usr/src/linux/Documentation/power/basic-pm-debugging.txt.
> > 
> > Hi,
> > 
> > I have the same problem on TW even with the latest 4.4.3 kernel (maybe
> > update the title?) but on a different hardware (Dell Latitude E7450). I
> > tried your direct S4 suggestion and it worked 2 out of 2. Certainly not a
> > definitive result but good enough I suppose. I am not clearing up the
> > needinfo flag because this is different hardware than the original report.
> 
> Are your *user space* also TW or Leap?  Or is it openSUSE 13.2?
> If the direct S4 works, it means that the problem isn't in the kernel.  Or
> it's a user-mode S4 that hasn't been tested (and possibly broken) on recent
> kernels.

Yes the entire system is TW.

> 
> In anyway, check whether suspend and pm-utils packages are installed on your
> system.  If yes, kill them.

None of them is installed