linux-kernel - Re: 2.6.26-rc9-git9 doesn't boot on Macintel

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <dd18b0c30807181120r4462e904t94d37dbd383995ba@mail.gmail.com>
Date:	Fri, 18 Jul 2008 18:20:47 +0000
From:	"Justin Mattock" <justinmattock@...il.com>
To:	"Yinghai Lu" <yhlu.kernel@...il.com>
Cc:	"Jack Howarth" <howarth@...mo.msbb.uc.edu>,
	"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
	"Ingo Molnar" <mingo@...e.hu>,
	"jbarnes@...tuousgeek.org" <jbarnes@...tuousgeek.org>,
	"Thomas Gleixner" <tglx@...utronix.de>
Subject: Re: 2.6.26-rc9-git9 doesn't boot on Macintel

On Fri, Jul 18, 2008 at 4:36 PM, Yinghai Lu <yhlu.kernel@...il.com> wrote:
> On Fri, Jul 18, 2008 at 9:29 AM, Jack Howarth <howarth@...mo.msbb.uc.edu> wrote:
>> YH,
>>   I'll file a radar bug report on this with Apple but wouldn't
>> hold my breath for them to fix the firmware. Also, it would be
>> a good idea to encourage all of the folks using 2.6.26 on
>> Macintel to watch out for the "MMCONFIG not used" message in
>> their dmesg and report that to you. I strongly suspect that
>> the MacBook Pro v2 isn't the only model with broken firmware.
>>                   Jack
>>
>> On Fri, Jul 18, 2008 at 09:19:19AM -0700, Yinghai Lu wrote:
>>> On Fri, Jul 18, 2008 at 5:09 AM, Jack Howarth <howarth@...mo.msbb.uc.edu> wrote:
>>> > YH,
>>> >   Do you see anything in the pci earlydump and the associated lspci --vvxxxx
>>> > output that sheds any light on why we have to clean up the dmi with your
>>> > mmconfig patch on a MacBookPro2? I am wondering if the BIOS information is
>>> > being misused by the linux kernel or if the BIOS is just buggy.
>
> it only happened when 3G ram installed.
>
> when 2G installed, it will use [0xe0000000 - 0xf0000000), for bus [0,255]
> and that is ok
>
> YH
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>

Where might us mac users locate a custom
dsdt to try?


-- 
Justin P. Mattock
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/