From: Salvador Eduardo Tropea <salvador@inti.gov.ar>
To: Ingo.Saitz@stud.uni-hannover.de,
Marcelo Tosatti <marcelo@conectiva.com.br>,
Linus Torvalds <torvalds@transmeta.com>,
AlanCox <alan@lxorguk.ukuu.org.uk>,
willy@w.ods.org, ast@domdv.de, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19 BUG in page_alloc.c:91
Date: Tue, 27 Aug 2002 09:47:42 -0300 [thread overview]
Message-ID: <3D6B74EE.4000801@inti.gov.ar> (raw)
I can´t find a final conclusion about this topic.
What I found is that it happends some hours after the kernel killed a
process that was eating the memory.
Example:
Aug 26 13:07:22 ice kernel: Out of Memory: Killed process 18432
(mozilla-bin).
Aug 26 13:07:22 ice kernel: Out of Memory: Killed process 18443
(mozilla-bin).
Aug 26 13:07:22 ice kernel: Out of Memory: Killed process 18444
(mozilla-bin).
Aug 26 13:07:22 ice kernel: Out of Memory: Killed process 18445
(mozilla-bin).
Aug 26 13:07:22 ice kernel: Out of Memory: Killed process 18447
(mozilla-bin).
Aug 26 13:07:22 ice kernel: Out of Memory: Killed process 30410
(mozilla-bin).
....
Aug 27 06:26:00 ice kernel: kernel BUG at page_alloc.c:91!
Aug 27 06:26:00 ice kernel: invalid operand: 0000
Aug 27 06:26:00 ice kernel: CPU: 0
Aug 27 06:26:00 ice kernel: EIP: 0010:[__free_pages_ok+45/624]
Tainted: P
Aug 27 06:26:00 ice kernel: EFLAGS: 00010286
Aug 27 06:26:00 ice kernel: eax: c103a528 ebx: c1105760 ecx:
c1105760 edx: c0228e9c
Aug 27 06:26:00 ice kernel: esi: 00000000 edi: 00000016 ebp:
0000005e esp: c7f93f18
Aug 27 06:26:00 ice kernel: ds: 0018 es: 0018 ss: 0018
Aug 27 06:26:00 ice kernel: Process kswapd (pid: 4, stackpage=c7f93000)
Aug 27 06:26:00 ice kernel: Stack: c22d28c0 c1105760 00000016 0000005e
c013755c c1105760 00000
1d0 00000016
Aug 27 06:26:00 ice kernel: 0000005e c0135a09 c22d28c0 c1105760
c012d482 c012e3fb c012d
4bb 00000020
Aug 27 06:26:00 ice kernel: 000001d0 00000020 00000006 00000006
c7f92000 000003a4 00000
1d0 c0229034
Aug 27 06:26:00 ice kernel: Call Trace: [try_to_free_buffers+140/224]
[try_to_release_page+
73/80] [shrink_cache+482/768] [__free_pages+27/32] [shrink_cache+539/768]
Aug 27 06:26:00 ice kernel: [shrink_caches+86/128]
[try_to_free_pages+60/96] [kswapd_balance
_pgdat+67/144] [kswapd_balance+22/48] [kswapd+157/192] [kernel_thread+40/64]
At 6:25 the cron started the regular locate data base update and other
tasks I guess it made the kernel reduce the size of the cache and fail.
I saw reports it happends with "non-tainted" kernels and with or without
nVidia driver, so perhaps that´s a real bug in the mechanism used by the
kernel to kill a process that is eating all the memory introduced in 2.4.19.
I can fill a full bug report but perhaps any of you know about the
conclusion of this thread and I´m just too stupid to find it.
Note that it doesn´t happend if the kernel doesn´t kill mozilla-bin for
days, when kernel kills this process is just a matter of hours before it
and from this point the cache size won´t be reduced.
SET
--
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Visit my home page: http://welcome.to/SetSoft or
http://www.geocities.com/SiliconValley/Vista/6552/
Alternative e-mail: set@computer.org set@ieee.org
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013
next reply other threads:[~2002-08-27 12:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-27 12:47 Salvador Eduardo Tropea [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-08 2:45 2.4.19 BUG in page_alloc.c:91 Anthony Russo., a.k.a. Stupendous Man
2002-08-08 2:50 ` Rik van Riel
2002-08-08 2:54 ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 7:55 ` Willy Tarreau
2002-08-08 15:42 ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 19:43 ` Alan Cox
2002-08-08 18:26 ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 20:04 ` Alan Cox
2002-08-08 12:38 ` Alan Cox
2002-08-08 15:45 ` Anthony Russo., a.k.a. Stupendous Man
2002-08-08 16:07 ` Willy Tarreau
2002-08-08 16:15 ` Anthony Russo., a.k.a. Stupendous Man
2002-08-14 15:19 ` Ingo Saitz
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=3D6B74EE.4000801@inti.gov.ar \
--to=salvador@inti.gov.ar \
--cc=Ingo.Saitz@stud.uni-hannover.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=ast@domdv.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
--cc=torvalds@transmeta.com \
--cc=willy@w.ods.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