linux-kernel - Re: What can change in ways Linux handles memory when all memory >4G is disabled? (x86)

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: <CA+waHKVTONQVqj7=n5tHfmxa3FOWyYFi4rZvMD7j_eio4-NWLQ@mail.gmail.com>
Date:	Sun, 8 Jun 2014 22:06:35 +0400
From:	Nikolay Amiantov <nikoamia@...il.com>
To:	"H. Peter Anvin" <hpa@...or.com>
Cc:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: What can change in ways Linux handles memory when all memory >4G
 is disabled? (x86)

On Sun, Jun 8, 2014 at 9:53 PM, H. Peter Anvin <hpa@...or.com> wrote:
>
> This would point either to an iommu problem, or a problem in the driver
> where addresses somehow get truncated to 32 bits.  Since this is a
> graphics driver it is extremely complex, and subtle problems could be
> buried somewhere inside it.  The fact that you can trigger it without a
> driver would point to that kind of problem inside the firmware.
>
>         -hpa

My assumption is that in new BIOSes (old ones are working, as I've
said, for T440p) there is some new way nvidia should be enabled, and
it's not related to ACPI (the calls are same in Windows). There are no
related changelog entries for T440p [1] (between 1.14 and 1.16). Also,
about address truncation: I thought so too, but if I understand
correctly, then some memory in >=4G region should be reserved for some
driver's use, and this is not the case (see [2] for /proc/iomem).

Nikolay Amiantov.

[1]: http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles/gluj13us.txt
[2]: http://bpaste.net/show/355712/
--
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/