From: "Sapan Bhatia" <sapan.bhatia@gmail.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] FC4 rootfs - crash
Date: Tue, 16 Jan 2007 08:11:20 -0500 [thread overview]
Message-ID: <3cb76b010701160511i1ff30a49k467fc1f4d5887c94@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 599 bytes --]
Hi,
I'm using UML 2.6.19.2 on a 2.6.19-skas3 host, and observing the following
when I try booting with a root fs based on FC4/glibc- 2.6-20. UML gets stuck
with a 'Warning: unable to open an initial console'. gdb shows that it's
because it gets a stream of infinite segfaults. When I boot off another
rootfs and try to chroot into the one with FC4, it segfaults out. strace
shows that this happens just after libc is ldopened.. at a call to
rt_sigprocmask.
So I tried regressing glibc, and now (with glibc-2.6.3) chroot works, but
UML still gets stuck at the same place when I try to boot.
Sapan
[-- Attachment #1.2: Type: text/html, Size: 740 bytes --]
[-- Attachment #2: Type: text/plain, Size: 347 bytes --]
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
[-- Attachment #3: Type: text/plain, Size: 194 bytes --]
_______________________________________________
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:[~2007-01-16 13:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-16 13:11 Sapan Bhatia [this message]
2007-01-17 16:00 ` [uml-devel] FC4 rootfs - crash 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=3cb76b010701160511i1ff30a49k467fc1f4d5887c94@mail.gmail.com \
--to=sapan.bhatia@gmail.com \
--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