Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030652AbXAYX4i (ORCPT ); Thu, 25 Jan 2007 18:56:38 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030653AbXAYX4i (ORCPT ); Thu, 25 Jan 2007 18:56:38 -0500 Received: from mtaout01-winn.ispmail.ntl.com ([81.103.221.47]:36087 "EHLO mtaout01-winn.ispmail.ntl.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1030652AbXAYX4h convert rfc822-to-8bit (ORCPT ); Thu, 25 Jan 2007 18:56:37 -0500 Date: Thu, 25 Jan 2007 23:56:27 +0000 From: Ken Moffat To: Randy Dunlap Cc: Len Brown , linux-kernel@vger.kernel.org Subject: Re: x86 instability with 2.6.1{8,9} Message-ID: <20070125235627.GA17168@deepthought> References: <20070101160158.GA26547@deepthought> <200701021225.57708.lenb@kernel.org> <20070102180425.GA18680@deepthought> <200701021342.32195.lenb@kernel.org> <20070102193459.GA19894@deepthought> <20070106140459.a6b72039.randy.dunlap@oracle.com> <20070107142641.GA30379@deepthought> <20070115162911.GA13198@deepthought> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20070115162911.GA13198@deepthought> User-Agent: Mutt/1.5.12-2006-07-14 Content-Transfer-Encoding: 8BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1309 Lines: 28 On Mon, Jan 15, 2007 at 04:29:11PM +0000, Ken Moffat wrote: > > Today, I've built 2.6.19.2 without highmem (the box only has 1GB, > dunno why I'd included that in the original config) and I will > continue to wait patiently for either a week without problems, or > something that I can manage to note - although I think at the moment > that the second coming of the great prophet Zarquon is more likely. > Bizarre - it panic'd again last Thursday while I was in X, but I still didn't manage to log any output. At the weekend, I had the bright idea of using chattr +j on the syslog to try to journal any data, since then it has been fine. So, it isn't down to highmem, and I still can't trigger it reliably, or get any trace. Tried running as x86_64 this morning (because cold starts on Thursdays seem particularly problematic, perhaps it's a time/power-supply-noise problem), then x86 from a cold start this afternoon. Time to hope it won't bite me too often, and move on to testing 2.6.20-rc6. Ken -- das eine Mal als Trag?die, das andere Mal als Farce - 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/