linux-kernel - amd64 agpgart aperture base value

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

Date:	Wed, 13 Dec 2006 22:47:32 -0500
From:	Daniel Drake <dsd@...too.org>
To:	davej@...emonkey.org.uk
CC:	linux list <linux-kernel@...r.kernel.org>
Subject: amd64 agpgart aperture base value

Hi Dave,

I'm working on a solution for 
http://bugzilla.kernel.org/show_bug.cgi?id=6350

Certain BIOSes are screwing with the K8 aperture base value. However, 
these systems work after booting into windows and then rebooting into Linux.

It originally appeared to be a bug specific to asrock motherboard based 
on nforce3, but further reports have shown that this bug also manifests 
on ASUS+nforce3 and ASUS+via.

The BIOS sets some high bits at address 0x94 of the PCI config space of 
the northbridge, which falls under AMD64_GARTAPERTUREBASE

My current approach at a solution involves identifying the buggy systems 
by southbridge, and then fixing the northbridge in a PCI quirk. However 
as more systems are being uncovered I don't feel so good about this 
approach.

In amd64-agp.c, would it be dangerous to remove the "aperture base > 4G" 
thing and instead simply only read the rightmost 7 bits to ensure the 
aperture base is always in range? (This is coming from someone with 
little AGPGART understanding...)

Alternatively do you have other suggestions for how the problem might be 
solved better?

Thanks!
Daniel

-
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/