[Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt

2017-07-24 Thread Jim Duffield
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 24 06:15:01  kernel: [508525.301243] [ cut 
here ]
Jul 24 06:15:01  kernel: [508525.301252] WARNING: CPU: 22 
PID: 118193 at /build/linux-0uniEn/linux-4.4.0/net/ipv6/addrconf_core.c:159 
in6_dev_finish_destroy+0x6b/0xc0()
Jul 24 06:15:01  kernel: [508525.301253] Modules linked in: 
veth binfmt_misc xt_nat xt_tcpudp ipt_MASQUERADE nf_nat_masquerade_ipv4 
nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat 
nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 xt_addrtype iptable_filter 
ip_tables xt_conntrack x_tables nf_nat nf_conntrack br_netfilter bridge stp llc 
mpt3sas raid_class scsi_transport_sas mptctl mptbase dell_rbu zram lz4_compress 
zfs(PO) zunicode(PO) zcommon(PO) znvpair(PO) spl(O) zavl(PO) ipmi_ssif 
ipmi_devintf input_leds dcdbas intel_rapl x86_pkg_temp_thermal intel_powerclamp 
coretemp joydev kvm_intel kvm irqbypass sb_edac edac_core mei_me lpc_ich mei 
ipmi_si ipmi_msghandler shpchp 8250_fintek mac_hid acpi_power_meter ib_iser 
rdma_cm iw_cm ib_cm ib_sa ib_mad ib_core ib_addr iscsi_tcp libiscsi_tcp 
libiscsi scsi_transport_iscsi autofs4 xfs btrfs raid10 raid456 
async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq 
libcrc32c raid0 multipath linear raid1 se
 s enclosure crct10dif_pclmul crc32_pclmul ghash_clmulni_intel hid_generic 
usbhid hid mxm_wmi aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper 
cryptd tg3 ptp ahci pps_core libahci megaraid_sas fjes wmi
Jul 24 06:15:01  kernel: [508525.301326] CPU: 22 PID: 118193 
Comm: kworker/u384:0 Tainted: P   O4.4.0-83-generic #106-Ubuntu
Jul 24 06:15:01  kernel: [508525.301327] Hardware name: Dell 
Inc. PowerEdge R430/0CN7X8, BIOS 2.2.5 09/08/2016
Jul 24 06:15:01  kernel: [508525.301332] Workqueue: netns 
cleanup_net
Jul 24 06:15:01  kernel: [508525.301334]  0286 
631d084a 880c7680bba0 813f9513
Jul 24 06:15:01  kernel: [508525.301337]   
81d75940 880c7680bbd8 81081322
Jul 24 06:15:01  kernel: [508525.301339]  881f2bb2fc00 
881f2bb2e000 0006 880c7680bca8
Jul 24 06:15:01  kernel: [508525.301341] Call Trace:
Jul 24 06:15:01  kernel: [508525.301347]  
[] dump_stack+0x63/0x90
Jul 24 06:15:01  kernel: [508525.301352]  
[] warn_slowpath_common+0x82/0xc0
Jul 24 06:15:01  kernel: [508525.301354]  
[] warn_slowpath_null+0x1a/0x20
Jul 24 06:15:01  kernel: [508525.301356]  
[] in6_dev_finish_destroy+0x6b/0xc0
Jul 24 06:15:01  kernel: [508525.301359]  
[] ip6_route_dev_notify+0x116/0x130
Jul 24 06:15:01  kernel: [508525.301363]  
[] notifier_call_chain+0x4a/0x70
Jul 24 06:15:01  kernel: [508525.301365]  
[] raw_notifier_call_chain+0x16/0x20
Jul 24 06:15:01  kernel: [508525.301368]  
[] call_netdevice_notifiers_info+0x35/0x60
Jul 24 06:15:01  kernel: [508525.301371]  
[] netdev_run_todo+0x16d/0x320
Jul 24 06:15:01  kernel: [508525.301374]  
[] rtnl_unlock+0xe/0x10
Jul 24 06:15:01  kernel: [508525.301377]  
[] default_device_exit_batch+0x147/0x170
Jul 24 06:15:01  kernel: [508525.301382]  
[] ? __wake_up_sync+0x20/0x20
Jul 24 06:15:01  kernel: [508525.301384]  
[] ops_exit_list.isra.4+0x52/0x60
Jul 24 06:15:01  kernel: [508525.301386]  
[] cleanup_net+0x1c2/0x2a0
Jul 24 06:15:01  kernel: [508525.301389]  
[] process_one_work+0x165/0x480
Jul 24 06:15:01  kernel: [508525.301392]  
[] worker_thread+0x4b/0x4c0
Jul 24 06:15:01  kernel: [508525.301394]  
[] ? process_one_work+0x480/0x480
Jul 24 06:15:01  kernel: [508525.301396]  
[] kthread+0xe5/0x100
Jul 24 06:15:01  kernel: [508525.301398]  
[] ? kthread_create_on_node+0x1e0/0x1e0
Jul 24 06:15:01  kernel: [508525.301402]  
[] ret_from_fork+0x3f/0x70
Jul 24 06:15:01  kernel: [508525.301403]  
[] ? kthread_create_on_node+0x1e0/0x1e0
Jul 24 06:15:01  kernel: [508525.301405] ---[ end trace 
e4d2860c83257caf ]---

-- 
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt

2017-07-21 Thread Jim Duffield
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-
bin/cvename.cgi?name=2017-1000364

-- 
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt

2017-07-20 Thread John Fanjoy
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 in 4.4.0-79, but perhaps this is related.

-- 
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt

2017-07-08 Thread Joao Luis
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: Fatal exception in interrupt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt

2017-07-08 Thread Joao Luis
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 bug report number, so that I can add an
explanation to what is being reported.

Next time it happens, I will try to follow
https://wiki.ubuntu.com/Kernel/CrashdumpRecipe#Crash_kernel_fails_to_load:_Hang
(but it seems a bit complicated).

(and I will run a memory check first...)

Thank you for the followup.

-- 
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt

2017-07-07 Thread Seth Arnold
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 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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt

2017-07-07 Thread Joao Luis
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 of package
updates).

