Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262079AbVBXIjS (ORCPT ); Thu, 24 Feb 2005 03:39:18 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262031AbVBXIjS (ORCPT ); Thu, 24 Feb 2005 03:39:18 -0500 Received: from pentafluge.infradead.org ([213.146.154.40]:37274 "EHLO pentafluge.infradead.org") by vger.kernel.org with ESMTP id S262036AbVBXIi7 (ORCPT ); Thu, 24 Feb 2005 03:38:59 -0500 Subject: Re: kernel BUG at mm/rmap.c:483! From: Arjan van de Ven To: "Ammar T. Al-Sayegh" Cc: linux-kernel@vger.kernel.org In-Reply-To: <007d01c519f9$7c9a5f50$7101a8c0@shrugy> 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> Content-Type: text/plain Date: Thu, 24 Feb 2005 09:38:52 +0100 Message-Id: <1109234333.6530.19.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: 1372 Lines: 34 > really; it was supposed to do that already > > > >> i2c_dev 13249 0 > >> i2c_core 24513 1 i2c_dev > > > > try for fun to not use i2c for a while > > > >> microcode 11489 0 > > same for microcode... try removing that so that the microcode of your > > system doesn't get updated at boot > > What do these two modules do in particular? and how can I disable > them so that they don't get reloaded during boot time? do I need > to disable both i2c_dev and i2c_core or just one of them? i2c is used to directly talk to motherboard hardware such as temperature sensors. I've seen cases of certain chipset bugs leading to cacheline corruption when stuff talked to the slow i2c bus and did other stuff in parallel. microcode changes the microcode of the cpu (a part of your cpu is actually written in "software" that can be updated); however updating this behind the back of the bios might not always be a good idea. (but I have no hard proof of any failures due to this) As for how to disable these.. you could just rename the respective .ko files to .notko or something.... - 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/