Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
`make dep' with clock skew detected loops forever
19 views
Skip to first unread message
Nishanth Aravamudan
Feb 29, 2012, 2:10:03 PM2/29/12
to
Noticed something on a fresh FC16 based install on a test server in our
lab. Autotest by default runs `make dep` and it seems the clock is
pretty badly skewed on this server, resulting in an infinite loop of:
01:09:37 DEBUG| Running 'make dep'
01:09:38 DEBUG| [stderr] make: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112143 s in the future
01:09:38 DEBUG| [stderr] make[1]: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112143 s in the future
01:09:38 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112143 s in the future
01:09:38 DEBUG| [stdout] HOSTCC scripts/basic/fixdep
01:09:38 DEBUG| [stderr] make[2]: warning: Clock skew detected. Your build may be incomplete.
01:09:38 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112143 s in the future
01:09:38 DEBUG| [stdout] HOSTCC scripts/kconfig/conf.o
01:09:38 DEBUG| [stdout] SHIPPED scripts/kconfig/zconf.tab.c
01:09:38 DEBUG| [stdout] SHIPPED scripts/kconfig/zconf.lex.c
01:09:38 DEBUG| [stdout] SHIPPED scripts/kconfig/zconf.hash.c
01:09:39 DEBUG| [stdout] HOSTCC scripts/kconfig/zconf.tab.o
01:09:39 DEBUG| [stdout] HOSTLD scripts/kconfig/conf
01:09:39 DEBUG| [stdout] scripts/kconfig/conf --silentoldconfig Kconfig
01:09:39 DEBUG| [stderr] make[2]: warning: Clock skew detected. Your build may be incomplete.
01:09:39 DEBUG| [stderr] make[1]: warning: Clock skew detected. Your build may be incomplete.
01:09:39 DEBUG| [stderr] make: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112142 s in the future
01:09:39 DEBUG| [stderr] make[1]: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112142 s in the future
01:09:39 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112142 s in the future
01:09:39 DEBUG| [stdout] HOSTCC scripts/basic/fixdep
01:09:40 DEBUG| [stderr] make[2]: warning: Clock skew detected. Your build may be incomplete.
01:09:40 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112141 s in the future
01:09:40 DEBUG| [stdout] HOSTCC scripts/kconfig/conf.o
01:09:40 DEBUG| [stdout] SHIPPED scripts/kconfig/zconf.tab.c
01:09:40 DEBUG| [stdout] SHIPPED scripts/kconfig/zconf.lex.c
01:09:40 DEBUG| [stdout] SHIPPED scripts/kconfig/zconf.hash.c
01:09:40 DEBUG| [stdout] HOSTCC scripts/kconfig/zconf.tab.o
01:09:40 DEBUG| [stdout] HOSTLD scripts/kconfig/conf
01:09:40 DEBUG| [stdout] scripts/kconfig/conf --silentoldconfig Kconfig
Anyone know why that happens? Obvious fixes are to either not run `make
dep` or to install an NTP client, and I can do that, but figured I'd
report the above.
Thanks,
Nish
--
Nishanth Aravamudan <na...@us.ibm.com>
IBM Linux Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
lab. Autotest by default runs `make dep` and it seems the clock is
pretty badly skewed on this server, resulting in an infinite loop of:
01:09:37 DEBUG| Running 'make dep'
01:09:38 DEBUG| [stderr] make: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112143 s in the future
01:09:38 DEBUG| [stderr] make[1]: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112143 s in the future
01:09:38 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112143 s in the future
01:09:38 DEBUG| [stdout] HOSTCC scripts/basic/fixdep
01:09:38 DEBUG| [stderr] make[2]: warning: Clock skew detected. Your build may be incomplete.
01:09:38 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112143 s in the future
01:09:38 DEBUG| [stdout] HOSTCC scripts/kconfig/conf.o
01:09:38 DEBUG| [stdout] SHIPPED scripts/kconfig/zconf.tab.c
01:09:38 DEBUG| [stdout] SHIPPED scripts/kconfig/zconf.lex.c
01:09:38 DEBUG| [stdout] SHIPPED scripts/kconfig/zconf.hash.c
01:09:39 DEBUG| [stdout] HOSTCC scripts/kconfig/zconf.tab.o
01:09:39 DEBUG| [stdout] HOSTLD scripts/kconfig/conf
01:09:39 DEBUG| [stdout] scripts/kconfig/conf --silentoldconfig Kconfig
01:09:39 DEBUG| [stderr] make[2]: warning: Clock skew detected. Your build may be incomplete.
01:09:39 DEBUG| [stderr] make[1]: warning: Clock skew detected. Your build may be incomplete.
01:09:39 DEBUG| [stderr] make: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112142 s in the future
01:09:39 DEBUG| [stderr] make[1]: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112142 s in the future
01:09:39 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112142 s in the future
01:09:39 DEBUG| [stdout] HOSTCC scripts/basic/fixdep
01:09:40 DEBUG| [stderr] make[2]: warning: Clock skew detected. Your build may be incomplete.
01:09:40 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112141 s in the future
01:09:40 DEBUG| [stdout] HOSTCC scripts/kconfig/conf.o
01:09:40 DEBUG| [stdout] SHIPPED scripts/kconfig/zconf.tab.c
01:09:40 DEBUG| [stdout] SHIPPED scripts/kconfig/zconf.lex.c
01:09:40 DEBUG| [stdout] SHIPPED scripts/kconfig/zconf.hash.c
01:09:40 DEBUG| [stdout] HOSTCC scripts/kconfig/zconf.tab.o
01:09:40 DEBUG| [stdout] HOSTLD scripts/kconfig/conf
01:09:40 DEBUG| [stdout] scripts/kconfig/conf --silentoldconfig Kconfig
Anyone know why that happens? Obvious fixes are to either not run `make
dep` or to install an NTP client, and I can do that, but figured I'd
report the above.
Thanks,
Nish
--
Nishanth Aravamudan <na...@us.ibm.com>
IBM Linux Technology Center
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Michal Marek
Mar 5, 2012, 9:50:02 AM3/5/12
to
On 29.2.2012 20:01, Nishanth Aravamudan wrote:
> Noticed something on a fresh FC16 based install on a test server in our
> lab. Autotest by default runs `make dep` and it seems the clock is
> pretty badly skewed on this server, resulting in an infinite loop of:
>
> 01:09:37 DEBUG| Running 'make dep'
> 01:09:38 DEBUG| [stderr] make: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112143 s in the future
> 01:09:38 DEBUG| [stderr] make[1]: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112143 s in the future
> 01:09:38 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112143 s in the future
> 01:09:38 DEBUG| [stdout] HOSTCC scripts/basic/fixdep
> 01:09:38 DEBUG| [stderr] make[2]: warning: Clock skew detected. Your build may be incomplete.
> 01:09:38 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112143 s in the future
[...]
> Noticed something on a fresh FC16 based install on a test server in our
> lab. Autotest by default runs `make dep` and it seems the clock is
> pretty badly skewed on this server, resulting in an infinite loop of:
>
> 01:09:37 DEBUG| Running 'make dep'
> 01:09:38 DEBUG| [stderr] make: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112143 s in the future
> 01:09:38 DEBUG| [stderr] make[1]: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112143 s in the future
> 01:09:38 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112143 s in the future
> 01:09:38 DEBUG| [stdout] HOSTCC scripts/basic/fixdep
> 01:09:38 DEBUG| [stderr] make[2]: warning: Clock skew detected. Your build may be incomplete.
> 01:09:38 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112143 s in the future
> Anyone know why that happens?
generated files are older than source files and thus dependencies cannot
work. You need to fix the system time to be at least ahead of the mtime
of the sources.
> Obvious fixes are to either not run `make dep`
Michal
Nishanth Aravamudan
Mar 5, 2012, 10:40:03 AM3/5/12
to
On 05.03.2012 [15:40:56 +0100], Michal Marek wrote:
> On 29.2.2012 20:01, Nishanth Aravamudan wrote:
> > Noticed something on a fresh FC16 based install on a test server in our
> > lab. Autotest by default runs `make dep` and it seems the clock is
> > pretty badly skewed on this server, resulting in an infinite loop of:
> >
> > 01:09:37 DEBUG| Running 'make dep'
> > 01:09:38 DEBUG| [stderr] make: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112143 s in the future
> > 01:09:38 DEBUG| [stderr] make[1]: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112143 s in the future
> > 01:09:38 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112143 s in the future
> > 01:09:38 DEBUG| [stdout] HOSTCC scripts/basic/fixdep
> > 01:09:38 DEBUG| [stderr] make[2]: warning: Clock skew detected. Your build may be incomplete.
> > 01:09:38 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112143 s in the future
> [...]
>
> > Anyone know why that happens?
>
> Because the system time time is several hours, if not days, behind, so
> generated files are older than source files and thus dependencies cannot
> work. You need to fix the system time to be at least ahead of the mtime
> of the sources.
That makes sense.
> On 29.2.2012 20:01, Nishanth Aravamudan wrote:
> > Noticed something on a fresh FC16 based install on a test server in our
> > lab. Autotest by default runs `make dep` and it seems the clock is
> > pretty badly skewed on this server, resulting in an infinite loop of:
> >
> > 01:09:37 DEBUG| Running 'make dep'
> > 01:09:38 DEBUG| [stderr] make: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112143 s in the future
> > 01:09:38 DEBUG| [stderr] make[1]: Warning: File `/usr/local/autotest/tmp/build/linux/arch/powerpc/Makefile' has modification time 112143 s in the future
> > 01:09:38 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112143 s in the future
> > 01:09:38 DEBUG| [stdout] HOSTCC scripts/basic/fixdep
> > 01:09:38 DEBUG| [stderr] make[2]: warning: Clock skew detected. Your build may be incomplete.
> > 01:09:38 DEBUG| [stderr] make[2]: Warning: File `scripts/Makefile.host' has modification time 112143 s in the future
> [...]
>
> > Anyone know why that happens?
>
> Because the system time time is several hours, if not days, behind, so
> generated files are older than source files and thus dependencies cannot
> work. You need to fix the system time to be at least ahead of the mtime
> of the sources.
> > Obvious fixes are to either not run `make dep`
>
> I don't think this is limited to make dep.
-j16 vmlinux` did seem to complete. But it was a while ago and maybe I'm
mis-remembering.
Ah well, I've fixed up my testing scripts to ensure an ntp run is
performed before trying to build.
0 new messages