This bug was fixed in the package linux - 3.16.0-12.18
---
linux (3.16.0-12.18) utopic; urgency=low
[ Paolo Pisati ]
* Revert [Debian] dtb: symlink /lib/firmware/(uname -r)/device-tree to
/boot/dtb-(uname -r) to make flash-kernel happy
* Revert [Debian] dtb: don't remove a
** Changed in: linux (Ubuntu Utopic)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350522
Title:
EC2 kernel crash due to vmalloc
To manage notifications
Ok, finally it seems I found the problem. It seems Xen setup code is
accidentally setting up the kernel page tables in a way that causes the last 2G
of memory to be identically mapped (kernel mappings). This would just work
normally because the page table that covers the first 1G would
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350522
Title:
EC2 kernel crash due to vmalloc
To manage notifications about this bug go to:
No, this has been identified as an unfortunate fallout from Kernel Address
Space Layout Randomization. I am working on it. But right now you would need to
re-compile the kernel and disable CONFIG_RANDOMIZE_BASE. I shared the kernel
that I used to confirm this on
I'm running ubuntu 14.04 on Jiffybox, a German ec2 alternative. Due to
an unrelated problem with the 3.13 kernel (see
https://www.df.eu/forum/threads/72787-CONFIG_FHANDLE-Support-im-Jiffy-
Kernel?highlight=kernel if curious), it is not possible to use the stock
kernel: it will not boot. After
So I guess the next question would be whether in all 95% which do work
(deducted from the ~5% failing), are all Xen version != 4.2 or a mix of
versions, including 4.2? At least the fact that this persists while only
rebooting make some hypervisor code involvement likely.
The log looks to me like
One good thing: I get the same output when I start a utopic cloid-image
based PV guest on a Ubuntu 14.04 based Xen host (Xen-4.4).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350522
Title:
EC2
erge: d877215 b7dd0e3
Author: Linus Torvalds torva...@linux-foundation.org
Date: Wed Jul 30 09:00:20 2014 -0700
Merge tag 'stable/for-linus-3.16-rc7-tag' of git://git.kernel.org/pub/scm/li
Pull Xen fix from David Vrabel:
Fix BUG when trying to expand the grant table. This
Unfortunately it seems that patch (alone?) isn't helping. Or I made some
mistake in picking things. At least it still happens on th ePV guest
(but not on a HVM guest which really points to this patch). :/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Also affects: linux (Ubuntu Utopic)
Importance: High
Status: Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350522
Title:
EC2 kernel crash due to vmalloc
To manage
Ben,
A few questions that would be useful to answer:
* It would be useful to correlate Xen hypervisor versions. On each launch with
warnings we need to grep 'Xen version' in dmesg.
* Can you add the following to kernel cmdline options to get additional debug
information:
initcall_debug debug
This bug has been reported on the Ubuntu ISO testing tracker.
A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1350522
** Tags added: iso-testing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
apport information
** Description changed:
During Alpha-2 automated testing, I saw the following in a log:
19:35:02 [2.475810] systemd-udevd[95]: starting version 204
19:35:02 [2.547049] [ cut here ]
19:35:02 [2.547065] WARNING: CPU: 0 PID: 97 at
* It would be useful to correlate Xen hypervisor versions. On each launch with
warnings we need to grep 'Xen version' in dmesg.
Xen 4.2, w/ Amazon patches.
* Can you add the following to kernel cmdline options to get additional debug
information:
initcall_debug debug ignore_loglevel LOGLEVEL=8
apport information
** Tags added: apport-collected ec2-images third-party-packages utopic
** Description changed:
During Alpha-2 automated testing, I saw the following in a log:
19:35:02 [2.475810] systemd-udevd[95]: starting version 204
19:35:02 [2.547049] [ cut
I am seeing this happen in about 5% of the launches on EC2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1350522
Title:
EC2 kernel crash due to vmalloc
To manage notifications about this bug go
Another stack trace from another instance:
20:34:16 [2.425540] systemd-udevd[95]: starting version 204
20:34:16 [2.576097] [ cut here ]
20:34:16 [2.576111] WARNING: CPU: 0 PID: 98 at
/build/buildd/linux-3.16.0/mm/vmalloc.c:128
18 matches
Mail list logo
