From: "Michael H. Warfield" <mhw@wittsend.com>
To: Pierre Rousselet <pierre.rousselet@wanadoo.fr>
Cc: lkml <linux-kernel@vger.kernel.org>,
Tomasz Torcz <zdzichu@irc.pl>,
"Michael H. Warfield" <mhw@wittsend.com>,
Hans-Christian Armingeon <linux.johnny@gmx.net>
Subject: Re: swapper [was OOPS on 2.4.17 ...]
Date: Thu, 17 Jan 2002 15:22:26 -0500 [thread overview]
Message-ID: <20020117152226.A26267@alcove.wittsend.com> (raw)
In-Reply-To: <20020117182758.GA736@irc.pl> <3C472B64.6000206@wanadoo.fr>
In-Reply-To: <3C472B64.6000206@wanadoo.fr>
On Thu, Jan 17, 2002 at 08:52:04PM +0100, Pierre Rousselet wrote:
> Tomasz Torcz wrote:
> > Process swapper (pid: 1, stackpage=c1199000)
> Michael H. Warfield wrote:
> > Process swapper (pid: 0,stackpage=c022f000)
> Hans-Christian Armingeon wrote:
> > Process swapper (pid: 1, stackpage=cfe8d00)
> what is this swapper process involved in 2.4.17 oops ? could it be
> spawned when devfs thinks there is already a root fs mounted at boot
> time before mounting the root fs given to the boot loader ?
It's blowing chunks even without devfs.
But you've pointed out something important. This is a heavily
upgraded RedHat 6.0 system and maybe there are some things which it
is doing which is inappropriate for the 2.4 kernels. I vaguely remember
a problem a while back with swapping and the swapper daemon and some
systems blowing chunks. All my various RedHat systems (6.0, 6.1, 6.2,
and 7.2) are all running kswapd. No "swapper" process, per se. And
init always has "1".
But even if some old application is doing something ill behaved,
that's still a problem since applications should not be capable of causing
such an oops. So that makes two problems, one in user space and one in
kernel space.
But... I've disabled swap on the afflicted system (it's got
enough memory that it damn well should have never swapped anyways). We
shall see what we shall see over the next couple of days.
Good point though...
> Pierre
> --
> ------------------------------------------------
> Pierre Rousselet <pierre.rousselet@wanadoo.fr>
> ------------------------------------------------
Mike
--
Michael H. Warfield | (770) 985-6132 | mhw@WittsEnd.com
/\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/
NIC whois: MHW9 | An optimist believes we live in the best of all
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!
next prev parent reply other threads:[~2002-01-17 20:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-17 18:27 OOPS on 2.4.17 -18pre4 while mounting root (reiserfs, on LVM, devfs) Tomasz Torcz
2002-01-17 18:56 ` Pierre Rousselet
2002-01-17 19:52 ` swapper [was OOPS on 2.4.17 ...] Pierre Rousselet
2002-01-17 20:22 ` Michael H. Warfield [this message]
2002-01-20 20:45 ` OOPS on 2.4.17 -18pre4 while mounting root (reiserfs, on LVM, devfs) Richard Gooch
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=20020117152226.A26267@alcove.wittsend.com \
--to=mhw@wittsend.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.johnny@gmx.net \
--cc=pierre.rousselet@wanadoo.fr \
--cc=zdzichu@irc.pl \
/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®