Re: [Bug 1737187] Re: Unable to launch AWS M5 instance with newest Ubuntu AMI

[Rasmus Larsen]

No, I believe it's resolved.

On Tue, Jul 30, 2019, 10:31 Po-Hsu Lin  wrote:

> Do you still experiencing this issue?
>
> ** Changed in: linux-aws (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1737187
>
> Title:
>   Unable to launch AWS M5 instance with newest Ubuntu AMI
>
> Status in linux-aws package in Ubuntu:
>   Incomplete
>
> Bug description:
>   When booting Ubuntu Linux 16.04 on an M5.large instance, the instance
>   fails to startup and dies, seemingly during initialization of the NVMe
>   interface, here's the most relevant lines (full kernel log attached):
>
>   [8.840439] Btrfs loaded
>   [   61.888098] clocksource: tsc: mask: 0x max_cycles:
> 0x240939f1bb2, max_idle_ns: 440795263295 ns
>   [   64.807909] nvme :00:04.0: I/O 0 QID 0 timeout, disable controller
>   [   64.916220] nvme :00:04.0: Cancelling I/O 0 QID 0
>   [   64.920779] nvme :00:04.0: Identify Controller failed (-4)
>   [   64.925737] nvme :00:04.0: Removing after probe failure
>   [   64.930506] iounmap: bad address c9e5
>   [   64.934951] CPU: 1 PID: 32 Comm: kworker/1:1 Not tainted
> 4.4.0-1041-aws #50-Ubuntu
>   [   64.942528] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017
>   [   64.947684] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
>   [   64.952688]  0286 fd001be315a343d4 8800bbb4bcd8
> 813f7743
>   [   64.960923]  880036c6d4f0 c9e5 8800bbb4bcf8
> 8106ae7f
>   [   64.969368]  880036c6d4f0 880036c6d658 8800bbb4bd08
> 8106aebc
>   [   64.977878] Call Trace:
>   [   64.981322]  [] dump_stack+0x63/0x90
>   [   64.985878]  [] iounmap.part.1+0x7f/0x90
>   [   64.990583]  [] iounmap+0x2c/0x30
>   [   64.994873]  [] nvme_dev_unmap.isra.35+0x1a/0x30
> [nvme]
>   [   65.71]  [] nvme_remove+0xce/0xe0 [nvme]
>   [   65.005125]  [] pci_device_remove+0x39/0xc0
>   [   65.009912]  [] __device_release_driver+0xa1/0x150
>   [   65.015009]  [] device_release_driver+0x23/0x30
>   [   65.020019]  [] pci_stop_bus_device+0x8a/0xa0
>   [   65.024806]  []
> pci_stop_and_remove_bus_device_locked+0x1a/0x30
>   [   65.032326]  []
> nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme]
>   [   65.037731]  [] process_one_work+0x165/0x480
>   [   65.042482]  [] worker_thread+0x4b/0x4c0
>   [   65.046978]  [] ? process_one_work+0x480/0x480
>   [   65.051905]  [] kthread+0xe5/0x100
>   [   65.056224]  [] ? kthread_create_on_node+0x1e0/0x1e0
>   [   65.061380]  [] ret_from_fork+0x3f/0x70
>   [   65.066103]  [] ? kthread_create_on_node+0x1e0/0x1e0
>   [   65.071235] Trying to free nonexistent resource
> 
>   [  125.080477] random: nonblocking pool is initialized
>   (...End of output...)
>
>   Relevant data:
>   AMI id: ami-8fd760f6 (Should be the latest official release)
>   Instance type: m5.large
>   Region: eu-west-1
>
>   Issue seems completely repeatable.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1737187/+subscriptions
>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737187

Title:
  Unable to launch AWS M5 instance with newest Ubuntu AMI

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

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

[Bug 1737187] [NEW] Unable to launch AWS M5 instance with newest Ubuntu AMI

[Rasmus Larsen]

Public bug reported:

