public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* 2.6.14-rt13 does not build
@ 2005-11-21 18:58 Lee Revell
  2005-11-21 19:19 ` Lee Revell
  0 siblings, 1 reply; 5+ messages in thread
From: Lee Revell @ 2005-11-21 18:58 UTC (permalink / raw)
  To: linux-kernel; +Cc: Ingo Molnar

[-- Attachment #1: Type: text/plain, Size: 251 bytes --]

  CC      kernel/ktimers.o
kernel/ktimers.c: In function 'enqueue_ktimer':
kernel/ktimers.c:756: error: incompatible type for argument 1 of
'trace_special_u64'
make[1]: *** [kernel/ktimers.o] Error 1
make: *** [kernel] Error 2

.config attached.

Lee

[-- Attachment #2: config.gz --]
[-- Type: application/x-gzip, Size: 7484 bytes --]

^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.6.14-rt13 does not build
  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
  0 siblings, 1 reply; 5+ messages in thread
From: Lee Revell @ 2005-11-21 19:19 UTC (permalink / raw)
  To: linux-kernel; +Cc: Ingo Molnar

On Mon, 2005-11-21 at 13:58 -0500, Lee Revell wrote:
>   CC      kernel/ktimers.o
> kernel/ktimers.c: In function 'enqueue_ktimer':
> kernel/ktimers.c:756: error: incompatible type for argument 1 of
> 'trace_special_u64'
> make[1]: *** [kernel/ktimers.o] Error 1
> make: *** [kernel] Error 2

The problem is specific to !CONFIG_HIGH_RES_TIMERS.  This seems to fix
it (untested):

--- include/linux/ktimer.h~	2005-11-21 13:43:37.000000000 -0500
+++ include/linux/ktimer.h	2005-11-21 14:10:25.000000000 -0500
@@ -167,7 +167,7 @@
 	return 0;
 }
 
-#define ktimer_trace(a,b)		trace_special_u64(a,b)
+#define ktimer_trace(a,b)		trace_special(ktime_get_high(a),ktime_get_low(a),b)
 
 #endif
 


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.6.14-rt13 does not build
  2005-11-21 19:19 ` Lee Revell
@ 2005-11-22  1:28   ` Lee Revell
  2005-11-22 18:03     ` Lee Revell
  0 siblings, 1 reply; 5+ messages in thread
From: Lee Revell @ 2005-11-22  1:28 UTC (permalink / raw)
  To: linux-kernel; +Cc: Ingo Molnar, Thomas Gleixner

On Mon, 2005-11-21 at 14:19 -0500, Lee Revell wrote:
> On Mon, 2005-11-21 at 13:58 -0500, Lee Revell wrote:
> >   CC      kernel/ktimers.o
> > kernel/ktimers.c: In function 'enqueue_ktimer':
> > kernel/ktimers.c:756: error: incompatible type for argument 1 of
> > 'trace_special_u64'
> > make[1]: *** [kernel/ktimers.o] Error 1
> > make: *** [kernel] Error 2
> 
> The problem is specific to !CONFIG_HIGH_RES_TIMERS.  This seems to fix
> it (untested):
> 
> -#define ktimer_trace(a,b)		trace_special_u64(a,b)
> +#define ktimer_trace(a,b)		trace_special(ktime_get_high(a),ktime_get_low(a),b)

No good, this double faults on boot.  I'm trying to work around it by
compiling with high res timers even though I don't have the hardware to
support them.

Lee


^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.6.14-rt13 does not build
  2005-11-22  1:28   ` Lee Revell
@ 2005-11-22 18:03     ` Lee Revell
  2005-11-23  2:39       ` Lee Revell
  0 siblings, 1 reply; 5+ messages in thread
From: Lee Revell @ 2005-11-22 18:03 UTC (permalink / raw)
  To: linux-kernel; +Cc: Ingo Molnar, Thomas Gleixner

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?

Lee




^ permalink raw reply	[flat|nested] 5+ messages in thread

* Re: 2.6.14-rt13 does not build
  2005-11-22 18:03     ` Lee Revell
@ 2005-11-23  2:39       ` Lee Revell
  0 siblings, 0 replies; 5+ messages in thread
From: Lee Revell @ 2005-11-23  2:39 UTC (permalink / raw)
  To: linux-kernel; +Cc: Ingo Molnar, Thomas Gleixner

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


^ permalink raw reply	[flat|nested] 5+ messages in thread

end of thread, other threads:[~2005-11-23  2:40 UTC | newest]

Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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 is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox