All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Aravamudan <nacc@linux.vnet.ibm.com>
To: Michal Marek <mmarek@suse.cz>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-kbuild@vger.kernel.org
Subject: `make dep' with clock skew detected loops forever
Date: Wed, 29 Feb 2012 11:01:38 -0800	[thread overview]
Message-ID: <20120229190138.GG5136@linux.vnet.ibm.com> (raw)

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 <nacc@us.ibm.com>
IBM Linux Technology Center


             reply	other threads:[~2012-02-29 19:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29 19:01 Nishanth Aravamudan [this message]
2012-03-05 14:40 ` `make dep' with clock skew detected loops forever Michal Marek
2012-03-05 15:33   ` Nishanth Aravamudan

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=20120229190138.GG5136@linux.vnet.ibm.com \
    --to=nacc@linux.vnet.ibm.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mmarek@suse.cz \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.