When booting Ubuntu Linux 16.04 on an M5.large instance, the instance
fails to startup and dies, seemingly during initialization of the NVMe
interface, here's the most relevant lines (full kernel log attached):

[8.840439] Btrfs loaded
[   61.888098] clocksource: tsc: mask: 0x max_cycles: 
0x240939f1bb2, max_idle_ns: 440795263295 ns
[   64.807909] nvme :00:04.0: I/O 0 QID 0 timeout, disable controller
[   64.916220] nvme :00:04.0: Cancelling I/O 0 QID 0
[   64.920779] nvme :00:04.0: Identify Controller failed (-4)
[   64.925737] nvme :00:04.0: Removing after probe failure
[   64.930506] iounmap: bad address c9e5
[   64.934951] CPU: 1 PID: 32 Comm: kworker/1:1 Not tainted 4.4.0-1041-aws 
#50-Ubuntu
[   64.942528] Hardware name: Amazon EC2 m5.large/, BIOS 1.0 10/16/2017
[   64.947684] Workqueue: events nvme_remove_dead_ctrl_work [nvme]
[   64.952688]  0286 fd001be315a343d4 8800bbb4bcd8 
813f7743
[   64.960923]  880036c6d4f0 c9e5 8800bbb4bcf8 
8106ae7f
[   64.969368]  880036c6d4f0 880036c6d658 8800bbb4bd08 
8106aebc
[   64.977878] Call Trace:
[   64.981322]  [] dump_stack+0x63/0x90
[   64.985878]  [] iounmap.part.1+0x7f/0x90
[   64.990583]  [] iounmap+0x2c/0x30
[   64.994873]  [] nvme_dev_unmap.isra.35+0x1a/0x30 [nvme]
[   65.71]  [] nvme_remove+0xce/0xe0 [nvme]
[   65.005125]  [] pci_device_remove+0x39/0xc0
[   65.009912]  [] __device_release_driver+0xa1/0x150
[   65.015009]  [] device_release_driver+0x23/0x30
[   65.020019]  [] pci_stop_bus_device+0x8a/0xa0
[   65.024806]  [] 
pci_stop_and_remove_bus_device_locked+0x1a/0x30
[   65.032326]  [] nvme_remove_dead_ctrl_work+0x3c/0x50 [nvme]
[   65.037731]  [] process_one_work+0x165/0x480
[   65.042482]  [] worker_thread+0x4b/0x4c0
[   65.046978]  [] ? process_one_work+0x480/0x480
[   65.051905]  [] kthread+0xe5/0x100
[   65.056224]  [] ? kthread_create_on_node+0x1e0/0x1e0
[   65.061380]  [] ret_from_fork+0x3f/0x70
[   65.066103]  [] ? kthread_create_on_node+0x1e0/0x1e0
[   65.071235] Trying to free nonexistent resource 

[  125.080477] random: nonblocking pool is initialized
(...End of output...)

Relevant data:
AMI id: ami-8fd760f6 (Should be the latest official release)
Instance type: m5.large
Region: eu-west-1

Issue seems completely repeatable.

