Critical Linux bug that leads 100% CPU (leap second)

Post by gcr » Tue, Jul 03, 2012, 1:28 AM UTC

JVIDEL wrote: post #38

Oh man so that was causing it! My rig crashed all weekend because of this POS bug, I had to boot back to Windows to get anything done (oh cmd, I really didn't miss you at all you insufferable bitch...) Any fixes?

Post by pilif » Tue, Jul 03, 2012, 2:33 AM UTC

ajays wrote: post #35

pilif wrote: post #4

I would love to see what's really causing this bug. We read so many times over the weekend to either reboot or just run that date command - but nobody is telling us what's causing the problem. Also, seeing that other threaded applications had similar problems, I doubt this is a java issue - more likely a pthread, glibc or even kernel issue

This seems like the best explanation I've found so far: https://lkml.org/lkml/2012/7/1/203

Post by Negitivefrags » Tue, Jul 03, 2012, 5:32 AM UTC

MichaelGG wrote: post #25

wmf wrote: post #20

Earlier quoted context omitted.

Leap seconds aren't needed at all. I'd rather let them accumulate until there's a leap hour that can be rolled into DST (although DST may not exist that far in the future).

DST doesn't exist in UTC, so that's irrelevant. A one-hour UTC shift would totally, utterly, screw stuff up. But, at the current rate, a one-hour "leap" would happen in thousands of years, so maybe it's not such a bad idea after all. But I think the reason for leap seconds has to do with keeping UTC in sync with other clock systems, and that probably overrides any inconvenience to software.