Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752831AbYH2HWq (ORCPT ); Fri, 29 Aug 2008 03:22:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750739AbYH2HWk (ORCPT ); Fri, 29 Aug 2008 03:22:40 -0400 Received: from gw.goop.org ([64.81.55.164]:37945 "EHLO mail.goop.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750710AbYH2HWj (ORCPT ); Fri, 29 Aug 2008 03:22:39 -0400 Message-ID: <48B7A3BE.8010604@goop.org> Date: Fri, 29 Aug 2008 00:22:38 -0700 From: Jeremy Fitzhardinge User-Agent: Thunderbird 2.0.0.16 (X11/20080723) MIME-Version: 1.0 To: =?UTF-8?B?UmFmYcWCIE1pxYJlY2tp?= CC: Ingo Molnar , Alan Jenkins , Hugh Dickens , "H. Peter Anvin" , Linux Kernel Mailing List Subject: Re: [PATCH RFC] x86: check for and defend against BIOS memory corruption References: <48B701FB.2020905@goop.org> In-Reply-To: X-Enigmail-Version: 0.95.7 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 725 Lines: 25 Rafał Miłecki wrote: > I was trying my best to crash system with this patch applied and failed :) > > Works great. > Good. > Just wonder if I should expect any printk from > check_for_bios_corruption? I do not see any: > > zajec@sony:~> dmesg | grep -i corr > scanning 2 areas for BIOS corruption > I just followed up in detail to Ingo, but I think it's because I didn't put any checks where you would hit them. If you suspend/resume it should print something. J -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/