From: Tony Hoyle <tmh@nodomain.org>
To: Andi Kleen <ak@colin2.muc.de>
Cc: Andi Kleen <ak@muc.de>, linux-kernel@vger.kernel.org
Subject: Re: Oops linux 2.4.23-pre6 on amd64
Date: Sun, 05 Oct 2003 10:35:08 +0100 [thread overview]
Message-ID: <3F7FE5CC.8010602@nodomain.org> (raw)
In-Reply-To: <20031005092052.GC12880@colin2.muc.de>
Andi Kleen wrote:
> 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)
It's had 24 hours under memtest86 (I had to RMA one memory stick when I
first got the machine) and as I mentioned handles a make -j255 in 32bit
mode without a hitch. The kernel does work apart from that module (and
floppy.o which I discovered later does much the same thing as the
ehci-hcd.o).
> 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
>
OK I'll try that.
Tony
next prev parent reply other threads:[~2003-10-05 9:35 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
2003-10-05 9:35 ` Tony Hoyle [this message]
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=3F7FE5CC.8010602@nodomain.org \
--to=tmh@nodomain.org \
--cc=ak@colin2.muc.de \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.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