Hi community:
I am using Android8.1 BSP, when open a app,the debug console print several "alloc_contig_range: [5fc00, 603ea) PFNs busy", at the same time, the app page stuck some time,Is there anyway to fix it ?
Try
1) for imx6, check that sdma firmware is really loaded, by dmesg | grep sdma
2) check kernel cma configuration by menuconfig or, try to increase cma arean by "cma=" kernel param
Hello, seem I have the same problem on imx8mm during WiFi comunication.
After a while the comunication between two board via WiFi goes in blocking but the applications still running I can connect via serial port with putty.In this case I see : alloc_contig_range :[....] PFNs busy
The board is not reachable via ping and it's not able to reach any other host also.
I tryed to pull down the WiFi interface and pull-up using the command shell ( ifconfig wlan0 down -> ifconfig wlan0 up) but the comunication is always blocked beside the ifconfig shows UP state
The problem is not present if I use the eth interface (cable). Any suggestion?
Did you ever get to the bottom of this error? We are seeing the exact same thing when using WiFi...
Hi,
My apologies. I'm new to NXP. what is CMA here? and were you able to resolve this issue?
If yes, Please share the fix here. I'm getting the same warning, and my application is crashing when i get this warning.
Thanks,
Jahnavi.
any news ?
is still not solved?
thanks
Found similar issue on i.MX6ULLEVK when access ttymxc1.
root@imx6ull14x14evk:~# uname -a
Linux imx6ull14x14evk 4.14.98-imx_4.14.98_2.0.0_ga+g5d6cbea #1 SMP PREEMPT Wed Oct 30 23:55:04 UTC 2019 armv7l GNU/Linux
root@imx6ull14x14evk:~# stty -F /dev/ttymxc1 115200 -parity -cstopb
alloc_contig_range: [90900, 90914) PFNs busy
root@imx6ull14x14evk:~# echo 1234 > /dev/ttymxc1
alloc_contig_range: [90900, 90914) PFNs busy
alloc_contig_range: [90920, 90934) PFNs busy
alloc_contig_range: [90940, 90954) PFNs busy
root@imx6ull14x14evk:~# echo 1234 > /dev/ttymxc1
alloc_contig_range: [90900, 90914) PFNs busy
root@imx6ull14x14evk:~# echo 1234 > /dev/ttymxc1
root@imx6ull14x14evk:~# echo 1234 > /dev/ttymxc1
root@imx6ull14x14evk:~# echo 1234 > /dev/ttymxc1
alloc_contig_range: 8 callbacks suppressed
alloc_contig_range: [90900, 90914) PFNs busy
alloc_contig_range: [90920, 90934) PFNs busy
alloc_contig_range: [90940, 90954) PFNs busy
any news ?
is still not solved?
thanks
The same here with an other imx6 board, build linux-imx kernel with yocto, warrior branch.
No WiFi on my board, no Ethernet either.
Any body knows the reason of this log ?
Joel
Still not solved, evk board also has this print.
Was the issue solved?
The same issue cause coredump on linux 4.9.88_2.0.0 version
[10219.413664] alloc_contig_range: 85 callbacks suppressed
[10219.413670] alloc_contig_range: [68600, 69601) PFNs busy
[10219.425030] alloc_contig_range: [68600, 69701) PFNs busy
[10219.431136] alloc_contig_range: [68800, 69801) PFNs busy
[10219.437123] alloc_contig_range: [68800, 69901) PFNs busy
[10219.443162] alloc_contig_range: [68800, 69a01) PFNs busy
[10219.449136] alloc_contig_range: [68800, 69b01) PFNs busy
[10219.455168] alloc_contig_range: [68c00, 69c01) PFNs busy
[10219.460887] alloc_contig_range: [68d00, 69d01) PFNs busy
[10219.466670] alloc_contig_range: [68e00, 69e01) PFNs busy
Redistribute latency...
[10219.806379] alloc_contig_range: [72700, 735d5) PFNs busy
[10219.990513] ion-mxc imx_ion: Fail to allocate buffer
Caught SIGSEGV
#0 0x0000ffff9e0f2af4 in poll () from /lib/libc.so.6
#1 0x0000ffff9e1f8a80 in ?? () from /usr/lib/libglib-2.0.so.0
#2 0x000000001e54aac0 in ?? ()
Spinning. Please run 'gdb gst-launch-1.0 11541' to continue debugging, Ctrl-C to quit, or Ctrl-\ to dump core.
Still not solved, evk board also has this print
This error may be related to wifi MAC address.
Please try to set MAC address of wifi interface prior to enable it.
Have a great day,
Victor
-----------------------------------------------------------------------------------------------------------------------
Note: If this post answers your question, please click the Correct Answer button. Thank you!
-----------------------------------------------------------------------------------------------------------------------
Hi~:
I dont think so, I found that may be the cma problem when I trace the code?
the evk board also has the problem,you can check it.
Yes, it's about CMA. Got the same message with IMX6 (imx6q-sabresd) Android 8.0 Oreo release.