[lkml]   [2004]   [May]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: kernel BUG at page_alloc.c:98 -- compiling with distcc
    --On Monday, May 03, 2004 22:07:14 -0300 Marcelo Tosatti 
    <> wrote:

    > On Fri, Apr 02, 2004 at 12:21:03PM +0200, Marco Fais wrote:
    >> Hi!
    >> [1.] Kernel panic while using distcc
    >> [2.] I have 5-6 development linux systems that we use without problem
    >> under a normal development workload. Trying distcc for speeding up
    >> compilation, we have a fully reproducible kernel panic in a very short
    >> time (seconds after compilation start). The kernel panic happens *only*
    >> when the systems are "remotely controlled" (the distcc daemon is
    >> receiving source files from remote systems, compile and send back
    >> compiled objects). When compiling with distcc the local system doesn't
    >> show any kernel panic, while the same system used as a "remote compiler
    >> system" dies very quickly.
    >> [3.] Keywords: distcc BUG page_alloc.c
    > Marco, Carson,
    > Can you please try to reproduce this distcc generated oops using
    > 2.4.27-pre2?

    I'd love to. However 2.4.27-pre2 broke the tg3 driver. tg3.c contains
    WARN_ON(1). Sadly, WARN_ON doesn't exist in 2.4.x, so depmod correctly
    complains about an unresolved symbol.

    I'm beginning to wonder if anyone actually builds these pre releases... I
    mean, I know the tg3 driver is really obscure, and only used by 2 people,


    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:02    [W:0.020 / U:21.208 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site