Re: weirdness with compiling a 2.6.33 kernel on arm debian

[dave b]

Ok... however how should one test the memory of an arm machine? ...
memtest is only for x86. *I am referring to the kernel memtest and not
memtest86.


On 6 March 2010 21:41, Daniel Mack <daniel@xxxxxxxx> wrote:
> On Sat, Mar 06, 2010 at 09:24:49PM +1100, dave b wrote:
>> 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...
>
> Whenever I had comparable problems, it was _always_ faulty RAM on my
> local machine, and I'm very sure you're seeing a similar. _If_ gcc
> crashes, it will always do that for the same input.
>
> Daniel
>
>
--
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/