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

Reply via email to