| 2017-08-24 16:28:25 |
Joshua R. Poulson |
bug |
|
|
added bug |
| 2017-08-24 16:28:43 |
Joshua R. Poulson |
linux-azure (Ubuntu): status |
New |
Confirmed |
|
| 2017-08-24 17:56:36 |
Joshua R. Poulson |
bug |
|
|
added subscriber Marcelo Cerri |
| 2017-08-24 20:01:45 |
Marcelo Cerri |
linux-azure (Ubuntu): importance |
Undecided |
High |
|
| 2017-08-24 20:01:49 |
Marcelo Cerri |
linux-azure (Ubuntu): assignee |
|
Marcelo Cerri (mhcerri) |
|
| 2017-08-24 20:01:53 |
Marcelo Cerri |
nominated for series |
|
Ubuntu Xenial |
|
| 2017-08-29 08:32:34 |
Chris Valean |
bug |
|
|
added subscriber Chris Valean |
| 2017-08-30 14:13:18 |
Marcelo Cerri |
linux-azure (Ubuntu): status |
Confirmed |
In Progress |
|
| 2017-08-31 13:43:16 |
Andy Whitcroft |
bug task added |
|
linux-azure (Ubuntu Xenial) |
|
| 2017-08-31 14:25:22 |
Marcelo Cerri |
linux-azure (Ubuntu Xenial): assignee |
|
Marcelo Cerri (mhcerri) |
|
| 2017-08-31 14:25:26 |
Marcelo Cerri |
linux-azure (Ubuntu Xenial): status |
New |
In Progress |
|
| 2017-08-31 14:25:28 |
Marcelo Cerri |
linux-azure (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2017-09-01 15:23:09 |
Steve Langasek |
bug task added |
|
makedumpfile (Ubuntu) |
|
| 2017-09-01 15:23:25 |
Steve Langasek |
bug |
|
|
added subscriber Steve Langasek |
| 2017-09-08 16:45:06 |
Marcelo Cerri |
bug task added |
|
kexec-tools (Ubuntu) |
|
| 2017-09-08 16:45:27 |
Marcelo Cerri |
kexec-tools (Ubuntu): status |
New |
Confirmed |
|
| 2017-09-08 16:45:33 |
Marcelo Cerri |
kexec-tools (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2017-09-08 16:45:39 |
Marcelo Cerri |
makedumpfile (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2017-09-08 16:45:45 |
Marcelo Cerri |
makedumpfile (Ubuntu): status |
New |
Confirmed |
|
| 2017-09-08 18:42:54 |
Marcelo Cerri |
bug task deleted |
makedumpfile (Ubuntu) |
|
|
| 2017-09-08 18:43:04 |
Marcelo Cerri |
bug task deleted |
makedumpfile (Ubuntu Xenial) |
|
|
| 2017-09-08 19:04:23 |
Marcelo Cerri |
bug task added |
|
crash (Ubuntu) |
|
| 2017-09-08 19:05:02 |
Marcelo Cerri |
kexec-tools (Ubuntu): status |
Confirmed |
In Progress |
|
| 2017-09-08 19:05:06 |
Marcelo Cerri |
kexec-tools (Ubuntu Xenial): status |
Confirmed |
In Progress |
|
| 2017-09-08 19:05:09 |
Marcelo Cerri |
kexec-tools (Ubuntu): importance |
Undecided |
High |
|
| 2017-09-08 19:05:12 |
Marcelo Cerri |
kexec-tools (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2017-09-08 19:05:15 |
Marcelo Cerri |
kexec-tools (Ubuntu): assignee |
|
Marcelo Cerri (mhcerri) |
|
| 2017-09-08 19:05:18 |
Marcelo Cerri |
kexec-tools (Ubuntu Xenial): assignee |
|
Marcelo Cerri (mhcerri) |
|
| 2017-09-08 19:05:23 |
Marcelo Cerri |
crash (Ubuntu): status |
New |
Confirmed |
|
| 2017-09-08 19:05:26 |
Marcelo Cerri |
crash (Ubuntu): importance |
Undecided |
High |
|
| 2017-09-08 19:05:29 |
Marcelo Cerri |
crash (Ubuntu): assignee |
|
Marcelo Cerri (mhcerri) |
|
| 2017-09-08 20:06:58 |
Dexuan Cui |
bug |
|
|
added subscriber Dexuan Cui |
| 2017-09-08 21:21:49 |
Marcelo Cerri |
crash (Ubuntu): status |
Confirmed |
In Progress |
|
| 2017-09-14 18:59:15 |
Marcelo Cerri |
description |
Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the following error:
kdump-tools[1436]: ELF core (kcore) parse failed
Perhaps the artful kexec-tools should be backported? |
[Impact]
Currently it's not possible to use the kdump functionality in xenial when running the linux-azure kernel. The problem is actually caused but several factors:
1. kexec fails to parse /proc/kcore and thus fails to load the crash kernel. That's similar to bug #1713940 and it's related to 4.10+ kernels.
2. When the crash kernel boots, a bug in KASLR causes it to crash in a very early stage. For the user, it seems the system just rebooted after the crash.
3. Currently in azure, crashkernel=128G is not enough to boot and run the dump procedure with 4.11+ kernels. That value needs to be increased in order to kdump to succeed.
4. After the vmcore is dumped, the current version of crash in xenial is not able to parse it. All the necessary fixes are already upstream and can be backported.
[Test Case]
1. Install the linux-azure kernel in an azure instance (although it's possible to run linux-azure in bare metal or kvm, the KASLR issue only is triggered in azure).
2. Follow the instructions in https://help.ubuntu.com/lts/serverguide/kernel-crash-dump.html to setup kdump and manually trigger a crash using /proc/sysrq-trigger.
The vmcore must be generated and it should be possible to inspect it using crash.
[Regression Potential]
Since both kexec-tools and crash are being changed to support 4.10+ kernels, it's very important that they continue to handle 4.4 kernels properly.
The same steps above can be used to test linux-generic for regressions.
[Other Info]
Original description:
--8<--
Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the following error:
kdump-tools[1436]: ELF core (kcore) parse failed
Perhaps the artful kexec-tools should be backported?
--8<-- |
|
| 2017-09-14 22:24:43 |
Steve Langasek |
description |
[Impact]
Currently it's not possible to use the kdump functionality in xenial when running the linux-azure kernel. The problem is actually caused but several factors:
1. kexec fails to parse /proc/kcore and thus fails to load the crash kernel. That's similar to bug #1713940 and it's related to 4.10+ kernels.
2. When the crash kernel boots, a bug in KASLR causes it to crash in a very early stage. For the user, it seems the system just rebooted after the crash.
3. Currently in azure, crashkernel=128G is not enough to boot and run the dump procedure with 4.11+ kernels. That value needs to be increased in order to kdump to succeed.
4. After the vmcore is dumped, the current version of crash in xenial is not able to parse it. All the necessary fixes are already upstream and can be backported.
[Test Case]
1. Install the linux-azure kernel in an azure instance (although it's possible to run linux-azure in bare metal or kvm, the KASLR issue only is triggered in azure).
2. Follow the instructions in https://help.ubuntu.com/lts/serverguide/kernel-crash-dump.html to setup kdump and manually trigger a crash using /proc/sysrq-trigger.
The vmcore must be generated and it should be possible to inspect it using crash.
[Regression Potential]
Since both kexec-tools and crash are being changed to support 4.10+ kernels, it's very important that they continue to handle 4.4 kernels properly.
The same steps above can be used to test linux-generic for regressions.
[Other Info]
Original description:
--8<--
Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the following error:
kdump-tools[1436]: ELF core (kcore) parse failed
Perhaps the artful kexec-tools should be backported?
--8<-- |
[Impact]
Currently it's not possible to use the kdump functionality in xenial when running the linux-azure kernel. The problem is actually caused by several factors:
1. kexec fails to parse /proc/kcore and thus fails to load the crash kernel. That's similar to bug #1713940 and it's related to 4.10+ kernels.
2. When the crash kernel boots, a bug in KASLR causes it to crash in a very early stage. For the user, it seems the system just rebooted after the crash.
3. Currently in azure, crashkernel=128G is not enough to boot and run the dump procedure with 4.11+ kernels. That value needs to be increased in order to kdump to succeed.
4. After the vmcore is dumped, the current version of crash in xenial is not able to parse it. All the necessary fixes are already upstream and can be backported.
[Test Case]
1. Install the linux-azure kernel in an azure instance (although it's possible to run linux-azure in bare metal or kvm, the KASLR issue only is triggered in azure).
2. Follow the instructions in https://help.ubuntu.com/lts/serverguide/kernel-crash-dump.html to setup kdump and manually trigger a crash using /proc/sysrq-trigger.
The vmcore must be generated and it should be possible to inspect it using crash.
[Regression Potential]
Since both kexec-tools and crash are being changed to support 4.10+ kernels, it's very important that they continue to handle 4.4 kernels properly.
The same steps above can be used to test linux-generic for regressions.
[Other Info]
Original description:
--8<--
Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the following error:
kdump-tools[1436]: ELF core (kcore) parse failed
Perhaps the artful kexec-tools should be backported?
--8<-- |
|
| 2017-09-14 22:26:27 |
Steve Langasek |
description |
[Impact]
Currently it's not possible to use the kdump functionality in xenial when running the linux-azure kernel. The problem is actually caused by several factors:
1. kexec fails to parse /proc/kcore and thus fails to load the crash kernel. That's similar to bug #1713940 and it's related to 4.10+ kernels.
2. When the crash kernel boots, a bug in KASLR causes it to crash in a very early stage. For the user, it seems the system just rebooted after the crash.
3. Currently in azure, crashkernel=128G is not enough to boot and run the dump procedure with 4.11+ kernels. That value needs to be increased in order to kdump to succeed.
4. After the vmcore is dumped, the current version of crash in xenial is not able to parse it. All the necessary fixes are already upstream and can be backported.
[Test Case]
1. Install the linux-azure kernel in an azure instance (although it's possible to run linux-azure in bare metal or kvm, the KASLR issue only is triggered in azure).
2. Follow the instructions in https://help.ubuntu.com/lts/serverguide/kernel-crash-dump.html to setup kdump and manually trigger a crash using /proc/sysrq-trigger.
The vmcore must be generated and it should be possible to inspect it using crash.
[Regression Potential]
Since both kexec-tools and crash are being changed to support 4.10+ kernels, it's very important that they continue to handle 4.4 kernels properly.
The same steps above can be used to test linux-generic for regressions.
[Other Info]
Original description:
--8<--
Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the following error:
kdump-tools[1436]: ELF core (kcore) parse failed
Perhaps the artful kexec-tools should be backported?
--8<-- |
[Impact]
Currently it's not possible to use the kdump functionality in xenial when running the linux-azure kernel. The problem is actually caused by several factors:
1. kexec fails to parse /proc/kcore and thus fails to load the crash kernel. That's similar to bug #1713940 and it's related to 4.10+ kernels.
2. When the crash kernel boots, a bug in KASLR causes it to crash in a very early stage. For the user, it seems the system just rebooted after the crash.
3. Currently in azure, crashkernel=128G is not enough to boot and run the dump procedure with 4.11+ kernels. That value needs to be increased in order to kdump to succeed.
4. After the vmcore is dumped, the current version of crash in xenial is not able to parse it. All the necessary fixes are already upstream and can be backported.
[Test Case]
1. Install the linux-azure kernel in an azure instance (although it's possible to run linux-azure in bare metal or kvm, the KASLR issue only is triggered in azure).
2. Follow the instructions in https://help.ubuntu.com/lts/serverguide/kernel-crash-dump.html to setup kdump and manually trigger a crash using /proc/sysrq-trigger.
The vmcore must be generated and it should be possible to inspect it using crash.
3. Perform these same tests for the linux-generic kernel, on each supported architecture.
[Regression Potential]
Since both kexec-tools and crash are being changed to support 4.10+ kernels, it's very important that they continue to handle 4.4 kernels properly.
The same steps above can be used to test linux-generic for regressions.
[Other Info]
Original description:
--8<--
Because the linux-azure kernel is based on 4.11, kexec on 16.04 gives the following error:
kdump-tools[1436]: ELF core (kcore) parse failed
Perhaps the artful kexec-tools should be backported?
--8<-- |
|
| 2017-09-14 22:28:00 |
Steve Langasek |
kexec-tools (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2017-09-14 22:28:02 |
Steve Langasek |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2017-09-14 22:28:03 |
Steve Langasek |
bug |
|
|
added subscriber SRU Verification |
| 2017-09-14 22:28:10 |
Steve Langasek |
tags |
|
verification-needed verification-needed-xenial |
|
| 2017-09-15 16:01:13 |
Steve Langasek |
crash (Ubuntu Xenial): status |
New |
Fix Committed |
|
| 2017-09-15 23:18:12 |
Marcelo Cerri |
kexec-tools (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2017-09-15 23:18:29 |
Marcelo Cerri |
linux-azure (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2017-09-15 23:18:34 |
Marcelo Cerri |
linux-azure (Ubuntu): status |
In Progress |
Fix Committed |
|
| 2017-09-16 00:03:23 |
Steve Langasek |
crash (Ubuntu): status |
In Progress |
Fix Released |
|
| 2017-09-16 00:03:25 |
Steve Langasek |
kexec-tools (Ubuntu): status |
Fix Committed |
Fix Released |
|
| 2017-09-16 00:03:42 |
Marcelo Cerri |
tags |
verification-needed verification-needed-xenial |
verification-done verification-done-xenial |
|
| 2017-09-16 00:25:18 |
Launchpad Janitor |
kexec-tools (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-09-16 00:25:23 |
Steve Langasek |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2017-09-16 00:25:30 |
Launchpad Janitor |
crash (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2017-09-19 13:03:03 |
Marcelo Cerri |
crash (Ubuntu): status |
Fix Released |
Fix Committed |
|
| 2017-09-19 13:03:23 |
Marcelo Cerri |
crash (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2017-09-19 13:03:25 |
Marcelo Cerri |
crash (Ubuntu Xenial): assignee |
|
Marcelo Cerri (mhcerri) |
|
| 2017-09-20 00:26:27 |
Launchpad Janitor |
linux-azure (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
