I could "solve" this issue by resetting my BIOS (version 1.08) to optimal defaults on my Uniwill 259IA. So reports of a buggy BIOS causing this seem to be right. However, I think it might still be sensible to hardcode some frequency tables into the kernel as a fallback since many people don't even know what a BIOS is and for those who do, a BIOS update still is a very, very scary thing.
I could "solve" this issue by resetting my BIOS (version 1.08) to optimal defaults on my Uniwill 259IA. So reports of a buggy BIOS causing this seem to be right. However, I think it might still be sensible to hardcode some frequency tables into the kernel as a fallback since many people don't even know what a BIOS is and for those who do, a BIOS update still is a very, very scary thing.