Comment 5 for bug 1341195

On 07/16/2014 06:35 PM, Serge Hallyn wrote:

> To be clear, you have not yet gotten the bug since you've set
> KSM_ENABLED to 0, or have you?

I just did it, so no, not yet.

This happened by time:

Saucy (everything is fine) -> Trusty (issue happened) -> Trusty with
Saucy kernel 3 weeks ago (no issue) -> today with 3 weeks uptime (issue
happened) -> KSM_ENABLED=0 + reboot with Trusty kernel -> now

I just want to be clear, that both of us understand the same on this.

> Interesting about the saucy kernel. Ideally we could reproduce this
> reliably enough to really bisect.
>
> I wonder if we can reproduce without qemu.

I have a some other servers with LXC with no issue, If there is KVM,
then issue happens.
Does it really not show up anywhere else?

sysctl.conf:

kernel.printk = 3 4 1 3
net.ipv4.conf.default.rp_filter=1
net.ipv4.conf.all.rp_filter=1
net.ipv4.tcp_syncookies=1
net.ipv4.conf.all.secure_redirects = 1
net.ipv4.conf.all.send_redirects = 0
net.ipv4.conf.all.accept_source_route = 0
net.ipv6.conf.all.accept_source_route = 0
kernel.shmmax=335544320000
net.ipv4.tcp_rmem = 4096 16777216 33554432
net.ipv4.tcp_wmem = 4096 16777216 33554432
net.ipv4.tcp_mem = 4096 16777216 33554432
net.core.rmem_default = 16777216
net.core.wmem_default = 16777216
net.core.rmem_max = 16777216
net.core.wmem_max = 16777216
net.core.netdev_max_backlog = 30000
net.core.netdev_max_backlog = 30000
net.ipv6.neigh.default.gc_thresh1 = 512
net.ipv6.neigh.default.gc_thresh2 = 2048
net.ipv6.neigh.default.gc_thresh3 = 4096
vm.swappiness = 1

fs.inotify.max_user_watches = 81920
fs.inotify.max_user_instances = 1024

May that be important?

tamas