Re: allocation failures

[Goswin von Brederlow <brederlo@informatik.uni-tuebingen.de>]

Daniel van Eeden <daniel_e@dds.nl> writes:

> Which bugs are causing these allocation failures?
> Notice that cups and pdflush are both handling pdf's.
> setiathome is version 3.08
>
> $ dmesg | grep "allocation failure"
> setiathome: page allocation failure. order:0, mode:0x20
> setiathome: page allocation failure. order:0, mode:0x20
> setiathome: page allocation failure. order:0, mode:0x20
> setiathome: page allocation failure. order:0, mode:0x20
> setiathome: page allocation failure. order:0, mode:0x20
> pdflush: page allocation failure. order:0, mode:0x20
> pdflush: page allocation failure. order:0, mode:0x20
> pdflush: page allocation failure. order:0, mode:0x20
> pdflush: page allocation failure. order:0, mode:0x20
> setiathome: page allocation failure. order:0, mode:0x20
> setiathome: page allocation failure. order:0, mode:0x20
> bzip2: page allocation failure. order:0, mode:0x20
> setiathome: page allocation failure. order:0, mode:0x20
> setiathome: page allocation failure. order:0, mode:0x20
> setiathome: page allocation failure. order:0, mode:0x20
> pdflush: page allocation failure. order:0, mode:0x20
> cupsd: page allocation failure. order:0, mode:0x20
> cupsd: page allocation failure. order:0, mode:0x20
> -- 
> Daniel van Eeden <daniel_e@dds.nl>

Are you by chance just out of memory?

MfG
        Goswin