Bug#605648: closed by Ben Hutchings <ben@decadent.org.uk> (Re: Bug#605648: linux 2.6.32-27: page allocation failure (ath9k related?))
> This means your system ran very short of memory and was unable to
> allocate memory to handle incoming network traffic. This may be related
> to whatever you were doing with the disk you attached shortly before.
> Assuming the system continued to work after this low-memory condition,
> this is not a bug.
Fair enough. I didn't notice any ill effects other than these
messages. Just for the record, the system's typical memory load looks
something like this:
$ free -m
total used free shared buffers cached
Mem: 500 438 62 0 57 305
-/+ buffers/cache: 74 425
Swap: 1004 0 1004
At the time these errors occurred, I was copying about 100GB of data
from the USB hard drive (ntfs, mounted read-only) to the 2TB SATA disk
(ext4). I would not have expected that copying files would affect
networking.
> I'm sorry, it really is impossible to do much with just the last half.
As I said, no surprise there.
> problem with 'oops' messages on a standard VGA text console.
Indeed. I don't understand why /etc/modprobe.d/i915-kms.conf is
shipped as part of X.org. I don't have X installed on this machine.
Maybe this file should be moved to the udev package, since udev ships
fbdev-blacklist.conf, which seems somewhat related.
-- graham
Reply to: