Arch Linux

sh4wn

Member

Registered: 2013-09-17

Posts: 8

Your BIOS is broken, DMAR reported at address 0 - Can't boot anymore

Hi all,

Yesterday evening I did my weekly Arch update. But I was confronted with an unpleasant surprise this morning: my desktop doesn't boot anymore. After showing a few messages of fsck, it enters the systemd emergency mode. I can login with my root password. From here I can browse my files, but I have no internet connection, and if I try to start the service with systemd (systemctl start NetworkManager) I end up in the systemd emergency mode again, asking to enter my root password to login.

Kernel 3.12.6-1
Notable errors in journalctl -xb

WARNING: CPU: 0 PID: 0 at drivers/iommu/dmar.c:488 warn_invalid_dmar+0x7e/0x9()
Your BIOS is broken; DMAR reported at address 0!
BIOS vendor: American Megatrends Inc.; Ver: F7; Product Version: To be filled by O.E.M.
Modules linked in:
CPU: 0 PID: 0 Comm: swapper Not tainted 3.12.6-1-ARCH #1
Hardware name: Gigabyte Technology Co., Ltd. Z87X-D3H/Z87-D3H-CF BIOS F7 08/02/2013
...

More:

ACPI Warning: 0x0000000000001828-0x000000000000182f SystemIO conflicts with Region \PMIO 1 (20130725/utaddress251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
ACPI Warning: 0x0000000000001c30-0x0000000000001c3f SystemIO conflicts with Region \GPRL 1 (20130725/utaddress251)
ACPI Warning: 0x0000000000001c30-0x0000000000001c3f SystemIO conflicts with Region \GPR_ 2 (20130725/utaddress251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
ACPI Warning: 0x0000000000001c00-0x0000000000001c2f SystemIO conflicts with Region \GPRL 1 (20130725/utaddress251)
ACPI Warning: 0x0000000000001c00-0x0000000000001c2f SystemIO conflicts with Region \GPR_ 2 (20130725/utaddress251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

Another bit further:

ACPI Warning: 0x000000000000f040-0x000000000000f05f SystemIO conflicts with Region \_SB_.PCI0.SBUS.SMBI 1 (20130725/utaddress-251)
ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver

Another bit further:

systemd-udevd[185]: Error calling EVIOCSKEYCODE: Invalid argument
systemd-udevd[185]: Error calling EVIOCSKEYCODE: Invalid argument

Another bit further:

systemd[1]: Job tmpfs.device/start timed out
systemd[1]: Timed out waiting for device tmpfs.device

...

systemd[1]: Dependency failed for File System Check on /tmpfs

...

systemd[1]: Dependency failed for /tmp
-- Subject: Unit tmp.mount has failed

..

systemd[1]: Dependency failed for Local File Systems

Well basically: it seems that systemd is unable to mount /tmp (which I configured to be located in RAM using tmpfs). And because of this, everything fails, and systemd starts the emergency mode. But what caused this all of the sudden? And more important, how do I fix it? Anyone an idea what's wrong here?

I did upgrade my BIOS version from F5 to F7, but that didn't fix the issue.

Thanks in advance.

sh4wn

Member

Registered: 2013-09-17

Posts: 8

Re: Your BIOS is broken, DMAR reported at address 0 - Can't boot anymore

Ok, I fixed it myself. The BIOS error is not related. The issue I had was in my fstab file. I had:

tmpfs /tmp tmpfs nodec,nosuid 0 2

The last field should have been a zero, which disables fsck on this filesystem. After I changed that, the system successfully boots again.