This bug was fixed in the package linux - 4.4.0-24.43
---
linux (4.4.0-24.43) xenial; urgency=low
[ Kamal Mostafa ]
* CVE-2016-1583 (LP: #1588871)
- ecryptfs: fix handling of directory opening
- SAUCE: proc: prevent stacking filesystems on top
- SAUCE: ecryptfs: forbi
it seems the fix is in proposed according to this page:
https://launchpad.net/ubuntu/+source/linux. But when I enable the
proposed repository the version there is old, so the version on that
page must just be the source version, but the package hasn't actually
been put in the repo?
Clearly I don't
The Ubuntu 14.04 cloud images remain broken on m3.large and c3.large. Is
there a way to expedite building them with the fix? It seems that the
Ubuntu release process is broken, if bugs like this make it into the LTS
images and then don't get a clear timeline or priority for getting
fixed.
--
You
Travis, the urgency= field is completely ignored in all Ubuntu tooling.
--
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-
the kernel version this is fixed in is proposed, but has urgency=low,
which seems contradictory to the "critical" importance of this bug. Not
sure if that should be changed / how that would be changed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscri
Any update on when this is going to get released for 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-up
** Tags added: jalapeno
--
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 abo
This bug was fixed in the package linux - 4.4.0-23.41
---
linux (4.4.0-23.41) xenial; urgency=low
[ Kamal Mostafa ]
* Release Tracking Bug
- LP: #1582431
* zfs: disable module checks for zfs when cross-compiling (LP: #1581127)
- [Packaging] disable zfs module checks wh
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
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-
xenial' to 'verification-done-xenial'.
If verification is not done by 5 working days from t
Hello,
I'm getting kernel panic on m3.large with these AMI:
- ubuntu/images/hvm-ssd/ubuntu-xenial-16.04-amd64-server-20160420.3
(ami-840910ee)
- ubuntu/images/hvm-ssd/ubuntu-xenial-16.04-amd64-server-20160516.1
(ami-13be557e)
"Kernel panic - not syncing: Attempted to kill init!
exitcode=0x
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
Hi — any idea when the AMIs will be updated?
Xenial can't be launched on half of AWS instances so far. :(
--
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 Upgr
** Changed in: linux (Ubuntu Xenial)
Status: In Progress => Fix Committed
** Changed in: linux (Ubuntu Yakkety)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.
** Changed in: linux (Ubuntu Xenial)
Importance: High => Critical
** Changed in: linux (Ubuntu Yakkety)
Importance: High => Critical
--
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:
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 built a test kernel with the patch suggested by Thomas Gleixner. The
test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1573231/
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because you are a member of Ubuntu
Bugs, wh
@Joe, based upon the identified commit, I wonder if it would be worth
testing backports of follow-on fixes specifically for that commit?
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=b5d5f27d938fb6fc8d3202704e699d2694a02da6
http://git.kernel.org/cgit/linux/kernel/git/to
Err, apologies Joe, it does seem like upon more careful reading of the
bug report, the second mentioned commit (comment #18) specifically
introduced the regression? That seems unlikely at best given it's
contents, rights? That is, if the divisor was zero after that commit, it
was zero before it, to
comment #16 is the message I sent to 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 m
Hi Thomas,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit 1f12e32f4cd5243ae46d8b933181be0d022c6793
Author: Thomas Gleixner
Date: Mon Feb 22 22:19:15 2016 +
x86/topology: Create logic
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 built a test kernel with a revert of 1f12e32f4. To revert this commit,
I also had to revert e7ee3e8, 2d4de83, 87f01cc and 33c3cc7
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1573231/
Can you test this kernel and see if it resolves this bug?
--
You received t
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
I built a test kernel with a revert of 33c3cc7(8ae10f463 in Xenial). To
revert this commit, I also had to revert e7ee3e8, 2d4de83 and 87f01cc.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1573231/
Can you test this kernel and see if it resolves this bug?
--
Yo
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu Xenial)
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-
Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.6 kernel[0].
If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.
If the mainline kernel does not fix th
FWIW, m3.large is also affected.
--
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 notifica
** 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/1573231
Title:
Kernel Panic on EC2 After Upgrading from 14.
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
Sorry, I don't think there's any possible way to do it. The machine
won't boot. I could try to reproduce the issue again on a different VM,
but I still wouldn't be able to collect logs.
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification bec
** Package changed: ubuntu => linux (Ubuntu)
--
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 man
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It seems that your bug report is not filed about a
specific source package though, rather it is just filed against Ubuntu
in general. It is important that bug reports be filed about source
packages so that people
40 matches
Mail list logo