From: Robert Love <rml@ufl.edu>
To: Steve Kieu <haiquy@yahoo.com>
Cc: kernel <linux-kernel@vger.kernel.org>
Subject: Re: Preempt kernel and mc issue?
Date: 23 Sep 2001 22:05:25 -0400 [thread overview]
Message-ID: <1001297131.8416.9.camel@phantasy> (raw)
In-Reply-To: <20010924015137.659.qmail@web10408.mail.yahoo.com>
In-Reply-To: <20010924015137.659.qmail@web10408.mail.yahoo.com>
On Sun, 2001-09-23 at 21:51, Steve Kieu wrote:
> I got randomly mc hang with preempt enabled kernel.
> How could it possibly be?
>
> Kernel 2.4.10-pre15 and it happened both in light load
> and heavy load. Anyway I have not tested this kernel
> without preempt yet, so I can not say it is because
> preempt feature but it is likely to be . Under heavy
> load all other programms behaves so well !
Try this patch
http://tech9.net/rml/linux/patch-rml-2.4.10-preempt-ptrace-and-jobs-fix-2
It has not been merged into the 2.4.10-pre15 patch. Please report back
if it fixes your issue.
--
Robert M. Love
rml at ufl.edu
rml at tech9.net
next prev parent reply other threads:[~2001-09-24 2:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-24 1:51 Preempt kernel and mc issue? Steve Kieu
2001-09-24 2:05 ` Robert Love [this message]
2001-09-24 6:07 ` Steve Kieu
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=1001297131.8416.9.camel@phantasy \
--to=rml@ufl.edu \
--cc=haiquy@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/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