public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: ak@suse.de, linux-kernel@vger.kernel.org, discuss@x86-64.org
Subject: Re: two x86_64 fixes for 2.4.21-pre3
Date: Fri, 24 Jan 2003 20:37:21 +0100	[thread overview]
Message-ID: <20030124193721.GA24876@wotan.suse.de> (raw)
In-Reply-To: <15921.37163.139583.74988@harpo.it.uu.se>

On Fri, Jan 24, 2003 at 08:16:59PM +0100, Mikael Pettersson wrote:
> 1. The new IDE code in -pre references a few new macros and
>    inlines from <asm/system.h> that x86_64 doesn't provide.

Already fixed in my tree, but thanks for the reminder to push 
it to Marcelo. I have some more bug fixes that I will push to
him soon too.

> 2. bootsect.S has the same bug that i386' bootsect.S had
>    until I fixed it in 2.4.14 or so: it stops the floppy
>    controller in a way that cause newer FDCs to lock up.
>    The same patch as in i386' bootsect.S fixes the problem.

Ok, will check that.

> 
> The x86_64 kernel boots RH8.0 fairly well, but the IA32 emulation
> has some rough spots. In particular, "sleep" SEGVs with a #GP
> every time, and sys32_ioctl() complains:

The sys32_ioctl warnings are usually harmless.
I think some i386 hwclock versions even call bogus ioctls just in case
it is running on m68k or something like that.
I believe I fixed up all rtc clock ioctls that are actually used.
[someone familiar with rtc double checking it would be welcome of course]

Of course patches are always welcome.

> 
> sleep[15] general protection rip:4004441c rsp:ffffed60 error:0
> sys32_ioctl(hwclock:23): Unknown cmd fd(3) cmd(00004b50) arg(ffffeb50)
> date[28] general protection rip:4002141c rsp:ffffebc0 error:0
> date[30] general protection rip:400204ee rsp:ffffe4c4 error:0
> sys32_ioctl(mount:62): Unknown cmd fd(4) cmd(80041272) arg(ffff6948)
> sys32_ioctl(mount:62): Unknown cmd fd(4) cmd(80041272) arg(ffff6948)
> sys32_ioctl(mount:69): Unknown cmd fd(4) cmd(80041272) arg(ffff6968)
> sys32_ioctl(mount:69): Unknown cmd fd(4) cmd(80041272) arg(ffff6968)
> rpmq[120] general protection rip:401c641c rsp:ffffed40 error:0
> sleep[140] general protection rip:4003ebe5 rsp:ffffed60 error:0
> sys32_ioctl(iwconfig:183): Unknown cmd fd(3) cmd(00008b01) arg(ffffea90)
> sleep[196] general protection rip:4003ebe5 rsp:ffffed20 error:0
> 
> (The system is vanilla RH8.0 with Athlon binaries, running under
> the Virtutech Simics 1.4.7 simulator. The x86_64 kernel was
> cross-compiled with binutils-2.13.2.1 and gcc-3.2.1.)

Works for me on Simics with a SuSE 32bit userland.

You have to figure out what breaks on RedHat yourself.

We had some problems with the TLS register used on very new glibcs
(%gs), but they should be fixed now in the codedrop in 2.4.21pre3.

-Andi

  reply	other threads:[~2003-01-24 19:28 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 [this message]
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
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=20030124193721.GA24876@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