Luke Plant, thank you for reporting this bug and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .
If it remains an issue, could you run the following command in the development release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report. apport-collect -p linux <replace-with-bug-number> Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream- testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'. Please let us know your results. Thanks in advance. ** Tags removed: asusf8v dell-studio-17 hp6930 ** Tags added: needs-upstream-testing ** Attachment removed: "dmesg-s3-wakeup.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1471398/+files/dmesg-s3-wakeup.txt ** Attachment removed: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1497448/+files/syslog ** Attachment removed: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1497449/+files/kern.log ** Attachment removed: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1497450/+files/Xorg.0.log ** Attachment removed: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1497451/+files/dmesg ** Attachment removed: "udev" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1497452/+files/udev ** Attachment removed: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1503655/+files/Xorg.0.log ** Attachment removed: "Xorg.0.log.old" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1497453/+files/Xorg.0.log.old ** Attachment removed: "syslog.1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1497454/+files/syslog.1 ** Attachment removed: "kern.log.1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1497455/+files/kern.log.1 ** Attachment removed: "dmesg.0" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1497456/+files/dmesg.0 ** Attachment removed: "Xorg.0.log.old" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1503656/+files/Xorg.0.log.old ** Attachment removed: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1503657/+files/syslog ** Attachment removed: "syslog.1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1503658/+files/syslog.1 ** Attachment removed: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1503659/+files/kern.log ** Attachment removed: "kern.log.1" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1503661/+files/kern.log.1 ** Attachment removed: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1503662/+files/dmesg ** Attachment removed: "dmesg.0" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1503663/+files/dmesg.0 ** Attachment removed: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1520754/+files/syslog ** Attachment removed: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1520755/+files/Xorg.0.log ** Attachment removed: "kern.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1520758/+files/kern.log ** Attachment removed: "dmesg" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1520760/+files/dmesg ** Attachment removed: "udev" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/1520770/+files/udev ** Attachment removed: "syslog" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+attachment/2038953/+files/syslog ** Description changed: 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. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/391628 Title: Everything gets swapped out after resume from suspend using fglrx drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/391628/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
