On 17/06/11 23:33, Carl Fink wrote: > On Fri, Jun 17, 2011 at 07:28:30PM +1000, Scott Ferguson wrote: > >> Please send the recent suspend log events - if it makes it easier:- >> cat /var/log/pm-suspend.log | tail -n 120 > sample >> then edit sample. > > That's essentially what I did send you.
Aaah - the "Sun May 8 13:51:57 UTC 2011" caused me to jump to the conclusion it was an old, possible irrelevant log. No matter. In mitigation - I have only three brains cells - one reads the list, another is working, and the other one went out for coffee last week and has not returned ;-p > <snipped> > > During boot I see: > PM: Hibernation image not present or could not be loaded. That is as it should be. > > also during boot: > 0.280902] pci0000:00: Requesting ACPI _OSC control (0x1d) > [ 0.287986] ACPI: PCI Interrupt Link [LNKA] (IRQs 10 11) *0, disabled. > [ 0.288090] ACPI: PCI Interrupt Link [LNKB] (IRQs 10 11) *0, disabled. > [ 0.288172] ACPI: PCI Interrupt Link [LNKC] (IRQs 10 11) *0, disabled. > [ 0.288254] ACPI: PCI Interrupt Link [LNKD] (IRQs 10 11) *0, disabled. > [ 0.288336] ACPI: PCI Interrupt Link [LNKE] (IRQs 10 11) *0, disabled. > [ 0.288418] ACPI: PCI Interrupt Link [LNKF] (IRQs 10 11) *0, disabled. > [ 0.288501] ACPI: PCI Interrupt Link [LNKG] (IRQs 10 11) *0, disabled. > [ 0.288583] ACPI: PCI Interrupt Link [LNKH] (IRQs 10 11) *0, disabled. I "doubt" that is a problem. <snipped> > >> Is that a Windoof or Linux bootloader on the Windoof partition?? > > Don't understand the question. GRUB is my boot manager. Thanks - (it's a Linux bootloader) it's unlikely it would be relevant, but I like to have an idea of all the factors that might be at play. <snipped> Your image_size is 2/5 of RAM and smaller than swap - so I can't see a problem there. Before starting pm_tests, check whether your system "thinks" it supports hibernation (under Debian). $ cat /sys/power/state and check that "disk" is listed, (meaning it can hibernate) Then, find out what pm-hibernation switches are being used by:- $ cat /var/log/pm-suspend.log | grep -m 1 commandline and post the results If "disk" was listed try:- # echo disk > /sys/power/state And wait... (hibernation is slow, dunno why people use it...) Please post your results and any new, useful logs. Notes: hibernation using the last command will probably cause errors on resume. If hibernation was successful after grub starts you will see something like "loading resume image, please wait" then the screen will go black with a flashing cursor (you won't get the usual kernel messages during the boot). Cheers -- I don't mean to sound bitter, cold, or cruel, but I am, so that's how it comes out. ~ Bill Hicks -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4dfc294d.8050...@gmail.com
