From: Rob Landley <rob@landley.net>
To: David Lang <dlang@invendra.net>,
user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Does UML 2.6.14 work under x86-64?
Date: Sun, 6 Nov 2005 17:23:32 -0600 [thread overview]
Message-ID: <200511061723.32848.rob@landley.net> (raw)
David Lang is trying to get my firmware build working under x86-64, and when I
upgraded him to 2.6.14 (to get around the memory leak in 2.6.13.2), he
started getting this:
>> Checking PROT_EXEC mmap in /tmp...OK
>> Checking for the skas3 patch in the host:
>> - /proc/mm...not found
>> - PTRACE_FAULTINFO...not found
>> - PTRACE_LDT...not found
>> UML running in SKAS0 mode
>> Kernel panic - not syncing: get_skas_faultinfo : failed to wait for
>> SIGUSR1/SIGTRAP, pid = 16411, n = 16411, errno
>> 0, status = 0xb7f
This is 2.6.14 configured like so:
make ARCH=um allnoconfig &&
cat >> .config << EOF &&
CONFIG_MODE_SKAS=y
CONFIG_BINFMT_ELF=y
CONFIG_HOSTFS=y
CONFIG_SYSCTL=y
CONFIG_STDERR_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_UBD=y
CONFIG_TMPFS=y
CONFIG_SWAP=y
CONFIG_LBD=y
CONFIG_EXT2_FS=y
CONFIG_PROC_FS=y
EOF
yes "" | make ARCH=um oldconfig &&
make ARCH=um
And then run via:
tmpdir/linux rootfstype=hostfs rw quiet mem=64M ubd0=tmpdir/swap.img
init=/bin/sh
He first tried with the LDT patch applied. Then he tried reverting it (and
adding LD_ASSUME_KERNEL=2.4.1 to the kernel command line), but that didn't
help.
Any clues? (Should I tell him to just try -tt mode? Or revert to 2.6.13 with
the leak fix?)
Rob
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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:[~2005-11-06 23:24 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-06 23:23 Rob Landley [this message]
2005-11-07 16:25 ` [uml-devel] Does UML 2.6.14 work under x86-64? Jeff Dike
2005-11-07 19:32 ` Blaisorblade
2005-11-07 14:38 ` David Lang
2005-11-07 19:44 ` Blaisorblade
2005-11-08 0:53 ` Rob Landley
2005-11-07 14:47 ` David Lang
2005-11-07 15:30 ` David Lang
2005-11-08 3:39 ` Rob Landley
2005-11-08 5:13 ` [uml-devel] Making UML Single Threader Can Sar
2005-11-08 7:09 ` Rob Landley
2005-11-08 7:44 ` Can Sar
2005-11-09 0:35 ` Rob Landley
2005-11-09 0:48 ` Blaisorblade
2005-11-09 1:17 ` Rob Landley
2005-11-09 1:31 ` Blaisorblade
2005-11-09 3:18 ` Rob Landley
2005-11-10 4:18 ` Jeff Dike
2005-11-10 4:58 ` Rob Landley
2005-11-10 6:23 ` Henrik Nordstrom
2005-11-10 4:07 ` Jeff Dike
2005-11-10 3:55 ` Rob Landley
2005-11-08 15:46 ` Jeff Dike
2005-11-09 0:27 ` Rob Landley
2005-11-14 13:59 ` Nix
2005-11-14 19:37 ` Blaisorblade
2005-11-14 20:00 ` Nix
2005-11-14 20:05 ` Geert Uytterhoeven
2005-11-15 11:39 ` Henrik Nordstrom
2005-11-16 1:23 ` Rob Landley
2005-11-08 16:13 ` Blaisorblade
2005-11-09 0:51 ` Rob Landley
2005-11-08 15:43 ` Jeff Dike
2005-11-08 16:10 ` Blaisorblade
2005-11-08 19:11 ` Can Sar
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=200511061723.32848.rob@landley.net \
--to=rob@landley.net \
--cc=dlang@invendra.net \
--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