Hi Heinz, On 5 December 2010 14:33, Heinz Diehl <htd@xxxxxxxxxx> wrote: > On 05.12.2010, Theodore Tso wrote: > >> As another thought, what version of GCC are people using who >> are having difficulty? Could this perhaps be a compiler-related issue? > > htd@liesel:~> gcc -v > Using built-in specs. > Target: x86_64-suse-linux > Configured with: ../configure --prefix=/usr --infodir=/usr/share/info > --mandir=/usr/share/man --libdir=/usr/lib64 --libexecdir=/usr/lib64 > --enable-languages=c,c++,objc,fortran,obj-c++,java,ada > --enable-checking=release --with-gxx-include-dir=/usr/include/c++/4.3 > --enable-ssp --disable-libssp --with-bugurl=http://bugs.opensuse.org/ > --with-pkgversion='SUSE Linux' --disable-libgcj --disable-libmudflap > --with-slibdir=/lib64 --with-system-zlib --enable-__cxa_atexit > --enable-libstdcxx-allocator=new --disable-libstdcxx-pch > --enable-version-specific-runtime-libs --program-suffix=-4.3 > --enable-linux-futex --without-system-libunwind --with-cpu=generic > --build=x86_64-suse-linux > Thread model: posix > gcc version 4.3.2 [gcc-4_3-branch revision 141291] (SUSE Linux) A bit late to the party, but does memtest86 pass over multiple iterations? Also, can you send an 'sudo lspci -vv', so we can check for known-buggy controllers and bridges? Thanks, Daniel -- Daniel J Blueman -- To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
