From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: "Jack Howarth" <howarth@bromo.msbb.uc.edu>
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: Wed, 16 Jul 2008 21:13:28 -0700 [thread overview]
Message-ID: <86802c440807162113g4cea3bd9ic71210330417032b@mail.gmail.com> (raw)
In-Reply-To: <20080717034418.GA18951@bromo.msbb.uc.edu>
[-- Attachment #1: Type: text/plain, Size: 1323 bytes --]
On Wed, Jul 16, 2008 at 8:44 PM, Jack Howarth <howarth@bromo.msbb.uc.edu> wrote:
> YH,
> Okay, I can confirm that 2.6.25.10 boots okay with pci=nommconf
> which does disable MMCONFIG. It also works fine by default with
> MMCONFIG enabled. So there may be two possibly unrelated problems
> in 2.6.26. The first being that MMCONFIG doesn't start up properly
> without your patch and the second being that with or without
> MMCONFIG, the boot process hangs just before when the line...
>
> PCI: Transparent bridge - 0000:00:1e.0
please set CONFIG_PCI_DEBUG in your .config and apply attach two patches
should get sth like
calling acpi_pci_root_init+0x0/0x54
ACPI: PCI Root Bridge [PCI0] (0000:00)
PCI: Scanning bus 0000:00
PCI: Found 0000:00:00.0 [10de/005e] 000580 00
PCI: Found 0000:00:01.0 [10de/0051] 000601 00
pci 0000:00:01.0: calling nvidia_force_enable_hpet+0x0/0xe7
PCI: Found 0000:00:01.1 [10de/0052] 000c05 00
PCI: 0000:00:01.1 reg 10 io port: [ee00, ee1f]
PCI: 0000:00:01.1 reg 20 io port: [ed00, ed3f]
PCI: 0000:00:01.1 reg 24 io port: [ed40, ed7f]
PCI: Found 0000:00:02.0 [10de/005a] 000c03 00
PCI: 0000:00:02.0 reg 10 32bit mmio: [fdeff000, fdefffff]
PCI: Found 0000:00:02.1 [10de/005b] 000c03 00
PCI: 0000:00:02.1 reg 10 32bit mmio: [fdefec00, fdefecff]
PCI: Found 0000:00:06.0 [10de/0053] 000101 00
YH
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: debug_extra_pci_bus_res.patch --]
[-- Type: text/x-patch; name=debug_extra_pci_bus_res.patch, Size: 1299 bytes --]
Index: linux-2.6/drivers/pci/setup-bus.c
===================================================================
--- linux-2.6.orig/drivers/pci/setup-bus.c
+++ linux-2.6/drivers/pci/setup-bus.c
@@ -537,6 +537,36 @@ void __ref pci_bus_assign_resources(stru
}
EXPORT_SYMBOL(pci_bus_assign_resources);
+static void pci_bus_dump_res(struct pci_bus *bus)
+{
+ int i;
+
+ for (i = 0; i < PCI_BUS_NUM_RESOURCES; i++) {
+ struct resource *res = bus->resource[i];
+ if (!res)
+ continue;
+
+ printk(KERN_INFO "bus: %02x index %x %s: [%llx, %llx]\n", bus->number, i, (res->flags & IORESOURCE_IO)? "io port":"mmio", res->start, res->end);
+ }
+}
+
+static void pci_bus_dump_resources(struct pci_bus *bus)
+{
+ struct pci_bus *b;
+ struct pci_dev *dev;
+
+
+ pci_bus_dump_res(bus);
+
+ list_for_each_entry(dev, &bus->devices, bus_list) {
+ b = dev->subordinate;
+ if (!b)
+ continue;
+
+ pci_bus_dump_resources(b);
+ }
+}
+
void __init
pci_assign_unassigned_resources(void)
{
@@ -552,4 +582,9 @@ pci_assign_unassigned_resources(void)
pci_bus_assign_resources(bus);
pci_enable_bridges(bus);
}
+
+ /* dump the resource on buses */
+ list_for_each_entry(bus, &pci_root_buses, node) {
+ pci_bus_dump_resources(bus);
+ }
}
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: debug_extra_pci_res_range.patch --]
[-- Type: text/x-patch; name=debug_extra_pci_res_range.patch, Size: 1787 bytes --]
Index: linux-2.6/drivers/pci/probe.c
===================================================================
--- linux-2.6.orig/drivers/pci/probe.c
+++ linux-2.6/drivers/pci/probe.c
@@ -275,6 +275,7 @@ static void pci_read_bases(struct pci_de
}
res->start = l64 & PCI_BASE_ADDRESS_MEM_MASK;
res->end = res->start + sz64;
+ printk(KERN_INFO "PCI: %s reg %x 64bit mmio: [%llx, %llx]\n", pci_name(dev), reg, res->start, res->end);
#else
if (sz64 > 0x100000000ULL) {
printk(KERN_ERR "PCI: Unable to handle 64-bit "
@@ -290,6 +291,8 @@ static void pci_read_bases(struct pci_de
res->end = sz;
}
#endif
+ } else {
+ printk(KERN_INFO "PCI: %s reg %x %s: [%llx, %llx]\n", pci_name(dev), reg, (res->flags & IORESOURCE_IO)? "io port":"32bit mmio", res->start, res->end);
}
}
if (rom) {
@@ -357,6 +360,7 @@ void __devinit pci_read_bridge_bases(str
res->start = base;
if (!res->end)
res->end = limit + 0xfff;
+ printk(KERN_INFO "PCI: bridge %s io port: [%llx, %llx]\n", pci_name(dev), res->start, res->end);
}
res = child->resource[1];
@@ -368,6 +372,7 @@ void __devinit pci_read_bridge_bases(str
res->flags = (mem_base_lo & PCI_MEMORY_RANGE_TYPE_MASK) | IORESOURCE_MEM;
res->start = base;
res->end = limit + 0xfffff;
+ printk(KERN_INFO "PCI: bridge %s 32bit mmio: [%llx, %llx]\n", pci_name(dev), res->start, res->end);
}
res = child->resource[2];
@@ -402,6 +407,7 @@ void __devinit pci_read_bridge_bases(str
res->flags = (mem_base_lo & PCI_MEMORY_RANGE_TYPE_MASK) | IORESOURCE_MEM | IORESOURCE_PREFETCH;
res->start = base;
res->end = limit + 0xfffff;
+ printk(KERN_INFO "PCI: bridge %s %sbit mmio pref: [%llx, %llx]\n", pci_name(dev), (res->flags & PCI_PREF_RANGE_TYPE_64)?"64":"32",res->start, res->end);
}
}
next prev parent reply other threads:[~2008-07-17 4:13 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
[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 [this message]
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=86802c440807162113g4cea3bd9ic71210330417032b@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=howarth@bromo.msbb.uc.edu \
--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®