LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Fortier,Vincent [Montreal]" <Vincent.Fortier1@EC.GC.CA>
To: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: RE: 2.6.21.5 june 30th to july 1st date hang?
Date: Tue, 3 Jul 2007 08:55:12 -0400 [thread overview]
Message-ID: <F1D642E5A91BC94D9504EC83AE19E6B0128A5D@ecqcmtlmail3.quebec.int.ec.gc.ca> (raw)
In-Reply-To: <F1D642E5A91BC94D9504EC83AE19E6B0128A5C@ecqcmtlmail3.quebec.int.ec.gc.ca>
> -----Message d'origine-----
> De : linux-kernel-owner@vger.kernel.org
> [mailto:linux-kernel-owner@vger.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
>
next prev parent reply other threads:[~2007-07-03 12:55 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 12:44 Fortier,Vincent [Montreal]
2007-07-03 12:55 ` Fortier,Vincent [Montreal] [this message]
2007-07-03 13:05 ` Clemens Koller
2007-07-03 14:51 ` Fortier,Vincent [Montreal]
2007-07-03 13:56 ` Uli Luckas
2007-07-03 13:59 ` Florian Attenberger
2007-07-03 14:20 ` Arne Georg Gleditsch
2007-07-03 15:02 ` Florian Attenberger
2007-07-03 15:26 ` Arne Georg Gleditsch
2007-07-03 15:36 ` Fortier,Vincent [Montreal]
2007-07-03 17:19 ` Dave Jones
2007-07-03 19:28 ` Chris Friesen
2007-07-03 21:02 ` Chris Friesen
2007-07-03 21:02 ` Chuck Ebbert
2007-07-04 1:06 ` Fortier,Vincent [Montreal]
2007-07-04 8:56 ` Uli Luckas
2007-07-04 16:53 ` Chris Wright
2007-07-05 14:13 ` Clemens Koller
2007-07-05 17:48 ` Chris Friesen
2007-07-05 18:34 ` Clemens Koller
2007-07-05 20:10 ` Thomas Gleixner
2007-07-05 21:02 ` Chris Friesen
2007-07-05 21:17 ` Thomas Gleixner
2007-07-05 22:28 ` Ernie Petrides
2007-07-05 22:49 ` Chris Friesen
2007-07-05 23:12 ` Ernie Petrides
2007-07-05 23:45 ` Chris Friesen
2007-07-06 5:16 ` Thomas Gleixner
2007-07-06 5:17 ` Thomas Gleixner
2007-07-06 15:47 ` Chris Friesen
2007-07-06 20:03 ` Ernie Petrides
2007-07-03 15:59 ` Chris Friesen
2007-07-03 16:00 ` Fortier,Vincent [Montreal]
2007-07-03 16:03 ` Chris Friesen
2007-07-03 17:28 ` Chris Friesen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F1D642E5A91BC94D9504EC83AE19E6B0128A5D@ecqcmtlmail3.quebec.int.ec.gc.ca \
--to=vincent.fortier1@ec.gc.ca \
--cc=linux-kernel@vger.kernel.org \
--subject='RE: 2.6.21.5 june 30th to july 1st date hang?' \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).