From: Antoine Martin <antoine@nagafix.co.uk>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] tls: set_thread_area failed
Date: Fri, 09 Dec 2005 18:39:52 +0000 [thread overview]
Message-ID: <1134153592.29209.2.camel@localhost.localdomain> (raw)
In-Reply-To: <200512091852.15906.blaisorblade@yahoo.it>
On Fri, 2005-12-09 at 18:52 +0100, Blaisorblade wrote:
> On Thursday 08 December 2005 03:13, Antoine Martin wrote:
> > I'm still trying to get a regular FC4 image to boot with the latest x86
> > tls support code.
> Mainline kernel or with jdike patchset?
Latest jdike from sf
> > (since Gentoo works fine)
> > but this is what I get:
> > # fsck.ext3 -a /dev/ubda
> > set_thread_area failed when setting up thread-local storage
> > Segmentation fault
>
> > Is this glibc? Any ideas?
>
> Yes, I see that on Debian Sarge too. Don't ask me why fsck uses thread, but it
> seems to do that.
I wasn't even thinking about that! So true, why on earth would fsck
require threading!?
> Also, different glibc are more or less happy in using modify_ldt() rather than
> set_thread_area() - it seems that latter is better.
Ahh, is it planned or do I have to make heavily modified distro images?
Antoine
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2005-12-09 18:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-08 2:13 [uml-devel] tls: set_thread_area failed Antoine Martin
2005-12-09 17:52 ` Blaisorblade
2005-12-09 18:39 ` Antoine Martin [this message]
2005-12-10 14:26 ` Blaisorblade
2005-12-10 16:31 ` Antoine Martin
2005-12-11 6:34 ` Rob Landley
2005-12-11 16:01 ` Blaisorblade
2005-12-13 22:45 ` Nix
2005-12-14 3:05 ` [uml-devel] " Sven Köhler
2005-12-14 12:21 ` Blaisorblade
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=1134153592.29209.2.camel@localhost.localdomain \
--to=antoine@nagafix.co.uk \
--cc=blaisorblade@yahoo.it \
--cc=user-mode-linux-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox