From: "Oleg A. Yurlov" <kris@spylog.com>
To: andrea@suse.de
Cc: linux-kernel@vger.kernel.org
Subject: 2.4.10aa1 - 0-order allocation failed.
Date: Wed, 26 Sep 2001 18:07:48 +0400 [thread overview]
Message-ID: <1601012257268.20010926180748@spylog.com> (raw)
Hi, Andrea,
We have next problem on our servers:
Sep 26 11:22:39 sol kernel: __alloc_pages: 0-order allocation failed (gfp=0x20/0)
Sep 26 11:22:39 sol kernel: f048dd94 e02ab000 00000000 00000020 00000000 00000020 00000020 e298f820
Sep 26 11:22:39 sol kernel: e298f844 00000001 e030a56c e030a6c4 00000020 00000000 e01382be 00000000
Sep 26 11:22:39 sol kernel: e013874a e013488c 00000000 e298f820 00000202 e298f898 00000202 00000246
Sep 26 11:22:39 sol kernel: Call Trace: [put_dirty_page+122/132] [flush_old_exec+234/572] [sys_ustat+212/268] [kill_super+232/352] [unix_gc+394/748]
Sep 26 11:22:39 sol kernel: [Unused_offset+27374/99203] [Unused_offset+12842/99203] [call_spurious_interrupt+14521/27705] [Unused_offset+43342/99203] [call_spurious_interrupt+14615/27705] [call_spurious_interrupt+16483/27705]
Sep 26 11:22:39 sol kernel: [Unused_offset+90704/99203] [ipgre_rcv+233/636] [ipgre_rcv+503/636] [fcntl_getlk+327/624] [do_invalid_TSS+43/96]
Sep 26 11:22:39 sol kernel: __alloc_pages: 0-order allocation failed (gfp=0x20/0)
Sep 26 11:22:39 sol kernel: f048ddd4 e02ab000 00000000 00000020 00000000 00000020 00000020 e298f820
Sep 26 11:22:39 sol kernel: e298f844 00000001 e030a56c e030a6c4 00000020 00000000 e01382be 00000000
Sep 26 11:22:39 sol kernel: e013874a e013488c 00000000 e298f820 00000202 e298f898 00000202 00000246
Sep 26 11:22:39 sol kernel: Call Trace: [put_dirty_page+122/132] [flush_old_exec+234/572] [sys_ustat+212/268] [kill_super+232/352] [unix_gc+394/748]
Sep 26 11:22:39 sol kernel: [Unused_offset+27374/99203] [call_spurious_interrupt+13905/27705] [call_spurious_interrupt+17048/27705] [Unused_offset+90704/99203] [ipgre_rcv+233/636] [ipgre_rcv+503/636]
Sep 26 11:22:39 sol kernel: [fcntl_getlk+327/624] [do_invalid_TSS+43/96]
Also, we see next in process status:
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
vz 927 0.0 625.1 43900 4267034752 ? S 08:10 0:00 hits
vz 1030 0.0 625.1 43900 4267034752 ? S 08:11 0:00 hits
vz 4561 1.3 625.1 45948 4267034724 ? S 10:48 0:00 hits
root 4564 0.0 0.0 1460 548 pts/2 S 10:48 0:00 grep hits
vz 4566 0.0 625.1 45948 4267034724 ? S 10:48 0:00 hits
After these errors we see some uninterruptable processes (with flag D in
process status), gdb say that function "fdatasync" called and no returned...
Soft reboot not work.
Server has 2 CPUs (Pentium III Katmai), 2Gb RAM, 2Gb swap, Hardware
RAID (Mylex DAC960PTL1 PCI RAID Controller).
Any ideas ?
--
Oleg A. Yurlov aka Kris Werewolf, SysAdmin OAY100-RIPN
mailto:kris@spylog.com +7 095 332-03-88
next reply other threads:[~2001-09-26 14:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-26 14:07 Oleg A. Yurlov [this message]
2001-09-26 14:45 ` 2.4.10aa1 - 0-order allocation failed Andrea Arcangeli
2001-09-26 15:02 ` Marcelo Tosatti
2001-09-26 16:31 ` Andrea Arcangeli
2001-09-26 18:49 ` Marcelo Tosatti
2001-09-26 21:34 ` Andrea Arcangeli
2001-09-26 20:24 ` Marcelo Tosatti
2001-09-26 21:58 ` Andrea Arcangeli
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=1601012257268.20010926180748@spylog.com \
--to=kris@spylog.com \
--cc=andrea@suse.de \
--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