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 16:45:29 -0500 [thread overview]
Message-ID: <003001c519f1$031afc00$7101a8c0@shrugy> (raw)
In-Reply-To: <1109192040.6290.108.camel@laptopd505.fenrus.org>
> 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?
Is there a way to at least make the server reboot itself
next time the kernel is alerted to this problem before
crashing? When the server is rebooted, it works fine for
few more days before encountering this problem and
crashing again.
> which modules are you using?
[root ~]# lsmod
Module Size Used by
ip_conntrack_ftp 76145 0
md5 8001 1
ipv6 236769 78
autofs4 21829 0
i2c_dev 13249 0
i2c_core 24513 1 i2c_dev
sunrpc 135077 1
ipt_REJECT 10561 2
ipt_state 5825 79
ip_conntrack 45317 2 ip_conntrack_ftp,ipt_state
iptable_filter 7489 1
ip_tables 20929 3 ipt_REJECT,ipt_state,iptable_filter
microcode 11489 0
dm_mod 57925 0
video 19653 0
button 10577 0
battery 13253 0
ac 8773 0
uhci_hcd 33497 0
ehci_hcd 33737 0
e1000 84629 0
floppy 56913 0
ext3 117961 6
jbd 57177 1 ext3
3w_xxxx 30561 0
ata_piix 12485 7
libata 44101 1 ata_piix
sd_mod 20545 9
scsi_mod 116033 3 3w_xxxx,libata,sd_mod
Any clue?
-ammar
next prev parent reply other threads:[~2005-02-23 21:47 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 [this message]
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
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='003001c519f1$031afc00$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®