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: <F1D642E5A91BC94D9504EC83AE19E6B0128A5D@ecqcmtlmail3.quebec.int.ec.gc.ca>
Date:	Tue, 3 Jul 2007 08:55:12 -0400
From:	"Fortier,Vincent [Montreal]" <Vincent.Fortier1@...GC.CA>
To:	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: RE: 2.6.21.5 june 30th to july 1st date hang?

> -----Message d'origine-----
> De : linux-kernel-owner@...r.kernel.org 
> [mailto:linux-kernel-owner@...r.kernel.org] De la part de 
> Fortier,Vincent [Montreal]
> Envoyé : 3 juillet 2007 08:44
> 
> 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.
> 
> On my monitoring system every single station running a 
> 2.6.21.5 kernel stoped responding exactly after midnight on 
> the date shift from June 30th to July 1st.  Although, 
> stations still running 2.6.18 to 2.6.20.11 worked flawlessly.
> 
> I first tought there had been an electricity outage but two 
> of my servers (dell PE 2950 dual-quad core) on UPS in our 
> server room also
> hanged:
> Jun 30 23:55:01 urpdev1 /USR/SBIN/CRON[31298]: (root) CMD ([ -x
> /usr/lib/sysstat/sa1 ] && { [ -r "$DEFAULT" ] && . "$DEFAULT" 
> ; [ "$ENABLED" = "true" ] && exec /usr/lib/sysstat/sa1; }) 
> Jul  3 11:54:03 urpdev1 syslogd 1.4.1#17: restart.
> 
> 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?

Forgot to mention:

- All stations that failed where running a 2.6.21 kernel + CFS v18 (I don't have any stations running a plain 2.6.21 kernel so can't tell)
- Config file can be found at: http://linux-dev.qc.ec.gc.ca/kernel/debian/CONFIG-i686-2.6.21-005
- kernels can be found at: http://linux-dev.qc.ec.gc.ca/kernel/debian/sarge/i686/2.6.21/

> 
> - 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/