#11080 NORM 1.75-so: printk timestamp doesn't start at 0

[Zarro Boogs per Child]

#11080: printk timestamp doesn't start at 0
--------------------+-------------------------------------------------------
 Reporter:  pgf     |                 Owner:  saadia                            
     Type:  defect  |                Status:  new                               
 Priority:  normal  |             Milestone:  1.75-software                     
Component:  kernel  |               Version:  Development source as of this date
 Keywords:          |           Next_action:  never set                         
 Verified:  0       |   Deployment_affected:                                    
Blockedby:          |              Blocking:                                    
--------------------+-------------------------------------------------------
 often, but not always, the initial dmesg output looks like:

 {{{
 ....
     0.000000]       .data : 0xc0538000 - 0xc0562cf0   ( 172 kB)
 [    0.000000] NR_IRQS:320 nr_irqs:320 320
 [    0.000000] sched_clock: 32 bits at 6MHz, resolution 153ns, wraps every
 660764ms
 [    0.000000] setting oneshot mode
 [    0.000000] setting periodic mode
 [    0.000000] Console: colour dummy device 80x30
 [    0.000000] console [tty0] enabled
 [  660.724445] Calibrating delay loop... 795.44 BogoMIPS (lpj=3977216)
 [  660.813823] pid_max: default: 32768 minimum: 301
 [  660.813901] Mount-cache hash table entries: 512
 [  660.814216] CPU: Testing write buffer coherency: ok
 [  660.817796] print_constraints: dummy:
 ....
 }}}

 when it happens, the jump is always 660.  (i.e., the jump is either
 0, or 660, but never anything else.)

-- 
Ticket URL: <http://dev.laptop.org/ticket/11080>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system