Comment 0 for bug 206997

Revision history for this message
freak007 (freak-linux4freak) wrote :

Binary package hint: linux-image-2.6.24-12-generic

Description: Ubuntu hardy (development branch)
Release: 8.04

Package:
linux-image-2.6.24-12-generic:
  Installé : 2.6.24-12.22
  Candidat : 2.6.24-12.22
 Table de version :
 *** 2.6.24-12.22 0
        500 http://archive.ubuntu.com hardy/main Packages
        100 /var/lib/dpkg/status

There is a problem with hibernation where there is 4GB of RAM on my laptop.

Everything works fine with 2 GB.

Of course suspend to ram works like a charm with 2GB and 4GB of RAM

I think it's a kernel ' specific problem, because i have the same problem on my desktop computer.

In the changelog of kernel 2.6.25-rc7 at kernel.org i found this comment:

commit 2050d45d7c32cbad7a070d04256237144a0920db
Author: Pavel Machek <email address hidden>
Date: Thu Mar 13 23:05:41 2008 +0100

    x86: fix long standing bug with usb after hibernation with 4GB ram

    aperture_64.c takes a piece of memory and makes it into iommu
    window... but such window may not be saved by swsusp -- that leads to
    oops during hibernation.

    Signed-off-by: Pavel Machek <email address hidden>
    Acked-by: "Rafael J. Wysocki" <email address hidden>
    Signed-off-by: Ingo Molnar <email address hidden>
    Signed-off-by: Thomas Gleixner <email address hidden>

And in 2.6.25-rc1:

commit 5d38998ed15b31f524bde9a193d60150af30d916
Author: Rene Herman <email address hidden>
Date: Wed Feb 6 01:40:05 2008 -0800

    PNP: do not test PNP_DRIVER_RES_DO_NOT_CHANGE on suspend/resume

    The PNP_DRIVER_RES_DO_NOT_CHANGE flag is meant to signify that the PNP core
    should not change resources for the device -- not that it shouldn't
    disable/enable the device on suspend/resume.

    ALSA ISAPnP drivers set PNP_DRIVER_RES_DO_NOT_CHANAGE (0x0001) through
    setting PNP_DRIVER_RES_DISABLE (0x0003). The latter including the former
    may in itself be considered rather unexpected but doesn't change that
    suspend/resume wouldn't seem to have any business testing the flag.

    As reported by Ondrej Zary for snd-cs4236, ALSA driven ISAPnP cards don't
    survive swsusp hibernation with the resume skipping setting the resources
    due to testing the flag -- the same test in the suspend path isn't enough
    to keep hibernation from disabling the card it seems.

    These tests were added (in 2005) by Piere Ossman in commit
    68094e3251a664ee1389fcf179497237cbf78331, "alsa: Improved PnP suspend
    support" who doesn't remember why. This deletes them.

    Signed-off-by: Rene Herman <email address hidden>
    Tested-by: Ondrej Zary <email address hidden>
    Cc: Bjorn Helgaas <email address hidden>
    Cc: Pierre Ossman <email address hidden>
    Cc: Adam Belay <email address hidden>
    Signed-off-by: Andrew Morton <email address hidden>
    Signed-off-by: Linus Torvalds <email address hidden>

commit a6eb84bc1e069e1d285167e09035ed6c27978feb
Author: Rafael J. Wysocki <email address hidden>
Date: Fri Feb 1 15:28:16 2008 +0100

    suspend: cleanup reference to swsusp_pg_dir[]

    swsusp_pg_dir[] is used for suspend, but not for hibernation.
    clean-up the ifdefs which worked by accident, while implying the opposite.
    Delete the __nosavedata, which also implied the opposite.

    Some day we may optimize CONFIG_ACPI_SLEEP to build minimal kernels
    for just hibernate or just suspend but not both,
    but today isn't that day.

    Signed-off-by: Rafael J. Wysocki <email address hidden>
    Signed-off-by: Len Brown <email address hidden>