From: "Sven 'Darkman' Michels" <sven@darkman.de>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Problem with 2.4.22-uml6 & skas...
Date: Mon, 24 Nov 2003 04:02:14 +0100 [thread overview]
Message-ID: <3FC174B6.4030908@darkman.de> (raw)
Hi there,
i try to get 2.4.22-6 running with skas mode.
The host:
Running vanilla 2.4.22 with host-skas3.patch (applied without
any error), PROC_MM enabled.
GCC is 3.3.1
The box is running fine with the kernel.
The UML:
2.4.22 patched with uml6, skas enabled etc.pp.
Problem:
i start the uml with:
linux-2.4.22 ubd0=/home/uml1/uml/10/root_fs
ubd1=/home/uml1/uml/10/swap.disk mem=64M con1=pts umid=uml10
eth0=tuntap,uml10-eth0 devfs=mount
and it stops here:
VFS: Mounted root (ext2 filesystem) readonly.
Mounted devfs on /dev
if i take a look at the host, i can see the following:
uml1 12180 0.0 0.0 4 0 pts/4 TW 03:41 0:00
[linux-2.4.22-te]
uml1 12185 0.0 0.9 65956 4640 pts/4 S 03:41 0:00
/home/uml1/uml/linux-2.4.22-test
uml1 12186 0.0 0.9 65956 4640 pts/4 S 03:41 0:00
/home/uml1/uml/linux-2.4.22-test
uml1 12164 99.7 0.9 65956 4640 pts/4 R 03:41 4:13
/home/uml1/uml/linux-2.4.22-test
(one uml running with nearly 100% cpu usage..)
attached strace on that one, i get:
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
rt_sigprocmask(SIG_UNBLOCK, [USR1], [], 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [ALRM VTALRM PROF IO], NULL, 8) = 0
getpid() = 12164
write(12, "7\0\0\0\0`\1@\0\20\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
28) = 28
write(12, "6\0\0\0\0`\1@\0\20\0\0\7\0\0\0\21\0\0\0\3\0\0\0\0P\\\0"...,
28) = 28
sigreturn() = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
rt_sigprocmask(SIG_UNBLOCK, [USR1], [], 8) = 0
rt_sigprocmask(SIG_UNBLOCK, [ALRM VTALRM PROF IO], NULL, 8) = 0
getpid() = 12164
write(12, "7\0\0\0\0`\1@\0\20\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0"...,
28) = 28
write(12, "6\0\0\0\0`\1@\0\20\0\0\7\0\0\0\21\0\0\0\3\0\0\0\0P\\\0"...,
28) = 28
sigreturn() = ? (mask now [])
--- SIGSEGV (Segmentation fault) @ 0 (0) ---
and so on...
with mode=tt the kernel runs. Then i tried another kernel from
kernels.usermodelinux.org:
linux-2.4.23-rc3-djc3-6um (nomods)
and: it works.
I talked to david and he said the kernel builds without problems
which is not the case on my host. I get this error:
bugs.c: In function `disable_lcall':
bugs.c:111: error: storage size of `ldt' isn't known
bugs.c:118: warning: implicit declaration of function `modify_ldt'
bugs.c:111: warning: unused variable `ldt'
which is fixed with a patch from:
http://people.0x63.nu/~andersg/uml-minor-fixes.diff
so, for now, i don't have more ideas to solve this Problem. If someone
of you has an idea or fix, please commit ;)
Thanks and regards,
Sven
-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
Does SourceForge.net help you be more productive? Does it
help you create better code? SHARE THE LOVE, and help us help
YOU! Click Here: http://sourceforge.net/donate/
_______________________________________________
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:[~2003-11-24 3:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-24 3:02 Sven 'Darkman' Michels [this message]
2003-12-06 0:04 ` [uml-devel] Problem with 2.4.22-uml6 & skas Jeff Dike
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=3FC174B6.4030908@darkman.de \
--to=sven@darkman.de \
--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