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 15:29:38 +0100 [thread overview]
Message-ID: <3F802AD2.9010108@nodomain.org> (raw)
In-Reply-To: <20031005092052.GC12880@colin2.muc.de>
Andi Kleen wrote:
> To rule out the compiler you can use the compiler/binutils from
>
> ftp.suse.com:/pub/suse/x86-64/supplementary/CrossTools/8.1-i386/
>
OK I built with that and here are the results:
1. The ehci-hcd driver fails in exactly the same place.
2. It was still v. unstable, which led me to investigate why (since I'm
pretty sure the hardware is good & the suse compiler is supposed to be a
good one). I started stripping out options until eventually I found
that it's devfs that's the culprit - with that enabled I get random
compile errors every few seconds. With it disabled the compile works
perfectly, even with the debian compiler (tried -j20 and -j255 and both
passed).
My first guess was you can't use a 32bit devfsd with a 64bit kernel, but
stopping devfsd didn't seem to make a whole lot of difference to the
stability... only compiling out the entire devfs system solved it.
I suppose it could be insmod breaking the ehci-hcd... I'll see if I can
find a pure 64bit one (presumably suse have one) rather than the biarch
one that debian uses.
Tony
next prev parent reply other threads:[~2003-10-05 14:29 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
2003-10-05 14:29 ` Tony Hoyle [this message]
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=3F802AD2.9010108@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 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.