<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Page allocation failure when iperf through 5G module in i.MX Processors</title>
    <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1483708#M192138</link>
    <description>&lt;P&gt;Dear Support,&lt;/P&gt;&lt;P&gt;2&amp;gt; Need confirmed did their CMA pool is almost half size of total memory ? Try reduce CMA pool size, and check did issue reproduce rate become lower?&lt;/P&gt;&lt;P&gt;I tried to reduce CMA pool size by modifying arch/arm64/boot/dts/freescale/fsl-imx8dx.dtsi or disable CMA by disable CONFIG_CMA and CONFIG_DMA_CMA.&lt;BR /&gt;OOM is still occurred.&lt;/P&gt;&lt;P&gt;Test command is below. This time I only configure&amp;nbsp;xps_cpus&lt;/P&gt;&lt;P&gt;echo f &amp;gt; /sys/class/net/usb0/queues/tx-0/xps_cpus&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;================&lt;/P&gt;&lt;P&gt;We also ask our vendor ALPS of 5G module. They think maybe&amp;nbsp;xhci driver consumes imx8 memory until OOM and need some limitation to save memory consumption.&lt;/P&gt;&lt;P&gt;Is there any additional patch required for imx8 or any suggestion? We suppose the below kind of patch will be necessary to fix OOM issue.&lt;/P&gt;&lt;P&gt;Subject: [PATCH 1/2] xhci: make sure TRB is fully written before giving it to the controller&lt;BR /&gt;&lt;A href="https://lore.kernel.org/all/20210115161907.2875631-2-mathias.nyman@linux.intel.com/" target="_blank" rel="noopener"&gt;https://lore.kernel.org/all/20210115161907.2875631-2-mathias.nyman@linux.intel.com/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Sean&lt;/P&gt;</description>
    <pubDate>Mon, 04 Jul 2022 07:38:35 GMT</pubDate>
    <dc:creator>Sean_Lin_Askey</dc:creator>
    <dc:date>2022-07-04T07:38:35Z</dc:date>
    <item>
      <title>Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1463133#M190762</link>
      <description>&lt;P&gt;Dear all,&lt;/P&gt;&lt;P&gt;I want to test 5G downlink UDP throughput by iperf3, but error messages always appears.&lt;/P&gt;&lt;P&gt;Page allocation failure always happened when testing over 950Mbps bandwidth.&lt;/P&gt;&lt;P&gt;It looks like xhci's problem.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've tried to increase min_free_kbytes but nothing changed. The default value is 22528.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In order to get higher throughput, I modified the rps_cpus, xps_cpus and smp_affinity and used ECM dialer.&lt;/P&gt;&lt;P&gt;systemctl disable irqbalanced.service&lt;BR /&gt;echo 8 &amp;gt; /sys/class/net/usb0/queues/rx-0/rps_cpus&lt;BR /&gt;echo 4 &amp;gt; /sys/class/net/usb0/queues/tx-0/xps_cpus&lt;BR /&gt;echo 2 &amp;gt; /proc/irq/52/smp_affinity&amp;nbsp; &amp;nbsp;//IMX8-WU 271 Edge 5b110000.usb3&lt;BR /&gt;udhcpc -i usb0&lt;/P&gt;&lt;P&gt;root@ctx0800-c0:~# lsusb&lt;BR /&gt;Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub&lt;BR /&gt;Bus 002 Device 003: ID 05c6:9106 Qualcomm, Inc.&lt;BR /&gt;Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Kernel version: Linux version 4.14.98+g5d3f4fe&amp;nbsp;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please check the full log in attachment.&lt;/P&gt;&lt;PRE&gt;Connecting to host 172.22.1.201, port 5201
