Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 9 Apr 2002 12:57:37 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 9 Apr 2002 12:57:36 -0400 Received: from borg.kabelfoon.nl ([62.45.45.66]:8722 "HELO borg.kabelfoon.nl") by vger.kernel.org with SMTP id ; Tue, 9 Apr 2002 12:57:36 -0400 Message-ID: <3CB30E53.8020905@kabelfoon.nl> Date: Tue, 09 Apr 2002 17:52:51 +0200 From: Nick Martens User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.9) Gecko/20020404 X-Accept-Language: en-us, en MIME-Version: 1.0 To: vda@port.imtp.ilyichevsk.odessa.ua Cc: linux-kernel@vger.kernel.org, rowan.ingvar.wilson@0800dial.com Subject: Re: 2.4.18 Boot problem In-Reply-To: <3CB1B505.2010505@kabelfoon.nl> <3CB1FE78.6050606@kabelfoon.nl> <200204090939.g399dlX02029@Port.imtp.ilyichevsk.odessa.ua> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Yes much longer, more like for ever... Is there a way to find out what is causing it other then removing each piece of hardware one by one ?? Denis Vlasenko wrote: > On 8 April 2002 18:32, Nick Martens wrote: > >>I don't expect it to be a memory problem my system is really stable and >>the weirdest about the problem is that it only happens the first time I >>boot up after my pc has been turned off for a while and there are no >>problems when i boot 2.5.1 it only crashes on shutdowns on that kernel. >>I have tried updating all kind of things, but noting seems to work > > > Is your "for a while" >= ten seconds? Nothing in CPU/RAM can survive > that long. > > I'd say this is a hardware problem then. Something in your box does not like > to be cold. > -- > vda - 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/