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 at caiaq.de> wrote:
> On Sat, Mar 06, 2010 at 09:24:49PM +1100, dave b wrote:
>> On 6 March 2010 20:03, Mikael Pettersson <mikpe at it.uu.se> 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
>
>