September 6, 201510 yr I have some warnings in syslog. Do i have to do anything about these warnings or it is safe to use? Full syslog is attached. Sep 7 01:02:28 Tower kernel: ACPI BIOS Warning (bug): Optional FADT field Pm2ControlBlock has zero address or length: 0x0000000000000000/0x1 (20150410/tbfadt-654) Sep 7 01:02:28 Tower kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 64/32 (20150410/tbfadt-623) Sep 7 01:02:28 Tower kernel: ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B07 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\SOR1) (20150410/utaddress-254) Sep 7 01:02:28 Tower kernel: ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B07 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B2F (\SMRG) (20150410/utaddress-254) Sep 7 01:02:28 Tower kernel: ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B07 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B2F (\_SB_.PCI0.SBRG.ASOC.SMRG) (20150410/utaddress-254) tower-syslog-20150907-0108.zip
September 7, 201510 yr I have some warnings in syslog. Do i have to do anything about these warnings or it is safe to use? Nothing to do, safe to use. Most syslogs have ACPI messages, as the vendors and BIOS writers cater to what Windows wants, not to Linux. Sometimes when we see a lot of ACPI messages, we recommend looking for a BIOS update. There's absolutely nothing else you can do. A BIOS update *may* remove a few of them.
September 7, 201510 yr Author I have some warnings in syslog. Do i have to do anything about these warnings or it is safe to use? Nothing to do, safe to use. Most syslogs have ACPI messages, as the vendors and BIOS writers cater to what Windows wants, not to Linux. Sometimes when we see a lot of ACPI messages, we recommend looking for a BIOS update. There's absolutely nothing else you can do. A BIOS update *may* remove a few of them. RobJ thanks for your reply. Actually i did a BIOS update yesterday. and after reading your reply i search for old syslogs to find out if this warnings are new or not. And see that they are not new except below line. My old syslog is from unraid 5.x maybe that can make this difference. Sep 7 01:02:28 Tower kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 64/32 (20150410/tbfadt-623) It is a bit offtopic but i see that there are no syslog files after 17.06.2015 in the /boot/logs/ dir. I think that after upgrading to unraid 6 either it is not saving logs to flash when restarting syslogd or after that time there arent any syslogd restarts
September 7, 201510 yr Actually i did a BIOS update yesterday. and after reading your reply i search for old syslogs to find out if this warnings are new or not. And see that they are not new except below line. My old syslog is from unraid 5.x maybe that can make this difference. Sep 7 01:02:28 Tower kernel: ACPI BIOS Warning (bug): 32/64X length mismatch in FADT/Gpe0Block: 64/32 (20150410/tbfadt-623) That's probably because v6 is 64 bit. It is a bit offtopic but i see that there are no syslog files after 17.06.2015 in the /boot/logs/ dir. I think that after upgrading to unraid 6 either it is not saving logs to flash when restarting syslogd or after that time there arent any syslogd restarts The only thing I know of that saves syslogs to the /boot/logs folder is the Powerdown plugin. I assume you were running it previously, and haven't installed it in v6.
Archived
This topic is now archived and is closed to further replies.