Re: BUG?: "Cannot map mmconfig aperture"

2008-02-22 Thread Diego Calleja
El Thu, 21 Feb 2008 21:26:56 +0100 (CET), Thomas Gleixner <[EMAIL PROTECTED]> 
escribió:

> Thanks. Nothing new there. Can you please apply the patch below and
> provide the output of the ioremap code ?


[0.155485] ACPI: bus type pci registered
[0.155581] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory 
Controller Hub with MMCONFIG support.
[0.160814] ioremap: CPA e000 268435456 -12
[0.162182] PCI: Cannot map mmconfig aperture for segment 0
[0.162215] PCI: Using configuration type 1
[0.166956] ACPI: EC: Look up EC in DSDT
[0.173445] ACPI: Interpreter enabled
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: BUG?: Cannot map mmconfig aperture

2008-02-22 Thread Diego Calleja
El Thu, 21 Feb 2008 21:26:56 +0100 (CET), Thomas Gleixner [EMAIL PROTECTED] 
escribió:

 Thanks. Nothing new there. Can you please apply the patch below and
 provide the output of the ioremap code ?


[0.155485] ACPI: bus type pci registered
[0.155581] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory 
Controller Hub with MMCONFIG support.
[0.160814] ioremap: CPA e000 268435456 -12
[0.162182] PCI: Cannot map mmconfig aperture for segment 0
[0.162215] PCI: Using configuration type 1
[0.166956] ACPI: EC: Look up EC in DSDT
[0.173445] ACPI: Interpreter enabled
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: BUG?: "Cannot map mmconfig aperture"

2008-02-21 Thread Thomas Gleixner
On Thu, 21 Feb 2008, Diego Calleja wrote:
> > Hmm, that's confusing. Can you please provide a complete boot log ?
> > 
> > Thanks,
> 
> Sure

Thanks. Nothing new there. Can you please apply the patch below and
provide the output of the ioremap code ?

Thanks,

tglx

