From: Andi Kleen <ak@colin2.muc.de>
To: Tony Hoyle <tmh@nodomain.org>
Cc: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: Re: Oops linux 2.4.23-pre6 on amd64
Date: 5 Oct 2003 11:20:52 +0200
Date: Sun, 5 Oct 2003 11:20:52 +0200 [thread overview]
Message-ID: <20031005092052.GC12880@colin2.muc.de> (raw)
In-Reply-To: <3F7F4AFC.7000700@nodomain.org>
> AFAIK there is only one version that supports compiling to amd64 (only
> one for debian anyway) - I'm on 3.3.2-0pre4.biarch1. It is a bit flaky
> (in 32bit it'll happily do a make -j255 without worrying... going to 64
> bit needs about 10 attempts to do a single compile because it keeps
> falling over with internal compiler errors/segfaults/etc.).
That doesn't sound good. Why did you not mention this first, it's unlikely
that such a compiler produces a working kernel. When the segfaults
are not deterministic (go away when you try again) then you likely
have some hardware problem, like bad DIMMs (run memtest86 for 12+hours to
make sure)
To rule out the compiler you can use the compiler/binutils from
ftp.suse.com:/pub/suse/x86-64/supplementary/CrossTools/8.1-i386/
That's rpms for SuSE 8.1/i386, but I suspect you install it on Debian with
rpm2cpio or somesuch. That's an older gcc 3.2 that is known to work.
Then just put /opt/cross/bin in your $PATH and compile with
CROSS_COMPILE=x86_64-linux- ARCH=x86_64
-Andi
next prev parent reply other threads:[~2003-10-05 9:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CYRo.18k.9@gated-at.bofh.it>
2003-10-04 18:39 ` Oops linux 2.4.23-pre6 on amd64 Andi Kleen
2003-10-04 19:05 ` Tony Hoyle
2003-10-04 19:18 ` Tony Hoyle
2003-10-04 20:55 ` Andi Kleen
2003-10-04 22:34 ` Tony Hoyle
2003-10-05 9:20 ` Andi Kleen [this message]
2003-10-05 9:35 ` Tony Hoyle
2003-10-05 14:29 ` Tony Hoyle
2003-10-05 15:37 ` Andi Kleen
2003-10-05 15:42 ` Tony Hoyle
2003-10-05 17:21 ` Marcelo Tosatti
2003-10-05 17:41 ` Tony Hoyle
2003-10-07 20:33 ` calling devinet_ioctl from a kernel module Vishwas Raman
2003-10-04 17:50 Oops linux 2.4.23-pre6 on amd64 Tony Hoyle
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=20031005092052.GC12880@colin2.muc.de \
--to=ak@colin2.muc.de \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=tmh@nodomain.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.