Reverse mode, remote host 172.22.1.201 is sending
[  5] local 192.168.225.57 port 39004 connected to 172.22.1.201 port 5201
[ ID] Interval           Transfer     Bitrate         Jitter    Lost/Total Datagrams
[  5]   0.00-1.00   sec   121 MBytes  1.02 Gbits/sec  0.013 ms  0/87710 (0%)  
[  5]   1.00-2.00   sec   136 MBytes  1.14 Gbits/sec  0.005 ms  0/98432 (0%)  
[  5]   2.00-3.00   sec  26.6 MBytes   223 Mbits/sec  0.006 ms  0/19251 (0%)  
[  5]   3.00-4.00   sec  0.00 Bytes  0.00 bits/sec  0.006 ms  0/0 (0%)  
[  584.663946] swapper/1: page allocation failure: order:0, mode:0x1080020(GFP_ATOMIC), nodemask=(null)
[  584.673118] swapper/1 cpuset=/ mems_allowed=0
[  584.677492] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G           O    4.14.98+g58921c6 #1
[  584.685502] Hardware name: Freescale i.MX8QXP MEK (DT)
[  584.690646] Call trace:
[  584.693109] [&amp;lt;ffff000008089c48&amp;gt;] dump_backtrace+0x0/0x3c8
[  584.698523] [&amp;lt;ffff00000808a024&amp;gt;] show_stack+0x14/0x20
[  584.703587] [&amp;lt;ffff000008da41c0&amp;gt;] dump_stack+0x9c/0xbc
[  584.708643] [&amp;lt;ffff000008196178&amp;gt;] warn_alloc+0xe8/0x180
[  584.713786] [&amp;lt;ffff000008196d60&amp;gt;] __alloc_pages_nodemask+0xae8/0xb38
[  584.720056] [&amp;lt;ffff000008196f00&amp;gt;] page_frag_alloc+0x150/0x170
[  584.725731] [&amp;lt;ffff000008b771b0&amp;gt;] __netdev_alloc_skb+0xb0/0x138
[  584.731581] [&amp;lt;ffff00000885b264&amp;gt;] rx_submit+0x44/0x260
[  584.736640] [&amp;lt;ffff00000885b704&amp;gt;] rx_complete+0x1fc/0x228
[  584.741964] [&amp;lt;ffff00000886aea0&amp;gt;] __usb_hcd_giveback_urb+0x60/0xf0
[  584.748065] [&amp;lt;ffff00000886b0e8&amp;gt;] usb_hcd_giveback_urb+0xe8/0x120
[  584.754079] [&amp;lt;ffff0000088c8f5c&amp;gt;] xhci_giveback_urb_in_irq.isra.25+0x84/0xb0
[  584.761043] [&amp;lt;ffff0000088c9160&amp;gt;] xhci_td_cleanup+0xd0/0x118
[  584.766624] [&amp;lt;ffff0000088ccd90&amp;gt;] finish_td.isra.46+0xe8/0x120
[  584.772374] [&amp;lt;ffff0000088cd278&amp;gt;] xhci_irq+0x4b0/0x1528
[  584.777517] [&amp;lt;ffff00000886abbc&amp;gt;] usb_hcd_irq+0x2c/0x48
[  584.782661] [&amp;lt;ffff0000088ab908&amp;gt;] cdns3_host_irq+0x28/0x40
[  584.788063] [&amp;lt;ffff0000088a6370&amp;gt;] cdns3_irq+0xa0/0xa8
[  584.793035] [&amp;lt;ffff00000811ca74&amp;gt;] __handle_irq_event_percpu+0x5c/0x148
[  584.799488] [&amp;lt;ffff00000811cb7c&amp;gt;] handle_irq_event_percpu+0x1c/0x58
[  584.805681] [&amp;lt;ffff00000811cc00&amp;gt;] handle_irq_event+0x48/0x78
[  584.811262] [&amp;lt;ffff000008120a00&amp;gt;] handle_fasteoi_irq+0xa8/0x180
[  584.817108] [&amp;lt;ffff00000811bb94&amp;gt;] generic_handle_irq+0x24/0x38
[  584.822867] [&amp;lt;ffff00000811c214&amp;gt;] __handle_domain_irq+0x5c/0xb8
[  584.828703] [&amp;lt;ffff000008081960&amp;gt;] gic_handle_irq+0x78/0x174
[  584.834193] Exception stack(0xffff00000800bc50 to 0xffff00000800bd90)
[  584.840640] bc40:                                   0000000000000102 ffff800078392880
[  584.848474] bc60: 0000000000000000 0000000000000000 000000007459557a 0000000064172a21
[  584.856312] bc80: 0000000000000001 00000000c90116ac 0000000000000008 0000000000000000
[  584.864146] bca0: 0000000000004788 ffff800075e75c00 ffff00000800bd30 0000000000000004
[  584.871986] bcc0: 0000000000000000 0000000000000018 0000000000000000 0000ffffac47abc0
[  584.879828] bce0: 0000ffffac528a70 ffff80007df6ee80 ffff0000094bbe80 ffff80007df6efcc
[  584.887666] bd00: ffff0000094bb000 0000000000000140 ffff00000800be24 ffff80006799ec00
[  584.895508] bd20: ffff80007df6efb8 000000000000c8bd 0000000000000000 ffff00000800bd90
[  584.903347] bd40: ffff000008b87390 ffff00000800bd90 ffff000008b87394 0000000080000145
[  584.911189] bd60: 0000000000000000 0000000000000000 0000ffffffffffff ffff000008b8e290
[  584.919025] bd80: ffff00000800bd90 ffff000008b87394
[  584.923909] [&amp;lt;ffff000008083230&amp;gt;] el1_irq+0xb0/0x124
[  584.928793] [&amp;lt;ffff000008b87394&amp;gt;] enqueue_to_backlog+0x124/0x240
[  584.934718] [&amp;lt;ffff000008b8e2b8&amp;gt;] netif_rx_internal+0x100/0x1a8
[  584.940554] [&amp;lt;ffff000008b8e39c&amp;gt;] netif_rx+0xc/0x18
[  584.945353] [&amp;lt;ffff00000885a5e0&amp;gt;] usbnet_skb_return+0x68/0xb0
[  584.951022] [&amp;lt;ffff00000885b884&amp;gt;] usbnet_bh+0x154/0x238
[  584.956168] [&amp;lt;ffff0000080d3a2c&amp;gt;] tasklet_action+0x6c/0x108
[  584.961664] [&amp;lt;ffff000008081b8c&amp;gt;] __do_softirq+0x12c/0x228
[  584.967069] [&amp;lt;ffff0000080d3540&amp;gt;] irq_exit+0xc8/0x100
[  584.972036] [&amp;lt;ffff00000811c218&amp;gt;] __handle_domain_irq+0x60/0xb8
[  584.977875] [&amp;lt;ffff000008081960&amp;gt;] gic_handle_irq+0x78/0x174
[  584.983364] Exception stack(0xffff000009aebe20 to 0xffff000009aebf60)
[  584.989813] be20: 0000000000000000 0000000000000000 0000000000000001 0000000000000000
[  584.997658] be40: ffff0000094b4388 ffff000009aebf50 0000800074a83000 16ebdf868f31edd4
[  585.005501] be60: 0000000000000002 ffff0000094c8580 0000000000000980 0000000000000001
[  585.013339] be80: 000000737920ae80 0000000000000000 0000000000000000 0000000000000018
[  585.021182] bea0: 0000000000000000 0000ffffac47abc0 0000ffffac528a70 ffff0000094ae018
[  585.029020] bec0: ffff0000094ca000 ffff0000094ca000 ffff0000094b9cc0 ffff0000094ca31c
[  585.036864] bee0: 0000000000000000 0000000000000000 ffff800078392880 0000000000000000
[  585.044701] bf00: 0000000000000000 ffff000009aebf60 ffff00000808581c ffff000009aebf60
[  585.052545] bf20: ffff000008085820 0000000000000145 0000000000000000 0000000000000000
[  585.060382] bf40: ffffffffffffffff ffff000008142a4c ffff000009aebf60 ffff000008085820
[  585.068225] [&amp;lt;ffff000008083230&amp;gt;] el1_irq+0xb0/0x124
[  585.073108] [&amp;lt;ffff000008085820&amp;gt;] arch_cpu_idle+0x10/0x18
[  585.078426] [&amp;lt;ffff00000810d8a0&amp;gt;] do_idle+0x120/0x1e0
[  585.083392] [&amp;lt;ffff00000810dafc&amp;gt;] cpu_startup_entry+0x24/0x28
[  585.089060] [&amp;lt;ffff00000808fac8&amp;gt;] secondary_start_kernel+0x110/0x120
[  585.095329] Mem-Info:
[  585.097616] active_anon:10717 inactive_anon:2112 isolated_anon:0
[  585.097616]  active_file:62 inactive_file:104 isolated_file:0
[  585.097616]  unevictable:729 dirty:0 writeback:0 unstable:0
[  585.097616]  slab_reclaimable:4086 slab_unreclaimable:21377
[  585.097616]  mapped:962 shmem:2310 pagetables:529 bounce:0
[  585.097616]  free:181224 free_pcp:225 free_cma:179237
[  585.131021] Node 0 active_anon:42868kB inactive_anon:8448kB active_file:248kB inactive_file:416kB unevictable:2916kB isolated(anon):0kB isolated(file):0kB mapped:3848kB dirty:0kB writeback:0kB shmem:9240kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 8192kB writeback_tmp:0kB unstable:0kB all_unreclaimable? yes
[  585.158580] Node 0 DMA free:724896kB min:22528kB low:28160kB high:33792kB active_anon:42868kB inactive_anon:8448kB active_file:248kB inactive_file:416kB unevictable:2916kB writepending:0kB present:1949696kB managed:1763028kB mlocked:2916kB kernel_stack:3856kB pagetables:2116kB bounce:0kB free_pcp:900kB local_pcp:656kB free_cma:716948kB
[  585.188325] lowmem_reserve[]: 0 0 0
[  585.191827] Node 0 DMA: 198*4kB (UMEHC) 157*8kB (MEHC) 390*16kB (UMHC) 0*32kB 1*64kB (C) 0*128kB 1*256kB (C) 1*512kB (C) 1*1024kB (C) 1*2048kB (C) 0*4096kB 1*8192kB (C) 1*16384kB (C) 21*32768kB (C) = 724896kB
[  585.210423] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=2048kB
[  585.218860] 3112 total pagecache pages
[  585.222617] 0 pages in swap cache
[  585.225936] Swap cache stats: add 0, delete 0, find 0/0
[  585.231164] Free swap  = 0kB
[  585.234046] Total swap = 0kB
[  585.236924] 487424 pages RAM
[  585.239808] 0 pages HighMem/MovableOnly
[  585.243648] 46667 pages reserved
[  585.246877] 245760 pages cma reserved
[  585.250583] swapper/1: page allocation failure: order:0, mode:0x1080020(GFP_ATOMIC), nodemask=(null)
[  585.259737] swapper/1 cpuset=/ mems_allowed=0
[  585.264114] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G           O    4.14.98+g58921c6 #1
[  585.272124] Hardware name: Freescale i.MX8QXP MEK (DT)
[  585.277260] Call trace:
[  585.279714] [&amp;lt;ffff000008089c48&amp;gt;] dump_backtrace+0x0/0x3c8
[  585.285117] [&amp;lt;ffff00000808a024&amp;gt;] show_stack+0x14/0x20
[  585.290175] [&amp;lt;ffff000008da41c0&amp;gt;] dump_stack+0x9c/0xbc
[  585.295232] [&amp;lt;ffff000008196178&amp;gt;] warn_alloc+0xe8/0x180
[  585.300379] [&amp;lt;ffff000008196d60&amp;gt;] __alloc_pages_nodemask+0xae8/0xb38
[  5]   4.00-5.01   sec  0.00 Bytes  0.00 bits/sec  0.006 ms  0/0[  585.306653] [&amp;lt;ffff000008196f00&amp;gt;] page_frag_alloc+0x150/0x170
 (0%)  [  585.317956] [&amp;lt;ffff000008b771b0&amp;gt;] __netdev_alloc_skb+0xb0/0x138&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2022 09:47:49 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1463133#M190762</guid>
      <dc:creator>Sean_Lin_Askey</dc:creator>
      <dc:date>2022-05-24T09:47:49Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1463135#M190763</link>
      <description>&lt;P&gt;Full log here&lt;/P&gt;</description>
      <pubDate>Tue, 24 May 2022 09:49:22 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1463135#M190763</guid>
      <dc:creator>Sean_Lin_Askey</dc:creator>
      <dc:date>2022-05-24T09:49:22Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1472049#M191354</link>
      <description>&lt;P&gt;Is there anyone can help?&lt;/P&gt;</description>
      <pubDate>Fri, 10 Jun 2022 07:10:38 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1472049#M191354</guid>
      <dc:creator>Sean_Lin_Askey</dc:creator>
      <dc:date>2022-06-10T07:10:38Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1476094#M191608</link>
      <description>&lt;P&gt;Hello Sean,&lt;/P&gt;