** Affects: linux-aws (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "kernel.log"
   https://bugs.launchpad.net/bugs/1737187/+attachment/5020190/+files/kernel.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1737187

Title:
  Unable to launch AWS M5 instance with newest Ubuntu AMI

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

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

[Bug 1666260] Re: "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

[Rasmus Larsen]

I have only been able to reproduce this on our production workloads, and
we've recently downgraded from HWE (4.8.0-X) to GA (4.4.0-66), where we
currently aren't seeing any issues.

If I see the issue reappear, I'll try to verify it with a mainline
kernel, if someone finds a way to reproduce this consistently, I'll
happily help bisect this.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666260

Title:
  "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

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

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

[Bug 1666260] Re: "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

[Rasmus Larsen]

I can confirm hitting this on 4.8.41 as well.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1666260

Title:
  "Out of memory" errors after upgrade to 4.4.0-59 + 4.8.0-34

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

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

[Bug 1518457] Re: kswapd0 100% CPU usage

[Rasmus Larsen]

I had this issue too on AWS.

In my case, it was the udev rule for vm-hotadd and the fix as mentioned
previously basically came down to "touch /etc/udev/rules.d/40-vm-
hotadd.rules" which effectively disables the /lib/udev/rules.d/40-vm-
hotadd.rules file (after a reboot).

The udev rule basically seems to only be active for Xen or Hyper-V and
while it seems the Hyper-V stuff was also present in previous versions,
the Xen stuff seems to be introduced in 15.10 or newer.

So if you're seeing this issue on anything running on Xen, including
AWS, try:

touch /etc/udev/rules.d/40-vm-hotadd.rules
reboot

This is probably a bug in Xen or a bug in the kernel.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1518457

Title:
  kswapd0 100% CPU usage

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

I've verified that the linux-image-4.4.0-23-generic image in xenial-proposed 
boots correctly on a c3.large ec2 instance.
uname -v: #41-Ubuntu SMP Mon May 16 23:04:25 UTC 2016

root@ip-10-33-53-135:~# apt-cache showpkg linux-image-4.4.0-23-generic
Package: linux-image-4.4.0-23-generic
Versions:
4.4.0-23.41 
(/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-proposed_main_binary-amd64_Packages)
 Description Language:
 File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-proposed_main_binary-amd64_Packages
  MD5: 301993998617cbcae03feb3fe5d3aa55
 Description Language: en
 File: 
/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_xenial-proposed_main_i18n_Translation-en
  MD5: 301993998617cbcae03feb3fe5d3aa55


** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573231

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

Well, they're probably waiting for the patch to hit the LTS kernel 4.4
branch, which will probably happen on the 18th May... Or something like
that.

But you can easily run it until then...

Use the 16.04 Beta 2 AMIs, but just disable kernel updates (say, with
"apt-mark hold") and update everything else. That will basically give
you all the final stuff, just without the last few kernel updates,
including the one that broke most EC2 instances.

When a working kernel gets here, just apt-mark unhold and you should be
good.

You might want to temporarily disable automatic security updates until
then if you do it though...

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573231

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

Here you go, cpuid -1 -r output.

** Attachment added: "cpuid -1 -r output c3.large instances"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573231/+attachment/4657733/+files/cpuid_raw.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573231

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

CPUID output posted before was truncated...

** Attachment added: "Full CPUID output"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573231/+attachment/4657525/+files/cpuid_full.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573231

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

Kernel boots correctly on a c3.large with Thomas patch.

I've attached the output of the cpuid command (apt-get install cpuid) on
the instance, in case it has any interest.

** Attachment added: "cpuid command output c3.large"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573231/+attachment/4657524/+files/cpuid.txt

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573231

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

I can confirm that I can boot with this kernel on a C3.large instance.

If anyone else wants to verify this, the procedure is to boot one of the
failing instances with the Beta 2 AMIs and install the build (and
reboot).

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573231

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

I get the same issue with the build, which seemed weird so I retested and it 
looks like I must have mislabeled one of my builds, because now when I build 
31c2013e4ea2e594522980acc3d20e88664b19f1, I still get the issue, but if I go 
back to a6ebb4464659d35e0516900a8493f9720dd77d67 it works.
Somehow I must have swapped some builds...

a6ebb4464659d35e0516900a8493f9720dd77d67 Good
31c2013e4ea2e594522980acc3d20e88664b19f1   Bad
8ae10f463b7ae3455e9d0507176349c76580995f   Bad

Really sorry about the detour Joseph.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573231

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

Verified it on multiple instances.

31c2013e4ea2e594522980acc3d20e88664b19f1 is the last good commit.
8ae10f463b7ae3455e9d0507176349c76580995f is the first bad commit.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573231

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

According to my bisect this commit is responsible:

commit 8ae10f463b7ae3455e9d0507176349c76580995f
Author: Vikas Shivappa 
Date:   Thu Mar 10 15:32:09 2016 -0800

perf/x86/mbm: Add Intel Memory B/W Monitoring enumeration and init

BugLink: http://bugs.launchpad.net/bugs/1397880

The MBM init patch enumerates the Intel MBM (Memory b/w monitoring)
and initializes the perf events and datastructures for monitoring the
memory b/w.

Its based on original patch series by Tony Luck and Kanaka Juvva.

Memory bandwidth monitoring (MBM) provides OS/VMM a way to monitor
bandwidth from one level of cache to another. The current patches
support L3 external bandwidth monitoring. It supports both 'local
bandwidth' and 'total bandwidth' monitoring for the socket. Local
bandwidth measures the amount of data sent through the memory controller
on the socket and total b/w measures the total system bandwidth.

Extending the cache quality of service monitoring (CQM) we add two
more events to the perf infrastructure:

  intel_cqm_llc/local_bytes - bytes sent through local socket memory 
controller
  intel_cqm_llc/total_bytes - total L3 external bytes sent

The tasks are associated with a Resouce Monitoring ID (RMID) just like
in CQM and OS uses a MSR write to indicate the RMID of the task during
scheduling.

Signed-off-by: Vikas Shivappa 
Signed-off-by: Peter Zijlstra (Intel) 
Reviewed-by: Tony Luck 
Acked-by: Thomas Gleixner 
Cc: Alexander Shishkin 
Cc: Andy Lutomirski 
Cc: Arnaldo Carvalho de Melo 
Cc: Borislav Petkov 
Cc: Brian Gerst 
Cc: David Ahern 
Cc: Denys Vlasenko 
Cc: H. Peter Anvin 
Cc: Jiri Olsa 
Cc: Linus Torvalds 
Cc: Matt Fleming 
Cc: Namhyung Kim 
Cc: Peter Zijlstra 
Cc: Stephane Eranian 
Cc: Vince Weaver 
Cc: fenghua...@intel.com
Cc: h.peter.an...@intel.com
Cc: ravi.v.shan...@intel.com
Cc: vikas.shiva...@intel.com
Link: 
http://lkml.kernel.org/r/1457652732-4499-4-git-send-email-vikas.shiva...@linux.intel.com
Signed-off-by: Ingo Molnar 
(back ported from commit 33c3cc7acfd95968d74247f1a4e1b0727a07ed43)
Signed-off-by: Tim Gardner 

 Conflicts:
arch/x86/kernel/cpu/common.c

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573231

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

Bisecting...

Current candidate seems to be 31c2013e4ea2e594522980acc3d20e88664b19f1

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573231

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

I can still reproduce this in 4.6-rc5. See attached boot log.

I might do a bisect on this if I find the time...

** Attachment added: "kernel4.6-rc5.log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573231/+attachment/4650339/+files/kernel4.6-rc5.log

** Tags added: kernel-bug-exists-upstream

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573231

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

I've tested with some instance types with the ami-3079f543 image (eg.
ubuntu 16.04 final with Ubuntu 4.4.0-21.37-generic 4.4.6)

The following instance types fail to start with a kernel panic:

r3.large
c3.large

The following instance types seem to work:

t2.micro
c4.large
m3.medium

I haven't tested with all sizes, but I suspect all t2, c4 and m3
instances are good.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573231

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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

[Bug 1573231] Re: Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-release-upgrade -d

[Rasmus Larsen]

Currently also encountering this issue (the same kernel panic) with ami-
3079f543 on eu-west-1 with a c3.large instance.

So this seems to be a general ubuntu 16.04 on AWS issue and not an
upgrade specific issue. I haven't seen this issue with the beta2 AMIs.

Interestingly I seem to be able to start the AMI on t2.micro instances,
so this could well be instance type specific.

** Attachment added: "AWS Kernel panic log"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1573231/+attachment/4648152/+files/aws.log

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1573231

Title:
  Kernel Panic on EC2 After Upgrading from 14.04 to 16.04 via do-
  release-upgrade -d

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

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