[Bug 1602717] Re: modprobe does not honor blacklist options in kernel cmdline unless -b is used (at least on the installer)

[Kevin W. Rudd]

Sorry.  The original problem description and mirrored package may be a
bit misleading.  I believe that real issue is that the installer is
*not* using "-b", so any blacklist options passed via the kernel cmdline
are not being honored.  Tagging the package as "debian-installer" to
focus on the install-time issue of needing to be able to blacklist
modules during the install.  Passing blacklist options are reported to
work in 16.04 Pre-GA, so it appears that something changed (either in
the installer, or in modprobe handling).  But, the bottom line problem
we need to have solved is getting the installer to honor any
blacklisting passed on the cmdline.

** Package changed: linux (Ubuntu) => debian-installer (Ubuntu)

** Changed in: debian-installer (Ubuntu)
       Status: Invalid => New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to debian-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1602717

Title:
  modprobe does not honor blacklist options in kernel cmdline unless -b
  is used (at least on the installer)

Status in debian-installer 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 <mauricfo at br.ibm.com> / Lekshmi C. Pillai <lekshmi.cpillai at 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 at 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/debian-installer/+bug/1602717/+subscriptions