&lt;P&gt;You attached file , seems not a txt log file , it should be a html file, open it from web browser, it is show as loggin for jira; So you need share the log file again.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jun 2022 15:42:06 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1476094#M191608</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2022-06-17T15:42:06Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1476351#M191628</link>
      <description>&lt;P&gt;Hi Bio,&lt;/P&gt;&lt;P&gt;I re-uploaded the log here. Please check again.&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Sean&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jun 2022 01:32:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1476351#M191628</guid>
      <dc:creator>Sean_Lin_Askey</dc:creator>
      <dc:date>2022-06-20T01:32:16Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1476356#M191629</link>
      <description>&lt;P&gt;When memory leak happened, kernel log dumped the process list, but there is no process has huge memory usage.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jun 2022 01:36:15 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1476356#M191629</guid>
      <dc:creator>Sean_Lin_Askey</dc:creator>
      <dc:date>2022-06-20T01:36:15Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1476423#M191634</link>
      <description>&lt;P&gt;Before OOM happened, the available memory of testing 1.1Gbps throughput is about 1.3Gb(total 1.7Gb)&amp;nbsp;&lt;/P&gt;&lt;P&gt;I think the issue is related to IRQ of USB3 because I assigned it to CPU1 by command&amp;nbsp;&lt;SPAN&gt;echo 2 &amp;gt; /proc/irq/52/smp_affinity&amp;nbsp; &amp;nbsp;//IMX8-WU 271 Edge 5b110000.usb3&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;and page allocation message is CPU1.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;[ 325.016123] swapper/1: page allocation failure: order:0, mode:0x1080020(GFP_ATOMIC), nodemask=(null)&lt;BR /&gt;[ 325.025266] swapper/1 cpuset=/ mems_allowed=0&lt;BR /&gt;&lt;STRONG&gt;[ 325.029631] CPU: 1 PID: 0 Comm: swapper/1 Tainted: G O 4.14.98+g0a45016 #1&lt;/STRONG&gt;&lt;BR /&gt;[ 325.037637] Hardware name: Freescale i.MX8QXP MEK (DT)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I still tried to increase the&amp;nbsp;min_free_kbytes, but it could not stop this issue happened&lt;/P&gt;</description>
      <pubDate>Mon, 20 Jun 2022 03:14:23 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1476423#M191634</guid>
      <dc:creator>Sean_Lin_Askey</dc:creator>
      <dc:date>2022-06-20T03:14:23Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1477447#M191749</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;This issue more likely related memory&lt;/P&gt;
