From: "Toralf Förster" <toralf.foerster@gmx.de>
To: UML devel <user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] does 3.12.2 breaks UML with "con=xterm" ?
Date: Sat, 30 Nov 2013 15:43:41 +0100 [thread overview]
Message-ID: <5299F99D.9040503@gmx.de> (raw)
In-Reply-To: <5299F818.4070408@gmx.de>
On 11/30/2013 03:37 PM, Toralf Förster wrote:
>
> Today I realized that a UML cores if I use the xterm for the in/out.
>
> I do usually use "con0=fd:0,fd:1 con=pts" to start a 32bit UML but because the xterm way was fine during the past few weeks (yes, I know, it was broken for a longer time before) and the only change yesterday was to upgrade from vanilla kernel 3.12.1 to 3.12.2 I'm wondering if there's a "suspicous" commit in that stable kernel which could be the reason ?
>
>
> FWIW :
> tfoerste@n22 ~ $ gdb --core=/mnt/ramdisk/core /home/tfoerste/devel/linux/linux -n -batch -ex bt
> [New LWP 29559]
> Core was generated by `/home/tfoerste/devel/linux/linux earlyprintk ubda=/home/tfoerste/virtual/uml/tr'.
> Program terminated with signal 11, Segmentation fault.
> #0 finish_task_switch (prev=0xffff9d2f, rq=<optimized out>) at kernel/sched/core.c:1993
> 1993 prev_state = prev->state;
> #0 finish_task_switch (prev=0xffff9d2f, rq=<optimized out>) at kernel/sched/core.c:1993
> #1 0x08427418 in context_switch (next=<optimized out>, prev=0x46d9eecc, rq=<optimized out>) at kernel/sched/core.c:2130
> #2 __schedule () at kernel/sched/core.c:2568
> #3 0x08427505 in schedule () at kernel/sched/core.c:2604
> #4 0x0808b912 in sigsuspend (set=0x46d9eecc) at kernel/signal.c:3559
> #5 0x080646d8 in winch_thread (arg=0x46d9eecc) at arch/um/drivers/chan_user.c:210
> #6 0x083da38e in clone ()
>
>
Pff - glibc was upgrade from 2.15-r3 to 2.16 too - /me hope, that it is
not glibc.
--
MfG/Sincerely
Toralf Förster
pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
------------------------------------------------------------------------------
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-11-30 14:43 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 [this message]
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
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=5299F99D.9040503@gmx.de \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox