From: CoolCold <coolthecold@gmail.com>
To: Christian Kujau <lists@nerdbynature.de>
Cc: Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.28.10 - kernel BUG at mm/rmap.c:725
Date: Thu, 24 Dec 2009 16:47:06 +0300 [thread overview]
Message-ID: <f19d625d0912240547q2a82a82fueaef72c425c02279@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.01.0912240356070.3483@bogon.housecafe.de>
On Thu, Dec 24, 2009 at 3:01 PM, Christian Kujau <lists@nerdbynature.de> wrote:
> On Thu, 24 Dec 2009 at 14:09, CoolCold wrote:
>> 3 days ago LA on server become very high
>
> Was the higher load caused by "real" work, i.e. were there more processes
> running than usual or did the load increase "just so"?
Programmer was editing some scripts and reported he had messages in
console (actually the same messages as in the log), server was unable
to do usual work - LA becomes too high, so it was rebooted ( not
resetted ). After reboot server continued to work fine. Now I'm
figuring out what happened.
>
>> bug - kernel BUG at mm/rmap.c:725! . Googling didn't provide me with
>> exact answer is it bug or hardware problems, something similar was
>
> Did you check for hardware problems? Running memtest for a day would be a
> good start, I think. If the load did increase "just so" and the machine
> (and the same kernel) were stable before, it's most likely hardware
> related.
Machine was not rock solid - got occasional hangs once or two a month,
but without any records in logs and as there is no IPKVM, so i can't
say were something like kernel panic on console or not. Rephrasing
question - is this 'Kernel BUG' looking like bug or more than hardware
problem.
Memtest was not done yet though is planned when other machine will be rented.
>
> Christian.
> --
> BOFH excuse #102:
>
> Power company testing new voltage spike (creation) equipment
>
--
Best regards,
[COOLCOLD-RIPN]
next prev parent reply other threads:[~2009-12-24 13:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-24 11:09 CoolCold
2009-12-24 12:01 ` Christian Kujau
2009-12-24 13:47 ` CoolCold [this message]
2009-12-25 4:56 ` Américo Wang
2009-12-25 5:14 ` KOSAKI Motohiro
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=f19d625d0912240547q2a82a82fueaef72c425c02279@mail.gmail.com \
--to=coolthecold@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lists@nerdbynature.de \
/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®