Comment # 7 on bug 989176 from Michal Kube��ek

(In reply to Axel K��llhofer from comment #6)
> (In reply to Michal Kube��ek from comment #5)
> > When you reproduce the issue, could you try getting the contents of
> > /proc/PID/stack (with "PID" replaced by PID of the stuck iptables or
> > iptables-batch process) few times (5-10) and attach it here
> 
> I hope three times is enough, actually I do not only have to reboot after
> every test, the system also hangs on shut down and I have to do a hard reset.

Sorry for the confusion, I didn't want you to reboot between the attempts,
I meant just getting the stack few times with few seconds betweeen them
to check whether it's stuck somewhere or is actually doing something (even
if too slowly).

Anyway, as the stack seems to look the same all the time, three snapshots
are sufficient.

I can't see the cause from the stack but it's likely to be related to the
bsc#986362 fix. I guess I'll try to reproduce the issue on my test system,
that should make the investigation much easier.