linux-kernel - Re: PCI: Unable to reserve mem region problem

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]

Date:	Tue, 11 Sep 2007 11:16:41 +0100
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Robert Hancock <hancockr@...w.ca>
Cc:	Chuck Ebbert <cebbert@...hat.com>,
	Karl Bellve <Karl.Bellve@...ssmed.edu>,
	linux-kernel@...r.kernel.org
Subject: Re: PCI: Unable to reserve mem region problem

> > https://bugzilla.redhat.com/show_bug.cgi?id=280641
> 
> The last BAR on the nForce4 ADMA controllers on this board are at 
> 0xdfefe000 and 0xdfefd000. But it looks like PnP ACPI is also reserving 
> those memory ranges:
> 
> Aug 30 14:08:02 alcor kernel: pnp: 00:09: iomem range 
> 0xdfefd000-0xdfefd3ff has been reserved
> Aug 30 14:08:02 alcor kernel: pnp: 00:09: iomem range 
> 0xdfefe000-0xdfefe3ff has been reserved
> 
> Which I very much doubt it should be doing, the BIOS doesn't need to 
> reserve PCI BAR ranges in the ACPI tables. This sounds like a BIOS bug. 
> You might want to check for an update from Supermicro.

They may be doing it to force the system out of ADMA mode. Right now we
just blow up in that case but it appears other-OS may fall back (which is
I suspect what we need to be doing)
-
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/