Comment # 6 on bug 989176 from
First of all, I used 

kernel-default-4.1.28-1.1.gcdbda6b.x86_64

from Kernel:openSUSE-42.1/standard on openSUSE Leap 42.1 x86_64 to reproduce
the issue.

(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.

Here are the respective outputs of cat /proc/$(pidof iptables-batch)/stack
after trying to start SuSEfirewall2:

-----------------------------------------------------------------
[<ffffffff816660d9>] retint_kernel+0x1b/0x1d
[<ffffffff811a7e49>] vmap_page_range_noflush+0x279/0x390
[<ffffffffa0776160>] translate_table+0x720/0x820 [ip_tables]
[<ffffffffa07760fd>] translate_table+0x6bd/0x820 [ip_tables]
[<ffffffff811aa4ad>] vmalloc_node+0x4d/0x60
[<ffffffffa11e55ee>] xt_alloc_table_info+0xde/0x124 [x_tables]
[<ffffffffa11e55bd>] xt_alloc_table_info+0xad/0x124 [x_tables]
[<ffffffffa0776e91>] do_ipt_set_ctl+0x121/0x1df [ip_tables]
[<ffffffff8159b62e>] nf_setsockopt+0x3e/0x60
[<ffffffff815a9fcf>] ip_setsockopt+0x7f/0xa0
[<ffffffff8154c5af>] SyS_setsockopt+0x6f/0xd0
[<ffffffff816654f2>] system_call_fastpath+0x16/0x75
[<ffffffffffffffff>] 0xffffffffffffffff

-----------------------------------------------------------------
[<ffffffff816660d9>] retint_kernel+0x1b/0x1d
[<ffffffff811a7e49>] vmap_page_range_noflush+0x279/0x390
[<ffffffffa067b16c>] translate_table+0x72c/0x820 [ip_tables]
[<ffffffffa067b0fd>] translate_table+0x6bd/0x820 [ip_tables]
[<ffffffff811aa4ad>] vmalloc_node+0x4d/0x60
[<ffffffffa11f85ee>] xt_alloc_table_info+0xde/0x124 [x_tables]
[<ffffffffa11f85bd>] xt_alloc_table_info+0xad/0x124 [x_tables]
[<ffffffffa067be91>] do_ipt_set_ctl+0x121/0x1df [ip_tables]
[<ffffffff8159b62e>] nf_setsockopt+0x3e/0x60
[<ffffffff815a9fcf>] ip_setsockopt+0x7f/0xa0
[<ffffffff8154c5af>] SyS_setsockopt+0x6f/0xd0
[<ffffffff816654f2>] system_call_fastpath+0x16/0x75
[<ffffffffffffffff>] 0xffffffffffffffff

-----------------------------------------------------------------
[<ffffffff816660d9>] retint_kernel+0x1b/0x1d
[<ffffffff811a7e49>] vmap_page_range_noflush+0x279/0x390
[<ffffffffa067b160>] translate_table+0x720/0x820 [ip_tables]
[<ffffffffa067b0fd>] translate_table+0x6bd/0x820 [ip_tables]
[<ffffffff811aa4ad>] vmalloc_node+0x4d/0x60
[<ffffffffa11f85ee>] xt_alloc_table_info+0xde/0x124 [x_tables]
[<ffffffffa11f85bd>] xt_alloc_table_info+0xad/0x124 [x_tables]
[<ffffffffa067be91>] do_ipt_set_ctl+0x121/0x1df [ip_tables]
[<ffffffff8159b62e>] nf_setsockopt+0x3e/0x60
[<ffffffff815a9fcf>] ip_setsockopt+0x7f/0xa0
[<ffffffff8154c5af>] SyS_setsockopt+0x6f/0xd0
[<ffffffff816654f2>] system_call_fastpath+0x16/0x75
[<ffffffffffffffff>] 0xffffffffffffffff


> Also, what does "rpm -q iptables" say?

iptables-1.4.21-4.1.x86_64

AK


You are receiving this mail because: