Based on a comment from Robert Hooker downstream, I did some testing on the newest -rc5 based Ubuntu kernel (2.6.35-8.13). With this kernel, xorg does not fail, but I still get the kernel oops.
* Using the (invalid) kernel parameter vesafb=fubar did not change anything.
* With the Grub parameter 'set gfxpayload=text' instead of 'set gfxpayload=keep', I was not able to reproduce the oops.
This is apparently a recent change of defaults in Ubuntu [1]. There are some more comments on this issue on an Ubuntu bug report [2].
Based on a comment from Robert Hooker downstream, I did some testing on the newest -rc5 based Ubuntu kernel (2.6.35-8.13). With this kernel, xorg does not fail, but I still get the kernel oops.
* Using the (invalid) kernel parameter vesafb=fubar did not change anything.
* With the Grub parameter 'set gfxpayload=text' instead of 'set gfxpayload=keep', I was not able to reproduce the oops.
This is apparently a recent change of defaults in Ubuntu [1]. There are some more comments on this issue on an Ubuntu bug report [2].
[1]: https:/ /lists. ubuntu. com/archives/ ubuntu- devel/2010- July/030995. html /bugs.launchpad .net/ubuntu/ +source/ linux/+ bug/606244
[2]: https:/