From: Arjan van de Ven <arjan@infradead.org>
To: "Ammar T. Al-Sayegh" <ammar@kunet.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel BUG at mm/rmap.c:483!
Date: Thu, 24 Feb 2005 09:38:52 +0100 [thread overview]
Message-ID: <1109234333.6530.19.camel@laptopd505.fenrus.org> (raw)
In-Reply-To: <007d01c519f9$7c9a5f50$7101a8c0@shrugy>
> 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....
next prev parent reply other threads:[~2005-02-24 8:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 20:41 Ammar T. Al-Sayegh
2005-02-23 20:54 ` Arjan van de Ven
2005-02-23 21:45 ` Ammar T. Al-Sayegh
2005-02-23 22:01 ` Arjan van de Ven
2005-02-23 22:46 ` Ammar T. Al-Sayegh
2005-02-24 8:38 ` Arjan van de Ven [this message]
2005-02-24 9:25 ` Ammar T. Al-Sayegh
2005-02-24 9:30 ` Arjan van de Ven
2005-02-28 10:43 ` Giacomo A. Catenazzi
2005-02-28 11:09 ` Arjan van de Ven
2005-02-23 21:31 ` Hugh Dickins
2005-02-23 22:38 ` Ammar T. Al-Sayegh
2005-02-24 5:31 ` Hugh Dickins
2005-02-24 13:25 ` Horst von Brand
2005-02-23 22:05 Nick Warne
2005-02-24 12:15 ` Hugh Dickins
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1109234333.6530.19.camel@laptopd505.fenrus.org \
--to=arjan@infradead.org \
--cc=ammar@kunet.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®