Acpi | Ibm0068

If you use a ThinkPad or certain Lenovo laptops on Linux, you may have seen ACPI errors referencing “IBM0068” in dmesg or journalctl. These messages can be confusing and alarming, but in many cases they’re harmless or fixable. This post explains what the IBM0068 device is, why the kernel logs the error, how to diagnose its impact, and practical fixes and workarounds.

Without proper handling of IBM0068, Linux may not notice when you swap an UltraBay device.

Check if ACPI events are reaching the kernel: acpi ibm0068

grep . /sys/bus/acpi/devices/IBM0068:*/status
# Expected: 0x0f (device present and functioning)

Monitor live events when you release the latch:

acpi_listen
# When you pull the latch, you should see:
# ibm/hotkey HKEY 00000080 00006010  (example)
# or direct ACPI event: ibm0068:00 00000080 00000001

Force a rescan of the ATA bus (if SATA UltraBay): If you use a ThinkPad or certain Lenovo

echo "- - -" > /sys/class/scsi_host/hostX/scan   # replace X with your bay host number

Create a script in /etc/initramfs-tools/scripts/init-top/ that greps and removes ACPI lines from dmesg. This is overkill for 99% of users.

If you searched for "acpi ibm0068", you may be seeing: Monitor live events when you release the latch:

When you boot a ThinkPad with such a bay, you might see:

ACPI: IBM0068: found UltraBay SATA controller
ata_generic 0000:00:...: probe
scsi hostX: ata_generic
...
ataX: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
ataX.00: ATA-9: device in bay

Or, if using ahci:

ahci 0000:00:1f.2: AHCI 0001.0300 32 slots 4 ports 3 Gbps 0x3 impl SATA mode
...
ata3: SATA link up (UltraBay device detected)