linux-kernel - Re: [PATCH] trim memory not covered by WB MTRRs

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]

Message-ID: <467A8A20.7000302@macroscoop.nl>
Date:	Thu, 21 Jun 2007 16:24:32 +0200
From:	Pim Zandbergen <P.Zandbergen@...roscoop.nl>
To:	Jesse Barnes <jbarnes@...tuousgeek.org>
CC:	Justin Piszcz <jpiszcz@...idpixels.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] trim memory not covered by WB MTRRs

Jesse Barnes wrote:
>> What, are you going to report this to GigaByte?
>>     
>
> No, but you should if you haven't already.  I think GigaByte probably 
> gets its BIOS from another BIOS vendor (maybe Intel), so when that 
> vendor provides them with an update, they'll probably provide it on 
> their website.  And from what I understand, an Intel BIOS update is in 
> the works to address this issue for Intel boards, so a GigaByte version 
> may follow shortly.  I don't have an exact timeframe though...
>
>   
I reported this to GigaByte, and lo and behold, they sent me a fixed 
BIOS within 48 hours.
Kudos to Taipeh!

They sent the BIOS image in a private message, so it might take a while 
before it's available
on their website.


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