Re: [linux-pm] Re: swsusp 'disk' fails in bk-current - intel_agp at fault?

From: Dmitry Torokhov (dmitry.torokhov_at_gmail.com)
Date: 03/31/05

  • Next message: linux-os: "Low file-system performance for 2.6.11 compared to 2.4.26"
    Date:	Thu, 31 Mar 2005 11:32:52 -0500
    To: Patrick Mochel <mochel@digitalimplant.org>
    
    

    On Thu, 31 Mar 2005 08:02:44 -0800 (PST), Patrick Mochel
    <mochel@digitalimplant.org> wrote:
    >
    > On Thu, 31 Mar 2005, Dmitry Torokhov wrote:
    >
    > > Ok, what do you think about this one?
    > >
    > > ===================================================================
    > >
    > > swsusp: disable usermodehelper after generating memory snapshot and
    > > before resuming devices, so when device fails to resume we
    > > won't try to call hotplug - userspace stopped anyway.
    >
    > Hm, shouldn't we disable it before we start to freeze processes? We don't
    > want any more processes trying to start up after we've taken care of
    > them..
    >

    Can't a device be removed (for any reason) _while_ we are freezing
    processes? I think freeszing code will properly deal with it... What
    about suspend semantics - if suspend fails do we say the device should
    be operational or the system should attempt to re-initialize? I.e. we
    are not doing suspend after all - can we still drop messages on the
    floor? After all, we still have ability to run coldplug after failed
    suspend.

    I frankly am not sure at what point to disable usermode helper. Or
    maybe we need to have a list of pending events and suspend khelper_wq
    while suspending.

    -- 
    Dmitry
    -
    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: linux-os: "Low file-system performance for 2.6.11 compared to 2.4.26"

    Relevant Pages

    • Re: Suspend 2 merge
      ... since swsusp1 cheats and discards caches. ... before suspend attempt 800MB were in use. ... half-of-memory limit does not bite too badly). ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: 2.6.9-rc2-mm1 swsusp bug report.
      ... > It is easy to lose sight of the user perspective on these things if all ... > sprinkling the code with panics, ... never fails to suspend and is in Linus' tree. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: swsusp disk fails in bk-current - intel_agp at fault?
      ... You are right, for resume-during-suspend, we may as well risk it. ... > suspend and Nigel's partial device trees) would be so much ... :-) I think we can simply make device freeze/unfreeze fast enough. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [linux-pm] Re: swsusp disk fails in bk-current - intel_agp at fault?
      ... shouldn't we disable it before we start to freeze processes? ... > about suspend semantics - if suspend fails do we say the device should ... after failed suspend. ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)
    • Re: [lhcs-devel] Re: [PATCH][2.6-mm] i386 Hotplug CPU
      ... we steer the APs straight into the offline cpu ... I do not understand what AP and BSP means in this context. ... we can just shut those cpus down on suspend and completely boot ... send the line "unsubscribe linux-kernel" in ...
      (Linux-Kernel)