Dear Matan and Leon, I am trying to bring-up a Connect-X 5 Ex Endpoint, using a setup composed by a 32-bit CPU and 512MB of RAM (PCIe Prototyping Platform). The MLX5 Ethernet driver initializes well, but after MLX5 IB driver initiates, it consumes all the available memory in my board (400MB). Does this driver needs more than 400MB to work? Kernel used: Latest 4.12. Kernel log: mlx5_core 0000:01:00.0: enabling device (0000 -> 0002) mlx5_core 0000:01:00.0: Warning: couldn't set 64-bit PCI DMA mask mlx5_core 0000:01:00.0: Warning: couldn't set 64-bit consistent PCI DMA mask mlx5_core 0000:01:00.0: firmware version: 16.19.21102 mlx5_core 0000:01:00.0: mlx5_cmd_init:1765:(pid 1): descriptor at dma 0x9a25a000 mlx5_core 0000:01:00.0: dump_command:726:(pid 5): dump command ENABLE_HCA(0x104) INPUT mlx5_core 0000:01:00.0: cmd_work_handler:829:(pid 5): writing 0x1 to command doorbell mlx5_core 0000:01:00.0: dump_command:726:(pid 5): dump command ENABLE_HCA(0x104) OUTPUT mlx5_core 0000:01:00.0: mlx5_cmd_comp_handler:1418:(pid 5): command completed. ret 0x0, delivery status no errors(0x0) mlx5_core 0000:01:00.0: wait_func:893:(pid 1): err 0, delivery status no errors(0) (...) mlx5_ib: Mellanox Connect-IB Infiniband driver v2.2-1 (Feb 2014) (...) mlx5_core 0000:01:00.0: dump_command:726:(pid 40): dump command QUERY_HCA_VPORT_CONTEXT(0x762) INPUT mlx5_core 0000:01:00.0: cmd_work_handler:829:(pid 40): writing 0x1 to command doorbell mlx5_core 0000:01:00.0: mlx5_eq_int:394:(pid 5): eqn 16, eqe type MLX5_EVENT_TYPE_CMD (...) mlx5_core 0000:01:00.0: mlx5_eq_int:460:(pid 0): page request for func 0x0, npages 4096 mlx5_core 0000:01:00.0: dump_command:726:(pid 40): dump command CREATE_MKEY(0x200) INPUT mlx5_core 0000:01:00.0: cmd_exec:1558:(pid 61): err 0, status 0 mlx5_core 0000:01:00.0: cmd_exec:1558:(pid 61): err 0, status 0 mlx5_core 0000:01:00.0: cmd_exec:1558:(pid 61): err 0, status 0 (...) kworker/u2:3 invoked oom-killer: gfp_mask=0x14200c2(GFP_HIGHUSER), nodemask=(null), order=0, oom_score_adj=0 CPU: 0 PID: 61 Comm: kworker/u2:3 Not tainted 4.12.0-MLNX20170524 #46 Workqueue: mlx5_page_allocator pages_work_handler Stack Trace: arc_unwind_core.constprop.2+0xb4/0x100 dump_header.isra.6+0x82/0x1a8 out_of_memory+0x2fc/0x368 __alloc_pages_nodemask+0x22ee/0x24e4 give_pages+0x1fc/0x664 pages_work_handler+0x2a/0x88 process_one_work+0x1c8/0x390 worker_thread+0x120/0x540 kthread+0x116/0x13c ret_from_fork+0x18/0x1c Mem-Info: active_anon:2083 inactive_anon:7261 isolated_anon:0 active_file:0 inactive_file:0 isolated_file:0 unevictable:0 dirty:0 writeback:0 unstable:0 slab_reclaimable:94 slab_unreclaimable:709 mapped:0 shmem:9344 pagetables:0 bounce:0 free:311 free_pcp:57 free_cma:0 Node 0 active_anon:16664kB inactive_anon:58088kB active_file:0kB inactive_file:0kB unevictable:0kB isolated(anon):0kB isolated(file):0kB mapped:0kB dirty:0kB writeback:0kB shmem:74752kB writeback_tmp:0kB unstable:0kB all_unreclaimable? yes Normal free:2488kB min:2552kB low:3184kB high:3816kB active_anon:16664kB inactive_anon:58088kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:442368kB managed:407104kB mlocked:0kB slab_reclaimable:752kB slab_unreclaimable:5672kB kernel_stack:424kB pagetables:0kB bounce:0kB free_pcp:456kB local_pcp:456kB free_cma:0kB lowmem_reserve[]: 0 0 Normal: 1*8kB (U) 1*16kB (U) 1*32kB (U) 0*64kB 1*128kB (U) 1*256kB (U) 0*512kB 0*1024kB 1*2048kB (U) 0*4096kB 0*8192kB = 2488kB 9344 total pagecache pages 55296 pages RAM 0 pages HighMem/MovableOnly 4408 pages reserved [ pid ] uid tgid total_vm rss nr_ptes nr_pmds swapents oom_score_adj name Kernel panic - not syncing: Out of memory and no killable processes... ---[ end Kernel panic - not syncing: Out of memory and no killable processes... Thank you and best regards, Joao Pinto -- To unsubscribe from this list: send the line "unsubscribe linux-rdma" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html