Re: allocation failures

[Javier Kohen <jkohen@users.sourceforge.net>]

Hi Daniel,

What archive are you using?

Daniel van Eeden wrote:
> Which bugs are causing these allocation failures?
> Notice that cups and pdflush are both handling pdf's.

For your information, pdflush is a kernel process which has nothing to 
do with PDFs.

What architecture was seti@home build for?

> 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


--
Javier Kohen <jkohen@users.sourceforge.net>
ICQ: blashyrkh #2361802
Jabber: jkohen@jabber.org