Hello everyone.
We are experiencing a kernel-level warning that prevents our application from running while using the Hailo accelerator on a Texas Instruments J784S4 EVM.
Observed Behavior:
The Hailo driver appears to initialize successfully (as per
dmesg
logs). However, a kernel warning concerning find_vma then occurs during hailo_vdma_buffer_map
-related operations, causing processing to stop.
This issue happens while running an inference with a custom-developed model via the Hailo SDK.
Environment Information:
Hardware: Texas Instruments J784S4 EVM
OS / Kernel Version: Linux 6.12.35-ti-00948-gce4785d01a0b-dirty #1 (ARM64)
HailoRT Version: 4.23.0
Hailo Device: (Hailo-8)
Relevant Log Snippets (from dmesg):
[ 7.561291] hailo: Init module. driver version 4.23.0
[ 7.600443] hailo 0000:01:00.0: Probing on: 1e60:2864...
[ 7.605887] hailo 0000:01:00.0: Probing: Allocate memory for device extension, 9072
[ 7.613676] hailo 0000:01:00.0: enabling device (0000 - 0002)
[ 7.625027] hailo 0000:01:00.0: Probing: Device enabled
[ 7.638223] hailo 0000:01:00.0: Probing: mapped bar 0 - 00000000d51089ae 16384
[ 7.651048] hailo 0000:01:00.0: Probing: mapped bar 2 - 0000000004b7ff99 4096
[ 7.666931] hailo 0000:01:00.0: Probing: mapped bar 4 - 000000006d82af9d 16384
[ 7.683304] hailo 0000:01:00.0: Probing: Setting max_desc_page_size to 4096, (page_size=4096)
[ 7.695211] hailo 0000:01:00.0: Probing: Enabled 64 bit dma
[ 7.715455] hailo 0000:01:00.0: Probing: Using userspace allocated vdma buffers
[ 7.715470] hailo 0000:01:00.0: Disabling ASPM L0s
[ 7.715483] hailo 0000:01:00.0: Successfully disabled ASPM L0s
[ 7.731108] hailo 0000:01:00.0: Writing file hailo/hailo8_fw.bin
[ 7.806322] hailo 0000:01:00.0: File hailo/hailo8_fw.bin written successfully
[ 7.814106] hailo 0000:01:00.0: Writing file hailo/hailo8_board_cfg.bin
[ 7.814173] hailo 0000:01:00.0: File hailo/hailo8_board_cfg.bin written successfully
[ 7.829141] hailo 0000:01:00.0: Writing file hailo/hailo8_fw_cfg.bin
[ 7.844133] hailo 0000:01:00.0: File hailo/hailo8_fw_cfg.bin written successfully
[ 7.934072] hailo 0000:01:00.0: NNC Firmware loaded successfully
[ 7.949196] hailo 0000:01:00.0: FW loaded, took 218 ms
[ 7.961554] hailo 0000:01:00.0: Probing: Added board 1e60-2864, /dev/hailo0
[ 52.811292] Modules linked in: overlay bluetooth cfg80211 ecdh_generic ecc rfkill snd_usb_audio snd_hwdep uvcvideo snd_usbmidi_lib snd_rawmidi videobuf2_vmalloc uvc onboard_usb_dev rpmsg_ctrl rpmsg_char ti_am335x_adc cdns3 wave5 kfifo_buf cdns_usb_common cdns_pltfrm crct10dif_ce snd_soc_j721e_evm mux_gpio display_connector videobuf2_dma_contig omap_mailbox omap_hwspinlock v4l2_mem2mem phy_can_transceiver videobuf2_v4l2 snd_soc_davinci_mcasp videobuf2_memops ti_k3_r5_remoteproc hailo_pci(O) tidss m_can_platform videobuf2_common cdns_dsi at24 snd_soc_ti_udma m_can cdns_mhdp8546 ti_sn65dsi86 drm_dma_helper snd_soc_pcm3168a_i2c videodev snd_soc_ti_edma snd_soc_pcm3168a ti_am335x_tscadc pvrsrvkm(O) snd_soc_ti_sdma k3_j72xx_bandgap cdns_dphy can_dev drm_display_helper cdns3_ti ti_k3_dsp_remoteproc drm_dp_aux_bus sa2ul drm_kms_helper ti_j721e_ufs ti_k3_common mc rti_wdt cryptodev(O) fuse drm drm_panel_orientation_quirks backlight ipv6
[ 52.923645] lr : hailo_vdma_buffer_map+0x144/0x5c0 [hailo_pci]
[ 53.009536] hailo_vdma_buffer_map+0x144/0x5c0 [hailo_pci]
[ 53.015011] hailo_vdma_buffer_map_ioctl+0xd4/0x338 [hailo_pci]
[ 53.020918] hailo_vdma_ioctl+0xc4/0x248 [hailo_pci]
[ 53.025871] hailo_pcie_fops_unlockedioctl+0x1dc/0x600 [hailo_pci]
Questions:
The logs indicate the driver reporting
Using userspace allocated vdma buffers, followed by the find_vma warning. We suspect an issue with DMA mapping of userspace memory.
Is there a known compatibility issue between the current kernel (
6.12.35-ti-00948-gce4785d01a0b-dirty) and Hailo driver (4.23.0)?