From: Chris Rankin <rankinc@pacbell.net>
To: thecrown@softhome.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: on exit xterm totally wrecks linux 2.4.11 to 2.4.14-pre6 (unkillable processes)
Date: Thu, 01 Nov 2001 22:16:19 -0800 [thread overview]
Message-ID: <3BE23A33.7080001@pacbell.net> (raw)
Hi,
I see something similar with vanilla 2.4.13 (+devfs), except my
unkillable xterms don't appear until a modprobe has already failed.
Specifically, what seems to happen is:
- an open() call causes the kernel to grab the devfs rwsem for reading,
and then load a module (e.g. ide-cd).
- the modprobe process then waits forever for write-access to the devfs
rwsem.
Each xterm then waits forever in "wait_for_devfsd_finished()",
presumably when it tries to close its terminal.
Are you also using dynamic module loading? Are ALL of your unkillable
processes xterms, or do you also have a failed modprobe lurking somewhere?
Chris
next reply other threads:[~2001-11-02 10:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-02 6:16 Chris Rankin [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-11-01 16:25 on exit xterm totally wrecks linux 2.4.11 to 2.4.14-pre6 (unkillable processes) Ricardo Martins
2001-11-01 19:05 ` Pierre Rousselet
2001-11-01 19:19 ` Ricardo Martins
2001-11-01 19:31 ` Pierre Rousselet
2001-11-01 19:44 ` Nick LeRoy
2001-11-01 20:00 ` Pierre Rousselet
2001-11-01 20:06 ` Nick LeRoy
2001-11-01 20:13 ` Jeffrey W. Baker
2001-11-01 20:35 ` Nick LeRoy
2001-11-01 20:40 ` Rik van Riel
2001-11-01 21:34 ` Richard Gooch
2001-11-02 3:41 ` David Ford
2001-11-01 20:42 ` Brian Gerst
2001-11-09 1:17 ` Dr. Kelsey Hudson
2001-11-01 19:47 ` Ricardo Martins
2001-11-01 19:58 ` Per Lidén
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=3BE23A33.7080001@pacbell.net \
--to=rankinc@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
--cc=thecrown@softhome.net \
/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