From: dan carpenter <error27@email.com>
To: Ingo Molnar <mingo@elte.hu>, Linus Torvalds <torvalds@osdl.org>
Cc: Petr Vandrovec <vandrove@vc.cvut.cz>,
Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@zip.com.au>,
Roland McGrath <roland@redhat.com>
Subject: Re: [patch] Re: Problem with exiting threads under NPTL
Date: Sun, 14 Dec 2003 22:31:02 -0800 [thread overview]
Message-ID: <200312142230.20952.error27@email.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0312142358210.16392@earth>
I'm running the patch from BK and I still get unkillable zombies. I'm running
strace on these processes and I don't know if that makes a difference.
Basically, my program is a modified strace that calls the syscalls as well as
printing it out... (I'm trying to test the kernel with bogus syscalls).
When I hit ALT-SYSREQ-T most of the zombie processes look like this.
msgctl09 Z 9FF99D73 0 1503 1465 1505 1500 (L-TLB)
c9fc9f68 00000046 c88b49b0 9ff99d73 00000258 c81cea08 c9fc9f68 c012a65b
c81ce9b0 00000011 9ff99d73 00000258 c88b49b0 c11e5bc0 000734f9 a150a7ac
00000258 c81ce9b0 cbfa7f38 c81cefc4 cbfe8850 00000000 c81ce9b0 c9fc9f90
Call Trace:
[<c012a65b>] exit_notify+0x2eb/0x900
[<c012b08f>] do_exit+0x41f/0x5c0
[<c012b3d7>] do_group_exit+0x107/0x190
[<c010aa8f>] syscall_call+0x7/0xb
There are some process that are stuck but not in zombie state that look like
this.
mknod09 T 00000001 0 1403 1 1420 1394 (NOTLB)
c73adf80 00000082 c11e5bc0 00000001 00000001 c2e91c28 cbfa3f38 858434c0
00000256 c35529b0 c11e5bc0 00000ebe 85843808 c11e5bc0 000004c0 858731ea
00000256 c62c39b0 08053000 c73ac000 c73ac000 08053000 c73ac000 c73adfa4
Call Trace:
[<c0131209>] ptrace_notify+0x49/0xf6
[<c015c4ac>] sys_brk+0x2c/0x130
[<c0110cf8>] do_syscall_trace+0x48/0x73
[<c010ab01>] syscall_trace_entry+0x11/0x24
The CPU usage is normal.
thanks,
dan carpenter
next prev parent reply other threads:[~2003-12-15 9:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-14 5:25 Problem with exiting threads under NPTL Petr Vandrovec
2003-12-14 15:02 ` Martin Schlemmer
2003-12-14 19:38 ` [patch] " Ingo Molnar
2003-12-14 20:38 ` Linus Torvalds
2003-12-14 20:45 ` Linus Torvalds
2003-12-14 21:02 ` Ingo Molnar
2003-12-15 15:04 ` Jörn Engel
2003-12-14 21:06 ` Ingo Molnar
2003-12-14 22:10 ` Linus Torvalds
2003-12-14 22:17 ` Ingo Molnar
2003-12-14 22:32 ` Linus Torvalds
2003-12-15 23:04 ` Roland McGrath
2003-12-14 22:28 ` Ingo Molnar
2003-12-14 22:45 ` Linus Torvalds
2003-12-14 23:08 ` Ingo Molnar
2003-12-15 6:31 ` dan carpenter [this message]
2003-12-15 11:43 ` Ingo Molnar
2003-12-15 13:07 ` dan carpenter
2003-12-15 15:11 ` Linus Torvalds
2003-12-15 23:15 ` Roland McGrath
2003-12-15 8:54 ` Arjan van de Ven
2003-12-15 22:55 ` Roland McGrath
2003-12-15 23:06 ` Roland McGrath
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=200312142230.20952.error27@email.com \
--to=error27@email.com \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=roland@redhat.com \
--cc=torvalds@osdl.org \
--cc=vandrove@vc.cvut.cz \
/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.