Re: Warning: File `include/config/auto.conf' has modification time 1.9e+04 s in the future

[Sam Ravnborg <sam@ravnborg.org>]

On Sun, Mar 22, 2009 at 02:04:36AM +0530, Jaswinder Singh Rajput wrote:
> Hello Sam, Ingo:
> 
> On latest -tip I am getting following warnings:
> 
>   LD      arch/x86/pci/built-in.o
> make[1]: warning:  Clock skew detected.  Your build may be incomplete.
> make[1]: Warning: File `include/config/auto.conf' has modification time 1.9e+04 s in the future
>   CC      arch/x86/power/cpu_64.o
>   LD      arch/x86/power/built-in.o
> make[1]: warning:  Clock skew detected.  Your build may be incomplete.
> make[1]: Warning: File `include/config/auto.conf' has modification time 1.9e+04 s in the future
>   CC      net/socket.o
> make[2]: Warning: File `include/config/auto.conf' has modification time 1.9e+04 s in the future
> make[2]: warning:  Clock skew detected.  Your build may be incomplete.
> make[2]: Warning: File `include/config/auto.conf' has modification time 1.9e+04 s in the future
>   CC      net/core/sock.o
> 
> [jaswinder@hpdv5 linux-2.6-tip]$ ls -l include/config/auto.conf
> -rw-rw-r-- 1 jaswinder jaswinder 18788 2009-03-22 07:14 include/config/auto.conf
> 
> [jaswinder@hpdv5 linux-2.6-tip]$ date
> Sun Mar 22 02:02:44 IST 2009
> [jaswinder@hpdv5 linux-2.6-tip]$ 

I have checked the source code in kconfig where we minupulate auto.conf.
We do a simple 

fopen(".tmpconfig", "w");
write a lot
fclose()
rename(".tmpconfig", "auto.conf");

So nothing suspicious that involves changing the date of the file.

I expect you have to locate the issue locally if it happens again.

I wonder if we save filetime in UTC or in local time.
If it is the latter then if logged in as different users
with different timezone could maybe explain it.

You are UTC+5,5 hours in IST IIRC and the clock skew is 5,2 hours.

[And it was late in night too :-) ]

	Sam