From: Roger Larsson <roger.larsson@norran.net>
To: Roy Sigurd Karlsbakk <roy@karlsbakk.net>, Jens Axboe <axboe@suse.de>
Cc: Andrew Morton <akpm@zip.com.au>, <linux-kernel@vger.kernel.org>,
Tux mailing list <tux-list@redhat.com>
Subject: Re: Errors in the VM - detailed (or is it Tux? or rmap? or those together...)
Date: Sat, 2 Feb 2002 16:31:59 +0100 [thread overview]
Message-ID: <200202021535.g12FZ1417639@mailb.telia.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0202021619050.10720-200000@mustard.heime.net>
In-Reply-To: <Pine.LNX.4.30.0202021619050.10720-200000@mustard.heime.net>
On Saturdayen den 2 February 2002 16.22, Roy Sigurd Karlsbakk wrote:
> > > Problem #2 is _the_ worst problem, as it makes the server more-or-less
> > > unusable
> >
> > Please send sysrq-t traces for such stuck processes. It's _impossible_
> > to guess whats going on from here, the crystal ball just isn't good
> > enough :-)
>
> Decoded sysrq+t is attached.
>
> I've found only the first 60 wget processes started from the remote
> machine is being serviced. After they are done, Tux hangs, using 100%
> system time, still open on port ## (80), but doesn't do anything.
>
> I don't understand anything...
I have reread the first mail in this series - I would say that Bug#2 is much
worse than Bug#1. This since Bug#1 is "only" a performance problem,
but Bug#2 is about correctness...
Are you 100% sure that tux works with rmap?
I would suggest testing the simplest possible case.
* Standard kernel
* concurrent dd:s
What can your problem be:
* something to do with the VM - but the problem is in several different VMs...
* something to do with read ahead? you got some patch suggestions -
please use them on a standard kernel, not rmap (for now...)
/RogerL
--
Roger Larsson
Skellefteå
Sweden
next prev parent reply other threads:[~2002-02-02 15:35 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-31 15:05 Errors in the VM - detailed Roy Sigurd Karlsbakk
2002-01-31 15:44 ` David Mansfield
2002-01-31 20:21 ` Roger Larsson
2002-01-31 20:29 ` Jens Axboe
2002-01-31 20:43 ` Andrew Morton
2002-01-31 21:37 ` Jens Axboe
2002-02-01 16:05 ` Roy Sigurd Karlsbakk
2002-02-01 16:11 ` Roy Sigurd Karlsbakk
2002-02-01 18:44 ` Roger Larsson
2002-02-01 18:52 ` Roger Larsson
2002-02-01 18:57 ` Jens Axboe
2002-02-02 14:52 ` Roy Sigurd Karlsbakk
2002-02-02 14:43 ` Roy Sigurd Karlsbakk
2002-02-02 14:43 ` Roy Sigurd Karlsbakk
2002-02-02 14:44 ` Jens Axboe
2002-02-02 15:03 ` Roy Sigurd Karlsbakk
2002-02-02 15:06 ` Jens Axboe
2002-02-02 15:22 ` Errors in the VM - detailed (or is it Tux?) Roy Sigurd Karlsbakk
2002-02-02 15:31 ` Roger Larsson [this message]
2002-02-02 15:38 ` Errors in the VM - detailed (or is it Tux? or rmap? or those together...) Roy Sigurd Karlsbakk
2002-02-02 16:24 ` Roger Larsson
2002-02-02 16:39 ` Roy Sigurd Karlsbakk
2002-02-02 16:52 ` Roy Sigurd Karlsbakk
2002-02-02 17:29 ` Roger Larsson
2002-02-02 17:45 ` Errors in the VM - detailed Roy Sigurd Karlsbakk
2002-02-01 17:39 ` Denis Vlasenko
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=200202021535.g12FZ1417639@mailb.telia.com \
--to=roger.larsson@norran.net \
--cc=akpm@zip.com.au \
--cc=axboe@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=roy@karlsbakk.net \
--cc=tux-list@redhat.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
all inboxes | Powered by JetHome®