mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ammar T. Al-Sayegh" <ammar@kunet.com>
To: "Arjan van de Ven" <arjan@infradead.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: kernel BUG at mm/rmap.c:483!
Date: Wed, 23 Feb 2005 17:46:11 -0500	[thread overview]
Message-ID: <007d01c519f9$7c9a5f50$7101a8c0@shrugy> (raw)
In-Reply-To: <1109196074.6290.116.camel@laptopd505.fenrus.org>

----- Original Message ----- 
From: "Arjan van de Ven" <arjan@infradead.org>
To: "Ammar T. Al-Sayegh" <ammar@kunet.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Wednesday, February 23, 2005 5:01 PM
Subject: Re: kernel BUG at mm/rmap.c:483!


> On Wed, 2005-02-23 at 16:45 -0500, Ammar T. Al-Sayegh wrote:
>> > On Wed, 2005-02-23 at 15:41 -0500, Ammar T. Al-Sayegh wrote:
>> >> Hi All,
>> >> 
>> >> I recently installed Fedora RC3 on a new server.
>> >> The kernel is 2.6.10-1.741_FC3smp. The server
>> >> crashes every few days. When I examine /var/log/messages,
>> >> I find the following line just before the crash:
>> >> 
>> >> Feb 22 23:50:35 hostname kernel: ------------[ cut here ]------------
>> >> Feb 22 23:50:35 hostname kernel: kernel BUG at mm/rmap.c:483!
>> >> 
>> >> No further debug lines are given to diagnose the
>> >> source of the 
>> > no oops at all?
>> 
>> No. Is there a way to enable the kernel to give more
>> diagnostic debug output next time this error happens?
> 
> not 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?

Thanks.


-ammar

  reply	other threads:[~2005-02-23 22:51 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 [this message]
2005-02-24  8:38         ` Arjan van de Ven
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='007d01c519f9$7c9a5f50$7101a8c0@shrugy' \
    --to=ammar@kunet.com \
    --cc=arjan@infradead.org \
    --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®