[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20061020212244.56f9f02b@localhost>
Date: Fri, 20 Oct 2006 21:22:44 -0700
From: Chris Largret <largret@...il.com>
To: Gene Heskett <gene.heskett@...izon.net>
Cc: Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.19-rc1, timebomb?
On Fri, 20 Oct 2006 01:30:44 -0400
Gene Heskett <gene.heskett@...izon.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>
-
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/
Powered by blists - more mailing lists