linux-kernel - Re: weirdness with compiling a 2.6.33 kernel on arm debian

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 6 Mar 2010 10:03:41 +0100
From:	Mikael Pettersson <mikpe@...uu.se>
To:	dave b <db.pub.mail@...il.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: weirdness with compiling a 2.6.33 kernel on arm debian

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@...ts.infradead.org.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/