Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1759484AbYFUAOq (ORCPT ); Fri, 20 Jun 2008 20:14:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755139AbYFUAOi (ORCPT ); Fri, 20 Jun 2008 20:14:38 -0400 Received: from rv-out-0506.google.com ([209.85.198.228]:56295 "EHLO rv-out-0506.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753153AbYFUAOh (ORCPT ); Fri, 20 Jun 2008 20:14:37 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=n5fKa8zkcLcojAbU1MwZZh5DcJGRSJqA1/2K+hcl7u6IX+bCFAiJgtdRDfkm0E9Lkm G76eTk9m1zuCyslgJntWKvFyS7cOfelQnS5j/l0l7VWMUAWubHx9sOwamrFRo1U8IVpf pfBapw7Dc9gM+CX1fP56e8R9CxkeTjpLDK1Ok= Message-ID: <86802c440806201714p271b7b3fx68183c5f48208bee@mail.gmail.com> Date: Fri, 20 Jun 2008 17:14:36 -0700 From: "Yinghai Lu" To: "Kevin Winchester" Subject: Re: Bisecting tip/auto-x86-next? Cc: "Ingo Molnar" , "Ingo Molnar" , "Thomas Gleixner" , "H. Peter Anvin" , "Linux Kernel Mailing List" , "Rafael J. Wysocki" , "Pavel Machek" In-Reply-To: <485C4484.3080706@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <485AFC9B.7090502@gmail.com> <20080620101722.GD17692@elte.hu> <20080620153626.GE17373@elte.hu> <485C4484.3080706@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2832 Lines: 73 On Fri, Jun 20, 2008 at 5:00 PM, Kevin Winchester wrote: > Ingo Molnar wrote: >> >> * Kevin Winchester wrote: >> >>>> hm, could you send me the config that triggered this? >>> >>> I will do so tonight when I am home again. It is a UP AMD64 box with a >>> VIA chipset, if that helps. >>> >>>> btw., you can probably ignore this one safely. Also please tell me at >>>> which commit ID you were at when you triggered this warning. >>> >>> Good to know - I will get the commit ID tonight as well, although >>> wouldn't following the same bisection sequence that I did give you the same >>> bisection point? I guess that would assume that linus/master and >>> auto-x86-next haven't changed much since last night, which might not be >>> correct. >> >> yeah, you'd probably not hit that warning with the x86/gart bisection >> sequence. (Assuming the bug is introduced in that branch - so you should >> first check whether pure x86/gart kernel triggers the problem too.) >> >> If you still have the commit ID around then please send it - if you dont, >> no problem, it's no big issue. I wanted to check how wide the bisection >> window is where the warning triggers. >> > > I'm sorry - I accidentally checkout out x86/gart to test it before grabbing > the commit ID. > > I went ahead with the bisection and found: > > > > 8c9fd91a0dc503f085169d44f4360be025f75224 is first bad commit > commit 8c9fd91a0dc503f085169d44f4360be025f75224 > Author: Yinghai Lu > Date: Sun Apr 13 18:42:31 2008 -0700 > > x86: checking aperture size order > > some systems are using 32M for gart and agp when memory is less than 4G. > Kernel will reject and try to allcate another 64M that is not needed, > and we will waste 64M of perfectly good RAM. > > this patch adds a workaround by checking aper_base/order between NB and > agp bridge. If they are the same, and memory size is less than 4G, it > will allow it. > > Signed-off-by: Yinghai Lu > Signed-off-by: Ingo Molnar > Signed-off-by: Thomas Gleixner > > :040000 040000 848d6e4045a14d01fc0a794d4350d8a84f3ceff6 > 4a10a52b41309060cd5dc1bf0c322f6d43b2477b M arch > :040000 040000 aa1cee87b1f5b1b30ed03ce6164ad7f404fef2a3 > f9ce0aaa1f7d4fdc7bdc5a43285495db53a6f531 M drivers > > > as the first bad commit. I do not have time to look at the patch right now, > but in case anyone else does, I figured I would post it. > please send out whole boot logs with "debug" in command line. YH -- 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/