If you think I may have relevant information, please ask, and I will
upload/post.

-- 
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt

2017-07-06 Thread Khaled Massad
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 bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt

2017-07-06 Thread Khaled Massad
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://bugs.launchpad.net/bugs/1702164

Title:
  Kernel panic - not syncing: Fatal exception in interrupt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt

2017-07-05 Thread Joseph Salisbury
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.net/bugs/1702164

Title:
  Kernel panic - not syncing: Fatal exception in interrupt

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt

2017-07-04 Thread Khaled Massad
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 exception in interrupt
  [231490.197513] Shutting down cpus with NMI
  [231490.210772] Kernel Offset: disabled
  [0.00] Initializing cgroup subsys cpuset
  [0.00] Initializing cgroup subsys cpu
  [0.00] Initializing cgroup subsys cpuacct
  [0.00] Linux version 4.4.0-83-generic (buildd@lgw01-29) (gcc version 
5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.4) ) #106-Ubuntu SMP Mon Jun 26 
17:54:43 UTC 2017 (Ubuntu 4.4.0-83.106-generic 4.4.70)
  [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-4.4.0-83-generic 
root=UUID=e675b47c-3493-4ef8-8b6f-44acb3d1adb9 ro net.ifnames=0 biosdevname=0 
cgroup_enable=memory swapaccount=1 console=tty1 console=ttyS0
  [0.00] KERNEL supported cpus:
  [0.00]   Intel GenuineIntel
  [0.00]   AMD AuthenticAMD
  [0.00]   Centaur CentaurHauls
  [0.00] x86/fpu: xstate_offset[2]:  576, xstate_sizes[2]:  256
  [0.00] x86/fpu: Supporting XSAVE feature 0x01: 'x87 floating point 
registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x02: 'SSE registers'
  [0.00] x86/fpu: Supporting XSAVE feature 0x04: 'AVX registers'
  [0.00] x86/fpu: Enabled xstate features 0x7, context size is 832 
bytes, using 'standard' format.
  [0.00] x86/fpu: Using 'eager' FPU context switches.
  [0.00] e820: BIOS-provided physical RAM map:
  [0.00] BIOS-e820: [mem 0x-0x0009dfff] usable
  [0.00] BIOS-e820: [mem 0x0009e000-0x0009] reserved
  [0.00] BIOS-e820: [mem 0x000e-0x000f] reserved
  [0.00] BIOS-e820: [mem 0x0010-0x7fff] usable
  [0.00] BIOS-e820: [mem 0xfc00-0x] reserved
  [0.00] BIOS-e820: [mem 0x0001-0x00f47fff] usable
  [0.00] NX (Execute Disable) protection: active
  [0.00] SMBIOS 2.4 present.
  [0.00] Hypervisor detected: Xen
  [0.00] Xen version 4.2.
  [0.00] Netfront and the Xen platform PCI driver have been compiled 
for this kernel: unplug emulated NICs.
  [0.00] Blkfront and the Xen platform PCI driver have been compiled 
for this kernel: unplug emulated disks.
  [0.00] You might have to change the root device
  [0.00] from /dev/hd[a-d] to /dev/xvd[a-d]
  [0.00] in your root= kernel command line option
  [0.00] e820: last_pfn = 0xf48 max_arch_pfn = 0x4
  [0.00] x86/PAT: Configuration [0-7]: WB  WC  UC- UC  WB  WC  UC- WT  
  [0.00] e820: last_pfn = 0x8 max_arch_pfn = 0x4
  [0.00] found SMP MP-table at [mem 0x000fbc20-0x000fbc2f] mapped at 
[880fbc20]
  [0.00] Scanning 1 areas for low memory corruption
  [0.00] Using GB pages for direct mapping
  [0.00] RAMDISK: [mem 0x3612a000-0x3708cfff]
  [0.00] ACPI: Early table checksum verification disabled
  [0.00] ACPI: RSDP 0x000EA020 24 (v02 Xen   )
  [0.00] ACPI: XSDT 0xFC014140 5C (v01 XenHVM  
 HVML )
  [0.00] ACPI: FACP 0xFC0131A0 F4 (v04 XenHVM  
 HVML )
  [0.00] ACPI: DSDT 0xFC001CE0 011438 (v02 XenHVM  
 INTL 20090123)
  [0.00] ACPI: FACS 0xFC001CA0 40
  [0.00] ACPI: FACS 0xFC001CA0 40
  [0.00] ACPI: APIC 0xFC0132A0 000460 (v02 XenHVM  
 HVML )
  [0.00] ACPI: SRAT 0xFC013780 0008A8 (v01 XenHVM  
 HVML )
  [0.00] ACPI: HPET 0xFC014050 38 (v01 XenHVM  
 HVML )
  [0.00] ACPI: WAET 0xFC014090 28 (v01 XenHVM  
 HVML )
  [0.00] ACPI: SSDT 0xFC0140C0 31 (v02 XenHVM  
 INTL 20090123)
  [0.00] ACPI: SSDT 0xFC014100 31 (v02 XenHVM  
 INTL 20090123)
+ --- 
+ AlsaDevices:
+  total 0
+  crw-rw 1 root audio 116,  1 Jul  3 08:14 seq
+  crw-rw 1 root audio 116, 33 Jul  3 08:14 timer
+ AplayDevices: Error: [Errno 2] No such file or directory
+ ApportVersion: 2.20.1-0ubuntu2.6
+ Architecture: amd64
+ ArecordDevices: Error: [Errno 2] No such file or directory
+ CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
+ DistroRelease: Ubuntu 16.04
+ Ec2AMI: ami-e28530f4
+ Ec2AMIManifest: (unknown)
+ Ec2AvailabilityZone: us-east-1c
+ Ec2InstanceType: x1.16xlarge
+ Ec2Kernel: unavailable
+ Ec2Ramdisk: unavailable
+ IwConfig: Error: [Errno 2] No such file or 

[Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt

2017-07-04 Thread Khaled Massad
** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 1702164] Re: Kernel panic - not syncing: Fatal exception in interrupt

2017-07-04 Thread Khaled Massad
** 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 notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1702164/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs