RE: [BISECTION RESULT] sched: revert cpu_clock to pre-27ec4407790d075c325e1f4da0a19c56953cce23 state

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Luck, Tony
Date: Wednesday, August 13, 2008 - 1:11 pm

> Well Peter's patch was tested-by me, so I know it fixes the problem on

It would be nice to know ... I expect that you'll see crazy numbers
for the timestamps on the first few printk()s without Peter's fix (I
did on my system).

-Tony
--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[BISECTION RESULT] sched: revert cpu_clock to pre-27ec4407 ..., Nishanth Aravamudan, (Mon Aug 4, 12:46 pm)
Re: [BISECTION RESULT] sched: revert cpu_clock to pre-27ec ..., Nishanth Aravamudan, (Mon Aug 4, 3:45 pm)
Re: [BISECTION RESULT] sched: revert cpu_clock to pre-27ec ..., Nishanth Aravamudan, (Mon Aug 4, 4:30 pm)
Re: [BISECTION RESULT] sched: revert cpu_clock to pre-27ec ..., Nishanth Aravamudan, (Tue Aug 5, 10:34 am)
Re: [BISECTION RESULT] sched: revert cpu_clock to pre-27ec ..., Nishanth Aravamudan, (Wed Aug 13, 12:29 pm)
RE: [BISECTION RESULT] sched: revert cpu_clock to pre-27ec ..., Luck, Tony, (Wed Aug 13, 1:11 pm)
Re: [BISECTION RESULT] sched: revert cpu_clock to pre-27ec ..., Nishanth Aravamudan, (Tue Aug 19, 3:19 pm)