Hi Brijesh,
It still seems to lockup with that command as well. This is the message its spits out when it happens:
select 1 (init), adj 0, size 52, to kill
select 1742 (dbus-daemon), adj 0, size 62, to kill
select 1747 (hald), adj 0, size 240, to kill
select 2043 (gst-launch-0.10), adj 0, size 12930, to kill
send sigkill to 2043 (gst-launch-0.10), adj 0, size 12930
Another question I have is, if I kill the video early with CTRL + C how do I get the console back on the screen. I have looked through the /sys/devices/platform for a way to get it back but I have been unsuccessful. The stopped just remains on the display.
Thanks
Kevin
Kevin,
Are u using latest .dev branch for building gst-ti ? I think it may be
better to first ruleout any display sink problem. Have u tried using
"xvimagesink" or "omapfbsink" etc ? What happens if you use fakesink ?
Does decoder gets blocked.
In addition to this, there are some known issue with DSPLINK and
CTRL-C combination hence i tried to avoid hitting CTRL-C during
playback. Instead u have gracefully transition from READY->NULL using
gstreamer application programming. If you get gst-launch in defenc
state then first "reboot" is the only option for now.
Thanks
Brijesh
Brijesh,
In addition to this, there are some known issue with DSPLINK and
CTRL-C combination hence i tried to avoid hitting CTRL-C during
playback. Instead u have gracefully transition from READY->NULL using
gstreamer application programming.
This issue is due to the fact that DSPLINK registers for signal handling by default and GStreamer also does the same hence a conflict. Ideally application should be handling the signals.Below thread discusses how to disable this - it is not straightforward config option while building - requires patching DSPLINK sources.
http://patchwork.kernel.org/patch/47281/
Regards,
Pratheesh