From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Pavel Machek <pavel@ucw.cz>, Ben Collins <ben.collins@ubuntu.com>,
kernel list <linux-kernel@vger.kernel.org>,
linux1394-devel@lists.sourceforge.net,
Ingo Molnar <mingo@elte.hu>
Subject: Re: regression: fireware causes oops during system
Date: Sun, 16 Sep 2007 21:58:08 +0200 [thread overview]
Message-ID: <46ED8AD0.2040004@s5r6.in-berlin.de> (raw)
In-Reply-To: <200709162152.24793.rjw@sisk.pl>
Rafael J. Wysocki wrote:
>> Pavel Machek wrote:
>>> commit 831441862956fffa17b9801db37e6ea1650b0f69
>>> tree b0334921341f8f1734bdd3243de76d676329d21c
>>> parent 787d2214c19bcc9b6ac48af0ce098277a801eded
>>> author Rafael J. Wysocki <rjw@sisk.pl> Tue, 17 Jul 2007 04:03:35 -0700
>>> committer Linus Torvalds <torvalds@woody.linux-foundation.org> Tue, 17
>>> Jul 2007 10:23:02 -0700
>>>
>>> Freezer: make kernel threads nonfreezable by default
>
> Well, I don't think so.
>
> nodemgr_host_thread() calls set_freezable() as it should.
This commit is certainly OK, as it should merely preserve status quo.
Also note that Pavel wrote in his initial post that the problem became
apparent way after -rc1. Full quote:
| I noticed empty suspend stopped working around 2.6.23-rc4, and it is
| still present in 2.6.23-rc6. To reproduce
|
| swapoff -a
| echo disk > /sys/power/state
| echo disk > /sys/power/state
|
| Unsetting
|
| CONFIG_IEEE1394=y
|
| solves the problem.
--
Stefan Richter
-=====-=-=== =--= =----
http://arcgraph.de/sr/
next prev parent reply other threads:[~2007-09-16 19:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-11 19:00 regression: fireware causes oops during system Pavel Machek
2007-09-11 19:08 ` Ben Collins
2007-09-11 19:29 ` Stefan Richter
2007-09-11 19:45 ` Stefan Richter
2007-09-16 17:54 ` Pavel Machek
2007-09-16 18:41 ` Stefan Richter
2007-09-16 19:52 ` Rafael J. Wysocki
2007-09-16 19:58 ` Stefan Richter [this message]
2007-09-16 20:16 ` Rafael J. Wysocki
2007-10-05 7:08 ` Pavel Machek
2007-10-05 21:28 ` Rafael J. Wysocki
2007-09-16 17:57 ` Pavel Machek
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=46ED8AD0.2040004@s5r6.in-berlin.de \
--to=stefanr@s5r6.in-berlin.de \
--cc=ben.collins@ubuntu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--cc=mingo@elte.hu \
--cc=pavel@ucw.cz \
--cc=rjw@sisk.pl \
/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.