AnsweredAssumed Answered

Xorg - crash on   i.mx6 Solosabresd

Question asked by Alex Berenshtein on Jul 7, 2019
Latest reply on Jul 9, 2019 by Bio_TICFSL

Hi. We have a crash ,   Xorg  on i.mx6 - SoloSabresd.

 

Input 1:  EVB - imx6dlsabresd

Input 2:  Ours Board -  imx6solosabresd

 

On EVB - imx6dlsabresd  we run  :  linux-3.10.53   / linux-4.1.15 /

 / linux-4.9.11 / linux-4.14.78 / linux-4.14.98 . All  images we make with Yocto-System.

Yocto  from 1.8  to 2.5.

  1. On command line we start X11 . It is OK . Xorg is work fine.

 

On Ours Bord  iimx6solosabresd  we run  :  linux-3.10.53   / linux-4.1.15 /

 / linux-4.9.11 / linux-4.14.78 / linux-4.14.98 .  All  images we make with Yocto-System.

Yocto  from 1.8  to 2.5.

 On command line we start X11 , output:

 On  Systems with   linux-3.10.53   / linux-4.1.15  - Xorg is work fine.

 On System with  linux-4.9.11 / linux-4.14.78 / linux-4.14.98  - Xorg is crash.

 On Display we see:

 

 alloc_contig_range: [1c100, 1c8f9) PFNs busy
alloc_contig_range: [1c200, 1c9f9) PFNs busy
alloc_contig_range: [1c200, 1caf9) PFNs busy
alloc_contig_range: [1c400, 1cbf9) PFNs busy
[     1] Failed to open device: No such file or directory, Try again...
[     2] Failed to open device: No such file or directory, Try again...
[     3] Failed to open device: No such file or directory, Try again...
[     4] Failed to open device: No such file or directory, Try again...
[     5] _OpenDevice(1228): FATAL: Failed to open device, errno=No such file or directory.

 

Its very strange , we use identical images , on  imx6dlsabresdimx6solosabresd.

Images with  inux-3.10.53  / linux-4.1.15 - work fine.

Images with linux-4.9.11 / linux-4.14.78 / linux-4.14.98  - Xorg is crash.

Possible , this a problem because of One CPU - mx6dlsabresd , two CPU - imx6solosabresd.

 

Possible ,we have a problem with new version Yocto or Linux ?

Configuration Hardware  - minimum difference.

 

Best regards.

Outcomes