[lkml]   [2012]   [Apr]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] clocksource, prevent overflow in clocksource_cyc2ns
On 04/05/2012 04:00 AM, Prarit Bhargava wrote:
> On 04/04/2012 09:08 PM, John Stultz wrote:
>> So what kernel version are you using?
> I was on an earlier version of Fedora (F16) ... but I'll jump forward and see if
> I can still hit it.

Ok, but if you have the specific kernel version, it would help, since
even if the issue is resolved upstream, we can see if a backport to
stable is appropriate.

> Keep in mind that 10000 threads is the *minimum* I was able to cause
> this with, which is only ~315 threads/cpu, which isn't a lot :/. At
> that number of threads the dump takes about 6 mins. Doubling it, IIRC,
> exceeded 10 mins.

At that point, if we're starving the system of interrupts for over 10
minutes, a number of other non-timekeeping issues can crop up. I've seen
scsci controllers fall over if their heart-beat checks don't come in, etc.

I suspect if printk dumps taking 10 minutes or more is going to be
considered "acceptable" behavior, we may need to see about adding some
breaks in the printk code, so that the system can take a few necessary


 \ /
  Last update: 2012-04-05 18:27    [W:0.155 / U:2.232 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site