Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262606AbUCEO1Z (ORCPT ); Fri, 5 Mar 2004 09:27:25 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262602AbUCEO1Z (ORCPT ); Fri, 5 Mar 2004 09:27:25 -0500 Received: from mx1.redhat.com ([66.187.233.31]:1740 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S262606AbUCEO1G (ORCPT ); Fri, 5 Mar 2004 09:27:06 -0500 Subject: Re: Is there some bug in ext3 in 2.4.25? From: "Stephen C. Tweedie" To: Michael Frank Cc: Marcelo Tosatti , Daniel Fenert , linux-kernel , Michelle Konzack , Stephen Tweedie In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1078496816.14033.56.camel@sisko.scot.redhat.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 05 Mar 2004 14:26:56 +0000 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1057 Lines: 29 Hi, On Fri, 2004-03-05 at 14:14, Michael Frank wrote: > Although I have nt received a reply from LKML, it is definitively > a real kernel bug in 2.4.22 which has been fixed in 2.4.24. > > Ein weiterer Fehler trat mehrfach in 'exit.c' auf, der ebenfals > nach der Installation von Linux 2.4.24 verschwunden war. > > Further bug occuring several times in 'exit.c' has also vanished > after installation of 2.4.24. Sounds like bad memory. It's quite impossible for a bad memory module to show up a problem in one kernel but not in another, simply because kernels are storing their active data in slightly different memory locations from one release to another (or even from one compiler, or one set of config options, to another.) I'd definitely be running memtest86 as the next step here. Cheers, Stephen - 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/