From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1030315AbWGFRbT (ORCPT ); Thu, 6 Jul 2006 13:31:19 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1030320AbWGFRbT (ORCPT ); Thu, 6 Jul 2006 13:31:19 -0400 Received: from e2.ny.us.ibm.com ([32.97.182.142]:55504 "EHLO e2.ny.us.ibm.com") by vger.kernel.org with ESMTP id S1030315AbWGFRbS (ORCPT ); Thu, 6 Jul 2006 13:31:18 -0400 Subject: Re: 2.6.17-mm6 From: john stultz To: Alistair John Strachan Cc: Greg KH , Andrew Morton , linux-kernel@vger.kernel.org In-Reply-To: <200607052332.13028.s0348365@sms.ed.ac.uk> References: <20060703030355.420c7155.akpm@osdl.org> <1152131834.24656.57.camel@cog.beaverton.ibm.com> <20060705204614.GA24181@kroah.com> <200607052332.13028.s0348365@sms.ed.ac.uk> Content-Type: text/plain Date: Thu, 06 Jul 2006 10:31:13 -0700 Message-Id: <1152207073.24656.127.camel@cog.beaverton.ibm.com> Mime-Version: 1.0 X-Mailer: Evolution 2.2.3 (2.2.3-4.fc4) Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2006-07-05 at 23:32 +0100, Alistair John Strachan wrote: > On Wednesday 05 July 2006 21:46, Greg KH wrote: > > On Wed, Jul 05, 2006 at 01:37:13PM -0700, john stultz wrote: > > > On Tue, 2006-07-04 at 01:49 -0700, Andrew Morton wrote: > > > > On Tue, 4 Jul 2006 09:34:14 +0100 > > > > > > > > Alistair John Strachan wrote: > > > > > > a tested version... > > > > > > > > > > This one worked, thanks. Try the same URL again, I've uploaded two > > > > > better shots 6,7 that capture the first oops. Unfortunately, I have a > > > > > pair of oopses that interchange every couple of boots, so I've > > > > > included both ;-) > > > > > > > > OK, that's more like it. Thanks again. > > > > > > > > http://devzero.co.uk/~alistair/oops-20060703/oops6.jpg > > > > http://devzero.co.uk/~alistair/oops-20060703/oops7.jpg > > > > > > > > People cc'ed. Help! > > > > > > Hmmm. No clue on this one from just looking at it. > > > > > > Greg, do you see anything wrong with the way I'm registering the > > > timekeeping .resume hook in kernel/timer.c::timekeeping_init_device()? > > > It looks the same as the other users to me. > > > > At first glance, no, it looks sane to me. > > > > Are you sure you aren't registering two things with the same name > > somehow? Looking at it, I don't see how that could happen. > Whatever it is, it doesn't happen every time. Sometimes the kernel boots. Odd. Does this happen w/ 2.6.18-rc1? thanks -john