From: "Richard F. Rebel" <rrebel@whenu.com>
To: linux-kernel@vger.kernel.org
Subject: x86_64: pdflush: page allocation failure. order:0, mode:0x20
Date: Fri, 24 Sep 2004 12:13:21 -0400 [thread overview]
Message-ID: <1096042401.2297.14.camel@rebel.corp.whenu.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2409 bytes --]
Hello,
We recently replaced a dual processor intel system with a dual opteron
250 one. The new system is running 2.6.3-16 (from our mdk distro).
We have noticed about once a day the system wedges. Today we got some
debugging info in dmesg. I cannot list all processes (only some then it
wedges), I can't kill many processes (they never die), and I cannot
reboot. A hardware reset is required.
We are using XFS on an MD stripe containing 6 disks. Some directories
on the this filesystem cause ls to wedge when run on them.
If it matters, yes we have 1000bt cards that we do a lot of NFS traffic
over, but no special settings for large frames have been activated.
I saw a similar thread from earlier this year suggesting I increase
/proc/sys/vm/min_free_kbytes, which I did to no avail.
Any insight is appreciated.
pdflush: page allocation failure. order:0, mode:0x20
Call Trace:[<ffffffff80158cba>] [<ffffffff80158dc4>]
[<ffffffff80137340>]
[<ffffffff8015bbe7>] [<ffffffff8015c0c6>] [<ffffffffa000c039>]
[<ffffffffa000ffef>] [<ffffffff802358e5>] [<ffffffff8023974c>]
[<ffffffff80238293>] [<ffffffff80137340>] [<ffffffff802383c0>]
[<ffffffff801778ed>] [<ffffffffa0093de3>] [<ffffffffa009442c>]
[<ffffffff801322f0>] [<ffffffff801322f0>] [<ffffffffa0098ba5>]
[<ffffffffa00948b6>] [<ffffffffa0073b0d>] [<ffffffffa008b595>]
[<ffffffffa0099c09>] [<ffffffff8019223a>] [<ffffffff80192753>]
[<ffffffff80192885>] [<ffffffff801595d0>] [<ffffffff80159b1f>]
[<ffffffff80159550>] [<ffffffff80110327>] [<ffffffff801599d0>]
[<ffffffff8011031f>]
pdflush: page allocation failure. order:0, mode:0x20
Call Trace:[<ffffffff80158cba>] [<ffffffff80158dc4>]
[<ffffffff8015bbe7>]
[<ffffffff8015c0c6>] [<ffffffffa000c039>] [<ffffffffa000ffef>]
[<ffffffff802358e5>] [<ffffffff80238eec>] [<ffffffff8023673d>]
[<ffffffffa009442c>] [<ffffffff801322f0>] [<ffffffff801322f0>]
[<ffffffffa0098ba5>] [<ffffffffa00948b6>] [<ffffffffa0073b0d>]
[<ffffffffa008b595>] [<ffffffffa0099c09>] [<ffffffff8019223a>]
[<ffffffff80192753>] [<ffffffff80192885>] [<ffffffff801595d0>]
[<ffffffff80159b1f>] [<ffffffff80159550>] [<ffffffff80110327>]
[<ffffffff801599d0>] [<ffffffff8011031f>]
--
Richard F. Rebel
rrebel@whenu.com
t. 212.239.0000
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
reply other threads:[~2004-09-24 20:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1096042401.2297.14.camel@rebel.corp.whenu.com \
--to=rrebel@whenu.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
Powered by JetHome