Kernel panic - not syncing : Aiee, killing interrupt handler!


I’m trying to make my ap1302 camera work on Jetson Nano 4GB.

When I comment out the following line:
priv->otp_flash_instance = tevi_ap1302_otp_flash_init(priv->tc_dev->client);
if(IS_ERR(priv->otp_flash_instance)) {
err = -EINVAL;
dev_err(dev, “otp flash init failed\n”);
//goto err_reg_probe;

I get kernel panic, as follows:

Kernel panic - not syncing: Aiee, killing interrupt handler!
SMP: stopping secondary CPUs
Kernel Offset: disabled
Memory Limit: none

I’m not gonna use the otp_flash so that’s why I’m trying to comment out that line. The drivers are from the following github page: GitHub - TechNexion-Vision/TEV-Jetson_Camera_driver: TEV series camera drivers for Nvidia Jetson.

I’m suspecting about this line particularly:

bootdata_temp_area = devm_kzalloc(dev,
len_each_time * 4 + 2,

Do you have any idea why this happens ? Appreciate any help.


hello tunakayakaan,

may I know which release you’re using? it looks this driver is implemented based-on l4t-r32.7.1

Oh sorry, I forgot the mention. I’m using l4t-r32.5.1. And you are correct, on their github page its based on l4t-r32.7.1.

hello tunakayakaan,

please moving to the same release version to test the camera functionality.

Assuming you still have an error after switching to the correct kernel version+driver combination, be sure to get a serial console log message during the failure. That serial console runs on a PC and so even error messages can be logged and saved. There’s a good chance that using the right release mix will fix this, but all kernel OOPS and panic will produce a stack dump which is useful in knowing where such an error originates.

I solve the issue via debugging it’s all good now.

For anyone who face with this issue:

priv->header = priv->otp_flash_instance->header_data;

This following line was making problems. I think it returns NULL or similar to that.

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.