search

zhuravskiy / wl500g

Automatically exported from code.google.com/p/wl500g
0 stars 0 forks source link

Failed to change to Daylight saving time (DST, summer time) - 1.9.2.7-d-r2624 #303

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
I'm using the latest 2.4.37 kernel based Oleg's firmware: 1.9.2.7-d-r2624

Today, at 10:00, the clock of the router was still in normal time. It shows 
10:00, when it should be 11:00 because of changing to DST. The clock should 
have automatically changed to DST today (2012-03-25) at 03:00. Last year, there 
was no problem, the clock automatically changed to DST.

I guess this might be something to do with the leap year. Perhaps there is the 
same issue which is fixed here: 
http://code.google.com/p/wl500g/source/browse/toolchain/toolchain/uClibc/patches
/0.9.32/720-tm_isdst.patch?spec=svn3440&r=3440

Although the development of the 2.4.37 kernel based version seems to be 
suspended, I think it would be useful to provide an update to fix this issue. I 
can not update to kernel 2.6.22 because of hardware issues.

Original issue reported on code.google.com by mikko.ve...@gmail.com on 25 Mar 2012 at 8:50

GoogleCodeExporter commented 8 years ago 
The exact version of the firmware I have downloaded is: 
WL500gpv2-1.9.2.7-d-r2624.trx

Original comment by mikko.ve...@gmail.com on 25 Mar 2012 at 8:53

GoogleCodeExporter commented 8 years ago 
I admit that this bug is extremely rare. If this bug occurs because of the leap 
year, it seems to happen only if the year is a leap year and the last Sunday of 
March is exactly week behind the first of April. So, this bug happens probably 
once in 30 years or something. If I have understood correctly, the DST change 
is just delayed one week. So if the DST change happens next week, perhaps a bug 
fix is not so critical. At least the bug is now documented also here.

Original comment by mikko.ve...@gmail.com on 25 Mar 2012 at 9:00

GoogleCodeExporter commented 8 years ago 
Unfortunately, this fix requires too much time:

1) backport uClibc patch or switch uClibc to 0.9.32 for K24(never tested)
2) old(K24-based) toolchain rebuild
3) rebuild K24 fw
4) retest build for public

Maybe we will do it in future, but chances are too small...

Original comment by lly.dev on 26 Mar 2012 at 4:45

GoogleCodeExporter commented 8 years ago 
p.1 done in r4009

Original comment by lly.dev on 27 Mar 2012 at 5:03

GoogleCodeExporter commented 8 years ago 
As I suspected, the clock of the router did change to DST today, exactly a week 
later than it should have been.

Original comment by mikko.ve...@gmail.com on 1 Apr 2012 at 5:49