[nSLUG] Help: CPAN session "killed", "0-order allocation failed"

D G Teed donald.teed at gmail.com
Wed May 13 20:34:49 ADT 2009


On Wed, May 13, 2009 at 5:13 PM, Mike Spencer <mspencer at tallships.ca> wrote:

>
>
>
> So I added a line to /etc/fstab referencing /dev/hda1 as swap, ran
> swapon -a as root.  Then I tried the cpan command again.  This time,
> not only did cpan die, the shell, the instance of emacs in which the
> shell was running and X all died, leaving me at the command prompt in
> the console from which X had been started.  And dmesg reported:
>
>    __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
>     VM: killing process xterm
>
> Since the rule that stupidity is defined as "doing the same thing and
> expecting a different result" isn't true in the domain of heisenbugs,
> I did the same thing again.  Result was a successful fetch of the
> desired perl module, other required modules and graceful exit with no
> error messages.  Except in dmesg, where, once again, the message:
>
>    __alloc_pages: 0-order allocation failed (gfp=0x1d2/0)
>
> appeared.
>
> Any thoughts?  Anybody?
>

Random failures always makes me suspect hardware.
It was the main thing I learned via Gentoo back in 2003.
If compiling the same code fails at different points you
could have bad RAM.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nslug.ns.ca/mailman/private/nslug/attachments/20090513/38c7d4b5/attachment-0001.html>


More information about the nSLUG mailing list