3.2.0-15 would be a version even prior Precise release. I cannot even find a tag with that version. And for a 3.5.0 version number it would also be pre-release (but more likely possible).
I got no problems booting my test machine with that kernel, but that is AMD based. So its not quite a proof.
That 00228000 address from the IO space mapping error looks a bit related to the border of the last two E820 ranges. There is also this warning about MTRR ranges not covering all memory and ram being clamped down in some way... Seems all pointing to some odd memory setup issue. Maybe you could try to add "dom0_mem=512M,max:512M" as a test...
3.2.0-15 would be a version even prior Precise release. I cannot even find a tag with that version. And for a 3.5.0 version number it would also be pre-release (but more likely possible).
I got no problems booting my test machine with that kernel, but that is AMD based. So its not quite a proof.
That 00228000 address from the IO space mapping error looks a bit related to the border of the last two E820 ranges. There is also this warning about MTRR ranges not covering all memory and ram being clamped down in some way... Seems all pointing to some odd memory setup issue. Maybe you could try to add "dom0_mem= 512M,max: 512M" as a test...