* Re: [uml-devel] NPTL can't be disabled in fc4?
2005-06-27 21:13 [uml-devel] NPTL can't be disabled in fc4? William Stearns
@ 2005-06-27 21:27 ` Blaisorblade
2005-06-27 21:56 ` William Stearns
1 sibling, 0 replies; 4+ messages in thread
From: Blaisorblade @ 2005-06-27 21:27 UTC (permalink / raw)
To: user-mode-linux-devel, William Stearns; +Cc: Jeff Dike
On Monday 27 June 2005 23:13, William Stearns wrote:
> Good afternoon, all,
> I tried to boot an fc4 VM ( http://www.stearns.org/uml-root/ )on
> zaphod.
> Is there _any_ way to convince an fc4 userspace to not use NPTL?
Yes, it's indicated on the FC4 release notes, I already posted this link
(http://fedora.redhat.com/docs/release-notes/fc4/).
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Messenger: chiamate gratuite in tutto il mondo
http://it.beta.messenger.yahoo.com
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&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
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [uml-devel] NPTL can't be disabled in fc4?
2005-06-27 21:13 [uml-devel] NPTL can't be disabled in fc4? William Stearns
2005-06-27 21:27 ` Blaisorblade
@ 2005-06-27 21:56 ` William Stearns
2005-06-28 7:45 ` Henrik Nordstrom
1 sibling, 1 reply; 4+ messages in thread
From: William Stearns @ 2005-06-27 21:56 UTC (permalink / raw)
To: ML-uml-devel; +Cc: Blaisorblade, Jeff Dike, William Stearns
Good afternoon, all,
On Mon, 27 Jun 2005, William Stearns wrote:
> I tried to boot an fc4 VM ( http://www.stearns.org/uml-root/ )on
> zaphod.
> I compiled 2.6.12-mm1-um26121_20050627 at Jeff's suggestion, and
> still get:
>
> Setting hostname placeholder.stearns.org: [ OK ]
> set_thread_area failed when setting up thread-local storage
>
> It doesn't appear that any of the patches in Jeff's current 2.6 quilt
> patch set refer to set_thread_area (Although I could believe that one of them
> addresses it indirectly so the string doesn't show up in the patches.)
> Even adding LD_ASSUME_KERNEL=2.4.1 to the end of the kernel command
> line (which, according to doc/kernel-parameters.txt passes that environment
> variable on to the environment inside the VM) doesn't help.
> LD_ASSUME_KERNEL=2.2.5 on the kernel command line also exhibits
> set_thread_area failed....
> I've also tried disabling nptl from userspace with the following
> added lines:
>
> /etc/profile.d/glibc.sh
> export LD_ASSUME_KERNEL=2.4.19
>
> /etc/init.d/functions
> export LD_ASSUME_KERNEL=2.4.19
>
> /etc/initscript : (make mode 755)
> export LD_ASSUME_KERNEL=2.4.19
> eval exec "$4"
>
> Still hitting that set_thread_area error.
>
> Is there _any_ way to convince an fc4 userspace to not use NPTL?
Oops, forgot to mention that I already have renamed /lib/tls
(already done in stock dowmloadable root_fs....) and /usr/lib/tls (not
done in downloadable root_fs, but done by hand here.
Also, Blaisorblade wrote:
> Yes, it's indicated on the FC4 release notes, I already posted this link
> (http://fedora.redhat.com/docs/release-notes/fc4/).
I tried adding the following line to /etc/profile.d/glibc.sh,
/etc/init.d/functions, and /etc/initscript (skipped {,64} because this is
32 bit only):
export LD_LIBRARY_PATH=/lib/obsolete/linuxthreads
and I still get:
Setting hostname placeholder.stearns.org: [ OK ]
set_thread_area failed when setting up thread-local storage
/etc/rc.d/rc.sysinit: line 323: 757 Done echo
"raidautorun /dev/md0"
758 Segmentation fault | nash --quiet
set_thread_area failed when setting up thread-local storage
/etc/rc.d/rc.sysinit: line 340: 760 Done echo
"mkdmnod"
761 Segmentation fault | /sbin/nash --quiet >/dev/null 2>&1
set_thread_area failed when setting up thread-local storage
/etc/rc.d/rc.sysinit: line 340: 762 Segmentation fault
/sbin/lvm.static vgscan --mknodes --ignorelockingfailure >/dev/null 2>&1
Checking filesystems
Checking all file systems.
[/sbin/fsck.ext2 (1) -- /] fsck.ext2 -a /dev/ubd/0
set_thread_area failed when setting up thread-local storage
Warning... fsck.ext2 for device /dev/ubd/0 exited with signal 11.
[FAILED]
*** An error occurred during the file system check.
*** Dropping you to a shell; the system will reboot
*** when you leave the shell.
Give root password for maintenance
(or type Control-D to continue):
Blaisor, was there some other piece of that release note you were
referring to?
I've also tried, in addition to the three system files above,
adding the "LD_ASSUME_KERNEL=2.4.19
LD_LIBRARY_PATH=/lib/obsolete/linuxthreads" to the end of the kernel
command line. Same problem.
Cheers,
- Bill
---------------------------------------------------------------------------
Too many packets
Syn. Ack. Fin. I. C. M. P.
I am so tired
-- Dennis McGrath
--------------------------------------------------------------------------
William Stearns (wstearns@pobox.com). Mason, Buildkernel, freedups, p0f,
rsync-backup, ssh-keyinstall, dns-check, more at: http://www.stearns.org
--------------------------------------------------------------------------
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&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
^ permalink raw reply [flat|nested] 4+ messages in thread