[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b170af450808291039u7d036313x49acdaec079e6213@mail.gmail.com>
Date: Fri, 29 Aug 2008 19:39:57 +0200
From: "Rafał Miłecki" <zajec5@...il.com>
To: "Hugh Dickins" <hugh@...itas.com>
Cc: "Alan Jenkins" <alan-jenkins@...fmail.co.uk>,
"Alan Cox" <alan@...rguk.ukuu.org.uk>,
"Jeremy Fitzhardinge" <jeremy@...p.org>,
"Yinghai Lu" <yhlu.kernel@...il.com>,
"Ingo Molnar" <mingo@...e.hu>, "H. Peter Anvin" <hpa@...or.com>,
"Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH RFC] x86: check for and defend against BIOS memory corruption
2008/8/29 Hugh Dickins <hugh@...itas.com>:
> Here's my version of Jeremy's patch, that I've now tested on my machines,
> as x86_32 and as x86_64. It addresses none of the points Alan Cox made,
> and it stays silent for me, even after suspend+resume, unless I actually
> introduce corruption myself. Omits Jeremy's check in fault.c, but does
> a check every minute, so should soon detect Rafał's HDMI corruption
> without any need to suspend+resume.
Your periodic test works fine:
Corrupted low memory at ffff88000000be9c (be9c phys) = b02a0004
<IRQ> [<ffffffff8020fc9b>] check_for_bios_corruption+0x93/0x9f
[<ffffffff8020fca7>] ? periodic_check_for_corruption+0x0/0x25
[<ffffffff8020fcb0>] periodic_check_for_corruption+0x9/0x25
By the way I confirmed this bug on Sony Vaio FW11M (my one is FW11S).
Probably more machines from FW11* are affected.
--
Rafał Miłecki
Powered by blists - more mailing lists