dmesg.txt (143.7 KB)
You have a lot of i2c and USB timeouts on devices which are set up via the device tree. What is the exact model you are using? It is quite important to know if this is a third party carrier board versus one of the NVIDIA developer kits since this is the main reason for altering a device tree (to describe optional carrier board layout to drivers).
Also, what have you used for flashing?
I am using a custom board and would like to know what affects the kernel panic
You very likely have the wrong device tree (firmware).
You can think of the device tree as passing information to drivers as an argument. A big part of that is for passing physical addresses of hardware which is not plug-n-play. If you set up the pins incorrectly, or route drivers to the wrong location, then there is no predicting what will fail. Unless your custom carrier board is an exact electrical layout match to the dev kit, there is about a 99% chance that the issues are simply caused by passing incorrect information to drivers which are trying to apply to the wrong hardware.
You would need the device tree from the manufacturer of the custom board. Sometimes custom board manufacturers will tell you any of these:
- That their board works with NVIDIA flash software.
- They might provide a patch to NVIDIA flash software (which is basically a device tree).
- They might provide their own rebranded flash software (which is mostly the same as the NVIDIA flash software, except that it has a modified device tree).
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.