Bug#636306: mount.nfs: page allocation failure. order:4, mode:0xc0d0

To: debian-kernel@lists.debian.org
Cc: 636306@bugs.debian.org
Subject: Bug#636306: mount.nfs: page allocation failure. order:4, mode:0xc0d0
From: Berni Elbourn <berni@elbournb.fsnet.co.uk>
Date: Tue, 02 Aug 2011 12:22:25 +0100
Message-id: <[🔎] 4E37DDF1.9060002@elbournb.fsnet.co.uk>
Reply-to: Berni Elbourn <berni@elbournb.fsnet.co.uk>, 636306@bugs.debian.org
In-reply-to: <[🔎] 1312282198.2591.60.camel@deadeye>
References: <[🔎] 20110802071325.10241.44118.reportbug@sv22.site> <[🔎] 1312282198.2591.60.camel@deadeye>

On 02/08/11 11:49, Ben Hutchings wrote:

Does this system have swap enabled?


Afraid so...

elbournb@sv22:~$ free -m
             total       used       free     shared    buffers     cached
Mem:           184        172         11          0          5         69
-/+ buffers/cache:         98         85
Swap:          549         99        449

Reply to:

References:
- Bug#636306: mount.nfs: page allocation failure. order:4, mode:0xc0d0
  - From: Berni Elbourn <berni@elbournb.fsnet.co.uk>
- Bug#636306: mount.nfs: page allocation failure. order:4, mode:0xc0d0
  - From: Ben Hutchings <ben@decadent.org.uk>

Prev by Date: Bug#636340: linux-image-3.0.0-1-686-pae: KMS produces garbage on Zacate (E35M1-I)
Next by Date: Bug#636290: linux-image-2.6.32-5-amd64: serious ext4 filesystem corruption even after fsck
Previous by thread: Bug#636306: mount.nfs: page allocation failure. order:4, mode:0xc0d0
Next by thread: Bug#636306: Correction: "missing" parameter reference
Index(es):
- Date
- Thread