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: <20080718162923.GA6100@bromo.msbb.uc.edu>
Date:	Fri, 18 Jul 2008 12:29:23 -0400
From:	Jack Howarth <howarth@...mo.msbb.uc.edu>
To:	Yinghai Lu <yhlu.kernel@...il.com>
Cc:	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

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.
> 
> BIOS is buggy. it said it need 0-255, but only reserve address range
> for 64 buses
> 
> will resend patch to Ingo and Jesse,
> 
> 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/