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 11:41:31 +0100
From:	Daniel Mack <daniel@...aq.de>
To:	dave b <db.pub.mail@...il.com>
Cc:	Mikael Pettersson <mikpe@...uu.se>, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: weirdness with compiling a 2.6.33 kernel on arm debian

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

--
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/

Powered by blists - more mailing lists