From: antoine <antoine@nagafix.co.uk>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: UML devel <user-mode-linux-devel@lists.sourceforge.net>,
Jeff Dike <jdike@addtoit.com>
Subject: Re: [uml-devel] testing: 2.6.13 to 2.6.14-rc1 TT boot hangs early (sometimes)
Date: Fri, 16 Sep 2005 21:12:42 +0100 [thread overview]
Message-ID: <1126901562.17715.9.camel@localhost> (raw)
In-Reply-To: <200509162124.42522.blaisorblade@yahoo.it>
> > UML running in SKAS3 mode
> > Checking PROT_EXEC mmap in /tmp...OK
> > Kernel virtual memory size shrunk to 28311552 bytes
> This is running in SKAS3 mode - see message. However, the problem may be TT in
> the meaning you'd better probably disable it.
I enabled both to make it easier to test each mode, oh well... Noted.
> > What's this about shrinking vm size? (reducing the mem gets rid of this
> > warning)
> By how much? If you tried to pass it 1G of mem it's ok it complains (when TT
> mode is enabled and HIGHMEM disabled it doesn't work - disabling TT should
> fix this).
HIGHMEM was disabled, but mem=512M so this shouldn't matter, right?
It stopped complaining at about mem=200M (roughly IIRC)
> > # uname -a
> > Linux mamba 2.6.12-skas3-v9-pre4 #2 Thu Jun 23 16:28:29 GMT i686 AMD
> > Athlon(tm) XP 2000+ AuthenticAMD GNU/Linux
> > I tried the same filesystem as ext3 but that made no difference.
> > Guest is 2.6.14-rc1
>
> > Same kernel in skas3/skas0 works occasionally! But when it does not:
>
> > [42949374.340000] VFS: Mounted root (ext3 filesystem) readonly.
> > [42949384.250000] BUG: soft lockup detected on CPU#0!
> Does the box locks up thereafter? Jeff has been seeing these for some time,
> but IIRC the box didn't lock up. (Jeff, what's the actual situation?).
The host is fine... so far.
> > * Good points:
> > pcap works really well.
> > I just wished there was a way to easily figure out which libraries need
> > to be included in the chroot to make it work (beyond lipcap)
> Idea: try using ltrace with focus on dlopen (from libdl).
I'll do that and post the results.
> > * Some other small issues:
> > when building IPv6 & pcap, I get:
> > /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.6/../../../libc.a(in6_addr.o)(.rodat
> >a+0x10): multiple definition of `in6addr_loopback'
>
> > (This has been the case with the last few releases)
> It's a name conflict with libc... ugh, means adding another -D like
> -Derrno=kernel_errno in the same place. It's trivial, but it's getting boring.
> Attached the fix.
>
> A question: is it ok to be mentioned in the patch changelog? It was suggested
> to do so to give a bit of reward to testers - just I don't know if I should
> or not, and secondly if I should put your email or not.
Anything for credits ;-)
BTW, I can't contribute patches (I can code in C, but not kernel code) -
however I can provide free hosting, disk space, etc to all the uml
hackers that ask.
Feel free include my email, in the worst case it will train my spam
filters!
Antoine
-------------------------------------------------------
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 prev parent reply other threads:[~2005-09-16 19:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-13 23:25 [uml-devel] testing: 2.6.13 to 2.6.14-rc1 TT boot hangs early (sometimes) antoine
2005-09-14 20:19 ` [uml-devel] pcap antoine
2005-09-14 20:06 ` Blaisorblade
2005-09-14 20:44 ` [uml-devel] pcap - FIXED antoine
2005-09-16 19:24 ` [uml-devel] testing: 2.6.13 to 2.6.14-rc1 TT boot hangs early (sometimes) Blaisorblade
2005-09-16 20:12 ` antoine [this message]
2005-09-17 15:41 ` Blaisorblade
2005-09-17 18:15 ` Antoine Martin
2005-09-17 18:52 ` Jeff Dike
2005-09-17 18:34 ` Antoine Martin
2005-09-18 11:29 ` 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=1126901562.17715.9.camel@localhost \
--to=antoine@nagafix.co.uk \
--cc=blaisorblade@yahoo.it \
--cc=jdike@addtoit.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