&lt;P&gt;1&amp;gt; In case not enable below cmd, how about test result.&lt;/P&gt;
&lt;P&gt;echo 8 &amp;gt; /sys/class/net/usb0/queues/rx-0/rps_cpus&lt;BR /&gt;echo 4 &amp;gt; /sys/class/net/usb0/queues/tx-0/xps_cpus&lt;BR /&gt;echo 2 &amp;gt; /proc/irq/52/smp_affinity //IMX8-WU 271 Edge 5b110000.usb3&lt;/P&gt;
&lt;P&gt;2&amp;gt; Need confirmed did their CMA pool is almost half size of total memory ? Try reduce CMA pool size, and check did issue reproduce rate become lower?&lt;/P&gt;
&lt;P&gt;3&amp;gt; run kernel memory leak detector on this case.&lt;/P&gt;
&lt;P&gt;4&amp;gt; Could customer try reproduce this issue on 8QXP MEK board, with or without their 5G module. For example without 5G module , direct connect with PC , by using usb netowrk?&lt;/P&gt;
&lt;P&gt;5&amp;gt; On their board, is there one Ethernet port, if so , do iperf only on Ethernet port, result is ?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Tue, 21 Jun 2022 12:29:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1477447#M191749</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2022-06-21T12:29:31Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1480493#M191942</link>
      <description>&lt;P&gt;Dear NXP support,&lt;/P&gt;&lt;P&gt;1&amp;gt; In case not enable below cmd, how about test result.&lt;/P&gt;&lt;P&gt;echo 8 &amp;gt; /sys/class/net/usb0/queues/rx-0/rps_cpus&lt;BR /&gt;echo 4 &amp;gt; /sys/class/net/usb0/queues/tx-0/xps_cpus&lt;BR /&gt;echo 2 &amp;gt; /proc/irq/52/smp_affinity //IMX8-WU 271 Edge 5b110000.usb3&lt;/P&gt;&lt;P&gt;No OOM occurred but throughput is only about 450Mbps.&lt;/P&gt;&lt;P&gt;2&amp;gt; Need confirmed did their CMA pool is almost half size of total memory ? Try reduce CMA pool size, and check did issue reproduce rate become lower?&lt;/P&gt;&lt;P&gt;=&amp;gt; A stupid question. How to configure CMA pool size? Modify CONFIG_CMA_SIZE_MBYTE in menuconfig?&lt;BR /&gt;Current CMA pool size and memory information is below&lt;BR /&gt;root@ctx0800-c0:~# cat /proc/meminfo | grep Cma&lt;BR /&gt;CmaTotal: 983040 kB&lt;BR /&gt;CmaFree: 716948 kB&lt;BR /&gt;root@ctx0800-c0:~# free -ht&lt;BR /&gt;total used free shared buff/cache available&lt;BR /&gt;Mem: 1.7G 338M 1.3G 17M 38M 1.3G&lt;BR /&gt;Swap: 0B 0B 0B&lt;BR /&gt;Total: 1.7G 338M 1.3G&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In this case, contiguous memory reduced suddenly and imx8 cannot allocate new memory using GFP_ATOMIC.&lt;/P&gt;&lt;P&gt;root@ctx0800-c0:~# cat /proc/buddyinfo&lt;BR /&gt;Node 0, zone DMA 169 129 52 52 38 31 28 12 10 5 3 2 3 35&lt;BR /&gt;root@ctx0800-c0:~# iperf3 -c 192.168.2.230 -R -u -b 1100M -t 10&amp;amp;&lt;BR /&gt;[ 5] 0.00-1.23 sec 14.9 MBytes 102 Mbits/sec 34.335 ms 34640/45402 (76%)&lt;BR /&gt;Node 0, zone DMA 396 148 25 13 6 2 2 3 2 0 2 3 4 32&lt;BR /&gt;root@ctx0800-c0:~# [ 5] 1.23-2.00 sec 18.0 MBytes 195 Mbits/sec 0.017 ms 56931/69931 (81%)&lt;BR /&gt;Node 0, zone DMA 349 144 24 13 5 2 2 3 2 0 3 3 3 29&lt;BR /&gt;root@ctx0800-c0:~# [ 5] 2.00-3.00 sec 0.00 Bytes 0.00 bits/sec 0.017 ms 0/0 (0%)&lt;BR /&gt;Node 0, zone DMA 348 145 23 14 6 3 3 4 2 0 2 2 4 24&lt;BR /&gt;root@ctx0800-c0:~# [ 5] 3.00-4.00 sec 0.00 Bytes 0.00 bits/sec 0.017 ms 0/0 (0%)&lt;BR /&gt;Node 0, zone DMA 329 145 24 13 6 2 3 3 2 1 2 3 1 21&lt;BR /&gt;root@ctx0800-c0:~# [ 173.272163] swapper/1: page allocation failure: order:0, mode:0x1080020(GFP_ATOMIC), nodemask=(null)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3,4,5&amp;gt; still in progress....&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Sean&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 27 Jun 2022 09:35:10 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1480493#M191942</guid>
      <dc:creator>Sean_Lin_Askey</dc:creator>
      <dc:date>2022-06-27T09:35:10Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1480858#M191959</link>
      <description>&lt;P&gt;4&amp;gt; Could customer try reproduce this issue on 8QXP MEK board, with or without their 5G module. For example without 5G module , direct connect with PC , by using usb netowrk?&lt;/P&gt;&lt;P&gt;I don't have 8QXP MEK board so I tried usb network on our product.&lt;/P&gt;&lt;P&gt;systemctl disable irqbalanced.service&lt;BR /&gt;echo 8 &amp;gt; /sys/class/net/usb0/queues/rx-0/rps_cpus&lt;BR /&gt;echo 4 &amp;gt; /sys/class/net/usb0/queues/tx-0/xps_cpus&lt;BR /&gt;echo 2 &amp;gt; /proc/irq/50/smp_affinity //IMX8-WU 267 Edge&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 5b0d0000.usb&lt;/P&gt;&lt;P&gt;The result is.. no OOM occurred.&lt;BR /&gt;My PC could not send over 1Gbps iperf stream, so I reduced UDP packet size to 128bytes in this case. (Short packet test with 5G module can makes system OOM.)&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;5&amp;gt; On their board, is there one Ethernet port, if so , do iperf only on Ethernet port, result is ?&lt;/P&gt;&lt;P&gt;systemctl disable irqbalanced.service&lt;BR /&gt;echo 8 &amp;gt; /sys/class/net/usb0/queues/rx-0/rps_cpus&lt;BR /&gt;echo 4 &amp;gt; /sys/class/net/usb0/queues/tx-0/xps_cpus&lt;BR /&gt;echo 2 &amp;gt; /proc/irq/112/smp_affinity //IMX8-WU 262 Edge 5b050000.ethernet&lt;/P&gt;&lt;P&gt;Same as question4. Ethernet port test is also good with short packet stream.&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jun 2022 02:28:07 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1480858#M191959</guid>
      <dc:creator>Sean_Lin_Askey</dc:creator>
      <dc:date>2022-06-28T02:28:07Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1481331#M191989</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;The dts file could could be changed for cma size,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;A href="https://source.codeaurora.org/external/imx/linux-imx/tree/arch/arm64/boot/dts/freescale/fsl-imx8dx.dtsi?h=imx_4.14.98_2.3.0#n150" target="_blank" rel="nofollow noopener noreferrer"&gt;https://source.codeaurora.org/external/imx/linux-imx/tree/arch/arm64/boot/dts/freescale/fsl-imx8dx.d...&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;Or&amp;nbsp; boot parameter "CMA=" could be used.&lt;/P&gt;
