From: Richard Weinberger <richard@nod.at>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: UML devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] does 3.12.2 breaks UML with "con=xterm" ?
Date: Mon, 02 Dec 2013 22:21:42 +0100 [thread overview]
Message-ID: <7306830.yvMa5tydAA@sandpuppy> (raw)
In-Reply-To: <529B8893.1030703@gmx.de>
Am Sonntag, 1. Dezember 2013, 20:05:55 schrieb Toralf Förster:
> On 12/01/2013 11:20 AM, Richard Weinberger wrote:
> > I meant xterm for all consoles but con0...
> > Such that you can trigger the crash but are still able to see the output.
>
> Not sure if the 2 attached files contains useful info, but here they are:
>
> The back trace of a hanging linux process :
> $>sudo gdb /home/tfoerste/devel/linux/linux 27162 -n -batch -ex 'bt full' >
> bt
>
> and stdout, error and bt of the core file from round #18 of this command :
>
> $> I=0; while [[ : ]]; do ((I=I+1)); echo; echo; echo $I; date; for i in
> trinity.sh xterm linux port-helper start_uml.sh ; do pkill $i; done; rm -f
> /mnt/ramdisk/core; start_uml.sh -r ~/virtual/uml/trinity -l
> /home/tfoerste/devel/linux/linux -y 'con0=fd:0,fd:1 con=xterm'
> 1>/mnt/ramdisk/$I.out 2>/mnt/ramdisk/$I.err; [[ -f /mnt/ramdisk/core ]] &&
> gdb --core=/mnt/ramdisk/core /home/tfoerste/devel/linux/linux -n -batch -ex
> 'bt full' > /mnt/ramdisk/$I.bt; sleep 10; done
What I can see is that UML panic()ed because PTRACE_SETREGS is failing with
ESRCH. This means one of the UML SKAS0 helper threads got killed and is gone.
This is very strange and makes me worry, because in this stage the helper is
in stopped state and cannot really die by an UML error. Looks like it got
killed from outside.
Is your host setup 100% sane? :)
Thanks,
//richard
------------------------------------------------------------------------------
Rapidly troubleshoot problems before they affect your business. Most IT
organizations don't have a clear picture of how application performance
affects their revenue. With AppDynamics, you get 100% visibility into your
Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro!
http://pubads.g.doubleclick.net/gampad/clk?id=84349351&iu=/4140/ostg.clktrk
_______________________________________________
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:[~2013-12-02 21:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-30 14:37 [uml-devel] does 3.12.2 breaks UML with "con=xterm" ? Toralf Förster
2013-11-30 14:43 ` Toralf Förster
2013-11-30 14:51 ` Richard Weinberger
2013-11-30 15:56 ` Toralf Förster
2013-11-30 16:28 ` Toralf Förster
2013-11-30 16:36 ` Richard Weinberger
2013-11-30 17:26 ` Toralf Förster
2013-11-30 17:35 ` Richard Weinberger
2013-11-30 18:19 ` Toralf Förster
2013-11-30 18:23 ` Richard Weinberger
2013-11-30 18:43 ` Toralf Förster
2013-11-30 23:19 ` Richard Weinberger
2013-12-01 10:17 ` Toralf Förster
2013-12-01 10:20 ` Richard Weinberger
2013-12-01 17:07 ` Toralf Förster
2013-12-01 19:05 ` Toralf Förster
2013-12-02 16:42 ` Boaz Harrosh
2013-12-02 21:21 ` Richard Weinberger [this message]
2013-12-02 21:32 ` Toralf Förster
2013-12-02 21:59 ` Richard Weinberger
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=7306830.yvMa5tydAA@sandpuppy \
--to=richard@nod.at \
--cc=toralf.foerster@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.