Date: Tue, 24 Jun 2008 10:21:29 +0100
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: william <william@waisse.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: strange freeze with VIA C7 dedicated server and libc 2.6.1
Message-ID: <20080624102129.19d79eb0@lxorguk.ukuu.org.uk>
In-Reply-To: <2ffbcf00806232001o4bd314f4kc590e43b4ab27076@mail.gmail.com>
References: <2ffbcf00806232001o4bd314f4kc590e43b4ab27076@mail.gmail.com>
Organization: Red Hat UK Cyf., Amberley Place, 107-111 Peascod Street,
 Windsor, Berkshire, SL4 1TE, Y Deyrnas Gyfunol. Cofrestrwyd yng Nghymru a
 Lloegr o'r rhif cofrestru 3798903
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1088
Lines: 22

> "If the kernel completely locks up then that is a kernel bug or a hardware bug.
> It shouldn't be possible to lock up the kernel, regardless of what userland
> such as glibc does. Presumably the newer glibc is doing something different

Except for bugs in glibc that trigger things happening as root which go
on to do stuff like power down the system (root is allowed to power
down/reboot/etc). That is a fairly unlikely case.

> that is triggering the bug. Regardless of what that is and whether it should be
> doing it, it shouldn't completely hang the kernel."

The first thing is to find out which glibc version is the latest that
works, which is the earliest that fails. Second is to try and find out
what apps or event is the trigger for the fail (eg can you boot into text
mode with init s and then run 2 or 3 cpu hogs all day)

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