hi  I just checking the syslog  as Fix Common Issues finds errors  but never shows any errors

 

i tried googling some of these warrnings but i cant find any info... if anyone knows be great  so i can fix the errors... also i changed the ssh port  yet its still stating 22 also... and i try  ssh root@tower:2000   and i cant connect

but maybe you guys know

 

here is if the warnings 

 

Apr 17 20:40:43 Tower kernel: Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA
Apr 17 20:40:43 Tower kernel: ACPI: Early table checksum verification disabled
Apr 17 20:40:43 Tower kernel: pci 0000:03:00.0: BAR 9: failed to assign [mem size 0x00400000 64bit]
Apr 17 20:40:43 Tower kernel: pci 0000:03:00.0: BAR 7: failed to assign [mem size 0x00040000 64bit]
Apr 17 20:40:43 Tower kernel: floppy0: no floppy controllers found
Apr 17 20:40:43 Tower kernel: random: 6 urandom warning(s) missed due to ratelimiting
Apr 17 20:40:43 Tower kernel: EDAC sbridge: Failed to register device with error -19.
Apr 17 20:40:43 Tower kernel: EDAC sbridge: Failed to register device with error -19.
Apr 17 20:40:43 Tower kernel: EDAC sbridge: Failed to register device with error -19.
Apr 17 20:40:43 Tower kernel: EDAC sbridge: Failed to register device with error -19.
Apr 17 20:40:44 Tower kernel: EDAC sbridge: Failed to register device with error -19.
Apr 17 20:40:44 Tower kernel: EDAC sbridge: Failed to register device with error -19.
Apr 17 20:40:44 Tower kernel: EDAC sbridge: Failed to register device with error -19.
Apr 17 20:40:44 Tower kernel: EDAC sbridge: Failed to register device with error -19.
Apr 17 20:40:44 Tower kernel: EDAC sbridge: Failed to register device with error -19.
Apr 17 20:40:44 Tower kernel: EDAC sbridge: Failed to register device with error -19.
Apr 17 20:40:44 Tower kernel: EDAC sbridge: Failed to register device with error -19.
Apr 17 20:40:44 Tower rpc.statd[1808]: Failed to read /var/lib/nfs/state: Success
Apr 17 20:40:44 Tower sshd[1826]: Server listening on 0.0.0.0 port 22.
Apr 17 20:40:44 Tower sshd[1826]: Server listening on :: port 22.
Apr 17 20:40:44 Tower ntpd[1838]: bind(19) AF_INET6 fe80::68a0:9cff:fef4:afc1%10#123 flags 0x11 failed: Cannot assign requested address
Apr 17 20:40:44 Tower ntpd[1838]: failed to init interface for address fe80::68a0:9cff:fef4:afc1%10
Apr 17 20:41:00 Tower sshd[1826]: Received signal 15; terminating.
Apr 17 20:41:01 Tower sshd[12337]: Server listening on 0.0.0.0 port 2000.
Apr 17 20:41:01 Tower sshd[12337]: Server listening on :: port 2000.
Apr 17 20:41:02 Tower avahi-daemon[12865]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!

on my second server i get these errors

 

Apr 17 20:58:29 mitchsserver kernel: ACPI: Early table checksum verification disabled
Apr 17 20:58:29 mitchsserver kernel: ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has valid Length but zero Address: 0x0000000000000000/0x1 (20180531/tbfadt-624)
Apr 17 20:58:29 mitchsserver kernel: floppy0: no floppy controllers found
Apr 17 20:58:29 mitchsserver kernel: random: 6 urandom warning(s) missed due to ratelimiting
Apr 17 20:58:37 mitchsserver rpc.statd[1705]: Failed to read /var/lib/nfs/state: Success
Apr 17 20:58:58 mitchsserver sshd[1723]: Received signal 15; terminating.
Apr 17 20:58:59 mitchsserver sshd[12069]: Server listening on 0.0.0.0 port 22.
Apr 17 20:58:59 mitchsserver sshd[12069]: Server listening on :: port 22.
Apr 17 20:59:00 mitchsserver avahi-daemon[12167]: WARNING: No NSS support for mDNS detected, consider installing nss-mdns!
Apr 17 21:00:50 mitchsserver root: modprobe: ERROR: could not insert 'kvm_amd': Operation not supported
Apr 17 21:00:51 mitchsserver emhttpd: error: send_file, 139: Broken pipe (32): sendfile: /usr/local/emhttp/update.htm
Apr 17 21:04:20 mitchsserver ntpd[1735]: frequency error 797 PPM exceeds tolerance 500 PPM

 

 

and im guessing the login  for the port  22 is ok  as i checked the Login button and that's what showed

Edited April 18, 20197 yr by comet424

A bios update might fix some of the ACPI related errors, but none of those are something to worry about.