Hi,
I was having problems with linux-image-2.6.26-1-openvz-amd64 that seem
very similar to this. If I tried starting/rebooting any VE after
creating any NAT iptables rules, I got a NULL pointer dereference
followed by OOPSes just as the VE's network interfaces came up. I've
attached the relevant
Package: linux-image-2.6-openvz-amd64
Severity: normal
Tags: patch
I had Kernel oops every (3) time, when reconfiguring properties of eth3,
mapped
to a container by vzctl --netdev_add. The kernel oops leads to blocking the
entire machine from inputs. In two cases I managed to issue "sync && hal
2 matches
Mail list logo
