public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Daniel Mack <daniel@caiaq.de>
To: dave b <db.pub.mail@gmail.com>
Cc: Mikael Pettersson <mikpe@it.uu.se>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: weirdness with compiling a 2.6.33 kernel on arm debian
Date: Sat, 6 Mar 2010 11:41:31 +0100	[thread overview]
Message-ID: <20100306104131.GV28972@buzzloop.caiaq.de> (raw)
In-Reply-To: <25ae2d691003060224x67ab1c9au5102c8a22518aff@mail.gmail.com>

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


  reply	other threads:[~2010-03-06 10:41 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-06  3:58 weirdness with compiling a 2.6.33 kernel on arm debian dave b
2010-03-06  9:03 ` Mikael Pettersson
2010-03-06 10:24   ` dave b
2010-03-06 10:41     ` Daniel Mack [this message]
2010-03-07  1:05       ` dave b
2010-03-07 11:01         ` Martin Guy
2010-03-08  9:53         ` Uwe Kleine-König
2010-03-08 10:31           ` Daniel Mack
2010-03-11 13:10             ` dave b
2010-03-11 13:33     ` Russell King - ARM Linux
2010-03-15  1:02       ` Jamie Lokier
2010-03-26 10:12         ` dave b
2010-04-01  6:08           ` Pavel Machek

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100306104131.GV28972@buzzloop.caiaq.de \
    --to=daniel@caiaq.de \
    --cc=db.pub.mail@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox