** Package changed: hw-detect (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1602717
Title: hw-detect modprobes blindly, ignoring blacklists Status in linux package in Ubuntu: New Bug 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 <mauri...@br.ibm.com> / Lekshmi C. Pillai <lekshmi.cpil...@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) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1602717/+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