&lt;PRE class="literal-block"&gt;        cma=nn[MG]@[start[MG][-end[MG]]]
                        [ARM,X86,KNL]
                        Sets the size of kernel global memory area for
                        contiguous memory allocations and optionally the
                        placement constraint by the physical address range of
                        memory allocations. A value of 0 disables CMA
                        altogether. For more information, see
                        include/linux/dma-contiguous.h&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This issue only reproduced after enabled rps and xps of network stack, it means&amp;nbsp;&lt;SPAN&gt;frequently allocate memory.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;And note the using GFP_ATOMIC when issue got.&amp;nbsp;&amp;nbsp; GFP_ATOMIC means not sleep.&lt;/P&gt;
&lt;P&gt;And also note from alloc failure log, it is&amp;nbsp; allocate order 0 with GFP_ATOMIC.&amp;nbsp; The first time error log show :&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Node 0 DMA: 181*4kB (UMEC) 60*8kB (UMEC) 484*16kB (UMEC) 2*32kB (U) 1*64kB (C) 0*128kB 1*256kB (C) 1*512kB (C) 1*1024kB (C) 1*2048kB (C) 0*4096kB 1*8192kB (C) 1*16384kB (C) 21*32768kB (C) = 725620kB&lt;/P&gt;
&lt;P&gt;As this 181*4KB mark as&amp;nbsp;MIGRATE_CMA,&amp;nbsp; I doubt&amp;nbsp; that GFP_ATOMIC can not alloc from&amp;nbsp;MIGRATE_CMA.&amp;nbsp; If you need find the real reason of this issue, you need debug function&amp;nbsp;__alloc_pages_nodemask.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;This issue should not related to NXP usb driver code.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Tue, 28 Jun 2022 17:40:43 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1481331#M191989</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2022-06-28T17:40:43Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1483708#M192138</link>
      <description>&lt;P&gt;Dear Support,&lt;/P&gt;&lt;P&gt;2&amp;gt; Need confirmed did their CMA pool is almost half size of total memory ? Try reduce CMA pool size, and check did issue reproduce rate become lower?&lt;/P&gt;&lt;P&gt;I tried to reduce CMA pool size by modifying arch/arm64/boot/dts/freescale/fsl-imx8dx.dtsi or disable CMA by disable CONFIG_CMA and CONFIG_DMA_CMA.&lt;BR /&gt;OOM is still occurred.&lt;/P&gt;&lt;P&gt;Test command is below. This time I only configure&amp;nbsp;xps_cpus&lt;/P&gt;&lt;P&gt;echo f &amp;gt; /sys/class/net/usb0/queues/tx-0/xps_cpus&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;================&lt;/P&gt;&lt;P&gt;We also ask our vendor ALPS of 5G module. They think maybe&amp;nbsp;xhci driver consumes imx8 memory until OOM and need some limitation to save memory consumption.&lt;/P&gt;&lt;P&gt;Is there any additional patch required for imx8 or any suggestion? We suppose the below kind of patch will be necessary to fix OOM issue.&lt;/P&gt;&lt;P&gt;Subject: [PATCH 1/2] xhci: make sure TRB is fully written before giving it to the controller&lt;BR /&gt;&lt;A href="https://lore.kernel.org/all/20210115161907.2875631-2-mathias.nyman@linux.intel.com/" target="_blank" rel="noopener"&gt;https://lore.kernel.org/all/20210115161907.2875631-2-mathias.nyman@linux.intel.com/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Sean&lt;/P&gt;</description>
      <pubDate>Mon, 04 Jul 2022 07:38:35 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1483708#M192138</guid>
      <dc:creator>Sean_Lin_Askey</dc:creator>
      <dc:date>2022-07-04T07:38:35Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1484720#M192196</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;Did you get below test result from customer:&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;3&amp;gt; run kernel memory leak detector on this case.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;4&amp;gt; Could you try reproduce this issue on 8QXP MEK board,&amp;nbsp; with or without their 5G module. For example without 5G module , direct connect with PC , by using usb netowrk?&lt;/SPAN&gt;&lt;/P&gt;
