<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - cryptsetup: indefinite wait for encrypted swap device"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=90656">90656</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>cryptsetup: indefinite wait for encrypted swap device
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>systemd
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>x86-64 (AMD64)
          </td>
        </tr>

        <tr>
          <th>URL</th>
          <td>http://https://bugs.gentoo.org/show_bug.cgi?id=550358
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Linux (All)
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>general
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>ua_bugzilla_freedesktop@binary-island.eu
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>Updating to systemd 220 today (from 219) on a Gentoo system (~amd64), broke the
encrypted swap setup I had been using for ages now. Nothing else was touched,
except for the systemd upgrade.

The device is properly brought up and listed in /dev/mapper/ but
dev-mapper-crypt-swap.device stills waits indefinitely for the device to show
up, thus hanging the boot process if swap is listed in fstab.

This is definitely a regression in systemd -- and thus far, I have been unable
to figure out what is exactly causing it. :(

crypttab:
crypt-swap /dev/disk/by-id/md-uuid-f4f3dfc8:812e35f6:bfe78010:bc810f04
/dev/urandom
swap,cipher=aes-cbc-essiv:sha256,size=256,hash=sha512,x-systemd.device-timeout=15s

One more thing, maybe of relevance: I use dracut for the initrd... but have
been doing so for ages as well and I don't see how this could be relevant in
this case.

If there is anything I can do to help further debug/diagnose this, please let
me know and I will gladly do so.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>