** 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
