Leap Second Kernel Panic??

Andrew Bacchi bacchi at rpi.edu
Tue Jan 3 14:21:20 UTC 2006


It would help to provide the version you are running.  All 27 of my 
servers running AS 3 are just fine.

Michael D. Berger wrote:

>I have two linux boxes that run all the time.  I was away for
>a few days over New Year, and came home to find both boxes
>locked up with this on the screens, with the only differences
>shown by yy and xxxxxxxx:
>
>   Red Hat Enterprise Linux WS release 4(Nahant)
>   Kernel 2.6.9-5.EL on an i686
>
>   mbrcyy login: Clock: inserting leap second: 23:59:60 UTC
>   Kernel panic - not syncing: net/ipv4/tcp_timer.c:211:
>   spin_lock(net/ipv4/tcp_minisocks.c:xxxxxxxx) already locked by
>   net/ipv4/tcp_ipv4.c/1790
>
>   yy = 32, xxxxxxxx = f5fee080
>   yy = 20, xxxxxxxx = c276aa40
>
>I add that both boxes are running:
>   ntpd (but only one talks to the outside world)
>   net_queue_d, a new and rather complex libipq daemon I am developing
>
>I of course suspect my libipq daemon, but the apparent relation
>to the leap second is peculiar.
>
>Assistance would be much appreciated.  If additional information would
>help, please tell me what it is.
>
>Thanks,
>Mike.
>
>--
>Michael D. Berger
>m.d.berger at ieee.org 
>
>
>  
>

-- 
veritatis simplex oratio est
		- Seneca

Andrew Bacchi
Staff Systems Programmer
Rensselaer Polytechnic Institute
phone: 518 276-6415  fax: 518 276-2809

http://www.rpi.edu/~bacchi/





More information about the redhat-list mailing list