From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Jack Howarth" <howarth@bromo.msbb.uc.edu>
Cc: "Ingo Molnar" <mingo@elte.hu>,
"Thomas Gleixner" <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
jbarnes@virtuousgeek.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86,pci: dmi check for mackpro 2.2 mmconf
Date: Fri, 18 Jul 2008 21:45:08 -0700 [thread overview]
Message-ID: <86802c440807182145s58ce6cb2xfc85a6fc849a2a73@mail.gmail.com> (raw)
In-Reply-To: <20080719032845.GA9662@bromo.msbb.uc.edu>
On Fri, Jul 18, 2008 at 8:28 PM, Jack Howarth <howarth@bromo.msbb.uc.edu> wrote:
> YH,
> The mmconf_end_bus_num_detect.patch and mmconf_end_bus_num_detect_fix.patch both applied
> cleanly to the current linus kernel git and solve my problems with MMCONFIG not starting.
> I am attaching a dmesg log below of a boot with 'debug apic=verbose initcall_debug pci=routeirq'.
> If you look at the section immediately before the line...
>
> pci 0000:00:1e.0: transparent bridge
>
> you will see that it is radically different from what I posted for the freeze under PCIEASPM
> with MMCONFIG (using your original mmconfig patch)...
calling pci_arch_init+0x0/0x53
PCI: MCFG configuration 0: base f0000000 segment 0 buses 0 - 255
PCI: MCFG area at f0000000 reserved in E820
PCI: updated MCFG configuration 0: base f0000000 segment 0 buses 0 - 63
PCI: Using MMCONFIG at f0000000 - f3ffffff
PCI: Using configuration type 1 for base access
initcall pci_arch_init+0x0/0x53 returned 0 after 14 msecs
that mean it reduce the bus number according to e820 reserved area.
YH
next prev parent reply other threads:[~2008-07-19 4:45 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-18 16:41 Yinghai Lu
2008-07-18 16:50 ` Jack Howarth
2008-07-18 17:44 ` H. Peter Anvin
2008-07-18 17:47 ` Yinghai Lu
2008-07-18 17:49 ` H. Peter Anvin
2008-07-18 17:54 ` Yinghai Lu
2008-07-18 20:19 ` Ingo Molnar
2008-07-18 20:21 ` Yinghai Lu
2008-07-18 20:21 ` Ingo Molnar
2008-07-18 20:26 ` Yinghai Lu
2008-07-19 0:58 ` Jack Howarth
2008-07-19 1:22 ` Yinghai Lu
2008-07-19 3:28 ` Jack Howarth
2008-07-19 3:43 ` Justin Mattock
2008-07-19 4:45 ` Yinghai Lu [this message]
2008-07-19 5:12 ` Jack Howarth
2008-07-19 5:28 ` Yinghai Lu
2008-07-19 17:26 ` Jesse Barnes
2008-07-19 18:19 ` Jack Howarth
2008-07-19 18:40 ` Jack Howarth
2008-07-19 19:04 ` Jesse Barnes
2008-07-19 19:14 ` Jack Howarth
2008-07-21 6:49 ` Shaohua Li
2008-07-22 21:15 ` Jesse Barnes
2008-07-18 20:22 ` [PATCH] x86,pci: detect end_bus_number according to acpi/e820 reserved Yinghai Lu
2008-07-18 20:48 ` Ingo Molnar
2008-07-18 21:48 ` Jack Howarth
2008-07-18 22:27 ` Yinghai Lu
2008-07-18 22:42 ` Jesse Barnes
2008-07-20 6:48 ` Ingo Molnar
2008-07-19 9:16 ` [PATCH] x86,pci: detect end_bus_number according to acpi/e820 reserved - fix Yinghai Lu
2008-07-20 6:44 ` Ingo Molnar
2008-07-22 23:37 [PATCH] x86,pci: dmi check for mackpro 2.2 mmconf Jack Howarth
2008-07-23 0:23 ` Jesse Barnes
2008-07-23 1:00 ` Jack Howarth
2008-07-23 1:32 ` Jesse Barnes
2008-07-23 1:41 ` Jack Howarth
2008-07-23 1:54 ` Shaohua Li
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=86802c440807182145s58ce6cb2xfc85a6fc849a2a73@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=howarth@bromo.msbb.uc.edu \
--cc=hpa@zytor.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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®