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: Monday, August 4, 2008 - 3:53 pm

> Would you like me to test this patch on the box, to verify? It seems

As soon as I turned on CONFIG_PRINTK_TIME=y I hit what I presume
was the same problem.

If you have time to do so, then confirming that this is the
same issue that you are seeing on your system would be good.

Thanks

-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 ..., Luck, Tony, (Mon Aug 4, 3:53 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 ..., Nishanth Aravamudan, (Tue Aug 19, 3:19 pm)