Comment 5 for bug 1856163

Confirmed, was able to reproduce this, using the kernel as stated in the bug. This also appears to break the networking after the failure.

transaction with reduced feature level UDP.
Mar 3 02:55:01 s2lp4 CRON[4294]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Mar 3 02:55:20 s2lp4 systemd[1]: Started Session 11 of user ubuntu.
Mar 3 02:56:48 s2lp4 systemd[1]: Started Session 12 of user ubuntu.
Mar 3 02:58:26 s2lp4 kernel: [ 320.392257]
Mar 3 02:58:26 s2lp4 kernel: [ 320.392258] **********************************************************
Mar 3 02:58:26 s2lp4 kernel: [ 320.392259] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
Mar 3 02:58:26 s2lp4 kernel: [ 320.392259] ** **
Mar 3 02:58:26 s2lp4 kernel: [ 320.392260] ** trace_printk() being used. Allocating extra memory. **
Mar 3 02:58:26 s2lp4 kernel: [ 320.392260] ** **
Mar 3 02:58:26 s2lp4 kernel: [ 320.392261] ** This means that this is a DEBUG kernel and it is **
Mar 3 02:58:26 s2lp4 kernel: [ 320.392261] ** unsafe for production use. **
Mar 3 02:58:26 s2lp4 kernel: [ 320.392262] ** **
Mar 3 02:58:26 s2lp4 kernel: [ 320.392263] ** If you see this message and you are not debugging **
Mar 3 02:58:26 s2lp4 kernel: [ 320.392263] ** the kernel, report this immediately to your vendor! **
Mar 3 02:58:26 s2lp4 kernel: [ 320.392264] ** **
Mar 3 02:58:26 s2lp4 kernel: [ 320.392264] ** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
Mar 3 02:58:26 s2lp4 kernel: [ 320.392265] **********************************************************

Mar 3 02:58:37 s2lp4 kernel: [ 330.840545] sshd invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0

Connection to 10.245.80.42 closed by remote host.
Connection to 10.245.80.42 closed.
sfeole@bsg75:~$ ssh ubuntu@10.245.80.42
ssh_exchange_identification: read: Connection reset by peer

4: enP1p0s0d1: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qlen 1000