linux-kernel - Re: [PATCH] x86,pci: dmi check for mackpro 2.2 mmconf

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 18 Jul 2008 21:45:08 -0700
From:	"Yinghai Lu" <yhlu.kernel@...il.com>
To:	"Jack Howarth" <howarth@...mo.msbb.uc.edu>
Cc:	"Ingo Molnar" <mingo@...e.hu>,
	"Thomas Gleixner" <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>, jbarnes@...tuousgeek.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] x86,pci: dmi check for mackpro 2.2 mmconf

On Fri, Jul 18, 2008 at 8:28 PM, Jack Howarth <howarth@...mo.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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/