Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- ...
- Sep 16 14:39:01 pve systemd[1]: Started Proxmox VE replication runner.
- Sep 16 14:40:00 pve systemd[1]: Starting Proxmox VE replication runner...
- Sep 16 14:40:01 pve systemd[1]: pvesr.service: Succeeded.
- Sep 16 14:40:01 pve systemd[1]: Started Proxmox VE replication runner.
- Sep 16 14:41:00 pve systemd[1]: Starting Proxmox VE replication runner...
- Sep 16 14:41:01 pve systemd[1]: pvesr.service: Succeeded.
- Sep 16 14:41:01 pve systemd[1]: Started Proxmox VE replication runner.
- Sep 16 14:42:00 pve systemd[1]: Starting Proxmox VE replication runner...
- Sep 16 14:42:00 pve systemd[1]: pvesr.service: Succeeded.
- Sep 16 14:42:00 pve systemd[1]: Started Proxmox VE replication runner.
- Sep 16 14:42:19 pve kernel: [ 1455.297513] mce: [Hardware Error]: Machine check events logged
- Sep 16 14:43:00 pve systemd[1]: Starting Proxmox VE replication runner...
- Sep 16 14:43:00 pve systemd[1]: pvesr.service: Succeeded.
- Sep 16 14:43:00 pve systemd[1]: Started Proxmox VE replication runner.
- Sep 16 14:44:00 pve systemd[1]: Starting Proxmox VE replication runner...
- Sep 16 14:44:01 pve systemd[1]: pvesr.service: Succeeded.
- Sep 16 14:44:01 pve systemd[1]: Started Proxmox VE replication runner.
- Sep 16 14:45:00 pve systemd[1]: Starting Proxmox VE replication runner...
- Sep 16 14:45:01 pve systemd[1]: pvesr.service: Succeeded.
- Sep 16 14:45:01 pve systemd[1]: Started Proxmox VE replication runner.
- Sep 16 14:46:00 pve systemd[1]: Starting Proxmox VE replication runner...
- Sep 16 14:46:01 pve systemd[1]: pvesr.service: Succeeded.
- Sep 16 14:46:01 pve systemd[1]: Started Proxmox VE replication runner.
- ...
- Sep 16 08:49:15 pve kernel: [ 0.342415] rcu: Hierarchical SRCU implementation.
- Sep 16 08:49:15 pve kernel: [ 0.342751] random: crng done (trusting CPU's manufacturer)
- Sep 16 08:49:15 pve kernel: [ 0.343105] NMI watchdog: Enabled. Permanently consumes one hw-PMU counter.
- Sep 16 08:49:15 pve kernel: [ 0.343161] smp: Bringing up secondary CPUs ...
- Sep 16 08:49:15 pve kernel: [ 0.343204] x86: Booting SMP configuration:
- Sep 16 08:49:15 pve kernel: [ 0.343204] .... node #0, CPUs: #1 #2 #3 #4 #5 #6 #7
- Sep 16 08:49:15 pve kernel: [ 0.343725] mce: [Hardware Error]: Machine check events logged
- Sep 16 08:49:15 pve kernel: [ 0.343725] mce: [Hardware Error]: CPU 7: Machine Check: 0 Bank 2: b200000000000014
- Sep 16 08:49:15 pve kernel: [ 0.345144] mce: [Hardware Error]: TSC 0
- Sep 16 08:49:15 pve kernel: [ 0.345231] mce: [Hardware Error]: PROCESSOR 0:906ec TIME 1568612948 SOCKET 0 APIC e microcode 98
- Sep 16 08:49:15 pve kernel: [ 0.345334] #8
- Sep 16 08:49:15 pve kernel: [ 0.345632] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
- Sep 16 08:49:15 pve kernel: [ 0.345632] #9 #10 #11 #12 #13 #14 #15
- Sep 16 08:49:15 pve kernel: [ 0.345632] smp: Brought up 1 node, 16 CPUs
- Sep 16 08:49:15 pve kernel: [ 0.345632] smpboot: Max logical packages: 1
- Sep 16 08:49:15 pve kernel: [ 0.345632] smpboot: Total of 16 processors activated (115200.00 BogoMIPS)
- Sep 16 08:49:15 pve kernel: [ 0.350101] devtmpfs: initialized
- Sep 16 08:49:15 pve kernel: [ 0.350101] x86/mm: Memory block size: 128MB
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement