On Thursday 19 January 2006 12:00 pm, Geert Uytterhoeven wrote: > On Thu, 19 Jan 2006, P. Christeas wrote: > > Just to let you know: > > In a very interesting twist, gcc4.0.2 produces a faulty kernel with the > > 2.4.31 kernel (as the latter is provided from the hardware's > > manufacturer). I'm validating gcc and binutils at the moment. > > That's why 2 days ago this one went in in 2.4.x: > | [PATCH] document that gcc 4 is not supported > | > | gcc 4 is not supported for compiling kernel 2.4, and I don't see any > | compelling reason why kernel 2.4 should ever be adapted to gcc 4. Which comes round to the main reason I'm doing this work (port the platform to 2.6): if we are not using the *latest* kernel with the *latest* build/user tools, then we cannot share our work. Patches to an old kernel/gcc may probably get discarded when moving to the next version. Nevertheless, I think my problem has been the binutils. After switching to version 2.16.1, the oops probability (per reset) dropped from 80% to <20% and the oops is less random. (that is, there is also one, real, bug)
