Help
Invalid job definition:

extra keys not allowed @ data['actions[0]']['deploy']['nbd']['initrd']['allow_modify']

Description
AGL-gerrit-27988-3
Device-type
upsquare
Submitter
agl-jenkins-user
Created
2 years, 3 months ago
Priority
Medium
Visibility
Public
#28674
Incomplete
Device
upsquare-01
Started
2 years, 3 months ago
Duration
9 minutes
Results
  

Job error: Kernel panic - not syncing: Attempted to kill init! exitcode=0x00007f00 [ 64.270791] CPU: 0 PID: 1 Comm: init Not tainted 5.15.59-yocto-standard #1 [ 64.278474] Hardware name: AAEON UP-APL01/UP-APL01, BIOS UPA1AM52 08/04/2020 [ 64.286348] Call Trace: [ 64.289065] <TASK> [ 64.291404] dump_stack_lvl+0x38/0x4d [ 64.295500] dump_stack+0x10/0x16 [ 64.299199] panic+0xf4/0x2a5 [ 64.302514] do_exit.cold+0x15/0xa0 [ 64.306409] do_group_exit+0x3b/0xa0 [ 64.310399] __x64_sys_exit_group+0x18/0x20 [ 64.315069] do_syscall_64+0x43/0x90 [ 64.319063] entry_SYSCALL_64_after_hwframe+0x61/0xcb [ 64.324708] RIP: 0033:0x7f8fe0c9fb81 [ 64.328701] Code: a5 62 11 00 be e7 00 00 00 ba 3c 00 00 00 eb 16 66 0f 1f 84 00 00 00 00 00 89 d0 0f 05 48 3d 00 f0 ff ff 77 1c f4 89 f0 0f 05 <48> 3d 00 f0 ff ff 76 e7 f7 d8 64 41 89 00 eb df 0f 1f 80 00 00 00 [ 64.349683] RSP: 002b:00007fff99fd0e38 EFLAGS: 00000202 ORIG_RAX: 00000000000000e7 [ 64.358142] RAX: ffffffffffffffda RBX: 0000562e39db62a0 RCX: 00007f8fe0c9fb81 [ 64.366112] RDX: 000000000000003c RSI: 00000000000000e7 RDI: 000000000000007f [ 64.374082] RBP: 0000000000000004 R08: ffffffffffffff80 R09: 0000562e39dbb010 [ 64.382043] R10: d6a9d1a94d866b2e R11: 0000000000000202 R12: 0000000000000003 [ 64.390013] R13: 0000562e39d25e00 R14: 0000000000000000 R15: 00007f8fe0edb000 [ 64.397986] </TASK> [ 64.400464] Kernel Offset: 0x30400000 from 0xffffffff81000000 (relocation range: 0xffffffff80000000-0xffffffffbfffffff) [ 64.412518] ---[ end Kernel panic

Top of page

Please read the triage guidelines for help on debugging failures in the test job, test definitions or in individual test cases.

Job Timings

This section helps test writers to check for actions with a duration which is much shorter than the requested timeout. Reducing these timeouts will allow failures to be identified more quickly.

The graph only shows actions that are longer than 1 second. The full list is anyway available in the table.

Loading the data...