public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-acpi@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.17-mm3: swsusp fails when process is debugged by ptrace
Date: Mon, 3 Jul 2006 23:33:53 +0200	[thread overview]
Message-ID: <20060703213353.GC1674@elf.ucw.cz> (raw)
In-Reply-To: <44A2FA20.3020809@goop.org>

Hi!

> >Does it also happen when you do strace? ...I remember trying to solve
> >that, but 2.6.17-mm3 is very recent...?
> 
> I could suspend while running "strace sleep 100" without any problem.
> 
> I think the issue is when the process is blocked in T state,
> freeze_process() tries to kick the process with signal_wake_up(p, /*
> resume=0 */ 0), but with resume=0 it will only wake processes in
> TASK_INTERRUPTIBLE state.  With resume=1, it will also kick STOPPED and
> TRACED processes.  I also tried suspending while I had a process in T
> state caused by kill -STOP, and that worked, so some part of the puzzle
> is still missing.

So... does signal_wake_up(p, 1) fix it?

> I noticed that when I ran sleep 100 under strace over the suspend/resume
> cycle, its nanosleep() syscall was interrupted and not restarted.

I'm afraid there may be more problems lurking in the refrigerator.

(If this is going to take more than few mail iterations... perhaps you
should start bug at bugzilla.kernel.org?)
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2006-07-03 21:34 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-28 17:17 2.6.17-mm3: swsusp fails when process is debugged by ptrace Jeremy Fitzhardinge
2006-06-28 21:26 ` Pavel Machek
2006-06-28 21:52   ` Jeremy Fitzhardinge
2006-07-03 21:33     ` Pavel Machek [this message]
2006-07-03 21:54       ` Jeremy Fitzhardinge

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=20060703213353.GC1674@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=jeremy@goop.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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