Hi,
I told you I think that in regard of that machine having a bfs kernel or not is prabably not very important. I suppose if your kernel is non bfs, and the machine works ok with it, leave it.
The PSU you are showing has:
4 peripheral, 1 floppy drive and 2 S-ATA connectors
Can it connect to IDE hard drives as well ? I suppose your hard drives are of the IDE type ?
about the message 'unable to locate IOAPIC for GSI...' i have set currently the acpi back to 'on'. just to see how this goes.
IO usually means Input Output, and apic is not the same thing as acpi.
APIC :
http://en.wikipedia.org/wiki/Advanced_Programmable_Interrupt_ControllerACPI :
http://en.wikipedia.org/wiki/Advanced_Configuration_and_Power_InterfaceLAPIC : Local APIC :
http://en.wikipedia.org/wiki/LAPIC#Local_APICjust to give you an idea... I have not gone very deep in these definitions, just enough to know they must not be confused, as having each a different, specific function.
i can make choices for; linux
linux-non fb
failsafe
2.6.38.8-pclos3.bfs
2.6.37.4-pclos1
If you have booted to 2.6.37.4-pclos1 once, then the first default choice boots to 2.6.37.4-pclos1 each time after. You can check what kernel you are running with the command "uname -a", or "uname -r" in a console as simple user.
i had seen that website at fedora aswell but found later on a site that gave suggestions what you could do to 'fix' it. options were trying; noapic, noacpi and acpi=off
noacpi and acpi=off means the same thing.
I tend to think that if the people at Fedora consider the message as harmless, (and in that one case, the machine of the guy who was posting was working well in spite of the message), then the message is in fact harmless. Whereas the options you found on another place are exactly the one I gave you to try at the beginning, (almost : it was noapic nolapic... ) which didn't help stopping the freezes.
What seems to have calmed them down so far is removing one hard drive, and booting to an older kernel. What happens with zram : I am not sure at all that zram would bother in any way. Testing with and without, keeping the same 2.6.37.4-pclos1 kernel and running with just one hard drive plugged in, could be interesting, because the purpose of having the zram activated is enhancing the potential memory. You can use your applications as if you had a bit more RAM, and this makes the use more comfortable on machines having low memory, embedded systems, and so on...