Comment 8 for bug 1748513

Hi,

I've encountered very similar issue on one of our GCE boxes with kernel 4.4.0-111-generic

Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.129348] BUG: unable to handle kernel paging request at ffff87ff364673b0
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.136723] IP: [<ffffffff811e0e4d>] kmem_cache_alloc_trace+0x7d/0x220
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.143470] PGD 0
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.145708] Oops: 0000 [#1] SMP
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.149268] Modules linked in: tcp_diag inet_diag xt_comment xt_tcpudp nf_conntrack_ip
v4 nf_defrag_ipv4 xt_conntrack xt_CT nf_conntrack xt_multiport iptable_raw ip6table_filter ip6_tables iptable_filter ip_tables x_table
s dm_crypt ppdev parport_pc parport 8250_fintek pvpanic input_leds i2c_piix4 mac_hid serio_raw crct10dif_pclmul crc32_pclmul ghash_clm
ulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd psmouse virtio_scsi
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.193555] CPU: 2 PID: 27781 Comm: sshd Not tainted 4.4.0-111-generic #134~14.04.1-Ub
untu
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.201928] Hardware name: Google Google Compute Engine/Google Compute Engine, BIOS Go
ogle 01/01/2011
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.211254] task: ffff8800ba585400 ti: ffff8800b9f8c000 task.ti: ffff8800b9f8c000
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.218834] RIP: 0010:[<ffffffff811e0e4d>] [<ffffffff811e0e4d>] kmem_cache_alloc_trac
e+0x7d/0x220
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.228010] RSP: 0018:ffff8800b9f8faf0 EFLAGS: 00010286
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.233419] RAX: 0000000000000000 RBX: 00000000024000c0 RCX: 0000000000079622
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.240653] RDX: 0000000000079621 RSI: 00000000024000c0 RDI: ffff88020c403d00
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.247922] RBP: ffff8800b9f8fb30 R08: 000000000001a580 R09: ffff88020c403d00
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.255153] R10: ffffffff814dfdcc R11: ffffea0000d79200 R12: 00000000024000c0
Feb 27 11:55:10 userverlua-gce-sc-97 kernel: [54055.262386] R13: ffff8800ab077400 R14: ffff87ff364673b0 R15: ffff88020c403d00
Feb 27 14:21:32 userverlua-gce-sc-97 rsyslogd: [origin software="rsyslogd" swVersion="7.4.4" x-pid="1194" x-info="http://www.rsyslog.c
om"] start
Feb 27 14:21:32 userverlua-gce-sc-97 rsyslogd-2307: warning: ~ action is deprecated, consider using the 'stop' statement instead [try
http://www.rsyslog.com/e/2307 ]

There is no stack trace in syslog and no any crash reports in /var/crash&. The issue happened only once on Feb 27 at 11:55 UTC and till Feb 27 14:21 the box was in hanged state totally unresponsive.
So at 14:21 it was cold restarted and after restart the box works fine at the moment.

I'm interested if my issue actually related to this bug. If some one could help with this I will really appreciate.