| 2016-07-13 14:39:48 |
bugproxy |
bug |
|
|
added bug |
| 2016-07-13 14:39:50 |
bugproxy |
tags |
|
architecture-ppc64le bugnameltc-143679 severity-high targetmilestone-inin16041 |
|
| 2016-07-13 14:39:51 |
bugproxy |
ubuntu: assignee |
|
Taco Screen team (taco-screen-team) |
|
| 2016-07-13 14:40:01 |
bugproxy |
affects |
ubuntu |
linux (Ubuntu) |
|
| 2016-07-18 13:36:06 |
Tim Gardner |
linux (Ubuntu): status |
New |
Invalid |
|
| 2016-07-18 14:51:46 |
Kevin W. Rudd |
affects |
linux (Ubuntu) |
debian-installer (Ubuntu) |
|
| 2016-07-18 14:51:46 |
Kevin W. Rudd |
debian-installer (Ubuntu): status |
Invalid |
New |
|
| 2016-07-18 16:13:54 |
Adam Conrad |
affects |
debian-installer (Ubuntu) |
hw-detect (Ubuntu) |
|
| 2016-07-18 16:14:15 |
Adam Conrad |
summary |
modprobe does not honor blacklist options in kernel cmdline unless -b is used (at least on the installer) |
hw-detect modprobes blindly, ignoring blacklists |
|
| 2016-07-21 15:45:32 |
bugproxy |
affects |
hw-detect (Ubuntu) |
linux (Ubuntu) |
|
| 2016-07-21 16:00:45 |
Steve Langasek |
affects |
linux (Ubuntu) |
hw-detect (Ubuntu) |
|
| 2016-07-21 16:08:51 |
bugproxy |
affects |
hw-detect (Ubuntu) |
linux (Ubuntu) |
|
| 2016-07-21 19:09:46 |
Adam Conrad |
affects |
linux (Ubuntu) |
hw-detect (Ubuntu) |
|
| 2016-07-21 19:25:32 |
bugproxy |
affects |
hw-detect (Ubuntu) |
linux (Ubuntu) |
|
| 2016-07-22 06:20:09 |
Adam Conrad |
affects |
linux (Ubuntu) |
hw-detect (Ubuntu) |
|
| 2016-08-24 16:10:32 |
bugproxy |
tags |
architecture-ppc64le bugnameltc-143679 severity-high targetmilestone-inin16041 |
architecture-ppc64le bugnameltc-143679 severity-high targetmilestone-inin16042 |
|
| 2016-08-24 16:20:36 |
bugproxy |
attachment added |
|
hw-detect_modprobe-b.debdiff https://bugs.launchpad.net/bugs/1602717/+attachment/4727085/+files/hw-detect_modprobe-b.debdiff |
|
| 2016-09-27 18:55:13 |
Steve Langasek |
hw-detect (Ubuntu): assignee |
Taco Screen team (taco-screen-team) |
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2016-09-27 18:55:15 |
Steve Langasek |
hw-detect (Ubuntu): status |
New |
Triaged |
|
| 2016-09-27 18:55:17 |
Steve Langasek |
hw-detect (Ubuntu): importance |
Undecided |
Low |
|
| 2016-09-28 20:15:01 |
Mathieu Trudel-Lapierre |
hw-detect (Ubuntu): status |
Triaged |
In Progress |
|
| 2016-09-28 20:15:08 |
Mathieu Trudel-Lapierre |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-09-28 20:15:08 |
Mathieu Trudel-Lapierre |
bug task added |
|
hw-detect (Ubuntu Xenial) |
|
| 2016-09-28 20:15:49 |
Mathieu Trudel-Lapierre |
hw-detect (Ubuntu Xenial): status |
New |
In Progress |
|
| 2016-09-28 20:15:53 |
Mathieu Trudel-Lapierre |
hw-detect (Ubuntu Xenial): importance |
Undecided |
Low |
|
| 2016-09-28 20:16:00 |
Mathieu Trudel-Lapierre |
hw-detect (Ubuntu Xenial): assignee |
|
Mathieu Trudel-Lapierre (cyphermox) |
|
| 2016-09-29 14:03:15 |
Mathieu Trudel-Lapierre |
description |
== Comment: #0 - Mauricio Faria De Oliveira - 2016-07-11 18:47:59 ==
---Problem Description---
modprobe does not honor blacklist options in kernel cmdline unless -b is used (at least on the installer)
The modprobe.blacklist option is required as a work-around until a solution to a device-driver bug is found (IBM LTC bug 138273).
I've gone through the code of the kmod src pkg, but didn't spot anything obvious.
Passing along to the Ubuntu team.
Contact Information = Mauricio Faria de Oliveira <mauricfo@br.ibm.com> / Lekshmi C. Pillai <lekshmi.cpillai@in.ibm.com>
---Steps to Reproduce---
Boot the installer w/ this boot/kernel cmdline option (the alias w/ dashes is not required, but is here just in case):
modprobe.blacklist=scsi_dh_alua,scsi-dh-alua
On the dialog for username/password, select Go Back, then Exit to shell:
The blacklist is detected/present in the config:
~ # modprobe -c | grep alua
blacklist scsi_dh_alua
blacklist scsi-dh-alua
But the module is insmod-ed anyway:
~ # modprobe -v -n scsi-dh-alua
insmod /lib/modules/4.4.0-21-generic/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko
Unless -b is used:
~ # modprobe -v -n -b scsi-dh-alua
~ #
Installer kernel:
[ 0.000000] Linux version 4.4.0-21-generic (buildd@bos01-ppc64el-017) (gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:30:22 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6) |
[Impact]
Any system requiring specific modules to be blacklisted at install-time, when using server or alternate images.
[Test cases]
Boot the installer w/ this boot/kernel cmdline option (the alias w/ dashes is not required, but is here just in case):
modprobe.blacklist=scsi_dh_alua,scsi-dh-alua
On the dialog for username/password, select Go Back, then Exit to shell:
The blacklist is detected/present in the config:
~ # modprobe -c | grep alua
blacklist scsi_dh_alua
blacklist scsi-dh-alua
But the module is insmod-ed anyway:
~ # modprobe -v -n scsi-dh-alua
insmod /lib/modules/4.4.0-21-generic/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko
Unless -b is used:
~ # modprobe -v -n -b scsi-dh-alua
~ #
[Regression Potential]
Failure to load kernel modules at boot time due to unexpectedly blacklisted modules would consistute a regression for this bug report.
== Comment: #0 - Mauricio Faria De Oliveira - 2016-07-11 18:47:59 ==
---Problem Description---
modprobe does not honor blacklist options in kernel cmdline unless -b is used (at least on the installer)
The modprobe.blacklist option is required as a work-around until a solution to a device-driver bug is found (IBM LTC bug 138273).
I've gone through the code of the kmod src pkg, but didn't spot anything obvious.
Passing along to the Ubuntu team.
Contact Information = Mauricio Faria de Oliveira <mauricfo@br.ibm.com> / Lekshmi C. Pillai <lekshmi.cpillai@in.ibm.com>
---Steps to Reproduce---
Boot the installer w/ this boot/kernel cmdline option (the alias w/ dashes is not required, but is here just in case):
modprobe.blacklist=scsi_dh_alua,scsi-dh-alua
On the dialog for username/password, select Go Back, then Exit to shell:
The blacklist is detected/present in the config:
~ # modprobe -c | grep alua
blacklist scsi_dh_alua
blacklist scsi-dh-alua
But the module is insmod-ed anyway:
~ # modprobe -v -n scsi-dh-alua
insmod /lib/modules/4.4.0-21-generic/kernel/drivers/scsi/device_handler/scsi_dh_alua.ko
Unless -b is used:
~ # modprobe -v -n -b scsi-dh-alua
~ #
Installer kernel:
[ 0.000000] Linux version 4.4.0-21-generic (buildd@bos01-ppc64el-017) (gcc version 5.3.1 20160413 (Ubuntu/IBM 5.3.1-14ubuntu2) ) #37-Ubuntu SMP Mon Apr 18 18:30:22 UTC 2016 (Ubuntu 4.4.0-21.37-generic 4.4.6) |
|
| 2016-09-29 18:14:06 |
Brian Murray |
hw-detect (Ubuntu Xenial): status |
In Progress |
Fix Committed |
|
| 2016-09-29 18:14:08 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2016-09-29 18:14:14 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2016-09-29 18:14:18 |
Brian Murray |
tags |
architecture-ppc64le bugnameltc-143679 severity-high targetmilestone-inin16042 |
architecture-ppc64le bugnameltc-143679 severity-high targetmilestone-inin16042 verification-needed |
|
| 2016-09-29 23:39:38 |
bugproxy |
tags |
architecture-ppc64le bugnameltc-143679 severity-high targetmilestone-inin16042 verification-needed |
architecture-ppc64le bugnameltc-143679 severity-high targetmilestone-inin16042 verification-done |
|
| 2016-09-30 23:29:21 |
Launchpad Janitor |
hw-detect (Ubuntu): status |
In Progress |
Fix Released |
|
| 2016-10-12 12:05:56 |
Launchpad Janitor |
hw-detect (Ubuntu Xenial): status |
Fix Committed |
Fix Released |
|
| 2016-10-12 12:06:04 |
Chris J Arges |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
