Re: -mm swsusp: do not default to platform/firmware

From: Pavel Machek (pavel_at_ucw.cz)
Date: 07/29/04

  • Next message: Andrew Morton: "Re: 2.6.8-rc2-mm1 link errors" 
    Date:	Thu, 29 Jul 2004 01:43:52 +0200
To: Andrew Morton <akpm@osdl.org>

    Hi!

    > > > -mm swsusp now defaults to platform/firmware suspend... That's
    > > > certainly unexpected, changes behaviour from previous version, and
    > > > only works on one of three machines I have here. I'd like the default
    > > > to be changed back.
    > >
    > > You overestimate my knowledge of suspend stuff. AFAICT the current -mm
    > > default is to enter ACPI sleep state via the BIOS rather than via Linux's
    > > ACPI driver. Correct?
    >
    > Its actually bit more complex. There are 3 methods:
    >
    > shutdown: save state in linux, then tell bios to powerdown
    >
    > platform: save state in linux, then tell bios to powerdown and blink
    > "suspended led"
    >
    > firmware: tell bios to save state itself
    >
    > "platform" is actually right thing to do, but "shutdown" is most
    > reliable.

    ...could you apply this? I hope it is accurate.
                                                                    Pavel

    --- clean/Documentation/power/swsusp.txt 2004-06-22 12:35:44.000000000 +0200
    +++ linux/Documentation/power/swsusp.txt 2004-07-29 01:42:29.000000000 +0200
    @@ -199,3 +202,30 @@
     should be sent to the mailing list available through the suspend2
     website, and not to the Linux Kernel Mailing List. We are working
     toward merging suspend2 into the mainline kernel.
    +
    +Q: Kernel thread must voluntarily freeze itself (call 'refrigerator'). But
    +I did found some kernel threads don't do it, and they don't freeze, and
    +so the system can't sleep. Is this a known behavior?
    +
    +A: All such kernel threads need to be fixed, one by one. Select place
    +where it is safe to be frozen (no kernel semaphores should be held at
    +that point and it must be safe to sleep there), and add:
    +
    + if (current->flags & PF_FREEZE)
    + refrigerator(PF_FREEZE);
    +
    +Q: What is the difference between between "platform", "shutdown" and
    +"firmware" in /sys/power/disk?
    +
    +A:
    +
    +shutdown: save state in linux, then tell bios to powerdown
    +
    +platform: save state in linux, then tell bios to powerdown and blink
    + "suspended led"
    +
    +firmware: tell bios to save state itself [needs BIOS-specific suspend
    + partition, and has very little to do with swsusp]
    +
    +"platform" is actually right thing to do, but "shutdown" is most
    +reliable. 

    -- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/
  • Next message: Andrew Morton: "Re: 2.6.8-rc2-mm1 link errors"

    Relevant Pages

    • [RFC][PATCH 5/10] I/O context inheritance
      ... The raid1 module makes use of temporary bios to sync physical disks ... handled by one of the kernel threads in the modules. ... the iocontext will be inherited from the source bio. ...
      (Linux-Kernel)
    • [ANNOUNCE] ACPI BIOS Guideline for Linux
      ... Linux is urgently missing and should get published. ... I mainly try to get feedback from OEMs and BIOS developers, ... ACPI BIOS checks whether Linux is running...). ...
      (Linux-Kernel)
    • Re: [SLE] Yast gets incorrect hard disk size during install
      ... >>format as well as partition the HD. ... Linux wants the BIOS to be in control of the hardware but what almost ... everybody who installs M$ does is answer YES to the question in the BIOS ... the first 256 bytes of the partition. ...
      (SuSE)
    • Re: Found, a new rootkit
      ... to the serial port. ... I fail the see the difference between the Linux driver for a serial ... The drivers themselves simply make BIOS calls. ...
      (Fedora)
    • Re: [SLE] SuSE Linux killed my hardware!
      ... It is not a compatibility problem: Linux itself worked like a number one. ... I didn't change the BIOS - I didn't have the chance any more, ... Are you REALLY sure that an os can't destroy any hardware (possibly overloads ... > On my Sony I had to add the boot parameters... ...
      (SuSE)