From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932262AbWGGUtQ (ORCPT ); Fri, 7 Jul 2006 16:49:16 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751251AbWGGUtQ (ORCPT ); Fri, 7 Jul 2006 16:49:16 -0400 Received: from smtp.nildram.co.uk ([195.112.4.54]:22028 "EHLO smtp.nildram.co.uk") by vger.kernel.org with ESMTP id S1751249AbWGGUtP (ORCPT ); Fri, 7 Jul 2006 16:49:15 -0400 From: Alistair John Strachan To: Greg KH Subject: Re: 2.6.17-mm6 Date: Fri, 7 Jul 2006 21:48:08 +0100 User-Agent: KMail/1.9.3 Cc: john stultz , Andrew Morton , linux-kernel@vger.kernel.org References: <20060703030355.420c7155.akpm@osdl.org> <200607062102.50284.s0348365@sms.ed.ac.uk> <20060706201108.GA493@kroah.com> In-Reply-To: <20060706201108.GA493@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200607072148.08567.s0348365@sms.ed.ac.uk> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Thursday 06 July 2006 21:11, Greg KH wrote: > On Thu, Jul 06, 2006 at 09:02:50PM +0100, Alistair John Strachan wrote: > > On Thursday 06 July 2006 18:31, john stultz wrote: > > > 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. > > > > I don't think it's John's code. I commented out the sysfs registration > > code from timekeeping_init_device() and the kernel gets further, where it > > crashes on kmem_cache_create. SLAB also complains about "losing its name" > > and being "of size 0". > > > > This happens identically on 2.6.18-rc1, and 2.6.17-mm6. Greg, could it be > > anything you've changed recently? I considered bisectioning -mm, but > > there's been a lot of RAID problems and I'm using RAID5. > > Please bisect 2.6.18-rc1 if you have git, as the problem is there, and > would be good to track down. I tried this, but it's extremely difficult when the kernel boots successfully one every four times. I've already been thrown off the scent twice, bringing my bisection count to 25.. I think I'll try an allnoconfig on this machine, hopefully that will boot, then I just start enabling things again until it breaks. -- Cheers, Alistair. Third year Computer Science undergraduate. 1F2 55 South Clerk Street, Edinburgh, UK.