linux-kernel - Re: [PATCH] Fix 82875 PCI setup

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] [day] [month] [year] [list]

Message-ID: <20070329173700.GA9348@khazad-dum.debian.net>
Date:	Thu, 29 Mar 2007 14:37:00 -0300
From:	Henrique de Moraes Holschuh <hmh@....eng.br>
To:	Adam Jackson <ajackson@...hat.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Fix 82875 PCI setup

On Thu, 29 Mar 2007, Adam Jackson wrote:
> The 82875 EDAC driver enables an otherwise-hidden PCI device, but
> doesn't register it as a PCI device properly.  Therefore, the device
> list in /proc/bus/pci/devices is different than the tree in 
> /sys/bus/pci. This usually manifests as the X server failing to start,
> since it expects the two lists to be consistent.

Just a note: when EDAC needs to unhide the overflow configuration space of
the 82875, it is because the BIOS hid it.  And some BIOSes actually reserve
the area of the hidden device in the memory map/acpi tables/whatever.
Intel's D875PBZ motherboard does this.  EDAC can and does enable the
overflow device, but it might fail to reserve that region because of that
the BIOS did (and that is not a problem, in fact it is expected behaviour).

I don't know if this affects this patch in any way.  If it doesn't just
delete this email.

-- 
  "One disk to rule them all, One disk to find them. One disk to bring
  them all and in the darkness grind them. In the Land of Redmond
  where the shadows lie." -- The Silicon Valley Tarot
  Henrique Holschuh
-
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/