Skip to contentSkip to conversation

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

DISCUSSION Jaswinder Singh Rajput 2 participants 5 messages Mar 21, 2009 – Mar 22, 2009

lore
Share & tools
lore
#0 lore raw

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]$

Thanks,
--
JSR

#1 lore raw
Quoted 17 lines · Jaswinder Singh Rajput

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

Quoted 7 lines

[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]$

In the morning when I again tried it then it becomes OK :

[jaswinder@hpdv5 linux-2.6-tip]$ ls -l include/config/auto.conf -rw-rw-r-- 1 jaswinder jaswinder 18788 2009-03-22 10:53 include/config/auto.conf

why it behaves differently last night and showing 5:30 hours ahead of my time. BTW, my timezone IST is also +0530.

Thanks,
--
JSR

#2 lore raw
Quoted 26 lines · Jaswinder Singh Rajput
Quoted 17 lines · Jaswinder Singh Rajput

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

Quoted 7 lines

[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]$

Quoted 7 lines

In the morning when I again tried it then it becomes OK :

[jaswinder@hpdv5 linux-2.6-tip]$ ls -l include/config/auto.conf -rw-rw-r-- 1 jaswinder jaswinder 18788 2009-03-22 10:53 include/config/auto.conf

why it behaves differently last night and showing 5:30 hours ahead of my time. BTW, my timezone IST is also +0530.

Sorry, difference was 4:30.

--
JSR

#3 lore raw
In reply to Jaswinder Singh Rajput
Quoted 17 lines · Jaswinder Singh Rajput

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

Quoted 6 lines

[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

#4 lore raw

Hello Sam,

Quoted 12 lines · Sam Ravnborg

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.

OK, it is a dual boot machine may be Windows screws it, if I face similar problem again I will let you know.

Quoted 2 lines

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

hehe :-)

Thanks,

--
JSR