How to Fix ‘Gave up waiting for suspend/resume device’ in Ubuntu

Powering on an Ubuntu laptop or desktop only to have the startup sequence freeze for 30 to 90 seconds while displaying the warning message “W: Possible missing firmware… Gave up waiting for suspend/resume device” or “Gave up waiting for suspend/resume device /dev/disk/by-uuid/…” significantly prolongs system boot times.

The Linux kernel incorporates a resume subsystem designed to restore system memory state from swap partitions after hibernation. During early boot, the Initial RAM Filesystem (initramfs) reads the designated resume swap partition from /etc/initramfs-tools/conf.d/resume. When a user resizes partitions, reformats a swap partition, switches from a swap partition to a swapfile, or performs a clean distribution upgrade, the partition’s Universally Unique Identifier (UUID) changes. The initramfs scripts halt the boot sequence and wait for the specified device timeout (typically 90 seconds) before abandoning the attempt and proceeding with normal system initialization.

Failure Point Technical Mechanism Effective Resolution
Stale Swap UUID in initramfs /etc/initramfs-tools/conf.d/resume references obsolete partition UUID Update file with active swap UUID or set RESUME=none
Switched to Swapfile System migrated from dedicated swap partition to /swapfile Disable resume device waiting or configure swapfile resume offsets
Mismatched /etc/fstab Mapping Filesystem table contains outdated UUID for swap mount point Synchronise /etc/fstab with current blkid swap partition UUID
Outdated GRUB Kernel Resume Parameter GRUB_CMDLINE_LINUX_DEFAULT contains stale resume=UUID=… flag Remove or correct resume argument in /etc/default/grub

Method 1: Identify Current Swap UUID and Update Resume Configuration

The definitive fix is to ensure that the initramfs resume configuration points to the exact active swap partition on your system.

  1. Open a terminal in Ubuntu.
  2. Identify your active swap partition and its current UUID by executing:
    sudo blkid | grep swap

    Or inspect active swap interfaces:

    swapon --show
  3. Note down the current UUID string (e.g. UUID=a1b2c3d4-e5f6-7890-abcd-ef1234567890).
  4. Open the resume configuration file using an administrative editor:
    sudo nano /etc/initramfs-tools/conf.d/resume
  5. If the file contains an obsolete UUID, update the line to match your current partition:
    RESUME=UUID=a1b2c3d4-e5f6-7890-abcd-ef1234567890
  6. If your system does not utilize hibernation (suspend-to-disk) or uses a standard swapfile, simply disable the resume check entirely by editing the line to read:
    RESUME=none
  7. Save the file by pressing Ctrl + O, then Enter, and exit using Ctrl + X.
  8. Rebuild the initial RAM filesystem to bake the updated configuration into boot binaries:
    sudo update-initramfs -u -k all
  9. Restart your computer. The 90-second boot pause will be completely eliminated.

Method 2: Verify and Synchronise /etc/fstab Swap Entries

If /etc/fstab references an outdated swap partition UUID, the systemd partition generator will also stall while waiting for the device.

  1. Open /etc/fstab in your terminal editor:
    sudo nano /etc/fstab
  2. Locate the line configuring the swap partition (typically marked with none swap sw 0 0).
  3. Verify that the UUID matches the output from sudo blkid.
  4. If the UUID is incorrect, replace it with the verified identifier.
  5. Save and close the file.

Method 3: Clean Stale Kernel Parameters in GRUB

If a legacy installation script hardcoded a resume parameter directly into the GRUB bootloader parameters, clean the configuration string.

  1. Open the default GRUB configuration file:
    sudo nano /etc/default/grub
  2. Locate the line starting with GRUB_CMDLINE_LINUX_DEFAULT.
  3. If the string contains resume=UUID=... with an outdated identifier, remove the resume=... parameter (or update it to the matching UUID).
  4. Save the file and update the GRUB bootloader:
    sudo update-grub

Benchmarking Boot Performance in Ubuntu

To verify that startup delays have been fully resolved, run systemd-analyze in your terminal. This command displays the exact time consumed by the kernel, initramfs, and userspace daemons. Execute systemd-analyze blame to audit any remaining services contributing to boot latency.

Get the best tech tips delivered straight to your inbox.

Join thousands of readers mastering Apple, Google, Microsoft, and Linux.