Skip to content

Kernel panic (vxlan) #2580

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
brb opened this issue Jun 11, 2018 · 9 comments
Closed

Kernel panic (vxlan) #2580

brb opened this issue Jun 11, 2018 · 9 comments

Comments

@brb
Copy link
Contributor

brb commented Jun 11, 2018

The latest kernel https://github.com/raspberrypi/linux/tree/raspberrypi-kernel_1.20180417-1 used in Raspbian includes coreos/linux@4699beb#diff-4f541554c5f8f378effc907c8f0c9115 which is known to cause a kernel panic due to NULL pointer deref when the vxlan driver is used. The fix is available: torvalds/linux@f15ca72#diff-4f541554c5f8f378effc907c8f0c9115.

More context: weaveworks/weave#3314 and coreos/bugs#2382.

@alexellis
Copy link

Thanks for reporting.. vxlan is also important for Docker Swarm to operate.

@JamesH65
Copy link
Contributor

@pelwell @popcornmix Quick read through the context, seems OK to pull in.

@pelwell
Copy link
Contributor

pelwell commented Jun 26, 2018

As a bug fix, this commit was already included in Linux 4.14.40 so there's no need to cherry-pick.

@pelwell pelwell closed this as completed Jun 26, 2018
@alexellis
Copy link

Will this be in the next Raspbian release or do we need to run rpi-update?

@pelwell
Copy link
Contributor

pelwell commented Jun 26, 2018

It will be in the next Raspbian (the raspberrypi-kernel package may already have been updated - it's worth checking).

@bernhara
Copy link

I checked right now, and the latest raspbian kernel version is 4.14.34-v7+.
I'm afraid that we have still to way for the next release.

@JamesH65
Copy link
Contributor

rpi-update will get you 4.14.50. I think that will be the next one when the repos are updated, next few days I guess.

@KptnKMan
Copy link

KptnKMan commented Jun 28, 2018

Which version is the change included?
I just updated, and saw that 4.14.52-v7+ is pulled.

Edit: Sorry, I somewhow missed the comment by @pelwell
Looks like the update is in 4.14.40

root@raspberrypi:~# rpi-update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** Performing self-update
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 13545  100 13545    0     0  68365      0 --:--:-- --:--:-- --:--:-- 68756
 *** Relaunching after update
 *** Raspberry Pi firmware updater by Hexxeh, enhanced by AndrewS and Dom
 *** We're running for the first time
 *** Backing up files (this will take a few minutes)
 *** Backing up firmware
 *** Backing up modules 4.14.34-v7+
#############################################################
This update bumps to rpi-4.14.y linux tree
Be aware there could be compatibility issues with some drivers
Discussion here:
https://www.raspberrypi.org/forums/viewtopic.php?f=29&t=197689
##############################################################
 *** Downloading specific firmware revision (this will take a few minutes)
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   168    0   168    0     0    278      0 --:--:-- --:--:-- --:--:--   278
100 55.8M  100 55.8M    0     0   657k      0  0:01:27  0:01:27 --:--:-- 1901k
 *** Updating firmware
 *** Updating kernel modules
 *** depmod 4.14.52+
 *** depmod 4.14.52-v7+
 *** Updating VideoCore libraries
 *** Using HardFP libraries
 *** Updating SDK
 *** Running ldconfig
 *** Storing current firmware revision
 *** Deleting downloaded files
 *** Syncing changes to disk
 *** If no errors appeared, your firmware was successfully updated to 963a31330613a38e160dc98b708c662dd32631d5
 *** A reboot is needed to activate the new firmware

@JamesH65
Copy link
Contributor

Doing apt update/upgrade will get you the official 4.14.50 now, so that the best one to use. 52 is pretty bleeding edge.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants