From: William Weston <weston@lysdexia.org>
To: Mark Knecht <markknecht@gmail.com>
Cc: Lee Revell <rlrevell@joe-job.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: Overruns are killing my recordings.
Date: Fri, 28 Oct 2005 14:15:00 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0510281403410.26693@echo.lysdexia.org> (raw)
In-Reply-To: <5bdc1c8b0510281155w2b86be0bp9f85de02b806d664@mail.gmail.com>
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>
next prev parent reply other threads:[~2005-10-28 21:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-27 19:12 Avuton Olrich
[not found] ` <200510271528.28919.diablod3@gmail.com>
2005-10-27 19:57 ` Avuton Olrich
2005-10-27 21:06 ` Lee Revell
2005-10-28 0:00 ` Avuton Olrich
2005-10-28 3:40 ` Lee Revell
2005-10-28 14:52 ` Mark Knecht
2005-10-28 18:43 ` Lee Revell
2005-10-28 18:55 ` Mark Knecht
2005-10-28 21:15 ` William Weston [this message]
2005-10-28 23:07 ` Mark Knecht
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=Pine.LNX.4.58.0510281403410.26693@echo.lysdexia.org \
--to=weston@lysdexia.org \
--cc=linux-kernel@vger.kernel.org \
--cc=markknecht@gmail.com \
--cc=rlrevell@joe-job.com \
/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
all inboxes | Powered by JetHome®