linux-kernel - RE: 2.6.21.5 june 30th to july 1st date hang?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <F1D642E5A91BC94D9504EC83AE19E6B0128A61@ecqcmtlmail3.quebec.int.ec.gc.ca>
Date:	Tue, 3 Jul 2007 10:51:51 -0400
From:	"Fortier,Vincent [Montreal]" <Vincent.Fortier1@...GC.CA>
To:	"Clemens Koller" <clemens.koller@...gramm.de>
Cc:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Uli Luckas" <u.luckas@...d.de>,
	"Florian Attenberger" <valdyn@...il.com>,
	"Arne Georg Gleditsch" <argggh@...phinics.no>
Subject: RE: 2.6.21.5 june 30th to july 1st date hang?

> -----Message d'origine-----
> De : Clemens Koller [mailto:clemens.koller@...gramm.de] 
> Envoyé : 3 juillet 2007 09:05
> 
> Hi, Vincent!
> 
> Fortier,Vincent [Montreal] schrieb:
> > Hi all,
> > 
> > All my servers and workstations running a 2.6.21.5 kernel hanged 
> > exactly when the date shift from june 30th to july 1st.
> > 
> > I could not get anything on any of the 20+ consoles...  All the 
> > systems hanged at around the exact same time... When the date shifted 
> > from June 30th to July 1st in UTC ...?
> > 
> > Any clue any one?
> 
> No problems over here with plain 2.6.21.5 on x686
> 
> You could just reset the date back on one of these machines 
> and check the transition again... and see if it was really 
> the kernel who crashed.... and check your cron configuration.

I tried reverting to 23:50 June 30th and it did not hanged when switching to July 1st.  I've tried it a few times without any problems.  So I deactivated all NTP related jobs, switched the date back to June 30th 23:10 and reboot the system.  Wait and see.

> De : linux-kernel-owner@...r.kernel.org 
> [mailto:linux-kernel-owner@...r.kernel.org] De la part de Uli Luckas
> 
> Same thing here on two machines with plain vanilla 
> 2.6.21.(3/4), on debian testing & debian unstable.
> 

I am also using Debian... But Sarge 3.1.  There might be a relation there unless somebody comes up having the same problem using another dist.  At least it's not CFS related.

> -----Message d'origine-----
> De : linux-kernel-owner@...r.kernel.org 
> [mailto:linux-kernel-owner@...r.kernel.org] De la part de 
> Arne Georg Gleditsch
> 
> Florian Attenberger <valdyn@...il.com> writes:
> > there was one 'special' event at that date:
> > syslog.2.gz:Jul  1 01:59:59 master kernel: Clock: inserting leap 
> > second 23:59:60 UTC
> 
> As far as I can tell, no leap second was due to be inserted 
> at 1. of July this year.  Is the year set correctly for this box?
> 

All my server/workstations are in sync using ntp... And yes, the year is set properly on all of them.

Regards,

- vin
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/