mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: dave b <db.pub.mail@gmail.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: 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 21:24:49 +1100	[thread overview]
Message-ID: <25ae2d691003060224x67ab1c9au5102c8a22518aff@mail.gmail.com> (raw)
In-Reply-To: <19346.6765.457769.167118@pilspetsen.it.uu.se>

I had already reported it to debian -
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572653

I have cc'ed linux-arm-kernel into this email.



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...
>  >
>  > The device boots and runs fine with this kernel and modules appear to work.
>  > [root@nas ~]# uname -a
>  > Linux nas 2.6.33 #1 Fri Mar 5 23:54:51 EST 2010 armv5tel GNU/Linux
>  >
>  >
>  > *SO* is this a gcc bug or is it related to the changes to the build
>  > process on arm?
>  >
>  >
>  >
>  > gcc -v
>  > Using built-in specs.
>  > Target: arm-linux-gnueabi
>  > Configured with: ../src/configure -v --with-pkgversion='Debian
>  > 4.3.2-1.1' --with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs
>  > --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
>  > --enable-shared --with-system-zlib --libexecdir=/usr/lib
>  > --without-included-gettext --enable-threads=posix --enable-nls
>  > --with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3
>  > --enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc
>  > --enable-mpfr --disable-libssp --disable-sjlj-exceptions
>  > --enable-checking=release --build=arm-linux-gnueabi
>  > --host=arm-linux-gnueabi --target=arm-linux-gnueabi
>  > Thread model: posix
>  > gcc version 4.3.2 (Debian 4.3.2-1.1)
>
> GCC bug. Report it to Debian, just like it asked you to.
>
> In theory it could be flaky hardware or a kernel/CPU combination
> with cache coherency issues, but in those cases I'd have expected
> many more failures.
>
> The ARM kernel mailing list is linux-arm-kernel@lists.infradead.org.
>

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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-06  3:58 dave b
2010-03-06  9:03 ` Mikael Pettersson
2010-03-06 10:24   ` dave b [this message]
2010-03-06 10:41     ` Daniel Mack
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=25ae2d691003060224x67ab1c9au5102c8a22518aff@mail.gmail.com \
    --to=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

all inboxes | Powered by JetHome®