From: Denis Perchine <dyp@perchine.com>
To: linux-kernel@vger.kernel.org
Subject: Strange lines in dmesg
Date: Fri, 30 Mar 2001 16:33:14 +0700 [thread overview]
Message-ID: <200103300935.QAA02956@gw.ac-sw.com> (raw)
Hello,
I got the following lines in dmesg:
free sibling
task PC stack pid father child younger older
init S C144DF28 4912 1 0 840 (NOTLB)
Call Trace: [<c01111ab>] [<c01110f0>] [<c01398e5>] [<c0139c8e>] [<c01330c4>]
[<c0106dd7>]
keventd S FFFFFFFF 6020 2 1 (L-TLB) 3
Call Trace: [<c011d9db>] [<c01054f4>]
kswapd S C1455FAC 5812 3 1 (L-TLB) 4 2
Call Trace: [<c01111ab>] [<c01110f0>] [<c01116ea>] [<c0127499>] [<c01054f4>]
kreclaimd S 00000286 6316 4 1 (L-TLB) 5 3
Call Trace: [<c0111695>] [<c012754b>] [<c01054f4>]
bdflush S C1450000 5972 5 1 (L-TLB) 6 4
Call Trace: [<c012f97e>] [<c01054f4>]
kupdated S C147FFC8 6296 6 1 (L-TLB) 197 5
And more for other processes.
As far as I can understand lines containing 'Call Trace' are printed in
trap.c in show_trace function. Does anyone know what this thing can mean, and
how to found a real reason?
Problem is that on this machine I have install 2.3.2-ac26 + Morton's patch to
allow very large processes not be killed when there are not reused pages in
swap, etc.
My sci advisor have real problem as his process beying killed when reached
960Mb. There is 256Mb of RAM in machine, and 1.5Gb of swap... It looks like
it is again a problem with kernel does not use all possibilities before kill
a process.
And what worries me is that I found mentioned above lines in kernel log.
--
Sincerely Yours,
Denis Perchine
----------------------------------
E-Mail: dyp@perchine.com
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------
next reply other threads:[~2001-03-30 9:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-30 9:33 Denis Perchine [this message]
2001-03-30 18:07 ` Shawn Starr
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=200103300935.QAA02956@gw.ac-sw.com \
--to=dyp@perchine.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®