| |||||||||||||
what about the deadlocks?what about the deadlocks?Posted Jul 3, 2012 14:02 UTC (Tue) by joey (subscriber, #328)Parent article: Leaping seconds and looping servers
I'm surprised there's no mention of the kernel deadlocks experienced by some due to the leap second insertation.
This seems to be a good overview: http://landslidecoding.blogspot.com/2012/07/linuxs-leap-s...
There were reports of deadlocks with older kernels on, at least, Debian stable. Above page also points out reports of a "spinlock lockup" message whose cause remains unknown.
(Log in to post comments)
what about the deadlocks? Posted Jul 3, 2012 17:10 UTC (Tue) by mgedmin (subscriber, #34497) [Link]
They were briefly mentioned in the comments of the other LWN story: http://lwn.net/Articles/504835/
what about the deadlocks? Posted Jul 3, 2012 23:59 UTC (Tue) by mcisely (subscriber, #2860) [Link] I personally experienced the deadlock issue.
I spent 3+ unplanned hours at work last Saturday afternoon trying to figure out why our main server kept wedging itself every time it transitioned from single user to multi-user mode. I had no idea about the pending leap-second at the time and had been suspecting storm damage from the previous night. I finally clued-in when I found that the kernel hang would happen every time about 5-8 seconds after starting ntpd. It was running Debian Lenny (yeah, old) with a Debian stock 2.6.32-5-amd64 kernel. Server architecture is a multicore Athlon setup. The hangs started happening at about 7:43AM CDT. Once I figured out that trigger was ntp, I disabled that, then searched the web and found this: http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-during-a-leap-secondMonday morning I enabled ntp again and started it - and as expected, no lockup...
what about the deadlocks? Posted Jul 7, 2012 1:16 UTC (Sat) by BenHutchings (subscriber, #37955) [Link]
Did you get a kernel log for this?
what about the deadlocks? Posted Jul 7, 2012 1:22 UTC (Sat) by mcisely (subscriber, #2860) [Link] The system locked up solid each time, no signs of distress or trouble anywhere prior to the lockup, not even on the console. So no there were unfortunately no kernel logs for this.
|
|||||||||||||