From: Robert Hancock <hancockr@shaw.ca>
To: linux-kernel@vger.kernel.org
Subject: Re: seeing some "Bad page state in process.." msgs....
Date: Sun, 16 Nov 2008 21:32:16 -0600 [thread overview]
Message-ID: <4920E5C0.5050602@shaw.ca> (raw)
In-Reply-To: <49188EFB.7070601@atl.lmco.com>
Gautam Thaker wrote:
> I am running 2.6.26.6-rt11-1.2944.fc6.emulab-highmem #1 SMP PREEMPT RT
>
> My test pgm is a java pgm that has about 650 threads in it (i am doing
> some stress testing). This test runs w/o any kernel messages when run on
> vanilla 2.6.25 kernel. But w/ the above RT kernel I see some kernel msgs
> that I do not understand.
>
> ANy hints?
>
> root@node0> time java -classpath .:../../../utils/hist Test1 500 10001
> 1 > out.500_senders_RT
>
> Message from syslogd@node0 at Mon Nov 10 18:54:14 2008 ...
> node0 kernel: Bad page state in process 'java'
>
> Message from syslogd@node0 at Mon Nov 10 18:54:14 2008 ...
> node0 kernel: page:c8a690b8 flags:0x80000000 mapping:c8a690c8 mapcount:0
> count:0
>
> Message from syslogd@node0 at Mon Nov 10 18:54:14 2008 ...
>
> Message from syslogd@node0 at Mon Nov 10 18:54:14 2008 ...
> node0 kernel: Trying to fix it up, but a reboot is needednode0
> kernel: Backtrace:
>
> <MY ADDED NOTE: NO Backtrace is produced.>
You should be able to get this from dmesg, or from /var/log/messages if
you rebooted already..
>
> root@node0> uname -a
> Linux node0.onepc2950rtnode.atlqos.emulab.atl.lmco.com
> 2.6.26.6-rt11-1.2944.fc6.emulab-highmem #1 SMP PREEMPT RT Sat Nov 8
> 20:10:03MST 2008 i686 i686 i386 GNU/Linux
> root@node0>
>
prev parent reply other threads:[~2008-11-17 3:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 19:43 seeing some "Bad page state in process.." msgs Gautam Thaker
2008-11-17 3:32 ` Robert Hancock [this message]
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=4920E5C0.5050602@shaw.ca \
--to=hancockr@shaw.ca \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.