[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-06-14 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-23.25 --- linux (4.15.0-23.25) bionic; urgency=medium * linux: 4.15.0-23.25 -proposed tracker (LP: #1772927) * arm64 SDEI support needs trampoline code for KPTI (LP: #1768630) - arm64: mmu: add the entry trampolines start/end

[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-06-11 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-aws - 4.15.0-1010.10 --- linux-aws (4.15.0-1010.10) bionic; urgency=medium * linux-aws: 4.15.0-1010.10 -proposed tracker (LP: #1772931) * Switch Build-Depends: transfig to fig2dev (LP: #1770770) - [Config] update Build-Depends:

[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-06-11 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-aws - 4.15.0-1010.10 --- linux-aws (4.15.0-1010.10) bionic; urgency=medium * linux-aws: 4.15.0-1010.10 -proposed tracker (LP: #1772931) * Switch Build-Depends: transfig to fig2dev (LP: #1770770) - [Config] update Build-Depends:

[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-06-11 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-23.25 --- linux (4.15.0-23.25) bionic; urgency=medium * linux: 4.15.0-23.25 -proposed tracker (LP: #1772927) * arm64 SDEI support needs trampoline code for KPTI (LP: #1768630) - arm64: mmu: add the entry trampolines start/end

[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-06-11 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.13.0-45.50 --- linux (4.13.0-45.50) artful; urgency=medium * linux: 4.13.0-45.50 -proposed tracker (LP: #1774124) * CVE-2018-3639 (x86) - SAUCE: Set generic SSBD feature for Intel cpus linux (4.13.0-44.49) artful; urgency=medium

[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-05-27 Thread Francis Ginther
** Tags added: id-5afaf1e185d595101750bb7b -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771679 Title: Kernel panic on boot (m1.small in cn-north-1) To manage notifications about this bug go to:

[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-05-25 Thread Kamal Mostafa
Verified fixed in Artful kernel version 4.13.0-44.49-generic (installed on a Xenial m1.small in cn-north-1). ** Tags removed: verification-needed-artful ** Tags added: verification-done-artful -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to

[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-05-24 Thread Brad Figg
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- artful' to 'verification-done-artful'. If the problem still exists, change the tag

[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-05-24 Thread Kamal Mostafa
Verified fixed in Bionic kernel version 4.15.0-23.25-generic (installed on a Xenial m1.small in cn-north-1). ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic ** Changed in: linux-aws (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received

[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-05-24 Thread Kamal Mostafa
Fixed in Bionic linux-aws kernel version 4.15.0-1010.10 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771679 Title: Kernel panic on boot (m1.small in cn-north-1) To manage notifications about

[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-05-24 Thread Brad Figg
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag

[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-05-23 Thread Stefan Bader
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Artful) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Artful) Status: In Progress => Fix

[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-05-17 Thread Kamal Mostafa
** Also affects: linux (Ubuntu Artful) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Artful) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Artful) Status: New => In Progress ** Changed in: linux (Ubuntu Artful) Assignee:

[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-05-17 Thread Kamal Mostafa
This is documented and fixed by mainline commit: commit d1ecfa9d1f402366b1776fbf84e635678a51414f Author: van der Linden, Frank Date: Fri May 4 16:11:00 2018 -0400 x86/xen: Reset VCPU0 info pointer after shared_info remap This patch fixes crashes during boot

[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-05-16 Thread Kamal Mostafa
Some more data points: An m1.small instance running a Xenial AMI (with linux-aws-xenial) works fine in cn-north-1. An m1.small instance running the same kernel works fine in us-west-2. The Xen hypervisor version for m1.small in cn-north-1 differs from us-west-2: us-west-2: [0.00] SMBIOS

[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-05-16 Thread Brad Figg
** Also affects: linux-aws (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771679 Title: Kernel panic on boot (m1.small in cn-north-1) To

[Bug 1771679] Re: Kernel panic on boot (m1.small in cn-north-1)

2018-05-16 Thread Dan Watkins
We've only seen this on m1.small instances, but we haven't tested exhaustively (we do know, though, that m3.large is fine). The command used to create the instance was: aws --profile=china --region=cn-north-1 ec2 run-instances --key- name=Odd_Bloke --image-id=ami-8fcd13e2 --security-groups