&lt;DIV id="bodyDisplay_6" class="lia-message-body lia-component-message-view-widget-body lia-component-body-signature-highlight-escalation lia-component-message-view-widget-body-signature-highlight-escalation"&gt;
&lt;DIV class="lia-message-body-content"&gt;
&lt;P&gt;&lt;SPAN&gt;5&amp;gt; On your board,&amp;nbsp; is there one Ethernet port, if so , do iperf only on Ethernet port, result is ?&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;The test of reduce CMA size, purpose is for check did issue reproduce rate become lower, not means this issue will gone. &lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;As previous suggested, you should&amp;nbsp; debug function __alloc_pages_nodemask, to check out why issue occurs, and issue caused by too much allocation from&amp;nbsp; usb code Or&amp;nbsp; from network stack ?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If there NO memory leak,&amp;nbsp; suggest customer based on finding from debug&amp;nbsp;__alloc_pages_nodemask, to decide need&amp;nbsp;&lt;/SPAN&gt;&lt;SPAN&gt;optimize network stack memory usage or other part.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;Current can not&amp;nbsp; say issue related to xhci driver, did you could prove it ?&amp;nbsp; I do not think you give enough information on this.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;I do not think this link will help&amp;nbsp;&lt;A href="https://lore.kernel.org/all/20210115161907.2875631-2-mathias.nyman@linux.intel.com/" target="_blank" rel="nofollow noopener noreferrer"&gt;https://lore.kernel.org/all/20210115161907.2875631-2-mathias.nyman@linux.intel.com/&amp;nbsp;&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Tue, 05 Jul 2022 14:17:31 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1484720#M192196</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2022-07-05T14:17:31Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1485806#M192263</link>
      <description>&lt;P&gt;Dear Support,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;3&amp;gt; run kernel memory leak detector on this case.&lt;/P&gt;&lt;P&gt;Sean:&lt;BR /&gt;When OOM occurres, console always gets stuck. I could not dump information after OOM from /sys/kernel/debug/kmemleak&lt;BR /&gt;But, I still captured the log with lower throughput test. Please check attachment.&lt;/P&gt;&lt;P&gt;4&amp;gt; Could you try reproduce this issue on 8QXP MEK board, with or without their 5G module. For example without 5G module , direct connect with PC , by using usb netowrk?&lt;/P&gt;&lt;P&gt;Sean:&lt;BR /&gt;I don't have 8QXP MEK board. I need to contact other department to reproduce this issue.&lt;/P&gt;&lt;P&gt;5&amp;gt; On your board, is there one Ethernet port, if so , do iperf only on Ethernet port, result is ?&lt;/P&gt;&lt;P&gt;Sean:&lt;BR /&gt;I've tried on 3 different interfaces on our board. Issue is only happened on usb3 .&lt;/P&gt;&lt;P&gt;IMX8-WU 271 Edge 5b110000.usb3 // for 5G module&lt;BR /&gt;=&amp;gt; 5G network: rate drop to 0Mbps and OOM&lt;BR /&gt;=&amp;gt; 4G network: rate drop to 0Mbps but no OOM&lt;BR /&gt;IMX8-WU 267 Edge 5b0d0000.usb // USB port CN2302 (USB dongle)&lt;BR /&gt;=&amp;gt; OK&lt;BR /&gt;IMX8-WU 262 Edge 5b050000.ethernet //ethernet port&lt;BR /&gt;=&amp;gt; OK&lt;BR /&gt;&lt;BR /&gt;The test of reduce CMA size, purpose is for check did issue reproduce rate become lower, not means this issue will gone.&lt;/P&gt;&lt;P&gt;Sean:&lt;BR /&gt;Issue reproduce rate is still same when reduce the CMA pool size or disable CMA.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;As previous suggested, you should debug function __alloc_pages_nodemask, to check out why issue occurs, and issue caused by too much allocation from usb code Or from network stack ?&lt;BR /&gt;If there NO memory leak, suggest customer based on finding from debug __alloc_pages_nodemask, to decide need optimize network stack memory usage or other part.&lt;BR /&gt;Current can not say issue related to xhci driver, did you could prove it ? I do not think you give enough information on this.&lt;BR /&gt;I do not think this link will help &lt;A href="https://lore.kernel.org/all/20210115161907.2875631-2-mathias.nyman@linux.intel.com/" target="_blank" rel="noopener"&gt;https://lore.kernel.org/all/20210115161907.2875631-2-mathias.nyman@linux.intel.com/&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Sean:&lt;BR /&gt;I am not an expert on linux kernel, but from call trace log, I just saw the __alloc_pages_nodemask be triggered by handling xhci irq every time.&lt;BR /&gt;The call trace is all the same every OOM happened.&lt;BR /&gt;Does this information prove that xhci cause this issue, or do you have any suggestion of debug __alloc_pages_nodemask?&lt;/P&gt;&lt;P&gt;[ 187.104601] Call trace:&lt;BR /&gt;[ 187.107048] [&amp;lt;ffff000008089ed8&amp;gt;] dump_backtrace+0x0/0x3c8&lt;BR /&gt;[ 187.112452] [&amp;lt;ffff00000808a2b4&amp;gt;] show_stack+0x14/0x20&lt;BR /&gt;[ 187.117507] [&amp;lt;ffff000008da6940&amp;gt;] dump_stack+0x9c/0xbc&lt;BR /&gt;[ 187.122562] [&amp;lt;ffff000008196458&amp;gt;] warn_alloc+0xe8/0x180&lt;BR /&gt;[ 187.127706] [&amp;lt;ffff000008197040&amp;gt;] __alloc_pages_nodemask+0xae8/0xb38&lt;BR /&gt;[ 187.133980] [&amp;lt;ffff0000081971e0&amp;gt;] page_frag_alloc+0x150/0x170&lt;BR /&gt;[ 187.139642] [&amp;lt;ffff000008b7a918&amp;gt;] __netdev_alloc_skb+0xb0/0x138&lt;BR /&gt;[ 187.145479] [&amp;lt;ffff00000885d9cc&amp;gt;] rx_submit+0x44/0x260&lt;BR /&gt;[ 187.150535] [&amp;lt;ffff00000885de6c&amp;gt;] rx_complete+0x1fc/0x228&lt;BR /&gt;[ 187.155854] [&amp;lt;ffff00000886d608&amp;gt;] __usb_hcd_giveback_urb+0x60/0xf0&lt;BR /&gt;[ 187.161953] [&amp;lt;ffff00000886d850&amp;gt;] usb_hcd_giveback_urb+0xe8/0x120&lt;BR /&gt;[ 187.167964] [&amp;lt;ffff0000088cc6c4&amp;gt;] xhci_giveback_urb_in_irq.isra.25+0x84/0xb0&lt;BR /&gt;[ 187.174931] [&amp;lt;ffff0000088cc8c8&amp;gt;] xhci_td_cleanup+0xd0/0x118&lt;BR /&gt;[ 187.180507] [&amp;lt;ffff0000088d04f8&amp;gt;] finish_td.isra.46+0xe8/0x120&lt;BR /&gt;[ 187.186258] [&amp;lt;ffff0000088d09e0&amp;gt;] xhci_irq+0x4b0/0x1528&lt;BR /&gt;[ 187.191401] [&amp;lt;ffff00000886d324&amp;gt;] usb_hcd_irq+0x2c/0x48&lt;BR /&gt;[ 187.196545] [&amp;lt;ffff0000088ae070&amp;gt;] cdns3_host_irq+0x28/0x40&lt;BR /&gt;[ 187.201948] [&amp;lt;ffff0000088a8ad8&amp;gt;] cdns3_irq+0xa0/0xa8&lt;BR /&gt;[ 187.206918] [&amp;lt;ffff00000811ca74&amp;gt;] __handle_irq_event_percpu+0x5c/0x148&lt;BR /&gt;[ 187.213364] [&amp;lt;ffff00000811cb7c&amp;gt;] handle_irq_event_percpu+0x1c/0x58&lt;BR /&gt;[ 187.219549] [&amp;lt;ffff00000811cc00&amp;gt;] handle_irq_event+0x48/0x78&lt;BR /&gt;[ 187.225127] [&amp;lt;ffff000008120a00&amp;gt;] handle_fasteoi_irq+0xa8/0x180&lt;BR /&gt;[ 187.230964] [&amp;lt;ffff00000811bb94&amp;gt;] generic_handle_irq+0x24/0x38&lt;BR /&gt;[ 187.236716] [&amp;lt;ffff00000811c214&amp;gt;] __handle_domain_irq+0x5c/0xb8&lt;BR /&gt;[ 187.242553] [&amp;lt;ffff000008081960&amp;gt;] gic_handle_irq+0x78/0x174&lt;/P&gt;&lt;P&gt;Many thanks,&lt;/P&gt;&lt;P&gt;Sean&lt;/P&gt;</description>
      <pubDate>Thu, 07 Jul 2022 01:59:39 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1485806#M192263</guid>
      <dc:creator>Sean_Lin_Askey</dc:creator>
      <dc:date>2022-07-07T01:59:39Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1488157#M192434</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;My understanding:&amp;nbsp; i.MX8QXP as usb host,&amp;nbsp; iperf client,&amp;nbsp; 5G module as&amp;nbsp; usb device, iperf host (not sure), and&amp;nbsp; some special network stack change to make iperf result go to&amp;nbsp;&lt;SPAN&gt;1.1Gbps, right?&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;As customer no MEK board,&amp;nbsp; suggest connect board to Linux PC,&amp;nbsp; try test under above condition (I suggest using NCM, if they using ECM, please share how to using ECM),&amp;nbsp; and if reproduced,&amp;nbsp; share detail steps.&amp;nbsp; Or using two sets&amp;nbsp; customer&amp;nbsp; i.MX8QXP board&amp;nbsp; connected ?&lt;/P&gt;
