From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-acpi@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: 2.6.17-mm3: swsusp fails when process is debugged by ptrace
Date: Wed, 28 Jun 2006 10:17:35 -0700 [thread overview]
Message-ID: <44A2B9AF.50803@goop.org> (raw)
If I try to suspend the machine while a process debug-stopped by ptrace,
suspend fails:
PM: Preparing system for mem sleep
Freezing cpus ...
Breaking affinity for irq 0
Breaking affinity for irq 1
Breaking affinity for irq 12
Breaking affinity for irq 23
CPU 1 is now offline
SMP alternatives: switching to UP code
CPU1 is down
Stopping tasks: ==========================================================================================================================================================
stopping tasks timed out after 20 seconds (13 tasks remaining):
khubd
kseriod
pdflush
pdflush
kswapd0
kprefetchd
pccardd
kirqd
kjournald
kauditd
knodemgrd_0
kjournald
test-vsnprintf
Restarting tasks...<6> Strange, khubd not stopped
Strange, kseriod not stopped
Strange, pdflush not stopped
Strange, pdflush not stopped
Strange, kswapd0 not stopped
Strange, kprefetchd not stopped
Strange, pccardd not stopped
Strange, kirqd not stopped
Strange, kjournald not stopped
Strange, kauditd not stopped
Strange, knodemgrd_0 not stopped
Strange, kjournald not stopped
Strange, test-vsnprintf not stopped
done
Thawing cpus ...
In this case, test-vsnprintf is stopped in a breakpoint in gdb. If I
quit it, then suspend works as expected.
J
next reply other threads:[~2006-06-28 17:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 17:17 Jeremy Fitzhardinge [this message]
2006-06-28 21:26 ` 2.6.17-mm3: swsusp fails when process is debugged by ptrace Pavel Machek
2006-06-28 21:52 ` Jeremy Fitzhardinge
2006-07-03 21:33 ` Pavel Machek
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=44A2B9AF.50803@goop.org \
--to=jeremy@goop.org \
--cc=akpm@osdl.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