FS#63855 - Kernel panics with 5.3
Attached to Project:
Arch Linux
Opened by persson (persson) - Friday, 20 September 2019, 10:06 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 05 January 2020, 21:04 GMT
Opened by persson (persson) - Friday, 20 September 2019, 10:06 GMT
Last edited by Antonio Rojas (arojas) - Sunday, 05 January 2020, 21:04 GMT
|
Details
Description:
Getting kernel panics with 5.3.0-arch1 when trying to use wireguard (sending traffic via a wg interface) or disabling IPv6 via sysctl (ie sysctl -w net.ipv6.conf.all.disable_ipv6=1). These are the operation that reliably trigger the panic. I get other random panics too, mostly when using the network, but I can't reliably reproduce them; it's almost certainly network-related however. Attached sample kernel panic logs. |
This task depends upon
Closed by Antonio Rojas (arojas)
Sunday, 05 January 2020, 21:04 GMT
Reason for closing: Duplicate
Additional comments about closing: FS#63870
Sunday, 05 January 2020, 21:04 GMT
Reason for closing: Duplicate
Additional comments about closing:
Booting with ipv6.disable=1 seems to fix the problems, but of course it's just a workaround.
- install flex and bison if you don't have them already
- the source tree is different, you have to enter $HOME/build/linux/trunk
- put the patch file into that directory and rename it to end in .patch (eg ipv6.patch)
- edit PKGBUILD to add "ipv6.patch" to the source array, eg
source=(
"$_srcname::git+https://git.archlinux.org/linux.git?signed#tag=v$_srcver"
config # the main kernel config file
60-linux.hook # pacman hook for depmod
90-linux.hook # pacman hook for initramfs regeneration
linux.preset # standard config files for mkinitcpio ramdisk
ipv6.patch # test patch for kernel
)
- edit PKGBUILD to change the base name, eg pkgbase=linux-custom (or whatever you want, as long as it's not "linux")
- run updpkgsums
- import the trusted PGP keys listed in the PKGBUILD (eg gpg --recv-keys 8218F88849AAC522E94CF470A5E9288C4FA415FA)
- run makepkg -s (takes a LONG time). Make sure you see the messages indicating that the patch has been applied, otherwise you'll be building a standard kernel. Example:
-> Applying patch ipv6.patch...
patching file drivers/net/vrf.c
patching file include/net/ip6_route.h
patching file net/ipv6/fib6_rules.c
patching file net/ipv6/ip6_fib.c
patching file net/ipv6/route.c
patching file net/l3mdev/l3mdev.c
- install the kernel and headers packages as explained in the article, eg pacman -U linux-custom-headers-5.3.1.arch1-1-x86_64.pkg.tar.xz linux-custom-5.3.1.arch1-1-x86_64.pkg.tar.xz
- run grub-mkconfig -o /boot/grub/grub.cfg and make sure that your linux-custom kernel is detected and added to grub.cfg. Inspect the generated grub.cfg if needed.
- reboot, uname -a should show thhat you're running the custom kernel (example output: Linux lapt1 5.3.1-arch1-1-custom #2 SMP PREEMPT Mon Sep 23 18:00:03 CEST 2019 x86_64 GNU/Linux)
https://bugs.archlinux.org/task/63870#comment182067 contains another test patch to locate the cause.
General information to include in the report is detailed in [2] if you use the mailing list please CC Wei Wang who authored the causal commit.
[1] https://bugzilla.kernel.org
[2] https://www.kernel.org/doc/html/latest/admin-guide/reporting-bugs.html
Edit:
I had not read https://bugs.archlinux.org/task/63870#comment182069 as zx2c4 is investigating there may be no need to open a separate upstream report.