From: Lee Revell <rlrevell@joe-job.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.14-rt13 does not build
Date: Tue, 22 Nov 2005 21:39:51 -0500 [thread overview]
Message-ID: <1132713591.4774.6.camel@mindpipe> (raw)
In-Reply-To: <1132682597.7596.18.camel@mindpipe>
On Tue, 2005-11-22 at 13:03 -0500, Lee Revell wrote:
> On Mon, 2005-11-21 at 20:28 -0500, Lee Revell wrote:
> > I'm trying to work around it by
> > compiling with high res timers even though I don't have the hardware
> > to support them.
>
> Does not with with high res timers enabled either - it boots halfway
> then I just get endless screenfuls of "============================".
>
> Can anyone reproduce the failure to build or boot 2.6.14-rt13 with my
> config?
>
OK I tracked this down. It works as long as CONFIG_KTIME_SCALAR is on.
I tried -rt6 and -rt13 with various combinations of preemption levels
and debugging options and all configs with this unset failed to build or
boot.
Lee
prev parent reply other threads:[~2005-11-23 2:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 18:58 2.6.14-rt13 does not build Lee Revell
2005-11-21 19:19 ` Lee Revell
2005-11-22 1:28 ` Lee Revell
2005-11-22 18:03 ` Lee Revell
2005-11-23 2:39 ` Lee Revell [this message]
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=1132713591.4774.6.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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