From: M A Young <m.a.young@durham.ac.uk>
To: User-mode-linux-devel@lists.sourceforge.net
Cc: Ingo Molnar <mingo@elte.hu>
Subject: Re: [uml-devel] Re: uml-patch-2.6.0
Date: Sun, 18 Jan 2004 18:46:47 +0000 (GMT) [thread overview]
Message-ID: <Pine.GSO.4.58.0401181833270.921@altair.dur.ac.uk> (raw)
>* Jeff Dike <jdike@addtoit.com> wrote:
>
>> > * Any known issues with 2.6.1 kernels?
>>
>> Fewer, now that I got the 2.6.1 patch out. UML lacks
>> [gs]et_thread_area still, so 2.6 UMLs won't boot new libcs.
>
>hm, are you sure this is the reason why they dont boot? At least the
>ones in Fedora fall back to LinuxThreads if set_thread_area is -ENOSYS.
>Old 2.4 kernels work just fine - UML ought to work fine too.
Originally, the problem was with these calls as UML used to panic rather
than return -ENOSYS. Now however I believe there is no direct connection
between the [gs]et_thread_area calls and the hang that occurs early on in
tt mode for RedHat 9 glibcs if the /lib/tls libraries exist. For FC1
glibcs the hang happens anyway. See an earlier post of mine for more
details of the hang.
Michael Young
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next reply other threads:[~2004-01-18 18:46 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-18 18:46 M A Young [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-13 5:05 uml-patch-2.6.0 Jeff Dike
2004-01-13 5:18 ` [uml-devel] uml-patch-2.6.0 Jeff Dike
2004-01-13 10:19 ` Sven Köhler
2004-01-13 18:55 ` Gerd Knorr
2004-01-16 2:33 ` Jeff Dike
2004-01-16 10:03 ` M A Young
2004-01-16 11:42 ` Gerd Knorr
2004-01-17 16:10 ` BlaisorBlade
2004-01-16 17:27 ` Jeff Dike
2004-01-16 21:56 ` Gerd Knorr
2004-01-17 21:12 ` M A Young
2004-01-18 4:47 ` Jeff Dike
2004-01-16 23:47 ` Sven Köhler
2004-01-17 19:09 ` BlaisorBlade
2004-01-17 19:50 ` Jeff Dike
2004-01-17 20:03 ` BlaisorBlade
2004-01-18 4:51 ` Jeff Dike
2004-01-18 16:21 ` Ingo Molnar
2004-01-18 23:57 ` Jeff Dike
2004-01-19 7:53 ` Ingo Molnar
2004-01-19 8:28 ` Ingo Molnar
2004-01-20 0:19 ` M A Young
2004-01-20 0:23 ` Ingo Molnar
2004-01-20 0:41 ` M A Young
2004-01-20 1:27 ` Jeff Dike
2004-01-20 17:22 ` Jeff Dike
2004-01-20 19:59 ` Ingo Molnar
2004-01-17 19:09 ` [uml-devel] uml-patch-2.6.0 BlaisorBlade
2004-01-19 17:06 ` [uml-devel] uml-patch-2.6.0 Gerd Knorr
2004-01-20 19:42 ` BlaisorBlade
2004-01-20 21:30 ` Gerd Knorr
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=Pine.GSO.4.58.0401181833270.921@altair.dur.ac.uk \
--to=m.a.young@durham.ac.uk \
--cc=User-mode-linux-devel@lists.sourceforge.net \
--cc=mingo@elte.hu \
/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.