kernel-packages team mailing list archive

[Brad Figg <brad.figg@xxxxxxxxxxxxx>]

This bug is missing log files that will aid in diagnosing the problem.
>From a terminal window please run:

apport-collect 1328727

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

** Changed in: linux (Ubuntu)
       Status: New => Incomplete

** Tags added: trusty

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1328727

Title:
  s2disk/hibernate hangs during saving of image data

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Hibernation with the pm-hibernate command works fine on a freshly
  booted system, but when a significant portion of the RAM is in use,
  for instance by starting gimp, google-chrome and firefox at the same
  time, it stalls at the start of the saving of the image data:

  s2disk: Snapshotting system
  s2disk: System snapshot ready. Preparing to write
  s2disk: Image size: 441652 kilobytes
  s2disk: Free swap: 1798624 kilobytes
  s2disk: Saving 110413 image data pages (press backspace to abort) ...   0%

  The system is not usable at this point, although alt-sysrq still
  works. It looks like some sort of deadlock.

  The system is an Asus eeePC 1000HE with 2GB RAM and a 2GB swap
  partition and a Samsung SSD 840 EVO. The Ubuntu release is 14.04
  LTS. The kernel package is linux-image-3.13.0-27-generic version
  3.13.0-27.50 (32 bit).

  I found a kernel bug report that looks exactly the same:

  https://bugzilla.kernel.org/show_bug.cgi?id=75101

  In that bug report, the problem was bisected to commit a1c3bfb2.
  This commit is part of the 3.14 kernel, but was apparently backported
  to the 3.13 Ubuntu kernel. I've rebuild the kernel package with this
  commit reverted, and it seems to fix this issue for me.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1328727/+subscriptions