From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S264451AbTLGQY3 (ORCPT ); Sun, 7 Dec 2003 11:24:29 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S264452AbTLGQY3 (ORCPT ); Sun, 7 Dec 2003 11:24:29 -0500 Received: from web40514.mail.yahoo.com ([66.218.78.131]:51269 "HELO web40514.mail.yahoo.com") by vger.kernel.org with SMTP id S264451AbTLGQYZ (ORCPT ); Sun, 7 Dec 2003 11:24:25 -0500 Message-ID: <20031207162424.25571.qmail@web40514.mail.yahoo.com> Date: Sun, 7 Dec 2003 08:24:24 -0800 (PST) From: Alex Davis Subject: Re: 2.4.23 hard lock, 100% reproducible. To: Mark Symonds , linux-kernel@vger.kernel.org In-Reply-To: <03e201c3bc94$6b1a1900$7a01a8c0@gandalf> 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 Would it be possible to swap the RAM from another machine? --- Mark Symonds wrote: > > > I had the exact same thing happen to me about > > a year ago, with the same error message. It > > started after I had upraded my kernel. It > > turned out one of my RAM sticks had gone > > bad. Do you have another machine you can > > test 2.4.23 with? > > > > I do, but not with identical hardware. Thing is > it ran just fine for months on previous kernels, > and even now will run just fine with them. The > crashing only happens when using 2.4.23. > > -- > Mark > ===== I code, therefore I am __________________________________ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/