Comment # 2 on bug 917221 from John Leys

(In reply to Takashi Iwai from comment #1)
> My wild guess is the nouveau driver breakage.  We've got many bug reports
> regarding S3/S4 with nouveau, unfortunately.
> 
> Could you try the newer kernels in OBS Kernel:stable repo?

I will try a newer kernel, but i wondier if it is the nouveau driver. I would
think that during the resume phase, journal writing would be done via
synchronous I/O for diagnostic purposes, but i see no entries in the journal
for the stages of the resume before the video driver is activated.   In
particular, i see none of the journal entries generated during the final stages
of the hibernate, which usually are written immediately after the kernel
becomes active.

If i enable a crash dump, would the enablement survive a resume and create a
crash dump if a crash occurred doring resume?  Is there a way to force the
system buffers to be flushed immediately after a write?  There used to be a way
to set this, but the kernel has changed much since i knew how to do this.

Additional information.  It appears as if the video is always active on failed
resumes, but very faint; to see it, i often have to view the screen at an
angle.  The image on the screen is the splash screen shown during a fresh boot,
suggesting that the kernel tried to do a fresh boot instead of a resume.

I have also now had failures for short periods of time between hibernate and
thaw, as well as a successful thaw for a period of several hours after a
hibernation.  But the general rule still is that long periods are exceedingly
likely to cause failure and short period exceedingly likely to be successful.