From: Jack Howarth <howarth@bromo.msbb.uc.edu>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@elte.hu>,
"jbarnes@virtuousgeek.org" <jbarnes@virtuousgeek.org>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: 2.6.26-rc9-git9 doesn't boot on Macintel
Date: Thu, 17 Jul 2008 21:46:23 -0400 [thread overview]
Message-ID: <20080718014623.GA31111@bromo.msbb.uc.edu> (raw)
In-Reply-To: <86802c440807171825m24ffe140o81bb76286823568e@mail.gmail.com>
YH,
I did some googling and it looks like the dmicode should
be MacBookPro2...
http://www.odi.ch/prog/macbookpro/dmi.txt
Building a test kernel with that code in the mmconfig patch now.
Jack
On Thu, Jul 17, 2008 at 06:25:43PM -0700, Yinghai Lu wrote:
> On Thu, Jul 17, 2008 at 6:15 PM, Jack Howarth <howarth@bromo.msbb.uc.edu> wrote:
> > YH,
> > Success. It turns out that if I unset CONFIG_PCIEASPM when
> > I build 2.6.26 the hangs on boot are eliminated.
>
> good to know
>
> > I am currently
> > booted under the current fedora development 2.6.27-0.156.rc0.git4
> > with that change and everything is working fine.
> > I've not had any luck with pci_early_config_dump. If I just pass
> > that kernel option, it doesn't complain but it doesn't seem to
> > produce any additional output in dmesg. Do I need any other kernel
> > options for pci_early_config_dump to work?
> shoud be pci=early_config_dump
>
> > I will apply your mmconfig
> > patch next and test how well MMCONFIG works on my MacBook Pro.
>
> also please send out dmidecode printout, so i could update patch to
> apply dmi quirk to that model only.
>
> YH
next prev parent reply other threads:[~2008-07-18 1:46 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 19:52 2.6.26-rc9-git9 doesn't boot on Macintel Justin Mattock
[not found] ` <20080715231118.GA26807@bromo.msbb.uc.edu>
2008-07-16 0:26 ` Justin Mattock
[not found] ` <20080716012427.GA27398@bromo.msbb.uc.edu>
2008-07-16 3:05 ` Justin Mattock
[not found] ` <20080716035830.GA27935@bromo.msbb.uc.edu>
2008-07-16 5:30 ` Justin Mattock
2008-07-16 7:44 ` Yinghai Lu
2008-07-16 7:50 ` Justin Mattock
2008-07-16 8:36 ` Yinghai Lu
2008-07-16 14:08 ` Jack Howarth
2008-07-16 15:12 ` Justin Mattock
2008-07-16 17:30 ` Yinghai Lu
2008-07-16 17:29 ` Yinghai Lu
2008-07-16 22:35 ` Yinghai Lu
[not found] ` <20080717004004.GA17792@bromo.msbb.uc.edu>
2008-07-17 0:49 ` Yinghai Lu
2008-07-17 1:21 ` Jack Howarth
2008-07-17 2:29 ` Yinghai Lu
2008-07-17 2:40 ` Jack Howarth
2008-07-17 1:25 ` Justin Mattock
2008-07-17 2:35 ` Jack Howarth
2008-07-17 2:59 ` Yinghai Lu
2008-07-17 3:15 ` Jack Howarth
2008-07-17 4:04 ` Yinghai Lu
2008-07-17 3:44 ` Jack Howarth
2008-07-17 4:13 ` Yinghai Lu
2008-07-17 6:18 ` Jack Howarth
2008-07-17 6:48 ` Yinghai Lu
2008-07-17 11:56 ` Jack Howarth
2008-07-17 12:47 ` Jack Howarth
2008-07-17 14:13 ` Jack Howarth
2008-07-17 16:26 ` Jack Howarth
2008-07-17 16:42 ` Yinghai Lu
2008-07-17 18:39 ` Justin Mattock
[not found] ` <20080717195039.GA28694@bromo.msbb.uc.edu>
2008-07-17 22:09 ` Justin Mattock
2008-07-18 1:15 ` Jack Howarth
2008-07-18 1:25 ` Yinghai Lu
2008-07-18 1:46 ` Jack Howarth [this message]
2008-07-18 3:06 ` Jack Howarth
2008-07-18 6:09 ` Jack Howarth
2008-07-18 6:22 ` Yinghai Lu
2008-07-18 12:02 ` Jack Howarth
2008-07-18 12:09 ` Jack Howarth
2008-07-18 16:19 ` Yinghai Lu
2008-07-18 16:29 ` Jack Howarth
2008-07-18 16:36 ` Yinghai Lu
2008-07-18 18:20 ` Justin Mattock
2008-07-18 18:45 ` Yinghai Lu
2008-07-18 18:56 ` Justin Mattock
2008-07-18 16:07 ` Jack Howarth
2008-07-18 16:17 ` Yinghai Lu
2008-07-16 22:51 ` Yinghai Lu
-- strict thread matches above, loose matches on Subject: below --
2008-07-15 14:17 Jack Howarth
2008-07-15 2:00 Jack Howarth
2008-07-15 2:04 ` Justin Mattock
2008-07-14 13:51 Jack Howarth
2008-07-14 16:26 ` Justin Mattock
2008-07-14 17:02 ` Stefan Richter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080718014623.GA31111@bromo.msbb.uc.edu \
--to=howarth@bromo.msbb.uc.edu \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.