From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263775AbTLGHdm (ORCPT ); Sun, 7 Dec 2003 02:33:42 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263765AbTLGHdm (ORCPT ); Sun, 7 Dec 2003 02:33:42 -0500 Received: from ca1.symonds.net ([66.92.42.136]:22024 "EHLO symonds.net") by vger.kernel.org with ESMTP id S263775AbTLGHde (ORCPT ); Sun, 7 Dec 2003 02:33:34 -0500 Message-ID: <03e201c3bc94$6b1a1900$7a01a8c0@gandalf> From: "Mark Symonds" To: "Alex Davis" , References: <20031207065017.48483.qmail@web40506.mail.yahoo.com> Subject: Re: 2.4.23 hard lock, 100% reproducible. Date: Sat, 6 Dec 2003 23:33:33 -0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > 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