Index: linux-2.6/arch/x86/mm/ioremap.c
===
--- linux-2.6.orig/arch/x86/mm/ioremap.c
+++ linux-2.6/arch/x86/mm/ioremap.c
@@ -112,6 +112,7 @@ static void __iomem *__ioremap(unsigned 
unsigned long pfn, offset, last_addr, vaddr;
struct vm_struct *area;
pgprot_t prot;
+   int err;
 
/* Don't allow wraparound or zero size */
last_addr = phys_addr + size - 1;
@@ -130,8 +131,11 @@ static void __iomem *__ioremap(unsigned 
for (pfn = phys_addr >> PAGE_SHIFT; pfn < max_pfn_mapped &&
 (pfn << PAGE_SHIFT) < last_addr; pfn++) {
if (page_is_ram(pfn) && pfn_valid(pfn) &&
-   !PageReserved(pfn_to_page(pfn)))
+   !PageReserved(pfn_to_page(pfn))) {
+   printk(KERN_INFO "ioremap: (RAM) %lx %lu\n", phys_addr,
+  size);
return NULL;
+   }
}
 
WARN_ON_ONCE(page_is_ram(pfn));
@@ -157,16 +161,23 @@ static void __iomem *__ioremap(unsigned 
 * Ok, go for it..
 */
area = get_vm_area(size, VM_IOREMAP);
-   if (!area)
+   if (!area) {
+   printk(KERN_INFO "ioremap: !area PR %lx %lu\n", phys_addr,
+  size);
return NULL;
+   }
area->phys_addr = phys_addr;
vaddr = (unsigned long) area->addr;
if (ioremap_page_range(vaddr, vaddr + size, phys_addr, prot)) {
remove_vm_area((void *)(vaddr & PAGE_MASK));
+   printk(KERN_INFO "ioremap: IPR %lx %lu\n", phys_addr, size);
return NULL;
}
 
-   if (ioremap_change_attr(vaddr, size, mode) < 0) {
+   err = ioremap_change_attr(vaddr, size, mode);
+   if (err < 0) {
+   printk(KERN_INFO "ioremap: CPA %lx %lu %d\n", phys_addr, size,
+  err);
vunmap(area->addr);
return NULL;
}
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: BUG?: "Cannot map mmconfig aperture"

2008-02-21 Thread Diego Calleja
El Thu, 21 Feb 2008 08:53:39 +0100 (CET), Thomas Gleixner <[EMAIL PROTECTED]> 
escribió:

> Hmm, that's confusing. Can you please provide a complete boot log ?
> 
> Thanks,

Sure

[0.00] Linux version 2.6.25-rc2-00342-g5d9c4a7 ([EMAIL PROTECTED]) (gcc 
version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #17 SMP PREEMPT 
Wed Feb 20 19:54:40 CET 2008
[0.00] Command line: root=/dev/sda2 ro quiet splash locale=es_ES
[0.00] BIOS-provided physical RAM map:
[0.00]  BIOS-e820:  - 0009fc00 (usable)
[0.00]  BIOS-e820: 0009fc00 - 000a (reserved)
[0.00]  BIOS-e820: 000e4000 - 0010 (reserved)
[0.00]  BIOS-e820: 0010 - 3f79 (usable)
[0.00]  BIOS-e820: 3f79 - 3f79e000 (ACPI data)
[0.00]  BIOS-e820: 3f79e000 - 3f7e (ACPI NVS)
[0.00]  BIOS-e820: 3f7e - 3f80 (reserved)
[0.00]  BIOS-e820: fff8 - 0001 (reserved)
[0.00] Entering add_active_range(0, 0, 159) 0 entries of 256 used
[0.00] Entering add_active_range(0, 256, 259984) 1 entries of 256 used
[0.00] end_pfn_map = 1048576
[0.00] DMI 2.4 present.
[0.00] ACPI: RSDP 000FB0D0, 0024 (r2 ACPIAM)
[0.00] ACPI: XSDT 3F790100, 004C (r1 A_M_I_ OEMXSDT   6000706 MSFT  
 97)
[0.00] ACPI: FACP 3F790290, 00F4 (r3 A_M_I_ OEMFACP   6000706 MSFT  
 97)
[0.00] ACPI: DSDT 3F790590, 5870 (r1  A0356 A0356034   34 INTL 
20060113)
[0.00] ACPI: FACS 3F79E000, 0040
[0.00] ACPI: APIC 3F790390, 0080 (r1 A_M_I_ OEMAPIC   6000706 MSFT  
 97)
[0.00] ACPI: OEMB 3F79E040, 006B (r1 A_M_I_ AMI_OEM   6000706 MSFT  
 97)
[0.00] ACPI: HPET 3F795E00, 0038 (r1 A_M_I_ OEMHPET   6000706 MSFT  
 97)
[0.00] ACPI: MCFG 3F795E40, 003C (r1 A_M_I_ OEMMCFG   6000706 MSFT  
 97)
[0.00] Entering add_active_range(0, 0, 159) 0 entries of 256 used
[0.00] Entering add_active_range(0, 256, 259984) 1 entries of 256 used
[0.00] early res: 0 [0-fff] BIOS data page
[0.00] early res: 1 [6000-7fff] SMP_TRAMPOLINE
[0.00] early res: 2 [20-7d0c57] TEXT DATA BSS
[0.00] early res: 3 [9fc00-a0bff] EBDA
[0.00] early res: 4 [8000-afff] PGTABLE
[0.00] Zone PFN ranges:
[0.00]   DMA 0 -> 4096
[0.00]   DMA324096 ->  1048576
[0.00]   Normal1048576 ->  1048576
[0.00] Movable zone start PFN for each node
[0.00] early_node_map[2] active PFN ranges
[0.00] 0:0 ->  159
[0.00] 0:  256 ->   259984
[0.00] On node 0 totalpages: 259887
[0.00]   DMA zone: 56 pages used for memmap
[0.00]   DMA zone: 1497 pages reserved
[0.00]   DMA zone: 2446 pages, LIFO batch:0
[0.00]   DMA32 zone: 3498 pages used for memmap
[0.00]   DMA32 zone: 252390 pages, LIFO batch:31
[0.00]   Normal zone: 0 pages used for memmap
[0.00]   Movable zone: 0 pages used for memmap
[0.00] ACPI: PM-Timer IO Port: 0x808
[0.00] ACPI: Local APIC address 0xfee0
[0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[0.00] Processor #0 (Bootup-CPU)
[0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
[0.00] Processor #1
[0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
[0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
[0.00] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0])
[0.00] IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[0.00] ACPI: IRQ0 used by override.
[0.00] ACPI: IRQ2 used by override.
[0.00] ACPI: IRQ9 used by override.
[0.00] Setting APIC routing to flat
[0.00] ACPI: HPET id: 0x8086a201 base: 0xfed0
[0.00] Using ACPI (MADT) for SMP configuration information
[0.00] PM: Registered nosave memory: 0009f000 - 000a
[0.00] PM: Registered nosave memory: 000a - 000e4000
[0.00] PM: Registered nosave memory: 000e4000 - 0010
[0.00] Allocating PCI resources starting at 4000 (gap: 
3f80:c078)
[0.00] SMP: Allowing 2 CPUs, 0 hotplug CPUs
[0.00] PERCPU: Allocating 34692 bytes of per cpu data
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 254836
[0.00] Kernel command line: root=/dev/sda2 ro quiet splash locale=es_ES
[0.00] Initializing 

Re: BUG?: Cannot map mmconfig aperture

2008-02-21 Thread Diego Calleja
El Thu, 21 Feb 2008 08:53:39 +0100 (CET), Thomas Gleixner [EMAIL PROTECTED] 
escribió:

 Hmm, that's confusing. Can you please provide a complete boot log ?
 
 Thanks,

Sure

[0.00] Linux version 2.6.25-rc2-00342-g5d9c4a7 ([EMAIL PROTECTED]) (gcc 
version 4.1.3 20070929 (prerelease) (Ubuntu 4.1.2-16ubuntu2)) #17 SMP PREEMPT 
Wed Feb 20 19:54:40 CET 2008
[0.00] Command line: root=/dev/sda2 ro quiet splash locale=es_ES
[0.00] BIOS-provided physical RAM map:
[0.00]  BIOS-e820:  - 0009fc00 (usable)
[0.00]  BIOS-e820: 0009fc00 - 000a (reserved)
[0.00]  BIOS-e820: 000e4000 - 0010 (reserved)
[0.00]  BIOS-e820: 0010 - 3f79 (usable)
[0.00]  BIOS-e820: 3f79 - 3f79e000 (ACPI data)
[0.00]  BIOS-e820: 3f79e000 - 3f7e (ACPI NVS)
[0.00]  BIOS-e820: 3f7e - 3f80 (reserved)
[0.00]  BIOS-e820: fff8 - 0001 (reserved)
[0.00] Entering add_active_range(0, 0, 159) 0 entries of 256 used
[0.00] Entering add_active_range(0, 256, 259984) 1 entries of 256 used
[0.00] end_pfn_map = 1048576
[0.00] DMI 2.4 present.
[0.00] ACPI: RSDP 000FB0D0, 0024 (r2 ACPIAM)
[0.00] ACPI: XSDT 3F790100, 004C (r1 A_M_I_ OEMXSDT   6000706 MSFT  
 97)
[0.00] ACPI: FACP 3F790290, 00F4 (r3 A_M_I_ OEMFACP   6000706 MSFT  
 97)
[0.00] ACPI: DSDT 3F790590, 5870 (r1  A0356 A0356034   34 INTL 
20060113)
[0.00] ACPI: FACS 3F79E000, 0040
[0.00] ACPI: APIC 3F790390, 0080 (r1 A_M_I_ OEMAPIC   6000706 MSFT  
 97)
[0.00] ACPI: OEMB 3F79E040, 006B (r1 A_M_I_ AMI_OEM   6000706 MSFT  
 97)
[0.00] ACPI: HPET 3F795E00, 0038 (r1 A_M_I_ OEMHPET   6000706 MSFT  
 97)
[0.00] ACPI: MCFG 3F795E40, 003C (r1 A_M_I_ OEMMCFG   6000706 MSFT  
 97)
[0.00] Entering add_active_range(0, 0, 159) 0 entries of 256 used
[0.00] Entering add_active_range(0, 256, 259984) 1 entries of 256 used
[0.00] early res: 0 [0-fff] BIOS data page
[0.00] early res: 1 [6000-7fff] SMP_TRAMPOLINE
[0.00] early res: 2 [20-7d0c57] TEXT DATA BSS
[0.00] early res: 3 [9fc00-a0bff] EBDA
[0.00] early res: 4 [8000-afff] PGTABLE
[0.00] Zone PFN ranges:
[0.00]   DMA 0 - 4096
[0.00]   DMA324096 -  1048576
[0.00]   Normal1048576 -  1048576
[0.00] Movable zone start PFN for each node
[0.00] early_node_map[2] active PFN ranges
[0.00] 0:0 -  159
[0.00] 0:  256 -   259984
[0.00] On node 0 totalpages: 259887
[0.00]   DMA zone: 56 pages used for memmap
[0.00]   DMA zone: 1497 pages reserved
[0.00]   DMA zone: 2446 pages, LIFO batch:0
[0.00]   DMA32 zone: 3498 pages used for memmap
[0.00]   DMA32 zone: 252390 pages, LIFO batch:31
[0.00]   Normal zone: 0 pages used for memmap
[0.00]   Movable zone: 0 pages used for memmap
[0.00] ACPI: PM-Timer IO Port: 0x808
[0.00] ACPI: Local APIC address 0xfee0
[0.00] ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
[0.00] Processor #0 (Bootup-CPU)
[0.00] ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
[0.00] Processor #1
[0.00] ACPI: LAPIC (acpi_id[0x03] lapic_id[0x82] disabled)
[0.00] ACPI: LAPIC (acpi_id[0x04] lapic_id[0x83] disabled)
[0.00] ACPI: IOAPIC (id[0x02] address[0xfec0] gsi_base[0])
[0.00] IOAPIC[0]: apic_id 2, address 0xfec0, GSI 0-23
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 0 global_irq 2 dfl dfl)
[0.00] ACPI: INT_SRC_OVR (bus 0 bus_irq 9 global_irq 9 high level)
[0.00] ACPI: IRQ0 used by override.
[0.00] ACPI: IRQ2 used by override.
[0.00] ACPI: IRQ9 used by override.
[0.00] Setting APIC routing to flat
[0.00] ACPI: HPET id: 0x8086a201 base: 0xfed0
[0.00] Using ACPI (MADT) for SMP configuration information
[0.00] PM: Registered nosave memory: 0009f000 - 000a
[0.00] PM: Registered nosave memory: 000a - 000e4000
[0.00] PM: Registered nosave memory: 000e4000 - 0010
[0.00] Allocating PCI resources starting at 4000 (gap: 
3f80:c078)
[0.00] SMP: Allowing 2 CPUs, 0 hotplug CPUs
[0.00] PERCPU: Allocating 34692 bytes of per cpu data
[0.00] Built 1 zonelists in Zone order, mobility grouping on.  Total 
pages: 254836
[0.00] Kernel command line: root=/dev/sda2 ro quiet splash locale=es_ES
[0.00] Initializing CPU#0
[

Re: BUG?: Cannot map mmconfig aperture

2008-02-21 Thread Thomas Gleixner
On Thu, 21 Feb 2008, Diego Calleja wrote:
  Hmm, that's confusing. Can you please provide a complete boot log ?
  
  Thanks,
 
 Sure

Thanks. Nothing new there. Can you please apply the patch below and
provide the output of the ioremap code ?

Thanks,

tglx

Index: linux-2.6/arch/x86/mm/ioremap.c
===
--- linux-2.6.orig/arch/x86/mm/ioremap.c
+++ linux-2.6/arch/x86/mm/ioremap.c
@@ -112,6 +112,7 @@ static void __iomem *__ioremap(unsigned 
unsigned long pfn, offset, last_addr, vaddr;
struct vm_struct *area;
pgprot_t prot;
+   int err;
 
/* Don't allow wraparound or zero size */
last_addr = phys_addr + size - 1;
@@ -130,8 +131,11 @@ static void __iomem *__ioremap(unsigned 
for (pfn = phys_addr  PAGE_SHIFT; pfn  max_pfn_mapped 
 (pfn  PAGE_SHIFT)  last_addr; pfn++) {
if (page_is_ram(pfn)  pfn_valid(pfn) 
-   !PageReserved(pfn_to_page(pfn)))
+   !PageReserved(pfn_to_page(pfn))) {
+   printk(KERN_INFO ioremap: (RAM) %lx %lu\n, phys_addr,
+  size);
return NULL;
+   }
}
 
WARN_ON_ONCE(page_is_ram(pfn));
@@ -157,16 +161,23 @@ static void __iomem *__ioremap(unsigned 
 * Ok, go for it..
 */
area = get_vm_area(size, VM_IOREMAP);
-   if (!area)
+   if (!area) {
+   printk(KERN_INFO ioremap: !area PR %lx %lu\n, phys_addr,
+  size);
return NULL;
+   }
area-phys_addr = phys_addr;
vaddr = (unsigned long) area-addr;
if (ioremap_page_range(vaddr, vaddr + size, phys_addr, prot)) {
remove_vm_area((void *)(vaddr  PAGE_MASK));
+   printk(KERN_INFO ioremap: IPR %lx %lu\n, phys_addr, size);
return NULL;
}
 
-   if (ioremap_change_attr(vaddr, size, mode)  0) {
+   err = ioremap_change_attr(vaddr, size, mode);
+   if (err  0) {
+   printk(KERN_INFO ioremap: CPA %lx %lu %d\n, phys_addr, size,
+  err);
vunmap(area-addr);
return NULL;
}
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: BUG?: "Cannot map mmconfig aperture"

2008-02-20 Thread Thomas Gleixner
On Wed, 20 Feb 2008, Diego Calleja wrote:

> I get the following new message in my dmesg:
> 
> [0.155476] ACPI: bus type pci registered
> [0.155567] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory 
> Controller Hub with MMCONFIG support.
> [0.161149] PCI: Cannot map mmconfig aperture for segment 0
> [0.161181] PCI: Using configuration type 1
> [0.165980] ACPI: EC: Look up EC in DSDT
> 
> when previously i'd have:
> 
> [0.156577] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory 
> Controller Hub with MMCONFIG support.
> [0.166403] PCI: Using MMCONFIG at e000 - efff
> [0.166407] PCI: Using configuration type 1
> [0.171548] ACPI: EC: Look up EC in DSDT
> 
> 
> No idea if this is a regression or not, or what it means, the system works 
> well.
> git-bisect says the problem cames from:
> 
> commit c31c7d4844ea4817692ae16bf70f9c96c05a50eb
> Author: Thomas Gleixner <[EMAIL PROTECTED]>
> Date:   Mon Feb 18 20:54:14 2008 +0100
> 
> x86: CPA, fix alias checks

Hmm, that's confusing. Can you please provide a complete boot log ?

Thanks,

tglx
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: BUG?: "Cannot map mmconfig aperture"

2008-02-20 Thread Robert Hancock

Diego Calleja wrote:

I get the following new message in my dmesg:

[0.155476] ACPI: bus type pci registered
[0.155567] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory 
Controller Hub with MMCONFIG support.
[0.161149] PCI: Cannot map mmconfig aperture for segment 0
[0.161181] PCI: Using configuration type 1
[0.165980] ACPI: EC: Look up EC in DSDT

when previously i'd have:

[0.156577] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory 
Controller Hub with MMCONFIG support.
[0.166403] PCI: Using MMCONFIG at e000 - efff
[0.166407] PCI: Using configuration type 1
[0.171548] ACPI: EC: Look up EC in DSDT


No idea if this is a regression or not, or what it means, the system works well.
git-bisect says the problem cames from:

commit c31c7d4844ea4817692ae16bf70f9c96c05a50eb
Author: Thomas Gleixner <[EMAIL PROTECTED]>
Date:   Mon Feb 18 20:54:14 2008 +0100

x86: CPA, fix alias checks


Yeah, sounds like a regression.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


BUG?: "Cannot map mmconfig aperture"

2008-02-20 Thread Diego Calleja
I get the following new message in my dmesg:

[0.155476] ACPI: bus type pci registered
[0.155567] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory 
Controller Hub with MMCONFIG support.
[0.161149] PCI: Cannot map mmconfig aperture for segment 0
[0.161181] PCI: Using configuration type 1
[0.165980] ACPI: EC: Look up EC in DSDT

when previously i'd have:

[0.156577] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory 
Controller Hub with MMCONFIG support.
[0.166403] PCI: Using MMCONFIG at e000 - efff
[0.166407] PCI: Using configuration type 1
[0.171548] ACPI: EC: Look up EC in DSDT


No idea if this is a regression or not, or what it means, the system works well.
git-bisect says the problem cames from:

commit c31c7d4844ea4817692ae16bf70f9c96c05a50eb
Author: Thomas Gleixner <[EMAIL PROTECTED]>
Date:   Mon Feb 18 20:54:14 2008 +0100

x86: CPA, fix alias checks
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


BUG?: Cannot map mmconfig aperture

2008-02-20 Thread Diego Calleja
I get the following new message in my dmesg:

[0.155476] ACPI: bus type pci registered
[0.155567] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory 
Controller Hub with MMCONFIG support.
[0.161149] PCI: Cannot map mmconfig aperture for segment 0
[0.161181] PCI: Using configuration type 1
[0.165980] ACPI: EC: Look up EC in DSDT

when previously i'd have:

[0.156577] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory 
Controller Hub with MMCONFIG support.
[0.166403] PCI: Using MMCONFIG at e000 - efff
[0.166407] PCI: Using configuration type 1
[0.171548] ACPI: EC: Look up EC in DSDT


No idea if this is a regression or not, or what it means, the system works well.
git-bisect says the problem cames from:

commit c31c7d4844ea4817692ae16bf70f9c96c05a50eb
Author: Thomas Gleixner [EMAIL PROTECTED]
Date:   Mon Feb 18 20:54:14 2008 +0100

x86: CPA, fix alias checks
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: BUG?: Cannot map mmconfig aperture

2008-02-20 Thread Robert Hancock

Diego Calleja wrote:

I get the following new message in my dmesg:

[0.155476] ACPI: bus type pci registered
[0.155567] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory 
Controller Hub with MMCONFIG support.
[0.161149] PCI: Cannot map mmconfig aperture for segment 0
[0.161181] PCI: Using configuration type 1
[0.165980] ACPI: EC: Look up EC in DSDT

when previously i'd have:

[0.156577] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory 
Controller Hub with MMCONFIG support.
[0.166403] PCI: Using MMCONFIG at e000 - efff
[0.166407] PCI: Using configuration type 1
[0.171548] ACPI: EC: Look up EC in DSDT


No idea if this is a regression or not, or what it means, the system works well.
git-bisect says the problem cames from:

commit c31c7d4844ea4817692ae16bf70f9c96c05a50eb
Author: Thomas Gleixner [EMAIL PROTECTED]
Date:   Mon Feb 18 20:54:14 2008 +0100

x86: CPA, fix alias checks


Yeah, sounds like a regression.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


Re: BUG?: Cannot map mmconfig aperture

2008-02-20 Thread Thomas Gleixner
On Wed, 20 Feb 2008, Diego Calleja wrote:

 I get the following new message in my dmesg:
 
 [0.155476] ACPI: bus type pci registered
 [0.155567] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory 
 Controller Hub with MMCONFIG support.
 [0.161149] PCI: Cannot map mmconfig aperture for segment 0
 [0.161181] PCI: Using configuration type 1
 [0.165980] ACPI: EC: Look up EC in DSDT
 
 when previously i'd have:
 
 [0.156577] PCI: Found Intel Corporation 945G/GZ/P/PL Express Memory 
 Controller Hub with MMCONFIG support.
 [0.166403] PCI: Using MMCONFIG at e000 - efff
 [0.166407] PCI: Using configuration type 1
 [0.171548] ACPI: EC: Look up EC in DSDT
 
 
 No idea if this is a regression or not, or what it means, the system works 
 well.
 git-bisect says the problem cames from:
 
 commit c31c7d4844ea4817692ae16bf70f9c96c05a50eb
 Author: Thomas Gleixner [EMAIL PROTECTED]
 Date:   Mon Feb 18 20:54:14 2008 +0100
 
 x86: CPA, fix alias checks

Hmm, that's confusing. Can you please provide a complete boot log ?

Thanks,

tglx
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/