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://
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
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 c
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
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
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
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
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 subscrib
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 Ub
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/+attach
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
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.
Someho
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.launch
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 MB
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
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-
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 tes
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 sta
18 matches
Mail list logo
