[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Patch removed: "debdiff for disco"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239779/+files/disco_makedumpfile_1.6.5-1ubuntu2.debdiff
** Patch removed: "debdiff for cosmic"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239780/+files/cosmic_makedumpfile_1.6.4-2ubuntu2.debdiff
** Patch removed: "debdiff for bionic"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239781/+files/bionic_makedumpfile_1.6.3-2ubuntu2.debdiff
** Patch removed: "debdiff for xenial"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239782/+files/xenial_makedumpfile_1.6.3-2~16.04.1ubuntu1.debdiff
** Summary changed:
- Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
+ Remove obsolete "nousb" option in kdump command-line for newer kernels
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Remove obsolete "nousb" option in kdump command-line for newer kernels
Status in makedumpfile package in Ubuntu:
Opinion
Status in makedumpfile source package in Xenial:
In Progress
Status in makedumpfile source package in Bionic:
In Progress
Status in makedumpfile source package in Cosmic:
In Progress
Status in makedumpfile source package in Disco:
Opinion
Bug description:
[Impact]
Crash kernels include an obsolete "nousb" parameter by default, which can
cause confusion since it's been deprecated in newer kernel versions.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line appears to be saying the
opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[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 'nousb' 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 extremely low, since it doesn't need any changes
in makedumpfile code and we're only removing an already ineffective parameter
from the crashkernel cmdline. Nonetheless, patches will be tested with
autopkgtests and normal kdump use-case scenarios.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
Thanks for bringing that up, Cascardo. That was one scenario we didn't
consider, and you're right about it causing problems for users with
encrypted systems.
It does seem more sensible to just remove the 'nousb' option in this case,
since this parameter has no effect in recent kernels. I'll respin the patches
and change this LP to better reflect this.
Thanks!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Opinion
Status in makedumpfile source package in Xenial:
In Progress
Status in makedumpfile source package in Bionic:
In Progress
Status in makedumpfile source package in Cosmic:
In Progress
Status in makedumpfile source package in Disco:
Opinion
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[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 'usbcore.nousb' 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 and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
Have you seen this cause any issue when kdumping from bionic or any
releases later than xenial?
Because we should not disable usb, and I would apply the opposite fix
and just remove "nousb" from the command line.
The reason for this is supporting kdump on encrypted systems, where the
user must type a password and use a USB keyboard.
Cascardo.
** Changed in: makedumpfile (Ubuntu Disco)
Status: In Progress => Opinion
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Opinion
Status in makedumpfile source package in Xenial:
In Progress
Status in makedumpfile source package in Bionic:
In Progress
Status in makedumpfile source package in Cosmic:
In Progress
Status in makedumpfile source package in Disco:
Opinion
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[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 'usbcore.nousb' 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 and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Changed in: makedumpfile (Ubuntu Disco)
Status: Confirmed => In Progress
** Changed in: makedumpfile (Ubuntu Cosmic)
Status: Confirmed => In Progress
** Changed in: makedumpfile (Ubuntu Bionic)
Status: Confirmed => In Progress
** Changed in: makedumpfile (Ubuntu Xenial)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
In Progress
Status in makedumpfile source package in Xenial:
In Progress
Status in makedumpfile source package in Bionic:
In Progress
Status in makedumpfile source package in Cosmic:
In Progress
Status in makedumpfile source package in Disco:
In Progress
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[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 'usbcore.nousb' 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 and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
The attachment "debdiff for disco" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Confirmed
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Cosmic:
Confirmed
Status in makedumpfile source package in Disco:
Confirmed
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[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 'usbcore.nousb' 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 and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Description changed:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[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 'usbcore.nousb' 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 and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Confirmed
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Cosmic:
Confirmed
Status in makedumpfile source package in Disco:
Confirmed
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[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 'usbcore.nousb' 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 and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Patch added: "debdiff for xenial"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239782/+files/xenial_makedumpfile_1.6.3-2~16.04.1ubuntu1.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Confirmed
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Cosmic:
Confirmed
Status in makedumpfile source package in Disco:
Confirmed
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[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 'usbcore.nousb' 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 and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Patch added: "debdiff for cosmic"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239780/+files/cosmic_makedumpfile_1.6.4-2ubuntu2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Confirmed
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Cosmic:
Confirmed
Status in makedumpfile source package in Disco:
Confirmed
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[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 'usbcore.nousb' 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 and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Patch added: "debdiff for bionic"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239781/+files/bionic_makedumpfile_1.6.3-2ubuntu2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Confirmed
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Cosmic:
Confirmed
Status in makedumpfile source package in Disco:
Confirmed
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[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 'usbcore.nousb' 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 and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Patch added: "debdiff for disco"
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+attachment/5239779/+files/disco_makedumpfile_1.6.5-1ubuntu2.debdiff
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Confirmed
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Cosmic:
Confirmed
Status in makedumpfile source package in Disco:
Confirmed
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[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 'usbcore.nousb' 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 and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
[0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
parameters.rst
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Description changed:
- Since kernel v4.5, the correct parameter to disable USB subsystem
- initialization is "usbcore.nousb" always (instead of "nousb" in case the
- subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb:
- make "nousb" a clear module parameter").
+ [Impact]
+ Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
+
+
+ [Description]
+ Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
+
+ This affects Xenial onwards, since the system may be running an HWE or
+ other supported v4.5+ kernel.
+
+ [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 'usbcore.nousb' 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 and we're only adding a parameter on the crashkernel cmdline.
+ According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
+ Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
** Description changed:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
-
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[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 'usbcore.nousb' 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
+ /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 and we're only adding a parameter on the crashkernel cmdline.
According to kernel documentation [0], unknown parameters will be ignored if
they contain a dot (usbcore.nousb), so this change should have no impact on
v4.4 and earlier kernels.
Nonetheless, the fix will be tested with autopkgtests and normal kdump
use-case scenarios.
+
+ [0] https://www.kernel.org/doc/Documentation/admin-guide/kernel-
+ parameters.rst
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Confirmed
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Cosmic:
Confirmed
Status in makedumpfile source package in Disco:
Confirmed
Bug description:
[Impact]
Crash kernels come up with the usb subsystem enabled, even when it should be
disabled by default.
[Description]
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case the
subsystem is built-in). This was changed by commit 097a9ea0e48 ("usb: make
"nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
This affects Xenial onwards, since the system may be running an HWE or
other supported v4.5+ kernel.
[Test Case]
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Changed in: makedumpfile (Ubuntu Xenial)
Assignee: Guilherme G. Piccoli (gpiccoli) => Heitor R. Alves de Siqueira
(halves)
** Changed in: makedumpfile (Ubuntu Bionic)
Assignee: Guilherme G. Piccoli (gpiccoli) => Heitor R. Alves de Siqueira
(halves)
** Changed in: makedumpfile (Ubuntu Cosmic)
Assignee: Guilherme G. Piccoli (gpiccoli) => Heitor R. Alves de Siqueira
(halves)
** Changed in: makedumpfile (Ubuntu Disco)
Assignee: Guilherme G. Piccoli (gpiccoli) => Heitor R. Alves de Siqueira
(halves)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Confirmed
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Cosmic:
Confirmed
Status in makedumpfile source package in Disco:
Confirmed
Bug description:
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case
the subsystem is built-in). This was changed by commit 097a9ea0e48
("usb: make "nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Changed in: makedumpfile (Ubuntu Cosmic)
Status: New => Confirmed
** Changed in: makedumpfile (Ubuntu Bionic)
Status: New => Confirmed
** Changed in: makedumpfile (Ubuntu Xenial)
Status: New => Confirmed
** Changed in: makedumpfile (Ubuntu Cosmic)
Importance: Undecided => High
** Changed in: makedumpfile (Ubuntu Bionic)
Importance: Undecided => High
** Changed in: makedumpfile (Ubuntu Xenial)
Importance: Undecided => High
** Changed in: makedumpfile (Ubuntu Xenial)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: makedumpfile (Ubuntu Bionic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
** Changed in: makedumpfile (Ubuntu Cosmic)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Confirmed
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Cosmic:
Confirmed
Status in makedumpfile source package in Disco:
Confirmed
Bug description:
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case
the subsystem is built-in). This was changed by commit 097a9ea0e48
("usb: make "nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Replace "nousb" option in kdump command-line for the newer "usbcore.nousb"
** Also affects: makedumpfile (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu Disco)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: Confirmed
** Also affects: makedumpfile (Ubuntu Xenial)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Replace "nousb" option in kdump command-line for the newer
"usbcore.nousb"
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
New
Status in makedumpfile source package in Bionic:
New
Status in makedumpfile source package in Cosmic:
New
Status in makedumpfile source package in Disco:
Confirmed
Bug description:
Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case
the subsystem is built-in). This was changed by commit 097a9ea0e48
("usb: make "nousb" a clear module parameter").
We need to take this into account in kdump-tools, or else we may boot
with USB in kdump even the command-line saying the opposite.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
