Hi,
We are in the process of upgrading our device from JetPack 5.0.2 to JetPack 5.1.
We have the code ported to JetPack 5.1. When we boot using JetPack 5.1we are getting an error:
kernel BUG at drivers/soc/tegra/cbb/tegra194-cbb.c:2057!
and the device resets several times until it eventually boots.
We did not encounter this error in JetPack 5.02 and our application code has not changed.
I am looking for guidance on what causes this error so I can determine a solution to this on our device.
Malcolm
Hi,
what steps did you take to upgrade the JetPack version?
Can you give the UART log when it boots up?
Hi,
We checked out the JP5.1 as a new environment and then added our patch to the files in the kernel/ and hardware/ folders.
Attached is the serial log:
[ 7.287567] Extcon DP: HPD disabled
[ 7.287572] hpd: switching from state 0 (Reset) to state 1 (Check Plug)
[ 7.287584] hpd: state 1 (Check Plug), hpd 0, pending_hpd_evt 0
[ 7.292656] usb 1-2: Manufacturer: Microchip
[ 7.297696] hpd: switching from state 1 (Check Plug) to state 3 (Disabled)
[ 7.322288] tegra-se-nvhost 15810000.se: tegra_se_probe: complete
[ 7.328313] tegra_nvdisp_handle_pd_enable: Unpowergated Head0 pd
[ 7.328514] hub 1-2:1.0: USB hub found
[ 7.328604] hub 1-2:1.0: 7 ports detected
[ 7.331678] tegra-se-nvhost 15820000.se: Adding to iommu group 29
[ 7.338595] tegra_nvdisp_handle_pd_enable: Unpowergated Head1 pd
[ 7.342973] usb 2-3: new SuperSpeedPlus Gen 2 USB device number 2 using tegra-xusb
[ 7.345003] tegra-se-nvhost 15820000.se: initialized
[ 7.350362] tegra_nvdisp_handle_pd_enable: Unpowergated Head2 pd
[ 7.355892] tegra-se-nvhost 15820000.se: tegra_se_probe: complete
[ 7.363448] usb 2-3: New USB device found, idVendor=0424, idProduct=7216, bcdDevice= 6.22
[ 7.364902] tegra-se-nvhost 15830000.se: Adding to iommu group 30
[ 7.370609] usb 2-3: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 7.370619] usb 2-3: Product: USB7216 Smart Hub
[ 7.393020] CPU:0, Error: cbb-noc@2300000, irq=15
[ 7.393024] **************************************
[ 7.393026] CPU:0, Error:cbb-noc
[ 7.393030] Error Logger : 0
[ 7.393040] ErrLog0 : 0x80030000
[ 7.393042] Transaction Type : RD - Read, Incrementing
[ 7.393045] Error Code : SLV
[ 7.393047] Error Source : Target
[ 7.393050] Error Description : Target error detected by CBB slave
[ 7.393059] AXI2APB_5 bridge error: RDFIFOF - Read Response FIFO Full interrupt
[ 7.393065] Packet header Lock : 0
[ 7.393067] Packet header Len1 : 3
[ 7.393070] NOC protocol version : version >= 2.7
[ 7.393073] ErrLog1 : 0x350e2c
[ 7.393076] ErrLog2 : 0x0
[ 7.393079] RouteId : 0x350e2c
[ 7.393082] InitFlow : ccroc_p2ps/I/ccroc_p2ps
[ 7.393084] Targflow : host1x_p2pm/T/host1x_p2pm
[ 7.393087] TargSubRange : 7
[ 7.393089] SeqId : 0
[ 7.393093] ErrLog3 : 0x10180
[ 7.393095] ErrLog4 : 0x0
[ 7.393099] Address accessed : 0x15210180
[ 7.393102] ErrLog5 : 0xb09f851
[ 7.393105] Non-Modify : 0x1
[ 7.393108] AXI ID : 0x16
[ 7.393110] Master ID : CCPLEX
[ 7.393114] Security Group(GRPSEC): 0x7e
[ 7.393117] Cache : 0x1 – Bufferable
[ 7.393120] Protection : 0x2 – Unprivileged, Non-Secure, Data Access
[ 7.393123] FALCONSEC : 0x0
[ 7.393126] Virtual Queuing Channel(VQC): 0x0
[ 7.393130] **************************************
[ 7.393169] ------------[ cut here ]------------
[ 7.393172] kernel BUG at drivers/soc/tegra/cbb/tegra194-cbb.c:2057!
[ 7.393178] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
[ 7.393183] Modules linked in:
[ 7.393204] CPU: 0 PID: 123 Comm: kworker/0:3 Not tainted 5.10.104-tegra-pcm-0.0.1 #9
[ 7.393207] Hardware name: NVIDIA Jetson Xavier NX Developer Kit (DT)
[ 7.393224] Workqueue: usb_hub_wq hub_event
Malcolm
Hi,
just to make sure: The device is still able to boot into the system after encountering kernel panic right?
I will check it with our developer.
Yes. The device will boot. On occasion, I have seen it take 3 attempts, but it will boot. Its more likely to happen from a power on then a reboot.
Malcolm
Please upgrade tp jp5.1.1 and also check if this is related to the connection of the monitors.
We cannot upgrade right now.
Yes. There is an LCD connected when this occurs.
Please provide suggestions on how to correct this.
Thanks
Malcolm
You can check rel-35.3.1 dtb and check the “bootloader-status” keyword. Add it to your dtb and try again.