** Also affects: linux (Ubuntu Xenial)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: Fix Committed
** Changed in: linux (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs,
This bug was fixed in the package linux - 3.19.0-49.55
---
linux (3.19.0-49.55) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1536775
[ Colin Ian King ]
* SAUCE: (no-up) ACPI / tables: Add acpi_force_32bit_fadt_addr option to
force 32 bit FADT
This bug was fixed in the package linux - 3.19.0-49.55
---
linux (3.19.0-49.55) vivid; urgency=low
[ Brad Figg ]
* Release Tracking Bug
- LP: #1536775
[ Colin Ian King ]
* SAUCE: (no-up) ACPI / tables: Add acpi_force_32bit_fadt_addr option to
force 32 bit FADT
Hello!
I installed the kernel in -proposed (kernel version 3.19.0-49-generic),
triggered a kernel panic and it worked as expected. The crashkernel
memory sizes I used are 512M and 384M.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Tags removed: verification-needed-vivid
** Tags added: verification-done-vivid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440103
Title:
[Hyper-V] Kernel panic not functional on Vivid
To
Hi Chris,
Can you verify the kernel in -proposed as requested in #33? That way
the fix can move into -updates.
Thanks in advance!
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
We're looking at it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440103
Title:
[Hyper-V] Kernel panic not functional on Vivid
To manage notifications about this bug go to:
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-
vivid' to 'verification-done-vivid'.
If verification is not done by 5 working days from
** Changed in: linux (Ubuntu Vivid)
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.net/bugs/1440103
Title:
[Hyper-V] Kernel panic not functional on Vivid
To
Hi Joe,
Can you provide a list of commits and dependencies you have to include for the
working test kernel?
The same or a similar issue might be occurring on Ubuntu with linux-next so we
want to compare them.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
Hi Chris,
Here is the list of commits used in test kernel:
0f22bce staging: lustre: check kzalloc return value
1d67237 Drivers: hv: vmbus: prefer 'die' notification chain to 'panic'
a28d64c Drivers: hv: vmbus: add special crash handler
5990a10 Drivers: hv: don't do hypercalls when hypercall_page
Hello!
I tested the following kernel
http://kernel.ubuntu.com/~jsalisbury/lp1440103/vivid/ with the following
crashkernel values: 384M and 512M. Everything worked as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That is good news, paula. If those commits now fix this bug, I'll SRU
them to Vivid.
Thanks for the help testing!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440103
Title:
[Hyper-V] Kernel
I created one more test kernel, which is v5. I confirmed this test
kernel now boots. One of the prereq backports needed to be done
differently.
The new test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1440103/vivid/
Can you test this kernel and see if it resolves this
Hello!
I tested Willy with the latest kernel version (4.2.0-23-generic) and VM reboots
itself after kernel panic.
I also tested Vivid with the following kernel
http://kernel.ubuntu.com/~jsalisbury/lp1440103/vivid/. The VM doesn't boot
after installing the kernel. I attached the log.
**
Joe, can you please re-check on the patches included, based on the no-boot
issue from comment #24?
Thank you!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440103
Title:
[Hyper-V] Kernel panic
I made some changes to the backports and have a new V3 test kernel to
try. The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1440103/vivid
Can you test this kernel and see if it resolves this bug?
Also, can you confirm that Wily with the latest updates does not
** Changed in: linux (Ubuntu)
Status: Fix Released => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440103
Title:
[Hyper-V] Kernel panic not functional on Vivid
To manage
I've installed the test kernel but the VM doesn't boot.
You can check the boot log which I attached.
** Attachment added: "boot.log"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440103/+attachment/4516994/+files/boot.log
--
You received this bug notification because you are a
I built a V2 Vivid test kernel with the six patches posted in comment
#16 and some prereq commits I applied instead of backporting.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1440103/vivid
Can you test this kernel and see if it resolves this bug?
Also, can
The use of a different kdump-tools package version as in bug #1400319
was due to a different error, which was anyway only on 32bit.
Nevertheless, I still tried this on the Vivid VM and verified the crash
functionality with kdump-tools from Trusty and then the one from Wily.
With both attempts,
It may be that we need a combination of the six patches in the test
kernel and a new kdump-tools.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440103
Title:
[Hyper-V] Kernel panic not functional
It was found in bug 1400319 that the issue may be due to kdump-tools.
Can you see if this is also the case with this bug and try the version
of kdump-tools mentioned in comment #33 and #20?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi Joe,
I'm running the test kernel 3.19.0-32_3.19.0-32.37~lp1440103_amd64 on a Vivid
either default installed or fully updated, however crashdump is not happening
as expected.
It will show the usual crash log output, but the system will hang, never
reboot - and the crash dump file is not
I built a Vivid test kernel with the six patches posted in comment #16.
The test kernel can be downloaded from:
http://kernel.ubuntu.com/~jsalisbury/lp1440103/vivid
Can you test this kernel and see if it resolves this bug?
--
You received this bug notification because you are a member of
This bug was fixed in the package linux - 4.2.0-14.16
---
linux (4.2.0-14.16) wily; urgency=low
[ Tim Gardner ]
* Release Tracking Bug
- LP: #1501818
* rebase to v4.2.2
* [Config] CONFIG_RTC_DRV_XGENE=y
- LP: #1499869
[ Upstream Kernel Changes ]
* mei: do not
Applied to Wily:
Drivers: hv: kvp: check kzalloc return value
Drivers: hv: vmbus: prefer 'die' notification chain to 'panic'
Drivers: hv: vmbus: add special crash handler
Drivers: hv: don't do hypercalls when hypercall_page is NULL
Drivers: hv: vmbus: add special kexec handler
kexec: define
Hi Joseph,
We got the confirmation that all the below patches must be included for the
kdump issue.
Please provide us with a test kernel with these included so we can re-test.
Drivers: hv: vmbus: prefer 'die' notification chain to 'panic'
It resolved the bug. Tested successfully on Wily with 4.2.0-10-generic
#12~lp1440103 test kernel.
These are the traces in dmesg in the crash logs:
[ 187.204774] CPU: 3 PID: 946 Comm: bash Not tainted 4.2.0-10-generic
#12~lp1440103
[ 187.204774] Hardware name: Microsoft Corporation Virtual
I performed a cherry pick of the following three commits into Wily:
2b94ed2 kexec: define kexec_in_progress in !CONFIG_KEXEC case
2517281 Drivers: hv: vmbus: add special kexec handler
b4370df Drivers: hv: vmbus: add special crash handler
The test kernel can be downloaded from:
It looks like the commits requested in this bug have now landed in
upstream v4.3-rc1
** Also affects: linux (Ubuntu Wily)
Importance: Medium
Assignee: Joseph Salisbury (jsalisbury)
Status: In Progress
** Tags added: wily
--
You received this bug notification because you are a
Upstream thread:
https://lkml.org/lkml/2015/6/28/70
We can cherry-pick these commits once they are accepted in mainline.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440103
Title:
[Hyper-V]
** Also affects: linux (Ubuntu Vivid)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Vivid)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Joseph Salisbury (jsalisbury)
** Changed in: linux (Ubuntu Vivid)
Assignee:
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440103
Title:
[Hyper-V] Kernel panic not functional on Vivid
To manage notifications about this bug go to:
** Patch added: 05.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440103/+attachment/4422112/+files/05.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440103
Title:
[Hyper-V]
** Patch added: 03.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440103/+attachment/4422111/+files/03.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440103
Title:
[Hyper-V]
I'm attaching thee patches that went upstream as part of a larger bundle
to fix this kexec issue.
From K. Y. Srinivasan
Subject [PATCH V2 00/10] Drivers: hv: vmbus: Enable kexec and other misc
cleanup
Date Thu, 4 Jun 2015 16:25:39 -0700
In addition to enabling kexec, this patch-set has
FYI, re: upstream status, the series was resubmitted on 6/28 but needs
an ack from the CPU hotplug folks before gregkh will accept it into his
tree. We have tested it internally, as well as testing it with our
partners.
--
You received this bug notification because you are a member of Ubuntu
** Patch added: 02.patch
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1440103/+attachment/4422110/+files/02.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440103
Title:
[Hyper-V]
** 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/1440103
Title:
[Hyper-V] Kernel panic not functional on Vivid
To manage notifications about this bug go to:
Can you test the latest 4.1 upstream kernel and see if this bug still
exists? It can be downloaded from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-unstable/
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The patch has not been submitted yet upstream, we're going to update
this thread as soon as it will be ready.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440103
Title:
[Hyper-V] Kernel panic not
Thanks for the update, Chris!
** Changed in: linux (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440103
Title:
[Hyper-V] Kernel panic not functional on
** Tags removed: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440103
Title:
[Hyper-V] Kernel panic not functional on Vivid
To manage notifications about this bug go to:
It was requested that I test Ballooning on 14.04.02.
Ballooning fails on 14.04.02.
Ballooning test on 14.04.02 after running apt-get upgrade
Startup Memory : 2048
Minimum Memory : 1024
Maximum Memory : 8192
The utility stressapptest was used to generate memory demand.
Let memory settle to
** Tags added: kernel-key
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440103
Title:
[Hyper-V] Kernel panic not functional on Vivid
To manage notifications about this bug go to:
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1440103
Title:
[Hyper-V] Kernel panic not functional on Vivid
To manage
** Changed in: linux (Ubuntu)
Importance: Undecided = High
** Tags added: kernel-da-key kernel-hyper-v
** Changed in: linux (Ubuntu)
Importance: High = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
48 matches
Mail list logo
