I ran it while I was "watch 'dmesg | tail'" and caught glimpse of this:
[91476.783713] [<c142fdd0>] ? __netif_receive_skb+0x180/0x4e0 [91476.785510] [<c14301c2>] ? process_backlog+0x92/0x160 [91476.787300] [<c14319bd>] ? net_rx_action+0x10d/0x200 [91476.789093] [<c1056622>] ? __do_softirq+0x82/0x170 [91476.790892] [<c10565a0>] ? __do_softirq+0x0/0x170 [91476.792808] <IRQ> [<c1431d38>] ? netif_rx_ni+0x28/0x30 [91476.794925] [<c13987fd>] ? tun_chr_aio_write+0x23d/0x4b0 [91476.797021] [<c13985c0>] ? tun_chr_aio_write+0x0/0x4b0 [91476.799036] [<c1127676>] ? do_sync_readv_writev+0xa6/0xe0 [91476.800995] [<c11278a0>] ? do_readv_writev+0xa0/0x190
It still panics after I deleted membaloon (and redefined the config) and disabled the KSM. I can only afford to experiment once a day, as I don't want for it to panic during resync for obvious reasons.
I ran it while I was "watch 'dmesg | tail'" and caught glimpse of this:
[91476.783713] [<c142fdd0>] ? __netif_ receive_ skb+0x180/ 0x4e0 backlog+ 0x92/0x160 action+ 0x10d/0x200 0x82/0x170 0x0/0x170 ni+0x28/ 0x30 aio_write+ 0x23d/0x4b0 aio_write+ 0x0/0x4b0 readv_writev+ 0xa6/0xe0 writev+ 0xa0/0x190
[91476.785510] [<c14301c2>] ? process_
[91476.787300] [<c14319bd>] ? net_rx_
[91476.789093] [<c1056622>] ? __do_softirq+
[91476.790892] [<c10565a0>] ? __do_softirq+
[91476.792808] <IRQ> [<c1431d38>] ? netif_rx_
[91476.794925] [<c13987fd>] ? tun_chr_
[91476.797021] [<c13985c0>] ? tun_chr_
[91476.799036] [<c1127676>] ? do_sync_
[91476.800995] [<c11278a0>] ? do_readv_
It still panics after I deleted membaloon (and redefined the config) and disabled the KSM.
I can only afford to experiment once a day, as I don't want for it to panic during resync for obvious reasons.