Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Mon, 17 Jun 2002 14:23:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Mon, 17 Jun 2002 14:23:56 -0400 Received: from faraday.ee.utt.ro ([193.226.10.1]:23564 "EHLO faraday.ee.utt.ro") by vger.kernel.org with ESMTP id ; Mon, 17 Jun 2002 14:23:55 -0400 Date: Mon, 17 Jun 2002 21:23:45 +0300 (EEST) From: Sebastian Szonyi To: kk maddowx cc: Subject: Re: 2.4.18 kernel panics before and after boot In-Reply-To: <20020617165244.44049.qmail@web21001.mail.yahoo.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 3077 Lines: 106 On Mon, 17 Jun 2002, kk maddowx wrote: > Date: Mon, 17 Jun 2002 09:52:44 -0700 (PDT) > From: kk maddowx > To: Kristian Peters > Cc: linux-kernel@vger.kernel.org > Subject: Re: 2.4.18 kernel panics before and after boot > > Unfortunately I could not get memtest to work. I added > the lines: > > label=memtest > image=/boot/memtest > > to lilo.conf and ran lilo. try swapping the lines > I can see the selection for memtest but it wont accept > it as a bootable image. I did swap the memory out and > still recieve kernel panics with known working memory. > > However if I boot from my old 2.2.20 kernel I will > never see a panic or experience a panic after boot > making me think the memory is ok. Here is the dmesg > from a successful 2.4 boot if that helps: > > > > LILO > Loading 2.4.................. > Linux version 2.4.18a (root@birdbrain) (gcc version > 2.96 20000731 (Red Hat Linux > 7.0)) #1 Thu Jun 13 01:54:35 EDT 2002 Linux 2.4.18a ? Never heard about it :-) gcc 2.96 ? use 2.95.3 or 2.95.4 See $(kernel_root)/Documentation/Changes to find out what you need for compiling this kernel (where $(kernel_root) is where your kernel tree is located for example /usr/src/linux ) > > I have noticed that if the kernel does decide to panic > on boot it will happen after the "Freeing unused > memory" message is printed. Do you have any ideas what > might be casuing this? TIA > > An unsupported filesystem in your kernel (i.e. your filesystem is xfs for example and you don't have xfs support in kernel) Could be many things. > --- Kristian Peters > wrote: > > Hello. > > > > I suspect bad ram. Could you verify with memtest86 > > that your ram is ok ? > > > > *Kristian > > > > kk maddowx wrote: > > > >>EIP; 00000400 Before first symbol <===== > > > Trace; c0127b63 > > > Trace; c0127cd6 > > > Trace; c0127d40 > > > Trace; c0127dd4 > > > Trace; c0127e36 > > > Trace; c0127f51 > > > Trace; c0127eb0 > > > Trace; c010552b > > > > :... [snd.science] ...: > > :: _o) > > :: http://www.korseby.net /\\ > > :: http://gsmp.sf.net _\_V > > :.........................: > > > __________________________________________________ > Do You Yahoo!? > Yahoo! - Official partner of 2002 FIFA World Cup > http://fifaworldcup.yahoo.com > - > 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/ > - 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/