On Wed, Sep 01, 2004 at 11:36:09PM +0200, Christoph Hellwig wrote: > On Wed, Sep 01, 2004 at 11:33:31PM +0200, Jan-Jaap van der Heijden wrote: > > I don't think placing a strategic printk() qualifies as a fix though :-) > > Maybe GCC is to blame here. I'm using gcc 3.3.4-6sarge1.0.1 (current from > > testing) > > This indeed smells like a compiler bug > > > Is it safe to use GCC 3.4.1 on this kernel? > > GCC 3.4.1 works fine for me on powerpc. I'd suggest you try all > available compilers (2.95, 3.2, 3.3 and 3.4 should be in Debian IIRC) >
I can confirm that rebuilding with GCC 3.4.1 made the ext3 oops go away. Linux version 2.6.8-1-generic ([EMAIL PROTECTED]) (gcc version 3.4.1 (Debian 3.4.1-4sarge1)) #1 Tue Sep 7 15:40:36 CEST 2004 I'll stresstest it a bit later. I'm getting a lot of these: include/asm/spinlock.h:114: warning: matching constraint does not allow a register I also built 2.6.8.1-mm4 with GCC 3.4.1 on Alpha. This tree contains lots of fixes for compilation with gcc 3.4 and gcc-cvs. It builds without a lot of warnings.
