<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel about="http://permalink.gmane.org/gmane.linux.power-management.general">
    <title>gmane.linux.power-management.general</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11655"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11654"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11653"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11652"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11651"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11650"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11649"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11648"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11647"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11646"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11645"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11644"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11638"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11635"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11634"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11633"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11632"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11631"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11630"/>
        <rdf:li rdf:resource="http://permalink.gmane.org/gmane.linux.power-management.general/11629"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11655">
    <title>Re: resume from ram hangs on 2.6.26+ kernels on thinkpadz60m</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11655</link>
    <description>
Not really.  We must have broken something in 2.6.26, but there were not too
many suspend-specific patches in there vs .25.

What s2ram options are used?

What hardware is there in the box (chipset, graphics)?

Thanks,
Rafael
</description>
    <dc:creator>Rafael J. Wysocki</dc:creator>
    <dc:date>2008-08-21T12:43:43</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11654">
    <title>Re: forcedeth 10de:0373 doesn't work on resume</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11654</link>
    <description>
I cannot reproduce the problem locally, at least not with 2.6.27-rc4.

I was able to make my box resume from suspend to RAM by using

# s2ram --force --vbe_mode --vbe_post

(s2ram as shipped in openSUSE 11.0) and forcedeth works correctly
after the resume.  However, I had to add 'acpi_sleep=old_ordering' to the
kernel command line.

My box is a desktop with an Asus A8N-SLI motherboard and an Athlon 64 X2 CPU.

I have created a Bugzilla entry for this issue at
http://bugzilla.kernel.org/show_bug.cgi?id=11390
Please put a boot log from dmesg and the output of 'lspci -vvv' in there, as
text attachments.

Thanks,
Rafael
</description>
    <dc:creator>Rafael J. Wysocki</dc:creator>
    <dc:date>2008-08-21T12:34:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11653">
    <title>Re: [PATCH 2/6] Container Freezer: uninlinethaw_process()</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11653</link>
    <description>

20 bytes...

Does it still compile out if freezer is disabled?

Pavel
</description>
    <dc:creator>Pavel Machek</dc:creator>
    <dc:date>2008-08-20T16:44:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11652">
    <title>Re: [PATCH 1/6] Container Freezer: Fix freezer Kconfig</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11652</link>
    <description>Acked-by: Pavel Machek &lt;pavel&lt; at &gt;suse.cz&gt;

</description>
    <dc:creator>Pavel Machek</dc:creator>
    <dc:date>2008-08-20T16:42:12</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11651">
    <title>Re: Power management for individual devices</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11651</link>
    <description>Hi!

Just suspend devices when they are not used; you should not need
new interface(s) to do that.
</description>
    <dc:creator>Pavel Machek</dc:creator>
    <dc:date>2008-08-20T16:18:15</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11650">
    <title>[PATCH 6/6] Container Freezer: Document the cgroupfreezer subsystem.</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11650</link>
    <description>Describe why we need the freezer subsystem and how to use it in a documentation
file. Since the cgroups.txt file is focused on the subsystem-agnostic portions
of cgroups make a directory and move the old cgroups.txt file at the same time.

Signed-off-by: Matt Helsley &lt;matthltc&lt; at &gt;us.ibm.com&gt;
Cc: Andrew Morton &lt;akpm&lt; at &gt;linux-foundation.org&gt;
Cc: Paul Menage &lt;menage&lt; at &gt;google.com&gt;
Cc: containers&lt; at &gt;lists.linux-foundation.org
---
 Documentation/cgroups.txt                   |  548 ----------------------------
 Documentation/cgroups/cgroups.txt           |  548 ++++++++++++++++++++++++++++
 Documentation/cgroups/freezer-subsystem.txt |   99 +++++
 Documentation/cpusets.txt                   |    2 
 4 files changed, 648 insertions(+), 549 deletions(-)

Index: linux-2.6.27-rc1-mm1/Documentation/cgroups.txt
===================================================================
--- linux-2.6.27-rc1-mm1.orig/Documentation/cgroups.txt
+++ /dev/null
&lt; at &gt;&lt; at &gt; -1,548 +0,0 &lt; at &gt;&lt; at &gt;
-CGROUPS
--------
-
-Written by Paul Menage &lt;menage&lt; at &gt;google.</description>
    <dc:creator>Matt Helsley</dc:creator>
    <dc:date>2008-08-19T23:22:38</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11649">
    <title>[PATCH 3/6] Container Freezer: Make freezer state namesless generic</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11649</link>
    <description>Rename cgroup freezer states to be less generic to avoid any name collisions
