linux-kernel - Re: Intel BIOS - Corrupted low memory at ffff880000004200

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

Date:	Wed, 8 Jul 2009 12:39:49 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Alexey Fisher <bug-track@...her-privat.net>
Cc:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Kernel Testers List <kernel-testers@...r.kernel.org>,
	"Richard A. Holden III" <aciddeath@...il.com>,
	Ingo Molnar <mingo@...e.hu>
Subject: Re: Intel BIOS - Corrupted low memory at ffff880000004200

On Mon, Jul 06, 2009 at 06:24:47PM +0200, Alexey Fisher wrote:
> Hallo Ingo, Richard.
>
> I'm getting "Corrupted low memory" trace with my Intel DG45ID board
> after resume. This board  has different dmi-bios-vendor... so probably
> it will be nice to have it in your patch.

I'm beginning to think that we should be doing this on all hardware, 
perhaps with a kernel option to disable it for embedded devices that 
really need that 64K. The low-memory corruption issue seems to be very 
widespread.

-- 
Matthew Garrett | mjg59@...f.ucam.org
--
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/