* [uml-devel] FC4 rootfs - crash
@ 2007-01-16 13:11 Sapan Bhatia
2007-01-17 16:00 ` Blaisorblade
0 siblings, 1 reply; 2+ messages in thread
From: Sapan Bhatia @ 2007-01-16 13:11 UTC (permalink / raw)
To: user-mode-linux-devel
[-- 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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [uml-devel] FC4 rootfs - crash
2007-01-16 13:11 [uml-devel] FC4 rootfs - crash Sapan Bhatia
@ 2007-01-17 16:00 ` Blaisorblade
0 siblings, 0 replies; 2+ messages in thread
From: Blaisorblade @ 2007-01-17 16:00 UTC (permalink / raw)
To: user-mode-linux-devel; +Cc: Sapan Bhatia
On Tuesday 16 January 2007 14:11, Sapan Bhatia wrote:
> 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.
Which is the other root_fs? Slackware is way stablere than anything else,
since I guess they are much more conservative when building glibc.
> 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.
You mean glibc-2.3.6?
Can an older UML version boot fine on that root_fs? No definitive
incompatibility with FC4 exists that I know of.
However, there is a similar problem with _host_ glibc >= 2.4. Is this your
case?
> Sapan
--
Inform me of my mistakes, so I can add them to my list!
Paolo Giarrusso, aka Blaisorblade
http://www.user-mode-linux.org/~blaisorblade
Chiacchiera con i tuoi amici in tempo reale!
http://it.yahoo.com/mail_it/foot/*http://it.messenger.yahoo.com
-------------------------------------------------------------------------
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
_______________________________________________
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] 2+ messages in thread
end of thread, other threads:[~2007-01-17 16:01 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-01-16 13:11 [uml-devel] FC4 rootfs - crash Sapan Bhatia
2007-01-17 16:00 ` Blaisorblade
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox