Re: Overruns are killing my recordings.

[William Weston]

On Fri, 28 Oct 2005, Mark Knecht wrote:

> OK then I'll just hang tinght. I've not seen any response on the email
> I sent about 2.6.14-rc5-rt7. I cannot build it. It fails like this:
> 
> CC      arch/x86_64/kernel/sys_x86_64.o
>  CC      arch/x86_64/kernel/x8664_ksyms.o
>  CC      arch/x86_64/kernel/i387.o
>  CC      arch/x86_64/kernel/syscall.o
>  CC      arch/x86_64/kernel/vsyscall.o
> arch/x86_64/kernel/vsyscall.c:57: error: `SEQLOCK_UNLOCKED' undeclared
> here (not in a function)
> make[1]: *** [arch/x86_64/kernel/vsyscall.o] Error 1
> make: *** [arch/x86_64/kernel] Error 2
> lightning linux #
> 
> This is a new failure here since -rc5-rt3.

I don't have a 64 bit machine to test on, but the following patch should 
at least make the compiler happy.  This is the only place outside of 
seqlock.h that SEQLOCK_UNLOCKED is used, btw.

If this kernel gives you the 'BUG in get_monotonic_clock_ts' and 'time
warped' warnings, then you may want to look at the '2.6.14-rc4-rt7' lkml
thread for Steven's patch to fix the false positives.

Cheers,
--ww


--- linux-2.6.14-rc5-rt7/arch/x86_64/kernel/vsyscall.c.orig     2005-10-25 14:20:21.000000000 -0700
+++ linux-2.6.14-rc5-rt7/arch/x86_64/kernel/vsyscall.c  2005-10-28 14:08:37.000000000 -0700
@@ -54,7 +54,7 @@
 struct vsyscall_gtod_data_t __vsyscall_gtod_data __section_vsyscall_gtod_data;
 
 extern seqlock_t vsyscall_gtod_lock;
-seqlock_t __vsyscall_gtod_lock __section_vsyscall_gtod_lock = SEQLOCK_UNLOCKED;
+seqlock_t __vsyscall_gtod_lock __section_vsyscall_gtod_lock = SEQLOCK_UNLOCKED(__section_vsyscall_gtod_lock);
 
 
 #include <asm/unistd.h>

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/