From: Pavel Machek <pavel@ucw.cz>
To: Christoph Lameter <christoph@lameter.com>
Cc: akpm@osdl.org, torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] Task notifier: Implement todo list in task_struct
Date: Thu, 28 Jul 2005 23:32:54 +0200 [thread overview]
Message-ID: <20050728213254.GA1844@elf.ucw.cz> (raw)
In-Reply-To: <20050728212715.GA2783@elf.ucw.cz>
Hi!
> > Introduce a todo notifier in the task_struct so that a task can be told to do
> > certain things. Abuse the suspend hooks try_to_freeze, freezing and refrigerator
> > to establish checkpoints where the todo list is processed. This will break software
> > suspend (next patch fixes and cleans up software suspend).
>
> Ugh, this conflicts with stuff in -mm tree rather badly... In part
> thanks to patch by you that was already applied.
>
> I fixed up rejects manually (but probably lost fix or two in
> progress), and will test.
>
> Uff, and then it breaks suspend completely:
>
> Jul 28 23:21:12 amd kernel: Stopping tasks:
> =====================================Restarting tasks...khpsbpkt:
> received unexpected signal?!
> Jul 28 23:21:12 amd kernel: NodeMgr: received unexpected signal?!
> Jul 28 23:21:22 amd kernel: done
> Jul 28 23:21:32 amd pam_limits[1547]: wrong limit value 'unlimited'
>
> (Left me with basically all kernel threads going crazy:)
>
> top - 23:22:34 up 3 min, 4 users, load average: 5.10, 1.90, 0.69
> Tasks: 48 total, 2 running, 46 sleeping, 0 stopped, 0 zombie
> Cpu(s): 0.0% us, 100.0% sy, 0.0% ni, 0.0% id, 0.0% wa, 0.0% hi,
> 0.0% si
> Mem: 2064480k total, 155664k used, 1908816k free, 10280k
> buffers
> Swap: 2136448k total, 0k used, 2136448k free, 114624k
> cached
>
> PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
> 273 root 25 0 0 0 0 S 21.1 0.0 0:11.24 kswapd0
> 938 root 25 0 0 0 0 S 21.1 0.0 0:11.24 pccardd
> 940 root 25 0 0 0 0 S 21.1 0.0 0:11.30 pccardd
> 1060 root 25 0 0 0 0 R 21.1 0.0 0:21.34 kjournald
> 1409 root 25 0 0 0 0 S 17.3 0.0 0:19.71 kjournald
>
> You are doing rather intrusive changes. Is testing them too much to
> ask? I'm pretty sure you can get i386 machine to test swsusp on...
(And yes, I did apply the whole series. It would be nice if next
series was relative to -mm, it already contains some of your changes).
Pavel
--
teflon -- maybe it is a trademark, but it should not be.
next prev parent reply other threads:[~2005-07-28 21:35 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200507260340.j6Q3eoGh029135@shell0.pdx.osdl.net>
2005-07-28 3:30 ` Alternative to TIF_FREEZE -> a notifier in the task_struct? Christoph Lameter
2005-07-28 7:41 ` Pavel Machek
2005-07-28 15:05 ` Christoph Lameter
2005-07-28 19:34 ` Pavel Machek
2005-07-28 19:49 ` Christoph Lameter
2005-07-28 19:54 ` [PATCH 1/4] Task notifier: Allow the removal of a notifier from the notifier handler Christoph Lameter
2005-07-28 19:55 ` [PATCH 2/4] Task notifier: Implement todo list in task_struct Christoph Lameter
2005-07-28 19:57 ` [PATCH 3/4] Task notifier: Make suspend code SMP safe using the todo list in the task struct Christoph Lameter
2005-07-28 19:59 ` [PATCH 4/4] Task notifier: s/try_to_freeze/try_todo_list/ in some drivers [optional] Christoph Lameter
2005-07-28 21:27 ` [PATCH 2/4] Task notifier: Implement todo list in task_struct Pavel Machek
2005-07-28 21:32 ` Pavel Machek [this message]
2005-07-28 21:57 ` Christoph Lameter
2005-07-28 22:12 ` Pavel Machek
2005-07-28 23:02 ` Christoph Lameter
2005-07-28 23:27 ` Andrew Morton
2005-07-29 0:19 ` Christoph Lameter
2005-08-09 1:32 ` Nigel Cunningham
2005-08-09 2:01 ` Christoph Lameter
2005-08-09 3:51 ` Nigel Cunningham
2005-08-09 4:21 ` Nigel Cunningham
2005-08-09 17:05 ` Christoph Lameter
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=20050728213254.GA1844@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=christoph@lameter.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox