Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261153AbVB1LJY (ORCPT ); Mon, 28 Feb 2005 06:09:24 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261170AbVB1LJY (ORCPT ); Mon, 28 Feb 2005 06:09:24 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:18914 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S261153AbVB1LJU (ORCPT ); Mon, 28 Feb 2005 06:09:20 -0500 Subject: Re: kernel BUG at mm/rmap.c:483! From: Arjan van de Ven To: "Giacomo A. Catenazzi" Cc: "Ammar T. Al-Sayegh" , linux-kernel@vger.kernel.org In-Reply-To: <4222F5BE.7000301@pixelized.ch> References: <009d01c519e8$166768b0$7101a8c0@shrugy> <1109192040.6290.108.camel@laptopd505.fenrus.org> <003001c519f1$031afc00$7101a8c0@shrugy> <1109196074.6290.116.camel@laptopd505.fenrus.org> <007d01c519f9$7c9a5f50$7101a8c0@shrugy> <1109234333.6530.19.camel@laptopd505.fenrus.org> <004501c51a52$c4200380$7101a8c0@shrugy> <1109237429.6530.23.camel@laptopd505.fenrus.org> <4222F5BE.7000301@pixelized.ch> Content-Type: text/plain Date: Mon, 28 Feb 2005 12:09:09 +0100 Message-Id: <1109588950.6298.76.camel@laptopd505.fenrus.org> Mime-Version: 1.0 X-Mailer: Evolution 2.0.2 (2.0.2-3) Content-Transfer-Encoding: 7bit X-Spam-Score: 4.1 (++++) X-Spam-Report: SpamAssassin version 2.63 on pentafluge.infradead.org summary: Content analysis details: (4.1 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- 0.3 RCVD_NUMERIC_HELO Received: contains a numeric HELO 1.1 RCVD_IN_DSBL RBL: Received via a relay in list.dsbl.org [] 2.5 RCVD_IN_DYNABLOCK RBL: Sent directly from dynamic IP address [80.57.133.107 listed in dnsbl.sorbs.net] 0.1 RCVD_IN_SORBS RBL: SORBS: sender is listed in SORBS [80.57.133.107 listed in dnsbl.sorbs.net] X-SRS-Rewrite: SMTP reverse-path rewritten from by pentafluge.infradead.org See http://www.infradead.org/rpr.html Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1026 Lines: 28 On Mon, 2005-02-28 at 11:43 +0100, Giacomo A. Catenazzi wrote: > Arjan van de Ven wrote: > > >>but what what's the > >>penalty of preventing microcode from loading? a performance > >>hit? > > > > > > not even that; in theory a few cpu bugs may have been fixed. Nobody > > really knows since there's no changelog for the microcode.. > > You can see the processor bugs in intel website, i.e.: > ftp://download.intel.com/design/Xeon/specupdt/24967847.pdf > > The following sentence (IMHO) meens that bug is corrected in microcode: > "Workaround: It is possible for the BIOS to contain a workaround > for this erratum." yeah but it doesn't say in which microcode. Eg it's not possible to find out what a specific microcode update changes over the one the bios already put in... - 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/