X server Crash with I.MX6 boundary pyro release

cancel
Showing results for 
Search instead for 
Did you mean: 

X server Crash with I.MX6 boundary pyro release

620 Views
rajvikamdar
Contributor III

We are trying to port Pyro Yocto IMX.6 release to our custom IMX.6 platform.
We are able to get the console up and running, but we are facing issue at Xserver crash and as a result there is no HDMI display up after the raw BD image with tracker.
Please find the logs:
X.Org X Server 1.19.1
Release Date: 2017-01-11
X Protocol Version 11, Revision 0
Build Operating System: Linux 4.4.0-127-generic x86_64
Current Operating System: Linux nitrogen6x 4.1.15-gb943e97-dirty #31 SMP PREEMPT Mon Jun 25 12:39:59 IST 2018 armv7l
Kernel command line: console=ttymxc0,115200 earlyprintk vmalloc=400M consoleblank=0 rootwait fixrtc cpu=6D board=nitrogen6_max root=/dev/mmcblk3p3 rese
t_cause=0x1
Build Date: 20 June 2018  04:34:33PM
 
Current version of pixman: 0.34.0
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Thu Jun 21 05:57:13 2018
(==) Using config file: "/etc/X11/xorg.conf"
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
Starting bluetooth
bluetoothd
starting DNS forwarder and DHCP server: dnsmasq... done.
mxc_sdc_fb fb@0: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
Starting syslogd/klogd: done
mxc_sdc_fb fb@0: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
[ ok ]rting Avahi mDNS/DNS-SD Daemon: avahi-daemon
mxc_sdc_fb fb@0: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
Starting Telephony daemon
mxc_sdc_fb fb@0: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
Starting Linux NFC daemon
mxc_sdc_fb fb@0: 1280x720 h_sync,r,l: 40,110,220  v_sync,l,u: 5,5,20 pixclock=74250000 Hz
imx-ipuv3 2800000.ipu: try ipu internal clk
imx-ipuv3 2800000.ipu: disp=0, pixel_clk=74250000 74250000 parent=74250000 div=1
(EE)
(EE) Backtrace:
(EE)
(EE) Segmentation fault at address 0xc
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
(EE)
Please consult the The X.Org Foundation support
         at http://wiki.x.org
 for help.
(EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information.
(EE)
(EE) Server terminated with error (1). Closing log file.

FSLC X11 2.3.4 nitrogen6x /dev/ttymxc0

nitrogen6x login:

Labels (3)
0 Kudos
3 Replies

389 Views
gary_bisson
Senior Contributor III

Hi,

Can you please specify whether you are using the Nitrogen6_MAX or a custom hardware? Your post says both.

Is the display working ok when using our stock image on Nitrogen6_MAX (not a custom hw)?

https://boundarydevices.com/pyro-yocto-release/ 

Regards,

Gary

0 Kudos

389 Views
rajvikamdar
Contributor III

Hi Gary

Thanks for the reply.

Yes, thats correct pyro yocto release works fine with Nitrogen6_max board.

This issue is what we are facing with our custom I.MX6 hardware. We are using the same kernel as that of pyro yocto source that is 4.1.15 version.

Do you think there is some issues with device tree file? As that's the only change we have made.

Thanks

Rajvi

0 Kudos

389 Views
gary_bisson
Senior Contributor III

Hi,

In that case, please change the title (or close this thread and open a new one) since the issue isn't with Nitrogen6_MAX design but your custom one.

As for why it isn't working, I can only help you with a design I know, which is the 6_MAX one. What happens when you use our image as-is on your HW?

Good luck.

Regards,

Gary

0 Kudos