Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932266AbXFEJeI (ORCPT ); Tue, 5 Jun 2007 05:34:08 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761487AbXFEJd4 (ORCPT ); Tue, 5 Jun 2007 05:33:56 -0400 Received: from mx3.mail.elte.hu ([157.181.1.138]:52084 "EHLO mx3.mail.elte.hu" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1759042AbXFEJdz (ORCPT ); Tue, 5 Jun 2007 05:33:55 -0400 Date: Tue, 5 Jun 2007 11:33:49 +0200 From: Ingo Molnar To: Andrew Morton Cc: linux-kernel@vger.kernel.org Subject: Re: 2.6.22-rc3-mm1 Message-ID: <20070605093349.GA24956@elte.hu> References: <20070530235823.793f00d9.akpm@linux-foundation.org> <20070605091151.GA18385@elte.hu> <20070605022411.f303d28b.akpm@linux-foundation.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070605022411.f303d28b.akpm@linux-foundation.org> User-Agent: Mutt/1.5.14 (2007-02-12) X-ELTE-VirusStatus: clean X-ELTE-SpamScore: -2.0 X-ELTE-SpamLevel: X-ELTE-SpamCheck: no X-ELTE-SpamVersion: ELTE 2.0 X-ELTE-SpamCheck-Details: score=-2.0 required=5.9 tests=BAYES_00 autolearn=no SpamAssassin version=3.1.7 -2.0 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1403 Lines: 34 * Andrew Morton wrote: > On Tue, 5 Jun 2007 11:11:51 +0200 Ingo Molnar wrote: > > > hm, mm1 hangs during bootup on one of my boxes: > > > > Calling initcall 0xc0628d39: pci_mmcfg_late_insert_resources+0x0/0x44() > > initcall 0xc0628d39: pci_mmcfg_late_insert_resources+0x0/0x44() returned 0. > > initcall 0xc0628d39 ran for 0 msecs: > > pci_mmcfg_late_insert_resources+0x0/0x44() > > Calling initcall 0xc062abd1: tcp_congestion_default+0x0/0xf() > > initcall 0xc062abd1: tcp_congestion_default+0x0/0xf() returned 0. > > initcall 0xc062abd1 ran for 0 msecs: tcp_congestion_default+0x0/0xf() > > > > it usually hangs in different places. > > In my experience that means that it wedged in a timer tick. Often the > first one. yeah. I tried !hres and !dynticks too and that doesnt make any difference to the end result - so my guess is on the NMI watchdog re-programming thing on K8 CPUs (running the 32-bit kernel), which is done in every NMI tick. check_watchdog() for some reason thought there's no NMI, and later on an NMI still arrived? Something like that. vanilla kernel works fine. Ingo - 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/