From: Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
To: Rik van Riel <riel@redhat.com>
Cc: xen-devel@lists.sourceforge.net
Subject: Re: NPTL/TLS problem in -unstable ?
Date: Mon, 10 Jan 2005 18:56:35 +0000 [thread overview]
Message-ID: <20050110185635.GF18390@cl.cam.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0501101344370.12109@chimarrao.boston.redhat.com>
On Mon, Jan 10, 2005 at 01:47:36PM -0500, Rik van Riel wrote:
> when trying to boot with the latest xen-unstable tree,
> I can only get the system working when /lib/tls is
> moved out of the way.
>
> With it present, Xen hangs after the TLS warning box,
> in the big WARNING. It does its 5 seconds of waiting
> and then just hangs...
>
> I can't see an suspect code changes in seg_fixup.c, so
> it's probably something else...
Since you mentioned this in another message yesterday, I
tried booting xen-unstable with /lib/tls in place today
and it worked. Do you have any local changes in your kernel
or a different glibc?
christian
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
next prev parent reply other threads:[~2005-01-10 18:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-10 18:47 NPTL/TLS problem in -unstable ? Rik van Riel
2005-01-10 18:56 ` Christian Limpach [this message]
2005-01-10 19:08 ` Rik van Riel
2005-01-10 20:04 ` Rik van Riel
2005-01-10 22:14 ` Rik van Riel
2005-01-10 23:03 ` Christian Limpach
2005-01-11 16:03 ` Rik van Riel
2005-01-11 16:33 ` Christian Limpach
2005-01-11 19:21 ` Rik van Riel
[not found] <mailman.1105390411.29331@unix-os.sc.intel.com>
2005-01-10 23:47 ` Arun Sharma
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=20050110185635.GF18390@cl.cam.ac.uk \
--to=christian.limpach@cl.cam.ac.uk \
--cc=riel@redhat.com \
--cc=xen-devel@lists.sourceforge.net \
/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.