From: FORT David <popo.enlighted@free.fr>
To: Peter Zaitsev <pz@spylog.ru>
Cc: Anton Petrusevich <casus@mail.ru>, linux-kernel@vger.kernel.org
Subject: Re: threads & /proc
Date: Mon, 26 Nov 2001 00:46:31 -0500 [thread overview]
Message-ID: <3C01D737.5020308@free.fr> (raw)
In-Reply-To: <20011123233857.A25084@casus.tx> <97219676688.20011124111155@spylog.ru>
Peter Zaitsev wrote:
>Hello Anton,
>
>Saturday, November 24, 2001, 8:38:57 AM, you wrote:
>
>
>I would confirm the problem exists from the first 2.4.x kernels. Also
>programs "w","vmstat","snmpd" hangs. It seems to happen both for
>UP/SMP kernels. I have seen this only on High Memory (1-2G), therefore
>I do not have much low memory machines loaded. The workload seems to
>be the thing to affect this - I do not remember any hang on low VM
>load system (for example Web Server) therefore it's offen happens
>then there are a lot of I/O and swapping goes (i.e Mysql Server).
>Often this happens after appearing some of new __order allocation
>failed errors.
>
>
>
>
>Other issue which looks like connected to this - a thread hangs in
>"D" state forever and it's unable to be killed in this case even
>reboot -f does not work.
>
>AP> Hi Guys,
>
>AP> Well, I'm a bit surprised that nobody asked it yet. Do we have sound
>AP> thread support? I am able to put my linux-2.4.15-pre{1,7} --
>AP> definitely, and if I remember right, 2.4.14-pre{7,8} too in some strange
>AP> state, when any program like top, killall or ps that wanna get some
>AP> information from /proc (even midnight commander if you are trying to
>AP> look at state of any process) blocks indefinitely. It goes to unclean
>AP> shutdown, for example. kill doesn block, but do nothing. (I tried to
>AP> kill processes from ls /proc list). And I see it only after several
>AP> [unsuccessful] runs of my multithreaded program. Well, I can't say
>AP> it's a correctly written program, I am still looking for bugs there.
>AP> I don't have 100% way to get into this state, but I suspect some locking
>AP> issues with /proc.
>
>
>
I've also seen the case on a UP, ps was locking. And i had launched a
lot of multi-threaded processes(but i don't know if it's related).
I can had that i had also launched a lot of gdb on the multi-threaded
program. The program i was debugging is forking a process in a thread
that dies after the fork.
--
%--LINUX-HTTPD-PIOGENE----------------------------------------------------%
% -datamining <-/ | .~. %
% -networking/PHP/java/JSPs | /V\ L I N U X %
% -opensource | // \\ >Fear the Penguin< %
% -GNOME/enlightenment/GIMP | /( )\ %
% feel enlightened.... | ^^-^^ %
% HomePage: http://www.enlightened-popo.net %
%---------- -- This was sent by Djinn running Linux 2.4.13 -- ------------%
next prev parent reply other threads:[~2001-11-25 23:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-24 5:38 threads & /proc Anton Petrusevich
2001-11-24 6:19 ` Andrew Morton
2001-11-24 8:11 ` Peter Zaitsev
2001-11-26 5:46 ` FORT David [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-28 0:18 Luke
2001-11-28 10:08 ` Luigi Genoni
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=3C01D737.5020308@free.fr \
--to=popo.enlighted@free.fr \
--cc=casus@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=pz@spylog.ru \
/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