From: Ralf Baechle <ralf@oss.sgi.com>
To: K.H.C.vanHouten@kpn.com
Cc: linux-mips@fnet.fr, linux-mips@oss.sgi.com,
K.H.C.vanHouten@research.kpn.com
Subject: Re: process lockups
Date: Tue, 24 Oct 2000 16:38:43 +0200 [thread overview]
Message-ID: <20001024163843.A7342@bacchus.dhis.org> (raw)
In-Reply-To: <200010240551.HAA02069@sparta.research.kpn.com>; from K.H.C.vanHouten@research.kpn.com 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:
> > > I am running Kernel 2.4.0-test9 on a DECstation 5000/150. I am
> > > experiencing a strange behaviour when having strong I/O-load, such as
> > > running a "tar xvf foobar.tgz" with a large archive. After some time of
> > > activity the process (in this case tar) is stuck in status "D". There is
> > > neither an entry in the syslog nor on the console that would give me a
> > > hint what is happening. Is anyone else experiencing this?
> >
> > 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).
That matches my Origin experience with it's 1.5gb RAM and no swap.
> > 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?
It also happens for other filesystems; the heavier the usage of the
filesystem has been the more often. But I've never seen a hanging tar or
gcc process.
> Aside from this I stil get 'bug in get_wchan' messages, but everything
> seems to run fine. I hope to test my current kernels on a 5000/150 and
> a 3100.
This message is harmless. The only effect is that the WCHAN column of
ps axl will have bogus information.
Which is a problem - I need exactly the WCHAN information to debug this
problem.
Ralf
next prev parent reply other threads:[~2000-10-24 15:14 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
2000-10-24 14:38 ` Ralf Baechle [this message]
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=20001024163843.A7342@bacchus.dhis.org \
--to=ralf@oss.sgi.com \
--cc=K.H.C.vanHouten@kpn.com \
--cc=K.H.C.vanHouten@research.kpn.com \
--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