while also better describing what each state is.

Signed-off-by: Matt Helsley &lt;matthltc&lt; at &gt;us.ibm.com&gt;
Cc: Andrew Morton &lt;akpm&lt; at &gt;linux-foundation.org&gt;
---
 kernel/cgroup_freezer.c |   56 ++++++++++++++++++++++++------------------------
 1 file changed, 28 insertions(+), 28 deletions(-)

Index: linux-2.6.27-rc1-mm1/kernel/cgroup_freezer.c
===================================================================
--- linux-2.6.27-rc1-mm1.orig/kernel/cgroup_freezer.c
+++ linux-2.6.27-rc1-mm1/kernel/cgroup_freezer.c
&lt; at &gt;&lt; at &gt; -22,9 +22,9 &lt; at &gt;&lt; at &gt;
 #include &lt;linux/seq_file.h&gt;
 
 enum freezer_state {
-STATE_RUNNING = 0,
-STATE_FREEZING,
-STATE_FROZEN,
+CGROUP_THAWED = 0,
+CGROUP_FREEZING,
+CGROUP_FROZEN,
 };
 
 struct freezer {
&lt; at &gt;&lt; at &gt; -57,7 +57,7 &lt; at &gt;&lt; at &gt; int cgroup_frozen(struct task_struct *ta
 state = freezer-&gt;state;
 task_unlock(task);
 
-return state == STATE_FROZEN;
+return state == CGROUP_FROZEN;
 }
 
 /*
&lt; at &gt;&lt; at &gt; -65,7 +65,7 &lt; at &gt;&lt; at &gt; int cgroup_frozen(struct task_str</description>
    <dc:creator>Matt Helsley</dc:creator>
    <dc:date>2008-08-19T23:22:35</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11648">
    <title>[PATCH 5/6] Container Freezer: Rename check_if_frozen()</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11648</link>
    <description>check_if_frozen() sounds like it should return something when in fact it's just
updating the freezer state.

Signed-off-by: Matt Helsley &lt;matthltc&lt; at &gt;us.ibm.com&gt;
Cc: Andrew Morton &lt;akpm&lt; at &gt;linux-foundation.org&gt;
---
 kernel/cgroup_freezer.c |   12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

Index: linux-2.6.27-rc1-mm1/kernel/cgroup_freezer.c
===================================================================
--- linux-2.6.27-rc1-mm1.orig/kernel/cgroup_freezer.c
+++ linux-2.6.27-rc1-mm1/kernel/cgroup_freezer.c
&lt; at &gt;&lt; at &gt; -201,8 +201,8 &lt; at &gt;&lt; at &gt; static void freezer_fork(struct cgroup_s
 /*
  * caller must hold freezer-&gt;lock
  */
-static void check_if_frozen(struct cgroup *cgroup,
-     struct freezer *freezer)
+static void update_freezer_state(struct cgroup *cgroup,
+ struct freezer *freezer)
 {
 struct cgroup_iter it;
 struct task_struct *task;
&lt; at &gt;&lt; at &gt; -222,6 +222,10 &lt; at &gt;&lt; at &gt; static void check_if_frozen(struct cgrou
  */
 if (nfrozen == ntotal)
 freezer-&gt;state = CGROUP_FROZEN;
+else if (nfrozen &gt; 0)
+freeze</description>
    <dc:creator>Matt Helsley</dc:creator>
    <dc:date>2008-08-19T23:22:37</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11647">
    <title>[PATCH 0/6] Container Freezer: fixes for -mm</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11647</link>
    <description>Hi Andrew,

These patches stack on top of the series you already have for the
container freezer patches. I believe they address all of the comments from
you and Rafael so far. 

Please consider these for -mm.

[PATCH 1/6] Container Freezer: Fix freezer Kconfig
[PATCH 2/6] Container Freezer: uninline thaw_process()
[PATCH 3/6] Container Freezer: Make freezer state names less generic
[PATCH 4/6] Container Freezer: Cleanup comment
[PATCH 5/6] Container Freezer: Rename check_if_frozen()
[PATCH 6/6] Container Freezer: Document the cgroup freezer subsystem

Cheers,
-Matt Helsley

</description>
    <dc:creator>Matt Helsley</dc:creator>
    <dc:date>2008-08-19T23:22:32</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11646">
    <title>[PATCH 4/6] Container Freezer: Cleanup comment.</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11646</link>
    <description>Make this comment clearer.

Signed-off-by: Matt Helsley &lt;matthltc&lt; at &gt;us.ibm.com&gt;
Cc: Andrew Morton &lt;akpm&lt; at &gt;linux-foundation.org&gt;
---
Andrew was wondering if the comment was in the right place. I think it is but
suspect it could stand to be clarified.

 kernel/cgroup_freezer.c |    4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Index: linux-2.6.27-rc1-mm1/kernel/cgroup_freezer.c
===================================================================
--- linux-2.6.27-rc1-mm1.orig/kernel/cgroup_freezer.c
+++ linux-2.6.27-rc1-mm1/kernel/cgroup_freezer.c
&lt; at &gt;&lt; at &gt; -61,8 +61,8 &lt; at &gt;&lt; at &gt; int cgroup_frozen(struct task_struct *ta
 }
 
 /*
- * Buffer size for freezer state is limited by cgroups write_string()
- * interface. See cgroups code for the current size.
+ * cgroups_write_string() limits the size of freezer state strings to
+ * CGROUP_LOCAL_BUFFER_SIZE
  */
 static const char *freezer_state_strs[] = {
 "THAWED",

</description>
    <dc:creator>Matt Helsley</dc:creator>
    <dc:date>2008-08-19T23:22:36</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11645">
    <title>[PATCH 2/6] Container Freezer: uninline thaw_process()</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11645</link>
    <description>Now that the cgroup freezer system also calls thaw_process() inlining these
functions uses more space. Uninlining returns some space:

Before:
textdatabssdechexfilename
42608722755322908164827220 49a854vmlinux
After:
textdatabssdechexfilename
4260852275532290816482720049a840vmlinux

Signed-off-by: Matt Helsley &lt;matthltc&lt; at &gt;us.ibm.com&gt;
Cc: Andrew Morton &lt;akpm&lt; at &gt;linux-foundation.org&gt;
Cc: Rafael J. Wysocki &lt;rjw&lt; at &gt;sisk.pl&gt;
---
 include/linux/freezer.h |29 +++--------------------------
 kernel/freezer.c        |31 +++++++++++++++++++++++++++++++
 2 files changed, 34 insertions(+), 26 deletions(-)

Index: linux-2.6.27-rc1-mm1/include/linux/freezer.h
===================================================================
--- linux-2.6.27-rc1-mm1.orig/include/linux/freezer.h
+++ linux-2.6.27-rc1-mm1/include/linux/freezer.h
&lt; at &gt;&lt; at &gt; -46,34 +46,11 &lt; at &gt;&lt; at &gt; static inline bool should_send_signal(st
 
 /*
  * Wake up a frozen process
- *
- * task_lock() is needed to prevent the race with refrigerator() which may
- * oc</description>
    <dc:creator>Matt Helsley</dc:creator>
    <dc:date>2008-08-19T23:22:34</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11644">
    <title>[PATCH 1/6] Container Freezer: Fix freezer Kconfig</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11644</link>
    <description>kernel/power/Kconfig is not sourced from all architectures but the freezer code
should be available to all architectures for the cgroup freezer subsystem.
Sourcing a new kernel/Kconfig.freezer has the added advantage of keeping the
config definition close to its use in the kernel/Makefile.

Signed-off-by: Matt Helsley &lt;matthltc&lt; at &gt;us.ibm.com&gt;
Cc: Andrew Morton &lt;akpm&lt; at &gt;linux-foundation.org&gt;
Cc: Rafael J. Wysocki &lt;rjw&lt; at &gt;sisk.pl&gt;
---
This patch should probably be merged with the patch that put:
config FREEZER
in kernel/power/Kconfig

 arch/alpha/Kconfig     |    1 +
 arch/arm/Kconfig       |    2 ++
 arch/avr32/Kconfig     |    2 ++
 arch/blackfin/Kconfig  |    3 +++
 arch/cris/Kconfig      |    2 ++
 arch/frv/Kconfig       |    2 ++
 arch/h8300/Kconfig     |    2 ++
 arch/ia64/Kconfig      |    2 ++
 arch/m32r/Kconfig      |    2 ++
 arch/m68k/Kconfig      |    2 ++
 arch/m68knommu/Kconfig |    2 ++
 arch/mips/Kconfig      |    2 ++
 arch/mn10300/Kconfig   |    2 ++
 arch/parisc/Kconfig    |    2 ++
 arch/powerpc/Kco</description>
    <dc:creator>Matt Helsley</dc:creator>
    <dc:date>2008-08-19T23:22:33</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11638">
    <title>Re: [PATCH] PCI PM: Introduce function pci_wake_from_d3(rev. 2)</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11638</link>
    <description>Hi!


ACK.
Pavel
 
</description>
    <dc:creator>Pavel Machek</dc:creator>
    <dc:date>2008-08-19T09:29:57</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11635">
    <title>Re: forcedeth 10de:0373 doesn't work on resume</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11635</link>
    <description>
This was a question for me. :-)
</description>
    <dc:creator>Rafael J. Wysocki</dc:creator>
    <dc:date>2008-08-18T21:48:52</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11634">
    <title>Re: forcedeth 10de:0373 doesn't work on resume</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11634</link>
    <description>
I'm not sure what you're asking here...?

</description>
    <dc:creator>Simon Arlott</dc:creator>
    <dc:date>2008-08-18T21:43:02</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11633">
    <title>Re: forcedeth 10de:0373 doesn't work on resume</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11633</link>
    <description>
Well, maybe.  The only way to verify that would be to try with MSI
disabled. ;-)

Thanks,
Rafael
</description>
    <dc:creator>Rafael J. Wysocki</dc:creator>
    <dc:date>2008-08-18T21:42:31</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11632">
    <title>Re: forcedeth 10de:0373 doesn't work on resume</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11632</link>
    <description>
Yes.  Usually the BIOS does something to devices in that case.


OK, I will.


That's interesting.  I'll try to reproduce it.


Hm.  I wonder if that's specific to forcedeth or other drivers may be affected.

Thanks,
Rafael
</description>
    <dc:creator>Rafael J. Wysocki</dc:creator>
    <dc:date>2008-08-18T21:39:39</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11631">
    <title>Re: forcedeth 10de:0373 doesn't work on resume</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11631</link>
    <description>
same problem with nv_shutdown about setting it to D3Hot?

YH
</description>
    <dc:creator>Yinghai Lu</dc:creator>
    <dc:date>2008-08-18T21:34:58</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11630">
    <title>Re: forcedeth 10de:0373 doesn't work on resume</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11630</link>
    <description>
With hibernation would it re-initialise the devices differently?


Mine doesn't either, try standby?


With this applied, I can resume from standby *without MSI* and the 
NIC still works. I haven't tested it without MSI and without the 
patch... mostly because I got a BUG when I tried to recompile.


Attached. (The previous email has all the standby/resume log output.)


Standby - resume from RAM is completely broken for my system.


If I have MSI enabled, it still doesn't work.

</description>
    <dc:creator>Simon Arlott</dc:creator>
    <dc:date>2008-08-18T21:25:07</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11629">
    <title>Re: forcedeth 10de:0373 doesn't work on resume</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11629</link>
    <description>
[Must have missed this message.]

I have a box with forcedeth that evidently works after a resume from
hibernation.  Unfortunately, so far I haven't been able to make the box
resume from suspend to RAM.  I'll do my best to try again tomorrow, but there's
a little hope. :-(


Simon, I'd prefer the full dmesg to the grepped forcedeth messages.

I guess this was resume from suspend to RAM?


It probably is.

Thanks,
Rafael
</description>
    <dc:creator>Rafael J. Wysocki</dc:creator>
    <dc:date>2008-08-18T21:13:09</dc:date>
  </item>
  <item rdf:about="http://permalink.gmane.org/gmane.linux.power-management.general/11628">
    <title>Re: forcedeth 10de:0373 doesn't work on resume</title>
    <link>http://permalink.gmane.org/gmane.linux.power-management.general/11628</link>
    <description>On Tue, 05 Aug 2008 20:29:44 +0100
Simon Arlott &lt;simon&lt; at &gt;fire.lp0.eu&gt; wrote:

[two weeks pass...]


That seems like a sensible change.


Is it still broken in current kernels?


Thanks.
</description>
    <dc:creator>Andrew Morton</dc:creator>
    <dc:date>2008-08-18T20:48:14</dc:date>
  </item>
  <textinput about="http://search.gmane.org/?group=$group=gmane.linux.power-management.general">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.linux.power-management.general</link>
  </textinput>
</rdf:RDF>
