[Bug 236989] AWS EC2 lockups "Missing interrupt"
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Thu May 7 12:00:44 UTC 2020
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=236989
--- Comment #21 from Charles O'Donnell <cao at bus.net> ---
Colin,
At this point we are at 10 days uptime. Below are select excerpts from vmstat
logging. It appears to follow the path you predicted. I can attach the full
hourly log if it is of interest.
Best.
DAY 8 (first uptick of
===> Tue May 5 17:00:00 EDT 2020
mbuf_jumbo_page: 4096, 490945, 0, 31,40308027, 0, 0
mbuf_jumbo_9k: 9216, 145465, 7668, 286,58743917, 7, 0
mbuf_jumbo_16k: 16384, 81824, 0, 0, 0, 0, 0
dev.ena.0.queue7.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue6.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue5.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue4.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue3.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue2.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue1.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue0.rx_ring.mjum_alloc_fail: 0
DAY 9
===> Wed May 6 04:00:00 EDT 2020
mbuf_jumbo_page: 4096, 490945, 97, 446,41133523, 0, 0
mbuf_jumbo_9k: 9216, 145465, 7645, 412,59865306, 9, 0
mbuf_jumbo_16k: 16384, 81824, 0, 0, 0, 0, 0
dev.ena.0.queue7.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue6.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue5.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue4.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue3.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue2.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue1.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue0.rx_ring.mjum_alloc_fail: 0
===> Wed May 6 05:00:00 EDT 2020
mbuf_jumbo_page: 4096, 490945, 367, 449,41875931, 0, 0
mbuf_jumbo_9k: 9216, 145465, 7253, 108,60877108, 241, 0
mbuf_jumbo_16k: 16384, 81824, 0, 0, 0, 0, 0
dev.ena.0.queue7.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue6.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue5.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue4.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue3.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue2.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue1.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue0.rx_ring.mjum_alloc_fail: 0
===> Wed May 6 06:00:00 EDT 2020
mbuf_jumbo_page: 4096, 490945, 34, 41,42115282, 0, 0
mbuf_jumbo_9k: 9216, 145465, 7719, 267,61217632, 243, 0
mbuf_jumbo_16k: 16384, 81824, 0, 0, 0, 0, 0
dev.ena.0.queue7.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue6.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue5.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue4.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue3.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue2.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue1.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue0.rx_ring.mjum_alloc_fail: 0
DAY 10
===> Thu May 7 07:00:00 EDT 2020
mbuf_jumbo_page: 4096, 490945, 0, 65,45067065, 0, 0
mbuf_jumbo_9k: 9216, 145465, 7647, 322,65796230,1640, 0
mbuf_jumbo_16k: 16384, 81824, 0, 0, 0, 0, 0
dev.ena.0.queue7.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue6.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue5.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue4.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue3.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue2.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue1.rx_ring.mjum_alloc_fail: 0
dev.ena.0.queue0.rx_ring.mjum_alloc_fail: 0
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-virtualization
mailing list