From: "Alexander Stohr" <Alexander.Stohr@gmx.de>
To: linux-kernel@vger.kernel.org
Subject: [2.6.10-rc1-bk4/i386] app hangs and tasklisk corruption
Date: Mon, 17 Jan 2005 14:35:30 +0100 (MET) [thread overview]
Message-ID: <13732.1105968930@www18.gmx.net> (raw)
Hello,
i am test driving the bitkeeper snapshot from last night
and found strangs application hangs when compling e.g. gcc.
the problem happens with gcc and with the configure scripts.
when getting hung, the application wont respond to ctrl-c
anymore, but can be killed from a separate shell. despite
this temporary success, in the long term the task list gets
increasingly corrupt (like showing wrong users or even tasks
arent existing anymore) so that proceeding gets a mess.
I dont know if todays snapshop will improve anynthing
in that area and i am not sure if i will test that.
the kernel i lasted tested was 2.6.11-rc1-bk1 which
behaved as it should. my testing platform has 2 cpus.
-Alex.
PS: please CC me on replys. (i read the list only via MARC.)
--
GMX im TV ... Die Gedanken sind frei ... Schon gesehen?
Jetzt Spot online ansehen: http://www.gmx.net/de/go/tv-spot
reply other threads:[~2005-01-17 13:35 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=13732.1105968930@www18.gmx.net \
--to=alexander.stohr@gmx.de \
--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