From: Yaroslav Halchenko <yoh@psychology.rutgers.edu>
To: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: alienware hardware - memory problem?
Date: Thu, 24 Jun 2004 20:01:02 -0400 [thread overview]
Message-ID: <20040625000102.GI728@washoe.rutgers.edu> (raw)
In-Reply-To: <20040624215856.GA728@washoe.rutgers.edu>
because slow down seems to be linked to memory: brk(0) takes on average
0.5-1.5 second, I've decided to run silly memtest...
I have around 1GB total on that beast, I turned off swap and did memtest
1G
kernel killed the task with reporting:
Out of Memory: Killed process 1336 (memtest).
memtest: page allocation failure. order:0, mode:0xd2
[<c0140781>] __alloc_pages+0x2da/0x34a
[<c014c8f5>] do_anonymous_page+0x71/0x1d8
[<c014cabf>] do_no_page+0x63/0x398
[<c014aa06>] pte_alloc_map+0xa6/0xe7
[<c014d010>] handle_mm_fault+0xfe/0x1af
[<c014b79d>] get_user_pages+0x154/0x40b
[<c014d1b1>] make_pages_present+0x8c/0xa6
[<c014d5fb>] mlock_fixup+0xb7/0xc7
[<c014d6e8>] do_mlock+0xdd/0xea
[<c014d792>] sys_mlock+0x9d/0xa3
[<c0105b63>] syscall_call+0x7/0xb
memtest: page allocation failure. order:0, mode:0x1d2
[<c0140781>] __alloc_pages+0x2da/0x34a
[<c0143846>] do_page_cache_readahead+0x15d/0x1b9
[<c013d316>] filemap_nopage+0x337/0x395
[<c014cb21>] do_no_page+0xc5/0x398
[<c014aa06>] pte_alloc_map+0xa6/0xe7
[<c014d010>] handle_mm_fault+0xfe/0x1af
[<c0117c3e>] do_page_fault+0x325/0x50d
[<c01191ff>] wake_up_process+0x1e/0x22
[<c01f865a>] rwsem_wake+0xc2/0x144
[<c014d9c0>] .text.lock.mlock+0x1a/0x7e
[<c0117919>] do_page_fault+0x0/0x50d
[<c01065ed>] error_code+0x2d/0x38
last block 3 times and then
VM: killing process memtest
is that normal?
--
Yarik
On Thu, Jun 24, 2004 at 05:58:57PM -0400, Yaroslav Halchenko wrote:
> just once again and I will stop before I try with noioapic and acpi=off:
> when I did strace on ps auxw it spends second or two again on mmap2
> whenever it doesn't do that on any other machine
> here is strace with relative timestamps (strace -r) of ps auxw
> 3003 0.001784 open("/boot/System.map-2.6.7-bk7", O_RDONLY|O_NONBLOCK|O_NOCTTY) = 6
> 3003 0.001171 fstat64(6, {st_mode=S_IFREG|0644, st_size=932887, ...}) = 0
> 3003 0.001598 mmap2(NULL, 932888, PROT_READ|PROT_WRITE, MAP_PRIVATE, 6, 0) = 0x40163000
> 3003 0.001156 close(6) = 0
> 3003 1.930769 mmap2(NULL, 266240, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x40247000
> 3003 1.322821 open("/proc", O_RDONLY|O_NONBLOCK|O_LARGEFILE|O_DIRECTORY) = 6
> 3003 0.001124 fstat64(6, {st_mode=S_IFDIR|0555, st_size=0, ...}) = 0
> On Thu, Jun 24, 2004 at 05:26:00PM -0400, Yaroslav Halchenko wrote:
> > On Thu, Jun 24, 2004 at 11:58:55PM +0300, Denis Vlasenko wrote:
> > > Do a
> > > # strace -p 1501
> > > and you'll se what's going on
> > can you please help me to understand the dump?
> > time strace -p 2586
> > Process 2586 attached - interrupt to quit
> > brk(0) = 0x8dff000
> > brk(0x8e21000) = 0x8e21000
> > brk(0) = 0x8e21000
> > brk(0x8e43000) = 0x8e43000
> > brk(0) = 0x8e43000
> > brk(0x8e65000) = 0x8e65000
> > brk(0) = 0x8e65000
> > brk(0x8e87000) = 0x8e87000
> > brk(0) = 0x8e87000
> > brk(0x8ea9000) = 0x8ea9000
> > brk(0) = 0x8ea9000
> > brk(0x8ecb000) = 0x8ecb000
> > brk(0) = 0x8ecb000
> > brk(0x8eed000) = 0x8eed000
> > brk(0) = 0x8eed000
> > brk(0x8f0f000) = 0x8f0f000
> > brk(0) = 0x8f0f000
> > brk(0x8f30000) = 0x8f30000
> > brk(0) = 0x8f30000
> > brk(0x8f52000) = 0x8f52000
> > Process 2586 detached
> > real 0m6.927s
> > user 0m0.032s
> > sys 0m0.004s
> > if I dump longer than the rest kinda flies so it is slows down just
> > after
> > open("/var/lib/dpkg/available", O_RDONLY) = 4
> > fstat64(4, {st_mode=S_IFREG|0644, st_size=12398100, ...}) = 0
> > mmap2(NULL, 12398100, PROT_READ, MAP_SHARED, 4, 0) = 0x40157000
> > brk(0) = 0x840e000
> > brk(0x8430000) = 0x8430000
> > brk(0) = 0x8430000
> > ....
> > I will check once more when it 'delays'
--
Yaroslav Halchenko
Research Assistant, Psychology Department, Rutgers
Office (973) 353-5440 x263
Ph.D. Student CS Dept. NJIT
Key http://www.onerussian.com/gpg-yoh.asc
GPG fingerprint 3BB6 E124 0643 A615 6F00 6854 8D11 4563 75C0 24C8
next prev parent reply other threads:[~2004-06-25 0:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 19:10 alienware hardware Yaroslav Halchenko
[not found] ` <200406242315.56213.vda@port.imtp.ilyichevsk.odessa.ua>
2004-06-24 20:26 ` Yaroslav Halchenko
[not found] ` <200406242358.55782.vda@port.imtp.ilyichevsk.odessa.ua>
2004-06-24 21:09 ` Yaroslav Halchenko
2004-06-24 21:26 ` Yaroslav Halchenko
2004-06-24 21:58 ` Yaroslav Halchenko
2004-06-25 0:01 ` Yaroslav Halchenko [this message]
2004-06-25 8:54 ` alienware hardware - memory problem? Helge Hafting
2004-06-25 16:20 ` Yaroslav Halchenko
2004-06-26 12:07 ` Helge Hafting
2004-06-26 15:45 ` Yaroslav Halchenko
2004-06-26 18:41 ` Helge Hafting
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=20040625000102.GI728@washoe.rutgers.edu \
--to=yoh@psychology.rutgers.edu \
--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®