From: Marcel Ziswiler <marcel.ziswiler-2KBjVHiyJgBBDgjK7y7TUQ@public.gmane.org>
To: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: TK1 System Freeze
Date: Sun, 19 Nov 2017 23:57:36 +0000 [thread overview]
Message-ID: <1511135854.13661.3.camel@toradex.com> (raw)
Hi there
I lately was tasked to run some legacy Qt4e [1] application on Apalis
TK1. It should really only draw directly to the Linux frame buffer
/dev/fb0. Strangely as soon as that application is started the whole
system freezes. Running it with the VNC backend or a pure frame buffer
emulation it works just fine. So it must have something to do with the
particular way the frame buffer is done on TK1. So far no attempt in
debugging this any further bear any fruit. Whether stracing what the
application is doing nor tracing the linux kernel side of things
revealed where exactly the freeze happens. As I feared some kind of a
configuration issue on Apalis TK1 I also tried the same on Jetson TK1
with latest stock Linux kernel 4.14. However the same freeze happens.
Has anybody ever seen a similar complete system freeze? Any ideas what
it may be or how we could debug this any further?
[1] https://layers.openembedded.org/layerindex/recipe/43622/
Cheers
Marcel
next reply other threads:[~2017-11-19 23:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-19 23:57 Marcel Ziswiler [this message]
[not found] ` <1511135854.13661.3.camel-2KBjVHiyJgBBDgjK7y7TUQ@public.gmane.org>
2018-01-13 0:19 ` TK1 System Freeze Stefan Agner
[not found] ` <7d874417cbb2067bcb4f49af000f9f03-XLVq0VzYD2Y@public.gmane.org>
2018-02-06 7:51 ` stefan-XLVq0VzYD2Y
[not found] ` <19526d1015c3c60e8bbdf26ec9d082bb-XLVq0VzYD2Y@public.gmane.org>
2018-02-06 16:40 ` Tuomas Tynkkynen
2018-02-07 17:51 ` Thierry Reding
2018-02-07 19:20 ` stefan-XLVq0VzYD2Y
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=1511135854.13661.3.camel@toradex.com \
--to=marcel.ziswiler-2kbjvhiyjgbbdgjk7y7tuq@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
/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