From: sean darcy <seandarcy@hotmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 260t11-bk4 problem -- hung processes
Date: Sun, 07 Dec 2003 15:09:20 -0500 [thread overview]
Message-ID: <3FD388F0.3070205@hotmail.com> (raw)
In-Reply-To: <200312062254.RAA26015@clem.clem-digital.net.lucky.linux.kernel>
Pete Clements wrote:
> With 2.6.0-t11-bk4, mozilla hangs before it can come up.
> At this point other processes that touch the associated
> /proc entries hang also (such as a ps). Can not kill the
> process. Shutdown also hangs.
>
> Everything fine with bk3.
>
Same here.
I can run top. But as soon as I try to start mozilla, top freezes. Other
odd processes hang: the shutdown script for cups hangs; uic from qt
hangs; startkde hangs ( good thing gnome works! ).
bk3 also works for me. From the bk4 changelog, not clear whats the problem
sean
next parent reply other threads:[~2003-12-07 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200312062254.RAA26015@clem.clem-digital.net.lucky.linux.kernel>
2003-12-07 20:09 ` sean darcy [this message]
2003-12-07 20:19 ` 260t11-bk4 problem -- hung processes Zwane Mwaikambo
2003-12-07 22:34 ` David B. Stevens
2003-12-06 22:54 Pete Clements
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=3FD388F0.3070205@hotmail.com \
--to=seandarcy@hotmail.com \
--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