There was a power cycle during the upgrade.

We got following trace during kernel panic.

Cannot login after software upgrade – system initializing message on Portal; on cli login prompt is seen following messages:

System crashing due to
[ 8780.678167] Hardware name: Cisco Systems, Inc. ENCS5412/K9/ENCS5412/K9, BIOS ENCS54_2.7.020620190951 02/06/2019
[ 8780.800565] Workqueue: events flush_to_ldisc
[ 8780.853390] task: ffff9707f4bf30c0 ti: ffff9707f4448000 task.ti: ffff9707f4448000
[ 8780.944588] RIP: 0010:[<ffffffff83874b73>] [<ffffffff83874b73>] uart_write_room+0x13/0x50
[ 8781.045274] RSP: 0018:ffff9707f444bc60 EFLAGS: 00010286
[ 8781.110468] RAX: 0000000000000800 RBX: 000000000000000a RCX: ffff9707f444bfd8
[ 8781.197509] RDX: ffffffff83874b60 RSI: ffff970ed8206c00 RDI: ffff970ed8205000
[ 8781.284540] RBP: ffff9707f444bc70 R08: ffff970ec1e6ec00 R09: a3c427ffdbc3c000
[ 8781.371561] R10: a3c427ffdbc3c000 R11: 0000000000000001 R12: 0000000000000000
[ 8781.458579] R13: ffff970ed8205000 R14: ffff970ed8206c00 R15: ffff970ec1e6ecf6
[ 8781.545589] FS: 0000000000000000(0000) GS:ffff970edf000000(0000) knlGS:0000000000000000
[ 8781.644060] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 8781.714429] CR2: 0000000000000150 CR3: 000000085b2be000 CR4: 00000000003607f0
[ 8781.801442] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 8781.888437] DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
[ 8781.975407] Call Trace:
[ 8782.006205] [<ffffffff8385c730>] tty_write_room+0x20/0x30
[ 8782.073406] [<ffffffff8385966e>] process_echoes+0x6e/0x2e0
[ 8782.141642] [<ffffffff83b65e92>] ? mutex_lock+0x12/0x2f
[ 8782.206744] [<ffffffff8385c14c>] n_tty_receive_char+0xd4c/0xe30
[ 8782.280188] [<ffffffff8385c3dc>] n_tty_receive_buf+0x1ac/0x470
[ 8782.352569] [<ffffffff8385f1ff>] flush_to_ldisc+0x10f/0x160
[ 8782.421832] [<ffffffff834b9d4f>] process_one_work+0x17f/0x440
[ 8782.493188] [<ffffffff834bade6>] worker_thread+0x126/0x3c0
[ 8782.561412] [<ffffffff834bacc0>] ? manage_workers.isra.25+0x2a0/0x2a0
[ 8782.641074] [<ffffffff834c1c31>] kthread+0xd1/0xe0
[ 8782.700887] [<ffffffff834c1b60>] ? insert_kthread_work+0x40/0x40
[ 8782.775363] [<ffffffff83b74c37>] ret_from_fork_nospec_begin+0x21/0x21
[ 8782.855038] [<ffffffff834c1b60>] ? insert_kthread_work+0x40/0x40
[ 8782.929516] Code: 01 00 00 81 e3 ff 0f 00 00 e8 0a 56 2f 00 89 d8 5b 41 5c 5d c3 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 41 54 53 4c 8b a7 18 02 00 00 <49> 8b bc 24 50 01 00 00 e8 50 59 2f 00 41 8b 9c 24 48 01 00 00
[ 8783.165634] RIP [<ffffffff83874b73>] uart_write_room+0x13/0x50
[ 8783.238184] RSP <ffff9707f444bc60>
[ 8783.281471] CR2: 0000000000000150

While going through the list of cases on centos, we found this similar case - https://bugs.centos.org/view.php?id=14265#history. However, there has been no activity on it since long.

Can you please help us out to find out if there is an ongoing fix for it?