Below is a stack trace from kern.log for one of the hosts. For security
reasons, I have redacted the hostname from the output. Stack traces for
other machines also mention /build/linux-
0uniEn/linux-4.4.0/net/ipv6/addrconf_core.c:160 in6_dev_finish_destroy.
Hopefully, this may prove useful:
Jul
We are experiencing these intermittent kernel panics running a very
similar setup; using Apache Mesos and docker. Due to security reasons,
we are not able to run a previous version kernel due to the fixes
included in 4.4.0-83 to address CVE-2017-1000364.
** CVE added: https://cve.mitre.org/cgi-
b
We are also seeing relatively frequent kernel panics using 4.4.0-83. We
run an Apache Mesos cluster using the docker containerizer. The
description of LP #1687512 appears to match quite nicely with our
configuration (cgroups enabled with small allocations). That issue
appears to have been addressed
Ooops! My first contact with ubuntu-bug was a bit messy. I seem to have
reported #1703091
Sorry for the mess.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702164
Title:
Kernel panic - not syncing
Today, kernel 4.4.0-83 its booting fine (and it doesn't crash/hang on
boot).
(And yesterday, I did many reboots using the laptop power-on button, and
it crashed every time, after the package upgrades).
I run ubuntu-bug and chose "distribution upgrade" category (what else
?), but it gave back no b
Joao, it's probably best to run ubuntu-bug linux to file a new report;
that should automatically attach what it can from the logs. Your photo
may be useful too. (I know it just reports a "warning" but that might be
useful all the same.)
Thanks
--
You received this bug notification because you ar
Sorry if this not the proper way to ask, but I think I may have the same
problem (with a Clevo P150SM laptop), and asked for help on
https://askubuntu.com/questions/933015/ubuntu-16-04-kernel-4-4-0-83
-panic-fatal-exception-in-interrupt
(For me, it started crashing again today after one more set o
sorry:
it's up since 2 days without crashes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702164
Title:
Kernel panic - not syncing: Fatal exception in interrupt
To manage notifications about this
Yes, I restored last kernel on another VM, and it worked fine
But panic just removed after kernel crashed, and server rebooted by itself 3
times.
it's up since 2 days with crash.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:/
Does the panic go away if you boot back into the prior kernel version?
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad
apport information
** Tags added: apport-collected ec2-images
** Description changed:
we updated Kernel of Ubuntu 16.04 from 4.4.0-81-generic to
generic_4.4.0-83.106 we had multiple reboots, and below appeared during
the boot :
[231489.162816] Kernel panic - not syncing: Fatal excepti
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702164
Title:
Kernel panic - not syncing: Fatal exception in interrupt
To manage
** Information type changed from Public to Public Security
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1702164
Title:
Kernel panic - not syncing: Fatal exception in interrupt
To manage notificati
13 matches
Mail list logo