Skip to contentSkip to conversation

2.6.14-rt13 does not build

DISCUSSION Lee Revell 1 participant 5 messages Nov 21, 2005 – Nov 23, 2005

lore
Share & tools
lore

Lee Revell

author
#0 lore raw

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

author
#1 lore raw
Quoted 6 lines · Lee Revell

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):

linux/ktimer.h renamed from linux/ktimer.h~ +1 -1
@@ -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
 
author
#2 lore raw

linux/ktimer.h line 170

Quoted 13 lines · Lee Revell
Quoted 6 lines · Lee Revell

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):

linux/ktimer.h renamed from linux/ktimer.h~ +1 -1
-#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

author
#3 lore raw
Quoted 3 lines · Lee Revell

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

author
#4 lore raw
Quoted 11 lines · Lee Revell
Quoted 3 lines · Lee Revell

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