Re: oom-killer: gfp_mask=0xd1 with 2.6.15.4 on EM64T [previously 2.6.12]

[Andrew Morton <akpm@osdl.org>]

J M Cerqueira Esteves <jmce@artenumerica.com> wrote:
>
> Andrew Morton wrote:
> > We have a candidate fix at
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.16-rc5/2.6.16-rc5-mm2/broken-out/x86_64-mm-blk-bounce.patch.
> >  Could you test that?  (and don't alter the Cc: list!).  The patch is
> > against 2.6.16-rc5.
> 
> Testing that kernel now, with good news: the machine has been apparently
> stable, running Gaussian processes for the last 20 hours, with no
> oom-killer messages.

OK, thanks.  The first iteration of that patch caused ia64 to go BUG, so we
took the BUG out.  We're calling init_emergency_isa_pool() on ia64 which
seems rather silly.  So my confidence level in that patch remains low, and
our need for it is high.

> A new "feature": 36 of these kernel message pairs as boot time:
>   device-mapper: dm-linear: Device lookup failed
>   device-mapper: error adding target to table
> 

OK, there were some fairly large DM patches touching on
dm_get_device().  Cc added ;)

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/