From: Karsten Merker <karsten@excalibur.cologne.de>
To: linux-mips@fnet.fr, linux-mips@oss.sgi.com
Subject: Re: process lockups
Date: Tue, 24 Oct 2000 13:15:23 +0200 [thread overview]
Message-ID: <20001024131523.A2431@excalibur.cologne.de> (raw)
In-Reply-To: <200010240551.HAA02069@sparta.research.kpn.com>; from Houten K.H.C. van (Karel) on Tue, Oct 24, 2000 at 07:51:42AM +0200
On Tue, Oct 24, 2000 at 07:51:42AM +0200, Houten K.H.C. van (Karel) wrote:
>
> Ralf Baechle wrote:
[hanging processes in status "D"]
> > I observe similar stuck processes on Origins - even without massive I/O
> > load. I'm trying to track them but little success aside of fixing a few
> > unrelated little bugs. Do you observe those on your R4k box also?
> On my DEC 5000/260 (R4k) I have no stuck processes, but I should mention
> that I am running without swap (I have 192Mb RAM).
Having swap or not does not seem to influence the behaviour - I also get
hangs with swap disabled. Good candidates for hangig are either tar or
gcc.
> > Another things which I'm observing is that I occasinally can't unmount
> > a filesystem. umount then says the fs is still in use. Sometimes it's
> > at least possible to remount the fs r/o. Have you also observed this one?
> Yes, but only the root FS. I thought I might have to upgrade to a newer
> mount program for the 2.4 kernel, or is the system call returning the error?
Similar effect here - sometimes unmounting the root fs on shutdown is
successfull, sometimes I get "/ is busy" without being able to find a
reason for that. Possibly it is a bug in the mount (I am still running
mount-2.9o).
> > > Another thing I see on my 5000/150 (and only there - this is my only
> > > R4K-machine, so I do not know whether this is CPU- or machine-type-bound)
> > > is "top" going weird, eating lots of CPU cycles and spitting messages
> > > "schedule_timeout: wrong timeout value fffbd0b2 from 800900f8; Setting
> > > flush to zero for top". I know Florian also has this on his 5000/150.
> > > Anyone else with the same behavoiur or any idea about the cause for this?
> >
> > Setting flush to zero for <process name> means that the floating point
> > approximator is now enabled ;-)
???
Greetings,
Karsten
--
#include <standard_disclaimer>
Nach Paragraph 28 Abs. 3 Bundesdatenschutzgesetz widerspreche ich der Nutzung
oder Uebermittlung meiner Daten fuer Werbezwecke oder fuer die Markt- oder
Meinungsforschung.
next prev parent reply other threads:[~2000-10-24 11:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-10-24 1:22 process lockups Karsten Merker
2000-10-24 2:47 ` Ralf Baechle
2000-10-24 5:51 ` Houten K.H.C. van (Karel)
2000-10-24 11:15 ` Karsten Merker [this message]
2000-10-24 14:38 ` Ralf Baechle
2000-10-24 17:55 ` Karsten Merker
2000-10-25 1:29 ` Ralf Baechle
2000-10-24 15:09 ` Ralf Baechle
2000-10-24 12:25 ` Florian Lohoff
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=20001024131523.A2431@excalibur.cologne.de \
--to=karsten@excalibur.cologne.de \
--cc=linux-mips@fnet.fr \
--cc=linux-mips@oss.sgi.com \
/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