From: Mike Fedyk <mfedyk@matchmail.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>, Robert Love <rml@tech9.net>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] preempt-kernel on 2.4.19-pre2-ac2 bugfix
Date: Sat, 9 Mar 2002 15:35:03 -0800 [thread overview]
Message-ID: <20020309233503.GE896@matchmail.com> (raw)
In-Reply-To: <20020308022751.GF28141@matchmail.com> <E16jKJX-00069s-00@the-village.bc.nu> <20020308192643.GA29073@matchmail.com>
In-Reply-To: <20020308192643.GA29073@matchmail.com>
On Fri, Mar 08, 2002 at 11:26:43AM -0800, Mike Fedyk wrote:
> I'll test without preempt and see if it shows up again. It took a day
> before though, so...
>
I've been running without preempt for about 28hrs with a make -j5 compile
loop of a kernel tree running, and it looks like it'll do the same thing
again.
Maybe it's from all of the forks as the only things that have been in use are:
mutt (left running, so scanning for new messages in several folders)
exim (receiving message for lkml, debian-(devel|user), etc
top
make -j loop
Mozilla is running, but I haven't been using it...
I'll change to single user mode in monday to check to see if the problem is
reproducable on non-preempt.
The only thing left would be the kernel or glibc (as init still keeps it
open so 'shutdown now' wouldn't free that).
How could I test to kill everything opening glibc and still be able to run a
command to read /proc/meminfo afterward?
Mike
next prev parent reply other threads:[~2002-03-09 23:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 0:23 [PATCH] preempt-kernel on 2.4.19-pre2-ac2 bugfix Robert Love
2002-03-05 0:41 ` Mike Fedyk
2002-03-05 0:52 ` Robert Love
2002-03-07 23:21 ` Mike Fedyk
2002-03-07 23:46 ` Alan Cox
2002-03-08 0:05 ` Mike Fedyk
2002-03-08 0:38 ` Alan Cox
2002-03-08 2:27 ` Mike Fedyk
2002-03-08 13:21 ` Alan Cox
2002-03-08 19:26 ` Mike Fedyk
2002-03-09 23:35 ` Mike Fedyk [this message]
2002-03-10 0:53 ` Alan Cox
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=20020309233503.GE896@matchmail.com \
--to=mfedyk@matchmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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