linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Andi Kleen <ak@suse.de>,
	linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: two x86_64 fixes for 2.4.21-pre3
Date: Wed, 29 Jan 2003 17:28:24 +0100	[thread overview]
Message-ID: <20030129162824.GA4773@wotan.suse.de> (raw)
In-Reply-To: <15927.62893.336010.363817@harpo.it.uu.se>

> 1. One unknown ioctl is logged from RH8.0 init:
> 
> ioctl32(iwconfig:185): Unknown cmd fd(3) cmd(00008b01){00} arg(ffffda90) on socket:[389]

Probably harmless, but if you figure it out please send me a patch.

Basically the steps are:

- find out which ioctl it is.

- check its arguments. if the arguments are 64bit clean (see
http://www.firstfloor.org/~andi/writing-ioctl32 for a definition) you just
add it as COMPATIBLE_IOCTL to arch/x86_64/ia32/ia32_ioctl.c

If not you have to write a conversion handler, also following the tutorial
in writing-ioctl32.

> 
> 2. gdb still seems broken. gdb ./sleep [where ./sleep is simply main() calling
>    nanosleep(), but linked with -lpthread] hangs or loops and takes forever
>    to respond to ^C.

It works with the SuSE 32bit gdb/userland.

I think RedHat has a different libpthread. I don't have a RedHat userland,
so someone else will have to debug it.

> 
> 3. bootsect.S still needs a patch to prevent 'bzdisk' kernels from
>    disabling the FDC

I put your previous patch already into CVS, but that was after the 
last Marcelo sync.

-Andi

  reply	other threads:[~2003-01-29 16:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-24 19:16 two x86_64 fixes for 2.4.21-pre3 Mikael Pettersson
2003-01-24 19:37 ` Andi Kleen
2003-01-28 20:51   ` Mikael Pettersson
2003-01-28 21:27     ` Andi Kleen
2003-01-29 15:39       ` Mikael Pettersson
2003-01-29 16:28         ` Andi Kleen [this message]
2003-02-03 19:17           ` Mikael Pettersson
2003-02-03 19:49             ` Jean Tourrilhes
2003-02-03 20:12               ` Andi Kleen
2003-02-03 21:43                 ` Jean Tourrilhes
2003-02-03 22:46                   ` 32bit emulation of wireless ioctls Andi Kleen
2003-02-03 23:17                     ` Jean Tourrilhes
2003-02-03 23:51                       ` Andi Kleen
2003-02-04  0:09                         ` Jean Tourrilhes
2003-02-03 23:58                       ` David Woodhouse
2003-02-04  0:04                       ` David Mosberger
2003-02-04  0:11                       ` Anton Blanchard
2003-02-07 10:58                 ` two x86_64 fixes for 2.4.21-pre3 Pavel Machek
2003-02-07 14:32                   ` Alan Cox
2003-02-07 22:58                     ` Erik Mouw
2003-02-04  3:13 ` Ton Hospel
2003-02-04 13:11   ` Mikael Pettersson

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=20030129162824.GA4773@wotan.suse.de \
    --to=ak@suse.de \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    /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;
as well as URLs for NNTP newsgroup(s).