Re: weirdness with compiling a 2.6.33 kernel on arm debian

[dave b]

I had already reported it to debian -
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572653

I have cc'ed linux-arm-kernel into this email.



On 6 March 2010 20:03, Mikael Pettersson <mikpe@xxxxxxxx> wrote:
> dave b writes:
> Â> Hi have now successfully built a 2.6.33 kernel on a linkstation pro
> Â> v2. This is an arm device. It is currently running debianÃÂ lenny
> Â> armel.
> Â>
> Â>
> Â> I compiledÃÂ (make) zImage, then did a make modules which failed on the
> Â> first two rounds of compiling the modules -
> Â>
> Â> "fs/afs/super.c: In function ÃâËafs_test_superÃââ:
> Â> fs/afs/super.c:278: internal compiler error: Segmentation fault
> Â> Please submit a full bug report,
> Â> with preprocessed source if appropriate.
> Â> See <file:///usr/share/doc/gcc-4.3/README.Bugs> for instructions."
> Â> This was the error encountered on the attempt at compiling the
> Â> modules.
> Â>
> Â> "crypto/gcm.c: In function ÃâËcrypto_gcm_setauthsizeÃââ:
> Â> crypto/gcm.c:152: internal compiler error: Segmentation fault
> Â> Please submit a full bug report,
> Â> with preprocessed source if appropriate.
> Â> See <file:///usr/share/doc/gcc-4.3/README.Bugs> for instructions.
> Â> make[1]: *** [crypto/gcm.o] Error 1"
> Â> This was the error the on the second attempt at compiling the modules.
> Â>
> Â> The 3rd attempt at building the modules was successful...
> Â>
> Â> The device boots and runs fine with this kernel and modules appear to work.
> Â> [root@nas ~]# uname -a
> Â> Linux nas 2.6.33 #1 Fri Mar 5 23:54:51 EST 2010 armv5tel GNU/Linux
> Â>
> Â>
> Â> *SO* is this a gcc bug or is it related to the changes to the build
> Â> process on arm?
> Â>
> Â>
> Â>
> Â> gcc -v
> Â> Using built-in specs.
> Â> Target: arm-linux-gnueabi
> Â> Configured with: ../src/configure -v --with-pkgversion='Debian
> Â> 4.3.2-1.1' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs
> Â> --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
> Â> --enable-shared --with-system-zlib --libexecdir=/usr/lib
> Â> --without-included-gettext --enable-threads=posix --enable-nls
> Â> --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3
> Â> --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc
> Â> --enable-mpfr --disable-libssp --disable-sjlj-exceptions
> Â> --enable-checking=release --build=arm-linux-gnueabi
> Â> --host=arm-linux-gnueabi --target=arm-linux-gnueabi
> Â> Thread model: posix
> Â> gcc version 4.3.2 (Debian 4.3.2-1.1)
>
> GCC bug. Report it to Debian, just like it asked you to.
>
> In theory it could be flaky hardware or a kernel/CPU combination
> with cache coherency issues, but in those cases I'd have expected
> many more failures.
>
> The ARM kernel mailing list is linux-arm-kernel@xxxxxxxxxxxxxxxxxxxx
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/