Hi all, I'm working on a custom board and this problem *always* happens. Few minutes after system boots, its date starts to jump forward 2^17 seconds.
The hwclock is ok, but date is not. I applied the kernel patch, but no difference. Maybe my system could help you to find the bug. Thank's Andre On Tuesday, June 18, 2013 8:20:07 PM UTC-3, Britton Kerin wrote: > > On further investigation... it was all my fault in this case. I may > have the time > warp problem others have encountered, but I have no evidence of it yet. > > Britton > > On Mon, Jun 17, 2013 at 6:25 PM, Britton Kerin > <[email protected]<javascript:>> > wrote: > > I think I'm having the same problems. Probably. I haven't tried the > patch. > > I make clock_gettime() calls (about 3-4 per minute), but I also > nanosleep > > pretty continually, which sounds like it might use related stuff. > > > > The only odd thing I have to add is that in my case, ntpd doesn't freak > out > > and die, but keep going. The ntpd program shows up in top like this: > > > > 466 ? Ss 1:26 /usr/bin/ntpd -p /var/run/ntp.pid -g > > > > Presumably its the -g option that keeps it alive. It seems that ntpd > does > > ultimately drag the clock back to accurate. But my logged data shows > that > > the clock is frequently way off for long periods, which isn't surprising > since > > if I understand correctly ntpd adjust things only by slewing the clock > rate, > > rather than resetting anything (and producing a discontinuity in the > clock). > > > > I guess the only known workaround at the moment is to run some code that > > watches for these discontinuities, and kill ntpd, and rerun ntpdate when > > they occur? > > > > Has anyone ever observed this issue on BBB, or on a BBW running 3.8? > > > > Britton > > > > On Wed, Jun 5, 2013 at 12:26 PM, Andrew Bradford > > <[email protected] <javascript:>> wrote: > >> On Thu, May 30, 2013, at 06:07 PM, David Anders wrote: > >>> can you register over on http://bugs.elinux.org and file a bug report > on > >>> this? > >> > >> Yes. > >> > >> http://bugs.elinux.org/issues/15 > >> > >> Thanks, > >> Andrew > >> > >>> On Monday, May 6, 2013 12:15:15 PM UTC-5, beagler001 wrote: > >>> > > >>> > > >>> > I have confirmed that even with the patch mentioned in this thread, > our > >>> > clock still jumps ahead. Did a few times over the weekend. > >>> > > >>> > One interesting note: The problem seems to be isolated to one board. > We > >>> > have 3-4 boards running and logging time on a regular basis just to > see if > >>> > the time ever jumps. We only get the problem on the board that is > logging > >>> > CAN data. > >>> > > >>> > I plan to roll up the sleeves and dig into this. It sure would be > nice to > >>> > output some extra debug information associated with clock_gettime() > or the > >>> > registers/variables that are holding timer counts. Anyone have any > >>> > suggestions on where to start? > >>> > > >>> > Thanks. > >>> > > >>> > >>> -- > >>> For more options, visit http://beagleboard.org/discuss > >>> --- > >>> You received this message because you are subscribed to the Google > Groups > >>> "BeagleBoard" group. > >>> To unsubscribe from this group and stop receiving emails from it, send > an > >>> email to [email protected] <javascript:>. > >>> For more options, visit https://groups.google.com/groups/opt_out. > >>> > >>> > >> > >> -- > >> For more options, visit http://beagleboard.org/discuss > >> --- > >> You received this message because you are subscribed to the Google > Groups "BeagleBoard" group. > >> To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected] <javascript:>. > >> For more options, visit https://groups.google.com/groups/opt_out. > >> > >> > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
