From: Jeff Garzik <jgarzik@pobox.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Ricky Beam <jfbeam@bluetronic.net>,
Zilvinas Valinskas <zilvinas@gemtek.lt>,
Erik Tews <erik@debian.franken.de>,
linux-kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.9 rc2 freezing
Date: Wed, 15 Sep 2004 11:58:09 -0400 [thread overview]
Message-ID: <41486691.3080202@pobox.com> (raw)
In-Reply-To: <1095263296.2406.141.camel@krustophenia.net>
Lee Revell wrote:
> On Wed, 2004-09-15 at 10:55, Ricky Beam wrote:
>
>>On Wed, 15 Sep 2004, Zilvinas Valinskas wrote:
>>
>>>Perhaps that is mixture of PREEMPT=y and ipsec ? dunno ...
>>
>>No mixture necessary. PREEMPT is uber-screwed up. Try rebuilding your
>>kernel/modules with it disabled. (make clean first; the kernel deps don't
>>track CONFIG_PREEMPT correctly.)
>
>
> Um, PREEMPT works just fine. Anything that breaks on PREEMPT will also
> break on SMP. And the kernel deps do track CONFIG_PREEMPT correctly.
PREEMPT is a hack. I do not recommend using it on production servers.
Jeff
next prev parent reply other threads:[~2004-09-15 16:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-13 16:55 2.6.9 rc2 freezing Zilvinas Valinskas
2004-09-13 17:12 ` Jeff Garzik
2004-09-13 17:16 ` Zilvinas Valinskas
2004-09-15 8:25 ` Erik Tews
2004-09-15 9:58 ` Zilvinas Valinskas
2004-09-15 14:55 ` Ricky Beam
2004-09-15 15:48 ` Lee Revell
2004-09-15 15:58 ` Jeff Garzik [this message]
2004-09-15 16:06 ` Lee Revell
2004-09-15 16:11 ` Jeff Garzik
2004-09-15 16:58 ` Ricky Beam
2004-09-15 17:49 ` Lee Revell
2004-09-15 17:52 ` Jeff Garzik
2004-09-15 17:59 ` Lee Revell
2004-09-16 8:39 ` Helge Hafting
2004-09-17 8:05 ` Zilvinas Valinskas
2004-09-17 13:21 ` Zilvinas Valinskas
2004-09-15 16:59 ` Dave Jones
2004-09-13 17:19 ` Zilvinas Valinskas
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=41486691.3080202@pobox.com \
--to=jgarzik@pobox.com \
--cc=erik@debian.franken.de \
--cc=jfbeam@bluetronic.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=zilvinas@gemtek.lt \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.