From: Chris Largret <largret@gmail.com>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.19-rc1, timebomb?
Date: Fri, 20 Oct 2006 21:22:44 -0700 [thread overview]
Message-ID: <20061020212244.56f9f02b@localhost> (raw)
In-Reply-To: <200610200130.44820.gene.heskett@verizon.net>
On Fri, 20 Oct 2006 01:30:44 -0400
Gene Heskett <gene.heskett@verizon.net> wrote:
> Greetings;
>
> I just arrived home a few hours ago, and my wife said the outside lights
> hadn't worked for the last 2 days.
>
> I come in to check, the this machine, which runs some heyu scripts to do
> this, was powered down. So I powered it back up and it had to e2fsk
> everything. I have a ups with a fresh battery which passes the tests just
> fine.
>
> The only thing in the logs is a single line about eth0 being down:
> Oct 17 05:31:11 coyote kernel: eth0: link down.
> Oct 19 20:37:49 coyote syslogd 1.4.1: restart.
>
> Uptime when this occurred was about 9 days. Was this a known problem?
Out of curiosity, did you check the UPS logs? The low- (and mid- ?)
range ones I've played with have logs as well as the ability to tell
the computer when there is a power problem. I'd check those logs and
also look in the system BIOS for a way to power the computer back on
when power returns. If it was powered off, I don't believe it would be
kernel-related.
I could always be wrong, but from my own experiences kernel problems
result in a system that is on but not operational.
--
Chris Largret <http://www.largret.com>
next prev parent reply other threads:[~2006-10-21 4:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-20 5:30 2.6.19-rc1, timebomb? Gene Heskett
2006-10-21 4:22 ` Chris Largret [this message]
2006-10-21 4:37 ` Gene Heskett
2006-10-21 5:03 ` Chris Wedgwood
2006-10-21 6:08 ` Gene Heskett
2006-10-21 15:10 ` Gene Heskett
2006-10-21 17:25 ` Andi Kleen
2006-10-22 0:11 ` Gene Heskett
2006-10-22 11:20 ` WAS Re: 2.6.19-rc1, timebomb?, now -rc2 progress Gene Heskett
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=20061020212244.56f9f02b@localhost \
--to=largret@gmail.com \
--cc=gene.heskett@verizon.net \
--cc=linux-kernel@vger.kernel.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox