CBB error kernel panic still found on JP5.1.1

Robotics & Edge Computing Jetson & Embedded Systems Jetson Xavier NX
,
1

Hi,

CBB error kernel panic still found on JP5.1.1, R35.3.1

▒▒[ 3.050264] CPU:0, Error: cbb-noc@2300000, irq=15
[ 3.090341] **************************************
[ 3.090501] CPU:0, Error:cbb-noc
[ 3.090607] Error Logger : 0
[ 3.090692] ErrLog0 : 0x80030000
[ 3.090796] Transaction Type : RD - Read, Incrementing
[ 3.090942] Error Code : SLV
[ 3.091030] Error Source : Target
[ 3.091121] Error Description : Target error detected by CBB slave
[ 3.091284] AXI2APB_5 bridge error: RDFIFOF - Read Response FIFO Full interrupt
[ 3.091481] Packet header Lock : 0
[ 3.091572] Packet header Len1 : 3
[ 3.091662] NOC protocol version : version >= 2.7
[ 3.091782] ErrLog1 : 0x350e2c
[ 3.091865] ErrLog2 : 0x0
[ 3.091935] RouteId : 0x350e2c
[ 3.092019] InitFlow : ccroc_p2ps/I/ccroc_p2ps
[ 3.092138] Targflow : host1x_p2pm/T/host1x_p2pm
[ 3.092267] TargSubRange : 7
[ 3.092348] SeqId : 0
[ 3.092442] ErrLog3 : 0x101c
[ 3.092521] ErrLog4 : 0x0
[ 3.092606] Address accessed : 0x1520101c
[ 3.092738] ErrLog5 : 0xb09f851
[ 3.092989] Non-Modify : 0x1
[ 3.095456] AXI ID : 0x16
[ 3.098347] Master ID : CCPLEX
[ 3.101672] Security Group(GRPSEC): 0x7e
[ 3.106130] Cache : 0x1 – Bufferable
[ 3.110074] Protection : 0x2 – Unprivileged, Non-Secure, Data Access
[ 3.117156] FALCONSEC : 0x0
[ 3.120305] Virtual Queuing Channel(VQC): 0x0
[ 3.124685] **************************************
[ 3.129965] kernel BUG at drivers/soc/tegra/cbb/tegra194-cbb.c:2057!
[ 3.136061] Internal error: Oops - BUG: 0 [#1] PREEMPT SMP
[ 3.141654] Modules linked in:
[ 3.144633] CPU: 0 PID: 0 Comm: swapper/0 Not tainted 5.10.104-tegra #1
[ 3.151199] Hardware name: NVIDIA Jetson Xavier NX, BIOS 07/17/2023
[ 3.162134] pstate: 60400089 (nZCv daIf +PAN -UAO -TCO BTYPE=–)
[ 3.167746] pc : tegra194_cbb_err_isr+0x19c/0x1b0
[ 3.172461] lr : tegra194_cbb_err_isr+0x11c/0x1b0
[ 3.177443] sp : ffff800010003df0
[ 3.180598] x29: ffff800010003df0 x28: 0000000000000001
[ 3.186368] x27: 0000000000000080 x26: ffffdee115931b08
[ 3.191794] x25: ffffdee11627ae38 x24: 0000000000000001
[ 3.197219] x23: ffffdee115c16000 x22: ffffdee11609e7b0
[ 3.202296] x21: 000000000000000f x20: 0000000000000005
[ 3.207811] x19: ffffdee11609e7a0 x18: 0000000000000010
[ 3.213235] x17: 0000000000006270 x16: 0000000000004350
[ 3.218831] x15: ffffdee115f12bf0 x14: 0720072007200720
[ 3.224343] x13: 0720072007200720 x12: 0720072007200720
[ 3.229856] x11: 0720072007200720 x10: 0720072007200720
[ 3.235116] x9 : 0720072007200720 x8 : 07200720072a072a
[ 3.240623] x7 : 072a072a072a072a x6 : c0000000ffffefff
[ 3.246391] x5 : 0000000000057fa8 x4 : ffffdee115f27968
[ 3.251820] x3 : 00000000ffffffff x2 : ffffdee1143edd60
[ 3.257154] x1 : ffffdee115f12680 x0 : 0000000100010001
[ 3.262236] Call trace:
[ 3.264949] tegra194_cbb_err_isr+0x19c/0x1b0
[ 3.269250] __handle_irq_event_percpu+0x68/0x2a0
[ 3.273781] handle_irq_event_percpu+0x40/0xa0
[ 3.277987] handle_irq_event+0x50/0xf0
[ 3.281750] handle_fasteoi_irq+0xc0/0x170
[ 3.285793] generic_handle_irq+0x40/0x60
[ 3.289798] __handle_domain_irq+0x70/0xd0
[ 3.294001] efi_header_end+0xb0/0xf0
[ 3.297501] el1_irq+0xd0/0x180
[ 3.300478] cpuidle_enter_state+0xb8/0x410
[ 3.304675] cpuidle_enter+0x40/0x60
[ 3.308432] call_cpuidle+0x44/0x80
[ 3.311931] do_idle+0x208/0x270
[ 3.315344] cpu_startup_entry+0x30/0x70
[ 3.319108] rest_init+0xdc/0xe8
[ 3.322089] arch_call_rest_init+0x18/0x20
[ 3.326286] start_kernel+0x514/0x54c
[ 3.329878] Code: a9446bf9 a94573fb a8c67bfd d65f03c0 (d4210000)
[ 3.335842] —[ end trace 024104ac590c1905 ]—
[ 3.340807] Kernel panic - not syncing: Oops - BUG: Fatal exception in interrupt
[ 3.348079] SMP: stopping secondary CPUs
[ 3.351963] Kernel Offset: 0x5ee104230000 from 0xffff800010000000
[ 3.358051] PHYS_OFFSET: 0xfffffd3340000000
[ 3.362162] CPU features: 0x8240002,03802a30
[ 3.366621] Memory Limit: none
[ 3.369779] —[ end Kernel panic - not syncing: Oops - BUG: Fatal exception in interrupt ]—

2

Custom board? devkit?

開機的時候UEFI logo有出現嗎?

多常發生一次?

3

Custom board, hasn’t run test on devkit.
UEFI logo is showed. When it happened, it will reboot triggered by watchdog.

4

Hi,

Yes we know watchdog will happen. Is boot logo a must-have one for your product?

5

If boot logo can be bypass, what’s the workaround? Thanks.

6

Hi,

你可以參考另外兩個head的device tree設定 “bootloader-status = disabled”
這個加上之後boot logo會被關閉
但可以確保這個問題不會發生

7

@WayneWWW Do you have any plan to fix it? in next which release? thanks.

8

This issue won’t really get fixed. We only have several workaround patch to make it won’t easier happened.

9

For example, add this to your display driver code.

diff --git a/drivers/video/tegra/dc/dc.c b/drivers/video/tegra/dc/dc.c
index 1cedba9..86058c2 100644
--- a/drivers/video/tegra/dc/dc.c
+++ b/drivers/video/tegra/dc/dc.c
@@ -6374,6 +6374,10 @@
 		pr_debug("dc->fb_mem not initialized\n");
 		return false;
 	}		
+		return false;
 	return (dc->fb_mem->start != 0);
 }
 EXPORT_SYMBOL(tegra_is_bl_display_initialized);
11

Thanks for your comments, compared to the workaround "“bootloader-status = disabled”, which one has better experience to customer, Thanks.

12

if your customer does not need logo, then disable boot logo can 100% bypass this error.

13

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