| 2018-10-29 23:15:32 |
Guilherme G. Piccoli |
bug |
|
|
added bug |
| 2018-10-29 23:15:52 |
Guilherme G. Piccoli |
bug |
|
|
added subscriber Thadeu Lima de Souza Cascardo |
| 2018-10-29 23:16:17 |
Guilherme G. Piccoli |
nominated for series |
|
Ubuntu Bionic |
|
| 2018-10-29 23:16:17 |
Guilherme G. Piccoli |
nominated for series |
|
Ubuntu Trusty |
|
| 2018-10-29 23:16:17 |
Guilherme G. Piccoli |
nominated for series |
|
Ubuntu Xenial |
|
| 2018-10-29 23:16:17 |
Guilherme G. Piccoli |
nominated for series |
|
Ubuntu Dd-series |
|
| 2018-10-29 23:16:17 |
Guilherme G. Piccoli |
nominated for series |
|
Ubuntu Cosmic |
|
| 2019-01-09 15:42:33 |
Eric Desrochers |
bug task added |
|
makedumpfile (Ubuntu Bionic) |
|
| 2019-01-09 15:42:38 |
Eric Desrochers |
bug task added |
|
makedumpfile (Ubuntu Cosmic) |
|
| 2019-01-09 15:42:42 |
Eric Desrochers |
bug task added |
|
makedumpfile (Ubuntu Disco) |
|
| 2019-01-09 15:42:46 |
Eric Desrochers |
bug task added |
|
makedumpfile (Ubuntu Trusty) |
|
| 2019-01-09 15:42:50 |
Eric Desrochers |
bug task added |
|
makedumpfile (Ubuntu Xenial) |
|
| 2019-01-09 15:57:49 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Cosmic): importance |
Undecided |
High |
|
| 2019-01-09 15:57:50 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Bionic): importance |
Undecided |
High |
|
| 2019-01-09 15:57:52 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Xenial): importance |
Undecided |
High |
|
| 2019-01-09 15:57:53 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Trusty): importance |
Undecided |
High |
|
| 2019-01-09 15:57:56 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Trusty): assignee |
|
Guilherme G. Piccoli (gpiccoli) |
|
| 2019-02-14 13:17:52 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Trusty): assignee |
Guilherme G. Piccoli (gpiccoli) |
Heitor R. Alves de Siqueira (halves) |
|
| 2019-02-14 13:17:59 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Xenial): assignee |
|
Heitor R. Alves de Siqueira (halves) |
|
| 2019-02-14 13:18:05 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Bionic): assignee |
|
Heitor R. Alves de Siqueira (halves) |
|
| 2019-02-14 13:18:11 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Cosmic): assignee |
|
Heitor R. Alves de Siqueira (halves) |
|
| 2019-02-14 13:18:18 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Disco): assignee |
Mauricio Faria de Oliveira (mfo) |
Heitor R. Alves de Siqueira (halves) |
|
| 2019-02-14 13:18:27 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Cosmic): status |
New |
Confirmed |
|
| 2019-02-14 13:18:29 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Bionic): status |
New |
Confirmed |
|
| 2019-02-14 13:18:31 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Xenial): status |
New |
Confirmed |
|
| 2019-02-14 13:18:32 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Trusty): status |
New |
Confirmed |
|
| 2019-02-14 18:49:50 |
Heitor Alves de Siqueira |
description |
Kernel has the "reset_devices" parameter that drivers can opt-in, and perform special activity in case this parameter is parsed from command-line. For example, in kdump kernels it hints the drivers that they (maybe) are booting from a non-healthy condition and needs to issue some reset to the adapter. Users currently (kernel v4.19) are: hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.
This should be enabled by default in the kdump config file to be added in the kdump kernel command-line for all versions. |
[Impact]
Crash kernels do not advise some subsystems to perform a reset by default.
[Description]
Kernel has the "reset_devices" parameter that drivers can opt-in, and perform special activity in case this parameter is parsed from command-line. For example, in kdump kernels it hints the drivers that they (maybe) are booting from a non-healthy condition and needs to issue some reset to the adapter. Users currently (kernel v4.19) are: hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.
This should be enabled by default in the kdump config file to be added in the kdump kernel command-line for all versions.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'reset_devices' parameter:
$ kdump-config test
[...]
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is very low, since it doesn't need any changes in makedumpfile code and we're only adding a parameter on the crashkernel cmdline.
The fix will be tested with autopkgtests and normal kdump use-case scenarios. |
|
| 2019-02-19 09:02:21 |
Eric Desrochers |
bug |
|
|
added subscriber STS Sponsors |
| 2019-02-19 09:33:12 |
Heitor Alves de Siqueira |
description |
[Impact]
Crash kernels do not advise some subsystems to perform a reset by default.
[Description]
Kernel has the "reset_devices" parameter that drivers can opt-in, and perform special activity in case this parameter is parsed from command-line. For example, in kdump kernels it hints the drivers that they (maybe) are booting from a non-healthy condition and needs to issue some reset to the adapter. Users currently (kernel v4.19) are: hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.
This should be enabled by default in the kdump config file to be added in the kdump kernel command-line for all versions.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'reset_devices' parameter:
$ kdump-config test
[...]
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is very low, since it doesn't need any changes in makedumpfile code and we're only adding a parameter on the crashkernel cmdline.
The fix will be tested with autopkgtests and normal kdump use-case scenarios. |
[Impact]
Crash kernels do not advise some subsystems to perform a reset by default.
[Description]
Kernel has the "reset_devices" parameter that drivers can opt-in, and perform special activity in case this parameter is parsed from command-line. For example, in kdump kernels it hints the drivers that they (maybe) are booting from a non-healthy condition and needs to issue some reset to the adapter. Users currently (kernel v4.19) are: hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.
This should be enabled by default in the kdump config file to be added in the kdump kernel command-line for all versions.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'reset_devices' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is very low, since it doesn't need any changes in makedumpfile code and we're only adding a parameter on the crashkernel cmdline.
The fix will be tested with autopkgtests and normal kdump use-case scenarios. |
|
| 2019-03-01 02:46:41 |
Eric Desrochers |
removed subscriber STS Sponsors |
|
|
|
| 2019-03-01 02:46:45 |
Eric Desrochers |
bug |
|
|
added subscriber Eric Desrochers |
| 2019-06-05 13:06:04 |
Heitor Alves de Siqueira |
tags |
sts |
|
|
| 2019-06-19 12:18:55 |
Guilherme G. Piccoli |
tags |
|
seg |
|
| 2019-07-04 14:14:00 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu): assignee |
Heitor Alves de Siqueira (halves) |
Guilherme G. Piccoli (gpiccoli) |
|
| 2019-07-04 14:14:03 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Xenial): assignee |
Heitor Alves de Siqueira (halves) |
Guilherme G. Piccoli (gpiccoli) |
|
| 2019-07-04 14:14:07 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Bionic): assignee |
Heitor Alves de Siqueira (halves) |
Guilherme G. Piccoli (gpiccoli) |
|
| 2019-07-04 14:14:12 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Disco): assignee |
Heitor Alves de Siqueira (halves) |
Guilherme G. Piccoli (gpiccoli) |
|
| 2019-07-04 14:14:13 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Trusty): status |
Confirmed |
Won't Fix |
|
| 2019-07-04 14:14:16 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Cosmic): assignee |
Heitor Alves de Siqueira (halves) |
Guilherme G. Piccoli (gpiccoli) |
|
| 2019-07-04 14:14:21 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Trusty): assignee |
Heitor Alves de Siqueira (halves) |
Guilherme G. Piccoli (gpiccoli) |
|
| 2019-07-04 14:14:32 |
Guilherme G. Piccoli |
nominated for series |
|
Ubuntu Eoan |
|
| 2019-07-04 14:14:32 |
Guilherme G. Piccoli |
bug task added |
|
makedumpfile (Ubuntu Eoan) |
|
| 2019-07-04 19:29:36 |
Guilherme G. Piccoli |
summary |
Make the reset_devices parameter default for kdump kernels |
Make reset_devices parameter default for kdump and decouple kdump systemd service from the KDUMP_CMDLINE_APPEND |
|
| 2019-07-04 19:58:04 |
Guilherme G. Piccoli |
description |
[Impact]
Crash kernels do not advise some subsystems to perform a reset by default.
[Description]
Kernel has the "reset_devices" parameter that drivers can opt-in, and perform special activity in case this parameter is parsed from command-line. For example, in kdump kernels it hints the drivers that they (maybe) are booting from a non-healthy condition and needs to issue some reset to the adapter. Users currently (kernel v4.19) are: hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.
This should be enabled by default in the kdump config file to be added in the kdump kernel command-line for all versions.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'reset_devices' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is very low, since it doesn't need any changes in makedumpfile code and we're only adding a parameter on the crashkernel cmdline.
The fix will be tested with autopkgtests and normal kdump use-case scenarios. |
[Impact]
* Kdump does not configure by default the crash kernel to perform a device reset by default, by passing the "reset_devices" parameter. Also, the systemd service "kdump-tools-dump" is tightly-coupled with KDUMP_CMDLINE_APPEND and it shouldn't, to prevent user confusion.
* Kernel has the "reset_devices" parameter that drivers can opt-in, and perform special activity in case this parameter is parsed from command-line. For example, in kdump kernels it hints the drivers that they are booting from a non-healthy condition and needs to issue some form of reset to the adapter, like clearing DMA mapping in their firmware for example. Users currently (kernel v5.2) are: aacraid, hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.
This should be enabled by default in the kdump config file to be added in the kdump kernel command-line for all versions.
* The systemd service"kdump-tools-dump" is responsible for triggering the execution of the makedumpfile tool ultimately. Kdump from Xenial+ releases rely on systemd as their init system, so this service is the way to trigger the kdump mechanism. Currently it is configured as any other parameter in KDUMP_CMDLINE_APPEND, meaning if user decides to change the line they need to remember adding the systemd service back. It's not really a parameter that should be easily manipulated in kdump line, since there's no use for it except to instruct systemd to load kdump; the only
reasonable case for removing it is to debug kdump itself.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'reset_devices' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz
Also, by changing the KDUMP_CMDLINE_APPEND we can see "systemd.unit=kdump-tools.service" to be removed.
[Regression Potential]
The regression potential is low, since it doesn't need any changes in makedumpfile code and we're only adding a parameter on the crash kernel command-line. The risks are related with bad behavior with the kernel when using "reset_devices", like if the driver has bugs in this path. It's considered safer to have the option (and this way prevent problems for booting a unhealthy kernel with potential stuck DMAs in the devices) than not having it.
Regarding the other change, about the systemd service, it'll only affect users the are debugging kdump itself and it has no known regression potential. |
|
| 2019-07-04 21:04:27 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Eoan): status |
Confirmed |
In Progress |
|
| 2019-07-04 21:05:36 |
Guilherme G. Piccoli |
attachment added |
|
lp1800566_eoan.debdiff https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800566/+attachment/5275118/+files/lp1800566_eoan.debdiff |
|
| 2019-07-05 00:20:26 |
Ubuntu Foundations Team Bug Bot |
tags |
seg |
patch seg |
|
| 2019-07-05 00:20:37 |
Ubuntu Foundations Team Bug Bot |
bug |
|
|
added subscriber Ubuntu Sponsors Team |
| 2019-07-27 03:31:17 |
Mathew Hodson |
makedumpfile (Ubuntu Cosmic): status |
Confirmed |
Won't Fix |
|
| 2019-12-12 20:53:47 |
Guilherme G. Piccoli |
nominated for series |
|
Ubuntu Focal |
|
| 2019-12-12 20:53:47 |
Guilherme G. Piccoli |
bug task added |
|
makedumpfile (Ubuntu Focal) |
|
| 2019-12-12 21:01:47 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Eoan): status |
In Progress |
Confirmed |
|
| 2019-12-12 21:01:52 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Focal): status |
In Progress |
Confirmed |
|
| 2019-12-20 14:23:32 |
Thadeu Lima de Souza Cascardo |
makedumpfile (Ubuntu Disco): status |
Confirmed |
Won't Fix |
|
| 2019-12-20 14:23:43 |
Thadeu Lima de Souza Cascardo |
makedumpfile (Ubuntu Focal): status |
Confirmed |
In Progress |
|
| 2019-12-20 14:23:49 |
Thadeu Lima de Souza Cascardo |
makedumpfile (Ubuntu Eoan): status |
Confirmed |
In Progress |
|
| 2019-12-20 14:23:54 |
Thadeu Lima de Souza Cascardo |
makedumpfile (Ubuntu Bionic): status |
Confirmed |
In Progress |
|
| 2019-12-20 14:23:59 |
Thadeu Lima de Souza Cascardo |
makedumpfile (Ubuntu Xenial): status |
Confirmed |
In Progress |
|
| 2019-12-20 15:51:33 |
Dan Streetman |
makedumpfile (Ubuntu Disco): status |
Won't Fix |
In Progress |
|
| 2019-12-20 17:56:58 |
Guilherme G. Piccoli |
summary |
Make reset_devices parameter default for kdump and decouple kdump systemd service from the KDUMP_CMDLINE_APPEND |
Make reset_devices parameter default for kdump |
|
| 2019-12-20 18:01:08 |
Guilherme G. Piccoli |
description |
[Impact]
* Kdump does not configure by default the crash kernel to perform a device reset by default, by passing the "reset_devices" parameter. Also, the systemd service "kdump-tools-dump" is tightly-coupled with KDUMP_CMDLINE_APPEND and it shouldn't, to prevent user confusion.
* Kernel has the "reset_devices" parameter that drivers can opt-in, and perform special activity in case this parameter is parsed from command-line. For example, in kdump kernels it hints the drivers that they are booting from a non-healthy condition and needs to issue some form of reset to the adapter, like clearing DMA mapping in their firmware for example. Users currently (kernel v5.2) are: aacraid, hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.
This should be enabled by default in the kdump config file to be added in the kdump kernel command-line for all versions.
* The systemd service"kdump-tools-dump" is responsible for triggering the execution of the makedumpfile tool ultimately. Kdump from Xenial+ releases rely on systemd as their init system, so this service is the way to trigger the kdump mechanism. Currently it is configured as any other parameter in KDUMP_CMDLINE_APPEND, meaning if user decides to change the line they need to remember adding the systemd service back. It's not really a parameter that should be easily manipulated in kdump line, since there's no use for it except to instruct systemd to load kdump; the only
reasonable case for removing it is to debug kdump itself.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'reset_devices' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz
Also, by changing the KDUMP_CMDLINE_APPEND we can see "systemd.unit=kdump-tools.service" to be removed.
[Regression Potential]
The regression potential is low, since it doesn't need any changes in makedumpfile code and we're only adding a parameter on the crash kernel command-line. The risks are related with bad behavior with the kernel when using "reset_devices", like if the driver has bugs in this path. It's considered safer to have the option (and this way prevent problems for booting a unhealthy kernel with potential stuck DMAs in the devices) than not having it.
Regarding the other change, about the systemd service, it'll only affect users the are debugging kdump itself and it has no known regression potential. |
[Impact]
* Kdump does not configure by default the crash kernel to perform a device reset by default, by passing the "reset_devices" parameter.
* Kernel has the "reset_devices" parameter that drivers can opt-in, and perform special activity in case this parameter is parsed from command-line. For example, in kdump kernels it hints the drivers that they are booting from a non-healthy condition and needs to issue some form of reset to the adapter, like clearing DMA mapping in their firmware for example. Users currently (kernel v5.5-rc2) are: aacraid, hpsa, ipr, megaraid_sas, mpt3sas, smartpqi, xenbus.
This should be enabled by default in the kdump config file to be added in the kdump kernel command-line for all versions.
[Test Case]
1) Deploy a Bionic VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'reset_devices' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1 systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0" /var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is low, since it doesn't need any changes in makedumpfile code and we're only adding a parameter on the crash kernel command-line. The risks are related with bad behavior with the kernel when using "reset_devices", like if the driver has bugs in this path. It's considered safer to have the option (and this way prevent problems for booting a unhealthy kernel with potential stuck DMAs in the devices) than not having it. |
|
| 2020-01-07 20:45:37 |
Launchpad Janitor |
makedumpfile (Ubuntu Focal): status |
In Progress |
Fix Released |
|
| 2020-01-09 17:08:19 |
Mauricio Faria de Oliveira |
bug |
|
|
added subscriber Mauricio Faria de Oliveira |
| 2020-01-10 18:04:43 |
Mauricio Faria de Oliveira |
makedumpfile (Ubuntu Disco): status |
In Progress |
Won't Fix |
|
| 2020-01-10 18:05:46 |
Mauricio Faria de Oliveira |
makedumpfile (Ubuntu Disco): importance |
High |
Undecided |
|
| 2020-01-10 18:05:50 |
Mauricio Faria de Oliveira |
makedumpfile (Ubuntu Disco): assignee |
Guilherme G. Piccoli (gpiccoli) |
|
|
| 2020-01-10 18:05:53 |
Mauricio Faria de Oliveira |
makedumpfile (Ubuntu Cosmic): importance |
High |
Undecided |
|
| 2020-01-10 18:05:57 |
Mauricio Faria de Oliveira |
makedumpfile (Ubuntu Cosmic): assignee |
Guilherme G. Piccoli (gpiccoli) |
|
|
| 2020-01-13 14:56:00 |
Andy Whitcroft |
makedumpfile (Ubuntu Eoan): status |
In Progress |
Fix Committed |
|
| 2020-01-13 14:56:03 |
Andy Whitcroft |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-01-13 14:56:05 |
Andy Whitcroft |
bug |
|
|
added subscriber SRU Verification |
| 2020-01-13 14:56:09 |
Andy Whitcroft |
tags |
patch seg |
patch seg verification-needed verification-needed-eoan |
|
| 2020-01-14 08:28:16 |
Andy Whitcroft |
makedumpfile (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-01-14 08:28:23 |
Andy Whitcroft |
tags |
patch seg verification-needed verification-needed-eoan |
patch seg verification-needed verification-needed-bionic verification-needed-eoan |
|
| 2020-01-14 14:18:13 |
Andy Whitcroft |
makedumpfile (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2020-01-14 14:18:20 |
Andy Whitcroft |
tags |
patch seg verification-needed verification-needed-bionic verification-needed-eoan |
patch seg verification-needed verification-needed-bionic verification-needed-eoan verification-needed-xenial |
|
| 2020-01-14 14:19:11 |
Andy Whitcroft |
removed subscriber Ubuntu Sponsors Team |
|
|
|
| 2020-01-15 16:56:40 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Trusty): importance |
High |
Undecided |
|
| 2020-01-15 16:56:49 |
Guilherme G. Piccoli |
makedumpfile (Ubuntu Trusty): assignee |
Guilherme G. Piccoli (gpiccoli) |
|
|
| 2020-01-15 16:57:25 |
Guilherme G. Piccoli |
tags |
patch seg verification-needed verification-needed-bionic verification-needed-eoan verification-needed-xenial |
patch seg verification-done verification-done-bionic verification-done-eoan verification-done-xenial |
|
| 2020-01-29 03:37:12 |
Chris Halse Rogers |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-01-29 03:38:31 |
Launchpad Janitor |
makedumpfile (Ubuntu Eoan): status |
Fix Committed |
Fix Released |
|
| 2020-01-29 03:47:35 |
Launchpad Janitor |
makedumpfile (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2020-01-29 03:50:17 |
Launchpad Janitor |
makedumpfile (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
