From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751968AbYFULuB (ORCPT ); Sat, 21 Jun 2008 07:50:01 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750896AbYFULtw (ORCPT ); Sat, 21 Jun 2008 07:49:52 -0400 Received: from an-out-0708.google.com ([209.85.132.244]:9643 "EHLO an-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750800AbYFULtv (ORCPT ); Sat, 21 Jun 2008 07:49:51 -0400 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; b=j8lFArcDbbq9qsUH+OtdvTsWsj6aBbyuv4tUyh+32y7qbTZWKRdS4JmXBRV4lYtP2Q Uryt6qyENn/yTKPzoG3NTeFQhx8H2a/yEAZDYHNfQbN8FwfnXDot0qsExhumU18IwxEo sCxrYm9zJBAGx5pk5TFC8ZqESzelvekn2LEaU= Message-ID: <485CEAD9.10401@gmail.com> Date: Sat, 21 Jun 2008 08:49:45 -0300 From: Kevin Winchester User-Agent: Thunderbird 2.0.0.14 (X11/20080505) MIME-Version: 1.0 To: Yinghai Lu CC: Ingo Molnar , Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , Linux Kernel Mailing List , "Rafael J. Wysocki" , Pavel Machek Subject: Re: Bisecting tip/auto-x86-next? References: <485AFC9B.7090502@gmail.com> <20080620153626.GE17373@elte.hu> <485C4484.3080706@gmail.com> <86802c440806201714p271b7b3fx68183c5f48208bee@mail.gmail.com> <485CD12C.9080404@gmail.com> <86802c440806210318p23fc61bo709c0965254de72@mail.gmail.com> <86802c440806210330r25529b93u9c57734ad4fce58d@mail.gmail.com> <485CDA6A.103@gmail.com> <86802c440806210350y2f05999fme0eba7ca6aca201a@mail.gmail.com> In-Reply-To: <86802c440806210350y2f05999fme0eba7ca6aca201a@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Yinghai Lu wrote: > On Sat, Jun 21, 2008 at 3:39 AM, Kevin Winchester > wrote: >> Yinghai Lu wrote: >>> On Sat, Jun 21, 2008 at 3:23 AM, Kevin Winchester >>> wrote: >>>> On Sat, Jun 21, 2008 at 7:18 AM, Yinghai Lu >>>> wrote: >>>>> On Sat, Jun 21, 2008 at 3:00 AM, Kevin Winchester >>>>> wrote: >>>>>> Yinghai Lu wrote: >>>>>>> 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. >>>>>>> >>>>>> "debug" in the command line doesn't seem to have any effect on the >>>>>> printout >>>>>> (is there some config option I need to use with it?), but here it is >>>>>> anyway: >>>>> are you using tip/master? >>>>> >>>>> http://people.redhat.com/mingo/sched-devel.git/README >>>>> >>>> That log is from tip/x86/gart, which is where the problem patch was >>>> bisected. Would you get better debugging info from tip/master (which >>>> includes tip/x86/gart, I believe, and thus would show the problem as >>>> well)? >>> tip/master doesn't work? >>> >> I will check tip/master now, but I believe it doesn't work. >> >> I will also correct myself, the log I sent you was from: >> >> 8c9fd91... x86: checking aperture size order >> > > please try attached patch... > Thanks for the patch. it fixes the problem for me. tip/master was indeed showing the problem as well, but it does not once your patch is applied. So you can add a: Tested-by: Kevin Winchester to the patch if you want. Thanks again, -- Kevin Winchester