From: Jiri Slaby <jirislaby@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
Jiri Slaby <jslaby@suse.cz>, LKML <linux-kernel@vger.kernel.org>,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
Subject: Re: PM: cannot hibernate -- BUG at kernel/workqueue.c:3659
Date: Wed, 25 Jan 2012 15:25:29 +0100 [thread overview]
Message-ID: <4F2010D9.5040900@gmail.com> (raw)
In-Reply-To: <201201250110.44360.rjw@sisk.pl>
On 01/25/2012 01:10 AM, Rafael J. Wysocki wrote:
> On Wednesday, January 25, 2012, Jiri Slaby wrote:
>> Yeah, 100%. Just try it with a small enough swap.
>
> Ah, thanks, so that's an error code path problem and most likely in the Linus'
> tree.
Just to emphasize what I wrote earlier. I would apprectiate this fixed
in 3.2 stable too.
--
js
WARNING: multiple messages have this Message-ID (diff)
From: Jiri Slaby <jirislaby@gmail.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jiri Slaby <jslaby@suse.cz>,
"Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>,
Linux-pm mailing list <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] PM: cannot hibernate -- BUG at kernel/workqueue.c:3659
Date: Wed, 25 Jan 2012 15:25:29 +0100 [thread overview]
Message-ID: <4F2010D9.5040900@gmail.com> (raw)
In-Reply-To: <201201250110.44360.rjw@sisk.pl>
On 01/25/2012 01:10 AM, Rafael J. Wysocki wrote:
> On Wednesday, January 25, 2012, Jiri Slaby wrote:
>> Yeah, 100%. Just try it with a small enough swap.
>
> Ah, thanks, so that's an error code path problem and most likely in the Linus'
> tree.
Just to emphasize what I wrote earlier. I would apprectiate this fixed
in 3.2 stable too.
--
js
next prev parent reply other threads:[~2012-01-25 14:25 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-24 15:05 PM: cannot hibernate -- BUG at kernel/workqueue.c:3659 Jiri Slaby
2012-01-24 16:18 ` [linux-pm] " Srivatsa S. Bhat
2012-01-24 16:24 ` Jiri Slaby
2012-01-24 16:24 ` [linux-pm] " Jiri Slaby
2012-01-24 22:36 ` Rafael J. Wysocki
2012-01-24 22:36 ` [linux-pm] " Rafael J. Wysocki
2012-01-24 22:47 ` Jiri Slaby
2012-01-24 22:47 ` [linux-pm] " Jiri Slaby
2012-01-24 23:02 ` Rafael J. Wysocki
2012-01-24 23:02 ` [linux-pm] " Rafael J. Wysocki
2012-01-25 0:04 ` Jiri Slaby
2012-01-25 0:04 ` [linux-pm] " Jiri Slaby
2012-01-25 0:10 ` Rafael J. Wysocki
2012-01-25 0:10 ` [linux-pm] " Rafael J. Wysocki
2012-01-25 14:25 ` Jiri Slaby [this message]
2012-01-25 14:25 ` Jiri Slaby
2012-01-25 15:31 ` Srivatsa S. Bhat
2012-01-25 16:00 ` Srivatsa S. Bhat
2012-01-25 18:44 ` Srivatsa S. Bhat
2012-01-25 18:44 ` [linux-pm] " Srivatsa S. Bhat
2012-01-25 23:51 ` Rafael J. Wysocki
2012-01-26 11:05 ` Jiri Slaby
2012-01-27 1:01 ` Rafael J. Wysocki
2012-01-26 19:22 ` Srivatsa S. Bhat
2012-01-27 1:01 ` Rafael J. Wysocki
2012-01-27 10:04 ` Srivatsa S. Bhat
2012-01-27 22:44 ` Rafael J. Wysocki
2012-01-28 15:41 ` Srivatsa S. Bhat
2012-01-29 0:14 ` Rafael J. Wysocki
2012-01-25 22:00 ` Jiri Slaby
2012-01-25 22:00 ` [linux-pm] " Jiri Slaby
2012-01-26 19:39 ` Srivatsa S. Bhat
2012-01-26 19:39 ` [linux-pm] " Srivatsa S. Bhat
2012-01-27 1:10 ` Rafael J. Wysocki
2012-01-27 1:10 ` [linux-pm] " Rafael J. Wysocki
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F2010D9.5040900@gmail.com \
--to=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=srivatsa.bhat@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.