From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Jack Howarth" <howarth@bromo.msbb.uc.edu>
Cc: "Justin Mattock" <justinmattock@gmail.com>,
"Ingo Molnar" <mingo@elte.hu>,
"Barnes, Jesse" <jesse.barnes@intel.com>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.26-rc9-git9 doesn't boot on Macintel
Date: Wed, 16 Jul 2008 15:35:17 -0700 [thread overview]
Message-ID: <86802c440807161535n3a4d6891n6f7c16bd4e1f19c3@mail.gmail.com> (raw)
In-Reply-To: <86802c440807161029n7e0dac98x1ec260879204b6f0@mail.gmail.com>
On Wed, Jul 16, 2008 at 10:29 AM, Yinghai Lu <yhlu.kernel@gmail.com> wrote:
> On Wed, Jul 16, 2008 at 7:08 AM, Jack Howarth <howarth@bromo.msbb.uc.edu> wrote:
>> Yunghai,
>> I had partial success with your proposed patch. The MacPro2
>> identifier doesn't appear to be correct for a second generation
>> MacBook Pro so I had to comment out the line...
>>
>> DMI_MATCH(DMI_PRODUCT_NAME, "MacPro2"),
>>
>> With that change, a patched 2.6.26-git2 kernel now uses MMCONFIG.
>> However I still see the same hang. The boot messages I see on
>> screen are...
>>
>> ACPI: bus type pci registered
>> PCI: MCFG configuration 0: base f0000000 segment 0 buses 0 - 63
>> PCI: MCFG area at f0000000 reserved in E820
>> PCI: Using MMCONFIG at f0000000 - f3ffffff
>> PCI: Using configuration type 1 for base access
>> ACPI: EC: EC description table is found, configuring boot EC
>> ACPI: EC: non-query interrupt received, switching to interrupt mode
>
> something wrong here
>
>> ACPI: BIOS_OSI(Linux) query ignored via DMI
>> ACPI: Interpreter enabled
>> ACPI: (S0 S3 S4 S5)
>> ACPI: Using IOAPIC for interrupt routing
>> ACPI: EC: GPE = 0x17, I/O: command/status = 0x66, data = 0x62
>> ACPI: EC: drivers started in interrupt mode
>> ACPI: PCI Root Bridge [PCI0] (0000.00)
>> pci 0000:00:1f.00 : quirk region 0400-047f claimed by ICH6 ACPI/GPIO/TCO
>> pci 0000.00:1f:00 : quirk region 0500-053f claimed by ICH6 GPIO
>>
>> ...at which the boot hangs. On the positive side, I was able to fully
>> boot if I passed 'pci=noacpi' to the kernel options (which never worked
>> before with 2.6.26).
>> I can post the dmesg from a noacpi boot of the
>> patched kernel to my bugzilla report tonight if it would help debug the
>> issues we are still seeing with ACPI.
>
> that will help.
>
>> One thing I notice with the patched kernel (without noacpi) is that I
>> only see buses 0 - 63. A normal boot of 2.6.25.10 on this machine (or
>> 2.6.26 reportedly on a MacMini) always shows buses 0 - 255.
>
> that is right
>
>> Could this
>> be related to the ACPI breakage? Let me know if I can do anything
>> else to debug the ACPI issues under MMCONFIG.
>
> please boot with
> debug apic=verbose pci=routeirq
>
please check latest linus tree.
the commit could be related.
commit c91d924e3af08d4f98eab6ebf81f2b8ce132448f
Author: Bob Moore <robert.moore@intel.com>
Date: Tue Jun 10 12:38:10 2008 +0800
ACPICA: Fix for hang on GPE method invocation
Fixes problem where the new method argument count validation mechanism
will enter an infinite loop when a GPE method is dispatched.
Problem fixed be removing the obsolete code that passes GPE block
information to the notify handler via the control method parameter pointer.
YH
next prev parent reply other threads:[~2008-07-16 22:35 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-15 19:52 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 [this message]
[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
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=86802c440807161535n3a4d6891n6f7c16bd4e1f19c3@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=howarth@bromo.msbb.uc.edu \
--cc=jesse.barnes@intel.com \
--cc=justinmattock@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®