From: db.pub.mail@gmail.com (dave b)
To: linux-arm-kernel@lists.infradead.org
Subject: weirdness with compiling a 2.6.33 kernel on arm debian
Date: Sun, 7 Mar 2010 12:05:21 +1100 [thread overview]
Message-ID: <25ae2d691003061705l5fc0bca7n4a07f558a0c410cf@mail.gmail.com> (raw)
In-Reply-To: <20100306104131.GV28972@buzzloop.caiaq.de>
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@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@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
>
>
next prev parent reply other threads:[~2010-03-07 1:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <25ae2d691003051958x72040b47g29d842f1d389a6cf@mail.gmail.com>
[not found] ` <19346.6765.457769.167118@pilspetsen.it.uu.se>
2010-03-06 10:24 ` weirdness with compiling a 2.6.33 kernel on arm debian dave b
2010-03-06 10:41 ` Daniel Mack
2010-03-07 1:05 ` dave b [this message]
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=25ae2d691003061705l5fc0bca7n4a07f558a0c410cf@mail.gmail.com \
--to=db.pub.mail@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).