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

Andi Kleen writes:
 > On Fri, Jan 24, 2003 at 08:16:59PM +0100, Mikael Pettersson wrote:
...
 > > sleep[196] general protection rip:4003ebe5 rsp:ffffed20 error:0
 > > 
 > > (The system is vanilla RH8.0 with Athlon binaries, running under
...
 > 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.

It looks as if %gs handling isn't quite right.

pthread_setcanceltype() SIGSEGVs in THREAD_SETMEM(self, p_canceltype, type).
The instruction that fails is "mov %dl,%gs:0x81", and %gs is zero.

RedHat linked /bin/sleep against libpthread.so, which (at least in the
glibc-2.2.93 used in RedHat 8.0) causes the nanosleep() system call
to be wrapped between a pair of pthread_setcanceltype() calls.
That's why /bin/sleep failed. Compile it yourself w/o -lpthread and it works.

Also: running gdb on a live process didn't work. I got "int3" errors in
the kernel's log, and gdb seemed to hang or loop somewhere. Postmortem
debugs of core files worked ok though.

/Mikael

  reply	other threads:[~2003-01-28 20:42 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 [this message]
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=15926.60767.451098.218188@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=ak@suse.de \
    --cc=discuss@x86-64.org \
    --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;
as well as URLs for NNTP newsgroup(s).