kernel-packages team mailing list archive

[gumkins <391628@xxxxxxxxxxxxxxxxxx>]

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

-- 
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/391628

Title:
  Everything gets swapped out after resume from suspend using fglrx
  drivers

Status in “linux” package in Ubuntu:
  Confirmed

Bug description:
  After resuming from suspend, hard disk activity goes crazy, and the
  machine is very unresponsive.  Looking at what is happening in htop,
  it seems that the system is moving many pages to swap -- I can see
  swap usage increasing several Mb/second, and resident memory usage
  decreasing similarly.

  I have 3 Gb physical memory, 9 Gb swap, and in my normal usage, 'free'
  often reports zero usage of swap - everything fits comfortably in RAM.
  So I cannot see any reason why the system would need to do this.  From
  a look at syslog, it seems this time the system was using about 600 Mb
  of swap immediately after resume.  It then moved about 1 Gb out of RAM
  to swap for no apparent reason.  Final stats (once the disk stopped
  churning) from 'free' are in 'free_output.txt', and the output of 'ps
  -eF' is in 'ps_eF_output.txt'.  A look at the virtual/resident figures
  in the latter shows that many processes have been almost entirely
  swapped out.

  This has happened several times, though not every time I
  suspend/resume.  I don't think it happens the first time I
  suspend/resume after rebooting. Previously I just gave up and
  rebooted, since the system did not show any sign of becoming usable.
  This time it has actually become usable after about 15 minutes (which
  is obviously unacceptable - I consider suspend/resume to be broken on
  this machine).

  My machine is a Dell Studio 17 laptop.  This started occurring when I
  switched from the open source video driver to fglrx, previously I
  never experienced it.  I'm also using a patched xserver, as provided
  by Bryce Harrington from
  https://edge.launchpad.net/~ubuntu-x-swat/+archive/xserver-no-backfill
  due to bug #351186 (since I'm affected by that bug).  I don't know if
  it happens without that xserver, I suspect it is unrelated.

  /var/logs/syslog is in syslog.txt.  The resume occurred at Jun 24
  09:32:57

  There is a crash of some kind in that log.

  After a bit more usage of my machine, I'm finding that physical memory
  usage has returned to nearly 100%, but swap usage hasn't gone down.  I
  have no idea what is going on here.

  WORKAROUND: Do not use the fglrx drivers.

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