### Author:  [@Dominik\_Stadler](https://discuss.elastic.co/u/Dominik_Stadler)
#### Post date: [January 24, 2018, 12:33pm UTC](https://discuss.elastic.co/t/kernel-update-on-ubuntu-17-10-causes-elasticsearch-to-panic/116865/1 "2018-01-24T12:33:14Z")
Hi,
anybody else seeing this? When we run Elasticsearch 5.3.3 on Ubuntu 17.10 after the most recent kernel update from 4.13.0-25-generic to 4.13.0-31-generic we see kernel oopses, any remedy except downgrading the kernel?
Thanks... Dominik.
> ProblemType: KernelOops
> Annotation: Your system might become unstable now and might need to be restarted.
> Date: Wed Jan 24 08:00:40 2018
> Failure: oops
> OopsText:
> BUG: unable to handle kernel paging request at 00007facb845b240
> IP: 0x7facb845b240
> PGD 8000000faed9a067
> P4D 8000000faed9a067
> PUD 1027e5d067
> PMD f58bd0067
> PTE f9f146025
>
> Oops: 0011 [#4] SMP PTI
> Modules linked in: rfcomm vmnet(OE) vmw\_vsock\_vmci\_transport vsock vmw\_vmci vmmon(OE) cmac bnep xt\_conntrack ip6table\_filter ip6table\_mangle ip6table\_nat nf\_conntrack\_ipv6 nf\_defrag\_ipv6 nf\_nat\_ipv6 nf\_nat nf\_conntrack libcrc32c ip6\_tables nls\_iso8859\_1 intel\_rapl x86\_pkg\_temp\_thermal intel\_powerclamp coretemp kvm\_intel dell\_wmi kvm sparse\_keymap wmi\_bmof mxm\_wmi irqbypass crct10dif\_pclmul crc32\_pclmul ghash\_clmulni\_intel snd\_hda\_codec\_hdmi pcbc aesni\_intel aes\_x86\_64 crypto\_simd glue\_helper cryptd intel\_cstate arc4 dell\_smm\_hwmon dell\_laptop dell\_smbios dcdbas snd\_hda\_codec\_realtek iwlmvm snd\_usb\_audio snd\_hda\_codec\_generic mac80211 snd\_usbmidi\_lib snd\_seq\_midi snd\_hda\_intel intel\_rapl\_perf snd\_seq\_midi\_event snd\_rawmidi snd\_hda\_codec snd\_hda\_core snd\_hwdep iwlwifi joydev snd\_pcm serio\_raw
> snd\_seq cfg80211 rtsx\_pci\_ms uvcvideo memstick snd\_seq\_device snd\_timer videobuf2\_vmalloc videobuf2\_memops uas videobuf2\_v4l2 input\_leds videobuf2\_core usb\_storage snd videodev btusb mei\_me nvidia\_uvm(POE) hci\_uart btrtl media soundcore mei btbcm serdev btqca btintel bluetooth int3403\_thermal shpchp acpi\_als intel\_pch\_thermal processor\_thermal\_device ecdh\_generic kfifo\_buf intel\_soc\_dts\_iosf int3402\_thermal int3400\_thermal industrialio dell\_smo8800 intel\_lpss\_acpi wmi int340x\_thermal\_zone dell\_rbtn mac\_hid intel\_lpss acpi\_thermal\_rel acpi\_pad parport\_pc ppdev lp parport ip\_tables x\_tables autofs4 hid\_generic usbhid nvidia\_drm(POE) nvidia\_modeset(POE) nvidia(POE) drm\_kms\_helper e1000e syscopyarea sysfillrect sysimgblt ptp fb\_sys\_fops rtsx\_pci\_sdmmc psmouse drm pps\_core ahci rtsx\_pci libahci
> pinctrl\_sunrisepoint i2c\_hid video pinctrl\_intel hid
> CPU: 7 PID: 6033 Comm: java Tainted: P D OE 4.13.0-31-generic #34-Ubuntu
> Hardware name: Dell Inc. Precision 7510/0M1YNP, BIOS 1.14.4 07/28/2017
> task: ffff9b66ef05df00 task.stack: ffffbe428a47c000
> RIP: 0010:0x7facb845b240
> RSP: 0018:ffffbe428a47ff50 EFLAGS: 00010202
> RAX: 00000000000003e7 RBX: 0000000000000000 RCX: 00007facf0ddaa49
> RDX: 00007facf0def996 RSI: 0000000006987877 RDI: 0000000000000000
> RBP: 0000000000000000 R08: 00007face8697730 R09: 000000000000000c
> R10: 00007facb845b240 R11: ffff9b66ef05df00 R12: 0000000000000000
> R13: 0000000000000000 R14: 0000000000000000 R15: 0000000000000000
> FS: 00007facf18e4700(0000) GS:ffff9b683ddc0000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: 00007facb845b240 CR3: 0000000f5c106006 CR4: 00000000003606e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400
> Call Trace:
> ? entry\_SYSCALL\_64\_fastpath+0x33/0xa3
> Code: Bad RIP value.
> RIP: 0x7facb845b240 RSP: ffffbe428a47ff50
> CR2: 00007facb845b240
> ---[end trace 9c824342d17ab268]---
>
> Package: linux-image-4.13.0-31-generic 4.13.0-31.34
> SourcePackage: linux
> Tags: kernel-oops
> Uname: Linux 4.13.0-31-generic x86\_64
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [January 24, 2018, 12:50pm UTC](https://discuss.elastic.co/t/kernel-update-on-ubuntu-17-10-causes-elasticsearch-to-panic/116865/2 "2018-01-24T12:50:48Z")
Same as reported here:
>
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [January 24, 2018, 12:56pm UTC](https://discuss.elastic.co/t/kernel-update-on-ubuntu-17-10-causes-elasticsearch-to-panic/116865/3 "2018-01-24T12:56:23Z")
As reported in this issue:
> Running Linux with last kernel 4.13.0-25-generic and ES works fine again!
---
### Author:  [@Janko](https://discuss.elastic.co/u/Janko)
#### Post date: [January 24, 2018, 2:36pm UTC](https://discuss.elastic.co/t/kernel-update-on-ubuntu-17-10-causes-elasticsearch-to-panic/116865/4 "2018-01-24T14:36:20Z")
Hi Dominik,
If you do not want to downgrade the kernel you will need to upgrade your Elasticsearch installation.
As I understand releases from version 5.6.4 onwards should not be affected.
Best,
Janko
---
### Author:  [@dadoonet](https://discuss.elastic.co/u/dadoonet)
#### Post date: [January 24, 2018, 2:58pm UTC](https://discuss.elastic.co/t/kernel-update-on-ubuntu-17-10-causes-elasticsearch-to-panic/116865/5 "2018-01-24T14:58:44Z")
Thanks for clarifying @Janko I missed that.
---
### Author:  [@Dominik\_Stadler](https://discuss.elastic.co/u/Dominik_Stadler)
#### Post date: [January 24, 2018, 3:01pm UTC](https://discuss.elastic.co/t/kernel-update-on-ubuntu-17-10-causes-elasticsearch-to-panic/116865/6 "2018-01-24T15:01:11Z")
Thanks for the links and suggestions, for us downgrading the kernel on a few affected developer machines is probably easier than upgrading all the elasticsearch installations everywhere.
Is there a list of affected Ubuntu versions? I.e. is it only 17.10 or do you know about other affected releases as well?
We tested 16.04 and it does not seem to be affected.
---
### Author:  [@jasontedor](https://discuss.elastic.co/u/jasontedor)
#### Post date: [January 25, 2018, 3:24am UTC](https://discuss.elastic.co/t/kernel-update-on-ubuntu-17-10-causes-elasticsearch-to-panic/116865/8 "2018-01-25T03:24:30Z")
This is a [kernel bug](https://github.com/elastic/elasticsearch/issues/28349#issuecomment-360233779). Upgrading ES might work around this issue (I have not verified), but this is the wrong solution. My point: the kernel has a bad bug, you should drop it immediately, it can’t be trusted.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [February 22, 2018, 3:24am UTC](https://discuss.elastic.co/t/kernel-update-on-ubuntu-17-10-causes-elasticsearch-to-panic/116865/9 "2018-02-22T03:24:40Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.