Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#43040 - [linux] 3.17.5-1 panic with nf_conntrack
Attached to Project:
Arch Linux
Opened by zless (roentgen) - Sunday, 07 December 2014, 20:33 GMT
Last edited by Evangelos Foutras (foutrelis) - Monday, 08 December 2014, 00:08 GMT
Opened by zless (roentgen) - Sunday, 07 December 2014, 20:33 GMT
Last edited by Evangelos Foutras (foutrelis) - Monday, 08 December 2014, 00:08 GMT
|
DetailsI'm not sure this is a problem with the linux package or with the iptables one. I hope to get some helpful hints here in order to make a bug report at the correct upstream.
The kernel panic is captured in these images https://imgur.com/a/9bJf4 The kernel panic happened twice at the same time with a rapidly connecting/disconnecting tun/tap device. Packages: linux 3.17.5-1 iptables 1.4.21-1 |
This task depends upon
Closed by Evangelos Foutras (foutrelis)
Monday, 08 December 2014, 00:08 GMT
Reason for closing: Fixed
Additional comments about closing: linux 3.17.6-1
Monday, 08 December 2014, 00:08 GMT
Reason for closing: Fixed
Additional comments about closing: linux 3.17.6-1