Comment 51 for bug 539020

Thanks. It's odd to hear that it breaks totally for you but works for another with the same IGP. I'm nearing despair. However I just found something suspicious in the syslog you attached:
[ 32.198735] VIA Graphics Intergration Chipset framebuffer 2.4 initializing
[ 32.255733] __ratelimit: 3 callbacks suppressed
[ 32.255737] vmap allocation for size 134221824 failed: use vmalloc=<size> to increase size.
[ 32.255742] ioremap failed
[ 32.255770] viafb: probe of 0000:01:00.0 failed with error -12
This means that viafb itself refuses to work as it can't map the framebuffer (128MB, is this correct?). I'm really puzzled how a module that itself refuses to do anything can cause any harm to (escpecially freeze) your machine.
So the best I can suggest as the next step would be to add the boot option "vmalloc=268435456" to reserve 256MB for remapping and see whether the behaviour of 2.6.33 changes, meaning
(a) whether the warning in the syslog vanishes (the different kernel version shouldn't make a difference but you can check if you like)
(b) whether viafb still freezes your PC