mount.nfs: page allocation failure: order:4, mode:0xc0d0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Incomplete
|
Medium
|
Unassigned |
Bug Description
I noticed an error in dmesg to the effect that mount.nfs was not able to allocate memory. We auto-mount NFS directories on this system, if that's relevant. The server has 2GB of RAM and typically has 1.5GB free with almost no swap used.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-
ProcVersionSign
Uname: Linux 3.2.0-24-generic i686
AlsaDevices:
total 0
crw-rw---T 1 root audio 116, 1 May 22 16:07 seq
crw-rw---T 1 root audio 116, 33 May 22 16:07 timer
AplayDevices: aplay: device_list:252: no soundcards found...
ApportVersion: 2.0.1-0ubuntu7
Architecture: i386
ArecordDevices: arecord: device_list:252: no soundcards found...
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found.
Date: Fri May 25 14:42:14 2012
IwConfig: Error: [Errno 2] No such file or directory
MachineType: Dell Computer Corporation PowerEdge 860
PciMultimedia:
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: root=/dev/sda1 ro
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageV
linux-
linux-
linux-firmware 1.79
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
WifiSyslog:
dmi.bios.date: 04/04/2007
dmi.bios.vendor: Dell Computer Corporation
dmi.bios.version: A03
dmi.board.name: 0XM089
dmi.board.vendor: Dell Computer Corporation
dmi.board.version: A00
dmi.chassis.type: 23
dmi.chassis.vendor: Dell Computer Corporation
dmi.modalias: dmi:bvnDellComp
dmi.product.name: PowerEdge 860
dmi.sys.vendor: Dell Computer Corporation
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
Did this issue start happening after an update/upgrade? Was there a kernel version where you were not having this particular problem? This will help determine if the problem you are seeing is the result of the introduction of a regression, and when this regression was introduced.