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  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:	Wed, 20 Jun 2012 19:43:22 -0700
From:	Yinghai Lu <>
To:	Brice Goglin <>
Cc:	Bjorn Helgaas <>,
	Ulrich Drepper <>,,
	Linux Kernel Mailing List <>,,,
Subject: Re: SNB PCI root information

On Wed, Jun 20, 2012 at 12:57 PM, Brice Goglin <> wrote:
> Le 20/06/2012 21:28, Yinghai Lu a écrit :
>> On Wed, Jun 20, 2012 at 11:46 AM, Bjorn Helgaas <> wrote:
> I agree that the most common problem is that _PXM is missing. But I've
> seen at least some HP Westmere-EP platforms where _PXM exists but it is
> wrong. Last time we checked, there was no BIOS update, even if we
> reported the bug a while ago.
Do you have boot log or acpi dump?

I suspected that could be other problem. intel system before
sandbridge does not have IIO.
they will have ioh instead, and one ioh would connect to two cpu sockets.
but _PXM for root bus in dsdt only can return one value. Aka it is
acpi spec limitation.

for example, Sun x4800 8 sockets server would have bus 00, 40, 80, c0.
but _PXM will only return 0, 2, 3, 6.


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists