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: Sat, 04 Oct 2003 23:34:36 +0100 [thread overview]
Message-ID: <3F7F4AFC.7000700@nodomain.org> (raw)
In-Reply-To: <20031004205545.GB71123@colin2.muc.de>
Andi Kleen wrote:
>>Oops, scratch that last one... It's invalid too as I used the original
>>oops rather than the new one. This one's the right one (honest!).
>
>
> I cannot see anything obviously wrong. At which kernel version did the
> problem start? And is your compiler version known to be not buggy ?
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.).
The problem with a brand new architecture is until the toolset
stabliizes I have to cross my fingers and hope. Certainly if it's
compiling dodgy code it'll explain why Alsa is about as stable as a
drunk in a high wind...
OK I'll forget it for now & go back to 32bit for a couple of months then
try again.
Tony
next prev parent reply other threads:[~2003-10-04 22:34 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 [this message]
2003-10-05 9:20 ` Andi Kleen
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=3F7F4AFC.7000700@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