mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andi Kleen <ak@colin2.muc.de>
To: Tony Hoyle <tmh@nodomain.org>
Cc: Andi Kleen <ak@muc.de>,
	linux-kernel@vger.kernel.org, marcelo.tosatti@cyclades.com.br
Subject: Re: Oops linux 2.4.23-pre6 on amd64
Date: 5 Oct 2003 17:37:07 +0200	[thread overview]
Date: Sun, 5 Oct 2003 17:37:07 +0200	[thread overview]
Message-ID: <20031005153707.GB30792@colin2.muc.de> (raw)
In-Reply-To: <3F802AD2.9010108@nodomain.org>

On Sun, Oct 05, 2003 at 03:29:38PM +0100, Tony Hoyle wrote:
> 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).

Thanks for tracking this down. I would have never noticed
because I don't use devfs.

Marcelo, any ideas? Do you get broken devfs reports for other
64bit architectures too?

AFAIK devfs is unmaintained and I don't really plan to maintain
it myself. My proposal is to just disable it in the configuration
for x86-64 for now.

> 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.

Very likely the devfs code in the kernel is buggy. It is known
to be race hell, I wouldn't be surprised if it has 64bit bugs too.

-Andi

  reply	other threads:[~2003-10-05 15:36 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 ` 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
2003-10-05 15:37             ` Andi Kleen [this message]
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=20031005153707.GB30792@colin2.muc.de \
    --to=ak@colin2.muc.de \
    --cc=ak@muc.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo.tosatti@cyclades.com.br \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®