Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752547AbYGSGys (ORCPT ); Sat, 19 Jul 2008 02:54:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751133AbYGSGyl (ORCPT ); Sat, 19 Jul 2008 02:54:41 -0400 Received: from an-out-0708.google.com ([209.85.132.245]:58114 "EHLO an-out-0708.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751045AbYGSGyk (ORCPT ); Sat, 19 Jul 2008 02:54:40 -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=CPypxQH6zmuJe7VvaungU8JUP//Pek0PULc3WL30y4auj+5nmc8OrYJN8yR1uwS3y3 e8HyuLHmSqJPH2GYpiNGpbGRQ4DEgtyql7wGDSu5mbRQNNnjy55cHszkXaqD11vm+BsR 02zsfAiowgu1j7LavyEgDNYakkI+pN2GKOoGc= Message-ID: Date: Fri, 18 Jul 2008 23:54:38 -0700 From: "Justin Mattock" To: "Yinghai Lu" Subject: Re: macbook2,2 latest git mmconfig issues Cc: "Linux Kernel Mailing List" , "Jack Howarth" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <86802c440807182145qa3d17e9k210c498109d86b58@mail.gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2229 Lines: 62 On Fri, Jul 18, 2008 at 10:54 PM, Justin Mattock wrote: > On Fri, Jul 18, 2008 at 9:45 PM, Yinghai Lu wrote: >> On Fri, Jul 18, 2008 at 8:39 PM, Justin Mattock wrote: >>> Hello; >>> Well I couldn't really see what was happening >>> until I could experience this myself; >>> It seems the macbook pro ati chipset >>> is having the same problem as jack was with mmconfig yesterday. >>> I'm confused as to why my system was able to run this kernel(2.6.26.git1) >>> without a problem, now after doing a reinstall of the operating system >>> I am confronted with this same issue. How do I find the 0x3f number on >>> my system, >>> so I could plug that into the patch? to see if I can boot up >>> Now keep in mind the only difference with this install is the >>> installer took a dump >>> therefore you have to manually install grub(could this be the source >>> of the issue?) >>> regards; >> >> can you disable ASPM in your config.? >> >> YH >> > > I enabled and disabled in the pci section > PCIEASPM still the same results. > applied the patch as well i.g. > mmconf_dmi_table > going to try detect end_bus_number patch to > see if it works > -- > Justin P. Mattock > applied both patches and messed with boot options but no go: this is what I'm seeing PCI: Fatal no config space access function found ata-piix 0000:00:1f11 device not available because of BAR0 [0xf0-0x1f7] collisions interesting how this kernel was running fine, and then BAM all of a sudden f*&^ed up, This tells me that this was something happening a while ago, or always happening just not noticed i.g. I plugged in 2.6.25-rc9(my favorite) and it too was giving the same response. after tracing back my steps the only application that might be causing this or hiding this is grub but could be wrong. any ideas or patches would be appreciated, until further notice I'll be using osx until there is a regards; : ( -- Justin P. Mattock -- 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/