← Back to team overview

touch-packages team mailing list archive

[Bug 1535840] [NEW] systemd ignoring /etc/modules due to blacklist

 

Public bug reported:

I tried the daily build of 16.04 32-bit to test out the watchdog daemon
code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in
/etc/modules so it is loaded at boot-time, as watchdog timer modules are
not normally auto-loaded due to the risk of an unexpected reboot.

However I now find that systemd is choosing to ignore my command to load
the module in /etc/modules since it appears in the watchdog blacklist.
Typical syslog entries look like this:

Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is blacklisted
Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is blacklisted

This is just dumb! I have explicitly told the system to load the module,
an action that works perfectly well using modprobe or by adding it to
the start script for the watchdog, and yet systemd chooses to override
that because of the blacklist for auto-loaded modules (in this case in
/etc/modprobe.d/blacklist-watchdog.conf).

$ lsb_release -rd
Description:	Ubuntu Xenial Xerus (development branch)
Release:	16.04

$ apt-cache policy systemd
systemd:
  Installed: 228-4ubuntu1
  Candidate: 228-4ubuntu1
  Version table:
 *** 228-4ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
        100 /var/lib/dpkg/status

What I expect to happen is modules added to /etc/modules are loaded at
boot time, and not subject to the blacklist for hardware detect /
automatic loading.

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1535840

Title:
  systemd ignoring /etc/modules due to blacklist

Status in systemd package in Ubuntu:
  New

Bug description:
  I tried the daily build of 16.04 32-bit to test out the watchdog
  daemon code. Usually (Ubuntu 10.04-14.04) I add the watchdog module in
  /etc/modules so it is loaded at boot-time, as watchdog timer modules
  are not normally auto-loaded due to the risk of an unexpected reboot.

  However I now find that systemd is choosing to ignore my command to
  load the module in /etc/modules since it appears in the watchdog
  blacklist. Typical syslog entries look like this:

  Jan 19 16:46:14 ubuntu systemd-modules-load[337]: Module 'softdog' is blacklisted
  Jan 19 17:53:23 ubuntu systemd-modules-load[342]: Module 'softdog' is blacklisted

  This is just dumb! I have explicitly told the system to load the
  module, an action that works perfectly well using modprobe or by
  adding it to the start script for the watchdog, and yet systemd
  chooses to override that because of the blacklist for auto-loaded
  modules (in this case in /etc/modprobe.d/blacklist-watchdog.conf).

  $ lsb_release -rd
  Description:	Ubuntu Xenial Xerus (development branch)
  Release:	16.04

  $ apt-cache policy systemd
  systemd:
    Installed: 228-4ubuntu1
    Candidate: 228-4ubuntu1
    Version table:
   *** 228-4ubuntu1 500
          500 http://us.archive.ubuntu.com/ubuntu xenial/main i386 Packages
          100 /var/lib/dpkg/status

  What I expect to happen is modules added to /etc/modules are loaded at
  boot time, and not subject to the blacklist for hardware detect /
  automatic loading.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1535840/+subscriptions