Re: Reports of (Debian?) Linux kernel 2.6.32 livelocking when notified of leap second
On Sun, Jul 01, 2012 at 08:42:02AM +, Camaleón wrote: > My "lennies" (2.6.26) are only reporting in both dmesg and kernel logs: > > "Clock: inserting leap second 23:59:60 UTC" Mmmm interesting... root@tal:~# dmesg | grep leap root@tal:~# root@tal:~# less /var/log/dmesg.0 | grep leap root@tal:~# root@tal:~# zless /var/log/dmesg.?.gz | grep leap root@tal:~# root@tal:~# uname -a Linux tal 3.2.0-2-686-pae #1 SMP Fri Jun 1 18:56:14 UTC 2012 i686 GNU/Linux No wonder my clock is wrong :) -- "If you're not careful, the newspapers will have you hating the people who are being oppressed, and loving the people who are doing the oppressing." --- Malcolm X -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120701224344.GE15677@tal
Re: Reports of (Debian?) Linux kernel 2.6.32 livelocking when notified of leap second
On Sat, 30 Jun 2012 21:52:21 + Andy Smith wrote: > Hello, > > Has anyone been seeing this sort of thing in the last 22-ish hours? > > http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-today > > I've run adjtimex -p on all of my servers and they're all reporting > status 17, which as far as I can tell means they've already been sent > adjtimex()by ntpd and will add a leap second at midnight. > > As I understand the reports so far, the livelock would happen at the > point where ntpd sends the adjtime(), soif they haven't locked > already then they aren't going to. > I didn't find out about this until last night, when I shut down ntpd on the two Squeeze machines I look after. Obviously that was far too late, as both machines did the leap-second thing at midnight, and neither had been affected by the problem. I've since seen it described as the result of a race hazard, so it would seem to be a matter of chance whether a particular machine had a problem. -- Joe -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120701221815.27e94...@jretrading.com
Re: Reports of (Debian?) Linux kernel 2.6.32 livelocking when notified of leap second
On Sat, 30 Jun 2012, Andy Smith wrote: > Has anyone been seeing this sort of thing in the last 22-ish hours? > > http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-today No problems with the kernel in _up-to-date_ Debian userspace and kernels, at least in stable. I will know about oldstable on monday. Now, I've had a few java apps get a bit crazy, might have been this: https://lkml.org/lkml/2012/6/30/122 And it happened on latest kernel 3.0, so if it indeed is the hrtimers issue, it is on more kernels than just 3.4.4/3.5. -- "One disk to rule them all, One disk to find them. One disk to bring them all and in the darkness grind them. In the Land of Redmond where the shadows lie." -- The Silicon Valley Tarot Henrique Holschuh -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120701133612.gd2...@khazad-dum.debian.net
Re: Reports of (Debian?) Linux kernel 2.6.32 livelocking when notified of leap second
On Sun, July 1, 2012 11:42, Camaleón wrote: > On Sat, 30 Jun 2012 21:52:21 +, Andy Smith wrote: > >> Has anyone been seeing this sort of thing in the last 22-ish hours? >> >> http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-today > > (...) > > Mmm, interesting. > > My "lennies" (2.6.26) are only reporting in both dmesg and kernel logs: > > "Clock: inserting leap second 23:59:60 UTC" > > But nothing more, all is running fine here, no kernel locked. Same here. Squeeze * 3 + Ubuntu 12.04 LTS * 2. All running ntpd, but no problems. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/0b7d7c82d23477569135640c95c212c3.squir...@jarif.iki.fi
Re: Reports of (Debian?) Linux kernel 2.6.32 livelocking when notified of leap second
On Sat, 30 Jun 2012 21:52:21 +, Andy Smith wrote: > Has anyone been seeing this sort of thing in the last 22-ish hours? > > http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-today (...) Mmm, interesting. My "lennies" (2.6.26) are only reporting in both dmesg and kernel logs: "Clock: inserting leap second 23:59:60 UTC" But nothing more, all is running fine here, no kernel locked. Greetings, -- Camaleón -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/jsp2gp$69j$6...@dough.gmane.org
Re: Reports of (Debian?) Linux kernel 2.6.32 livelocking when notified of leap second
> Hello, > > Has anyone been seeing this sort of thing in the last 22-ish hours? > > http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates > -of-linux-server-crashes-today I saw the buzz about this on Slashdot, but as far as I can tell none of my systems are having any problems. I have several Debian "squeeze" 2.6.32 64-bit systems, a mix of file servers, cluster nodes, and desktop workstation systems. I'm off-site, it being the weekend, but there's no evidence of trouble. I did see a lot of log traffic at "23:59:60" UTC, so the kernels have the info. If they're going to lock up at local midnight, well, I guess I'll find out in half an hour. -- A. -- Andrew Reid / rei...@bellatlantic.net -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201206302329.55719.rei...@bellatlantic.net
Reports of (Debian?) Linux kernel 2.6.32 livelocking when notified of leap second
Hello, Has anyone been seeing this sort of thing in the last 22-ish hours? http://serverfault.com/questions/403732/anyone-else-experiencing-high-rates-of-linux-server-crashes-today I've run adjtimex -p on all of my servers and they're all reporting status 17, which as far as I can tell means they've already been sent adjtimex()by ntpd and will add a leap second at midnight. As I understand the reports so far, the livelock would happen at the point where ntpd sends the adjtime(), soif they haven't locked already then they aren't going to. Cheers, Andy -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120630215221.gp3...@bitfolk.com