&lt;P&gt;Current i had started try to reproduce by using i.MX8QXP MEK, did not reproduce it yet. Need customer side provide reproduce steps.&lt;/P&gt;
&lt;P&gt;The callstack ,&amp;nbsp; there are some xhci function, but doesnot mean issue caused by xhci driver.&lt;/P&gt;
&lt;P&gt;Below call stack show: on xhci irq context, one urb is finished transfer,&amp;nbsp; that urb will return to device driver which is (&lt;SPAN&gt;drivers/net/usb/usbnet.c), callback is rx_complete,&amp;nbsp; then will enter to network stack to allocate memory , then alloc failure occurs.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;warn_alloc+0xe8/0x180&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;__alloc_pages_nodemask+0xae8/0xb38&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;page_frag_alloc+0x150/0x170&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;STRONG&gt;__netdev_alloc_skb&lt;/STRONG&gt;+0xb0/0x138&amp;nbsp; &amp;nbsp;//this code from &lt;STRONG&gt;network stack&amp;nbsp;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;rx_submit+0x44/0x260&amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp; &amp;nbsp;//this two function from&amp;nbsp;&lt;STRONG&gt;drivers/net/usb/usbnet.c&amp;nbsp;&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;STRONG&gt;&amp;nbsp;rx_complete&lt;/STRONG&gt;+0x1fc/0x228&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&amp;nbsp;__usb_hcd_giveback_urb+0x60/0xf0&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;usb_hcd_giveback_urb+0xe8/0x120&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;xhci_giveback_urb_in_irq.isra.25+0x84/0xb0&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;xhci_td_cleanup+0xd0/0x118&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;finish_td.isra.46+0xe8/0x120&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;xhci_irq+0x4b0/0x1528&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;The issue log "page allocation failure: order:0, mode:0x1080020(GFP_ATOMIC),",&amp;nbsp; please note it is&amp;nbsp;GFP_ATOMIC,&amp;nbsp; and only one page, so customer should add related debug log into function&amp;nbsp;__alloc_pages_slowpath , to check out why it alloc failure.&lt;/P&gt;
&lt;P&gt;Regards&lt;/P&gt;</description>
      <pubDate>Tue, 12 Jul 2022 13:21:30 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1488157#M192434</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2022-07-12T13:21:30Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1488619#M192461</link>
      <description>&lt;P&gt;Dear Support,&lt;/P&gt;&lt;P&gt;I tried to insert some log in&amp;nbsp;__alloc_pages_slowpath and found the&amp;nbsp;fail reason is from this part and goto nopage&amp;nbsp; then warn_alloc.&lt;/P&gt;&lt;P&gt;/* Caller is not willing to reclaim, we can't balance anything */&lt;BR /&gt;if (!can_direct_reclaim)&amp;nbsp;&lt;BR /&gt;goto nopage;&lt;/P&gt;&lt;P&gt;Kernel could not directly reclaim pages if out of pages.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Sean&lt;/P&gt;</description>
      <pubDate>Wed, 13 Jul 2022 08:32:16 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1488619#M192461</guid>
      <dc:creator>Sean_Lin_Askey</dc:creator>
      <dc:date>2022-07-13T08:32:16Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1490249#M192591</link>
      <description>&lt;P&gt;Update more information&lt;/P&gt;&lt;P&gt;I tried to dump by&amp;nbsp;cat /proc/pagetypeinfo when testing 1.1Gbps throughput as below&amp;nbsp;&lt;/P&gt;&lt;P&gt;The migrate type of "&lt;STRONG&gt;Unmovable&lt;/STRONG&gt;" looks out of pages.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Free pages count per migrate type at order 0 1 2 3 4 5 6 7 8 9 10 11 12 13&lt;BR /&gt;Node 0, zone DMA, type Unmovable &lt;STRONG&gt;0 0 1 1 1 3 4 1 1 0 0 0 0 0&lt;/STRONG&gt;&lt;BR /&gt;Node 0, zone DMA, type Movable 55 31 7 4 1 1 0 0 1 0 1 1 0 10&lt;BR /&gt;Node 0, zone DMA, type Reclaimable 3 6 0 1 1 1 1 0 1 1 1 1 0 0&lt;BR /&gt;Node 0, zone DMA, type HighAtomic 0 0 0 0 0 0 0 0 0 0 0 0 0 0&lt;BR /&gt;Node 0, zone DMA, type CMA 1 40 1 0 1 0 1 1 1 1 0 1 1 21&lt;BR /&gt;Node 0, zone DMA, type Isolate 0 0 0 0 0 0 0 0 0 0 0 0 0 0&lt;/P&gt;&lt;P&gt;Number of blocks type Unmovable Movable Reclaimable HighAtomic CMA Isolate&lt;BR /&gt;Node 0, zone DMA 112 344 16 0 480 0&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Jul 2022 10:11:19 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1490249#M192591</guid>
      <dc:creator>Sean_Lin_Askey</dc:creator>
      <dc:date>2022-07-15T10:11:19Z</dc:date>
    </item>
    <item>
      <title>Re: Page allocation failure when iperf through 5G module</title>
      <link>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1493359#M192824</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;As previous stated, if you can not allocate GFP_ATOMIC kind memory for their iperf use case. I also try to run this kind use case on MEK board(by only use 2GB memory as customer board) , but can not reproduce issue.&lt;/P&gt;
&lt;P&gt;This issue related to linux kernel common MM sub system code. And I had shared related debug suggestion.&lt;/P&gt;
&lt;P&gt;regards&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jul 2022 13:22:36 GMT</pubDate>
      <guid>https://community.nxp.com/t5/i-MX-Processors/Page-allocation-failure-when-iperf-through-5G-module/m-p/1493359#M192824</guid>
      <dc:creator>Bio_TICFSL</dc:creator>
      <dc:date>2022-07-21T13:22:36Z</dc:date>
    </item>
  </channel>
</rss>

