Jul 12 10:04:42 backup kernel: ACPI Warning: SystemIO range 0x0000000000000400-0x000000000000041F conflicts with OpRegion 0x0000000000000400-0x000000000000040
F (\SMRG) (20150410/utaddress-254)
Jul 12 10:04:42 backup kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 12 10:04:42 backup kernel: shpchp: Standard Hot Plug PCI Controller Driver version: 0.4
Jul 12 10:04:42 backup kernel: ACPI Warning: SystemIO range 0x00000000000004B0-0x00000000000004BF conflicts with OpRegion 0x0000000000000480-0x00000000000004B
F (\GPS0) (20150410/utaddress-254)
Jul 12 10:04:42 backup kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Jul 12 10:04:42 backup kernel: ACPI Warning: SystemIO range 0x0000000000000480-0x00000000000004AF conflicts with OpRegion 0x0000000000000480-0x00000000000004B
F (\GPS0) (20150410/utaddress-254)
Jul 12 10:04:42 backup kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
So I did some reading / googling and found that ACPI can cause issues on older boards.
Once I put acpi=off in my grub cmdline linux the problem seems to have gone away.
Edited
/etc/default/grub
from
GRUB_CMDLINE_LINUX="crashkernel=auto"
to
GRUB_CMDLINE_LINUX="crashkernel=auto acpi=off"
Are @sirhcjw strikes again.
Yes older systems can be a real pain and as Rockstor uses pretty new kernels they may start to become unworkable. For instance I heard the other day, though I don’t know if it is true or not, that no systemd developers are using spinning rust drives on /; fancy that. And acpi is very well established and sometimes very poorly implemented, especially on older motherboards. You could also try a firmware upgrade on your motherboard as they often contain acpi fixes. But again that in itself is a risky business so maybe if you are up and running then the “don’t fix what isn’t currently broken” idea might be the way to go. However acpi is rather assumed these days so there may be some potentially strange behaviour, disabling in the bios as many things as you can would also help to simplify things; ie sound card etc.
This may be a bit verbose but as I look at this maybe could be the basis of a system information page in Rockstor and you could have a collect hardware info and send to Rockstor button so you guys could start so compile a known working hardware list.
@sirhcjw we have had another recent post relating to ACPI and I quoted your original findings here in that forum thread and articulated how I thought it might relate. When I saw that you had effectively reverted your settings to full ACPI on I thought I’d wait and see how you got on. Drawing the two together now, though they are only tangentially related, I suggest you turn off “ACPI 2.0 support” in bios but leave on “ACPI APIC suport” as that combination found by @KarstenV from your original findings allowed all their CPU cores to be enabled whilst they were still able to install. But of course you may not have those options in your BIOS. Their situation was a little less instability and a little more “wont install” specifically around the grub area. I detail there what I think was happening but of course that may all be wrong. But their finding was that disabling just ACPI 2.0 Support allowed them to install past the final grub which previous to this BIOS adjustment was failing with unknown error. I surmised this to be similar to your mostly hidden timeout issue. Give that post a read and see if it helps, thanks for keeping us all posted as these kinds of issues are a real pain and if we could work out a blanket guide that would be great.
Tweaking just BIOS settings is also preferred as it’s less fiddly than kernel boot options but we may still need them in some circumstances of course.
Nice idea on the hardware database by the way, I’m just not quite sure how we would establish if the reports were from “known good” hardware as many settings event on the same board can affect stability. There is definately something to it though. Or maybe we should just reference CentOS certified hardware as that is essentially what Rockstor is linux wise at least.