-- Logs begin at Thu 2017-03-23 04:39:29 UTC, end at Thu 2017-03-23 12:17:01 UTC. --
Mar 23 04:39:29 ubuntu kernel: WARNING: x1-x3 nonzero in violation of boot protocol:
                                       x1: 0000000000000000
                                       x2: 0000000002faf080
                                       x3: 0000000000000001
                               This indicates a broken bootloader or old kernel
Mar 23 04:39:29 ubuntu kernel: dmi: Firmware registration failed.
Mar 23 04:39:29 ubuntu kernel: pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
Mar 23 04:39:29 ubuntu kernel: pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
Mar 23 04:39:29 ubuntu kernel: pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
Mar 23 04:39:29 ubuntu kernel: pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
Mar 23 04:39:29 ubuntu kernel: pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
Mar 23 04:39:29 ubuntu kernel: pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x4 may corrupt adjacent RW1C bits
Mar 23 04:39:29 ubuntu kernel: pci_bus 0000:00: 2-byte config write to 0000:00:00.0 offset 0x3e may corrupt adjacent RW1C bits
Mar 23 04:39:29 ubuntu kernel: pci_bus 0000:01: 2-byte config write to 0000:01:00.0 offset 0x4 may corrupt adjacent RW1C bits
Mar 23 04:39:29 ubuntu kernel: pci_bus 0000:01: 2-byte config write to 0000:01:00.0 offset 0x4 may corrupt adjacent RW1C bits
Mar 23 04:39:29 ubuntu kernel: pci_bus 0000:01: 2-byte config write to 0000:01:00.0 offset 0x4 may corrupt adjacent RW1C bits
Mar 23 04:39:29 ubuntu kernel: cacheinfo: Unable to detect cache hierarchy for CPU 0
Mar 23 04:39:29 ubuntu kernel: xgene-ahci 1a800000.sata: port 0 is not capable of FBS
Mar 23 04:39:29 ubuntu kernel: xgene-ahci 1a800000.sata: port 1 is not capable of FBS
Mar 23 04:39:29 ubuntu kernel: pci_generic_config_write32: 47 callbacks suppressed
Mar 23 04:39:29 ubuntu kernel: pci_bus 0000:01: 2-byte config write to 0000:01:00.0 offset 0x68 may corrupt adjacent RW1C bits
Mar 23 04:39:29 ubuntu kernel: pci_bus 0000:01: 2-byte config write to 0000:01:00.0 offset 0x70 may corrupt adjacent RW1C bits
Mar 23 04:39:29 ubuntu kernel: mlx4_core 0000:01:00.0: PCIe BW is different than device's capability
Mar 23 04:39:29 ubuntu kernel: pci_bus 0000:01: 2-byte config write to 0000:01:00.0 offset 0x9e may corrupt adjacent RW1C bits
Mar 23 04:39:29 ubuntu kernel: mlx4_en: 0000:01:00.0: Port 1: Using 64 TX rings
Mar 23 04:39:29 ubuntu kernel: mlx4_en: 0000:01:00.0: Port 1: Using 4 RX rings
Mar 23 04:39:29 ubuntu kernel: mlx4_en: 0000:01:00.0: Port 1:   frag:0 - size:1522 prefix:0 stride:1536
Mar 23 04:39:29 ubuntu kernel: mlx4_en: 0000:01:00.0: Port 1: Initializing port
Mar 23 04:39:29 ubuntu kernel: mlx4_en: 0000:01:00.0: Port 2: Using 64 TX rings
Mar 23 04:39:29 ubuntu kernel: mlx4_en: 0000:01:00.0: Port 2: Using 4 RX rings
Mar 23 04:39:29 ubuntu kernel: mlx4_en: 0000:01:00.0: Port 2:   frag:0 - size:1522 prefix:0 stride:1536
Mar 23 04:39:29 ubuntu kernel: mlx4_en: 0000:01:00.0: Port 2: Initializing port
Mar 23 04:39:32 ubuntu systemd-tmpfiles[793]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Mar 23 04:39:34 ubuntu kernel: mlx4_en: enp1s0:   frag:0 - size:1522 prefix:0 stride:1536
Mar 23 04:39:34 ubuntu kernel: mlx4_en: enp1s0d1:   frag:0 - size:1522 prefix:0 stride:1536
Mar 23 08:35:52 hostname kernel: cgroup: new mount options do not match the existing superblock, will be ignored
Mar 23 04:40:04 hostname iscsid[1308]: iSCSI logger with pid=1311 started!
Mar 23 04:40:05 hostname iscsid[1311]: iSCSI daemon with pid=1313 started!
Mar 23 08:36:06 hostname systemd[1]: Failed to start Apply the settings specified in cloud-config.
Mar 23 08:36:06 hostname systemd[1]: cloud-config.service: Failed with result 'exit-code'.
Mar 23 08:50:16 hostname systemd-tmpfiles[5207]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
Mar 23 09:00:01 hostname systemd-udevd[5695]: Process '/sbin/crda' failed with exit code 251.
Mar 23 09:00:04 hostname systemd-udevd[5703]: Process '/sbin/crda' failed with exit code 251.
Mar 23 09:00:07 hostname systemd-udevd[5706]: Process '/sbin/crda' failed with exit code 251.
Mar 23 09:00:11 hostname systemd-udevd[5708]: Process '/sbin/crda' failed with exit code 251.
Mar 23 09:00:14 hostname systemd-udevd[5710]: Process '/sbin/crda' failed with exit code 251.
Mar 23 09:00:17 hostname systemd-udevd[5712]: Process '/sbin/crda' failed with exit code 251.
Mar 23 09:00:21 hostname systemd-udevd[5714]: Process '/sbin/crda' failed with exit code 251.
Mar 23 09:00:24 hostname systemd-udevd[5716]: Process '/sbin/crda' failed with exit code 251.
Mar 23 09:00:27 hostname systemd-udevd[5718]: Process '/sbin/crda' failed with exit code 251.
Mar 23 09:00:31 hostname systemd-udevd[5720]: Process '/sbin/crda' failed with exit code 251.
Mar 23 09:00:34 hostname systemd-udevd[5722]: Process '/sbin/crda' failed with exit code 251.
Mar 23 10:44:31 hostname kernel: pgd = ffff800fa6c16000
Mar 23 10:44:31 hostname kernel: [18300750134] *pgd=0000000000000000
Mar 23 10:44:31 hostname kernel: 
Mar 23 10:44:31 hostname kernel: CPU: 7 PID: 1429 Comm: systemd-resolve Not tainted 4.10.0-13-generic #15-Ubuntu
Mar 23 10:44:31 hostname kernel: Hardware name: HP ProLiant m400 Server Cartridge (DT)
Mar 23 10:44:31 hostname kernel: task: ffff800fb34a0000 task.stack: ffff800fa6b40000
Mar 23 10:44:31 hostname kernel: PC is at 0xffff9406c600
Mar 23 10:44:31 hostname kernel: LR is at 0xffff9406cdc0
Mar 23 10:44:31 hostname kernel: pc : [<0000ffff9406c600>] lr : [<0000ffff9406cdc0>] pstate: 60000000
Mar 23 10:44:31 hostname kernel: sp : 0000ffffd0fe4840
Mar 23 10:44:31 hostname kernel: x29: 0000ffffd0fe4840 x28: 0000ffffd0fe5228 
Mar 23 10:44:31 hostname kernel: x27: 0000aaaabf3599b0 x26: 0000ffffd0fe5068 
Mar 23 10:44:31 hostname kernel: x25: 0000aaaab9c85590 x24: 0000aaaab9ca8000 
Mar 23 10:44:31 hostname kernel: x23: 0000000000000001 x22: 0000000000000000 
Mar 23 10:44:31 hostname kernel: x21: 0000ffffd0fe48c0 x20: 0000000000000000 
Mar 23 10:44:31 hostname kernel: x19: 0000018300750105 x18: 0000000000000000 
Mar 23 10:44:31 hostname kernel: x17: 0000ffff9406ce80 x16: 0000aaaab9ca8740 
Mar 23 10:44:31 hostname kernel: x15: 000030f82422c2a0 x14: fffffffffffffff8 
Mar 23 10:44:31 hostname kernel: x13: 0000000058d3a70f x12: 0000000000000018 
Mar 23 10:44:31 hostname kernel: x11: 0000000000000001 x10: 0000000000000064 
Mar 23 10:44:31 hostname kernel: x9 : 0000aaaabf33d5c0 x8 : 0000aaaabf33bca0 
Mar 23 10:44:31 hostname kernel: x7 : 0000000000000000 x6 : 0000000000000000 
Mar 23 10:44:31 hostname kernel: x5 : 00000000ffffffff x4 : 0000ffff93df19a0 
Mar 23 10:44:31 hostname kernel: x3 : 0000018300750105 x2 : 0000ffffd0fe48c0 
Mar 23 10:44:31 hostname kernel: x1 : 0000ffffd0fe48c8 x0 : 0000018300750105 
Mar 23 10:44:31 hostname kernel: 
Mar 23 10:44:31 hostname systemd[1]: systemd-resolved.service: Main process exited, code=killed, status=11/SEGV
Mar 23 10:44:31 hostname systemd[1]: systemd-resolved.service: Failed with result 'signal'.