NVIDIA has already identified/acknowledged that there is a regression in the 100.14.11 & 100.14.19 drivers for G72 based cards (7300 Go, GS...) on certain systems: http://www.nvnews.net/vbulletin/showpost.php?p=1399253&postcount=36
Note that most of the time, when using 100.14.11/19, the freeze is hard enough that you will be unable to switch to a console, or ssh to the box. You may however be able to use the magic keys to cleanly sync/unmount/reboot the box. This link<http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=blob;f=Documentation/networking/netconsole.txt;h=1caa6c734691bc8bc2d14493065ae6f08613f5e6;hb=7dcca30a32aadb0520417521b0c44f42d09fe05c>will help you setup a netconsole, if you have a second box, and will help capturing a stack trace of the kernel if/when it hangs. If you do want to use the 100.14.11/19 drivers on a dual core systems and avoid these freezes, you either will need to disable Desktop effects, or boot with maxcpus=1 as a kernel option. This will disable your second core. -- Random NVidia Proprietary Driver Lynches / Lock-Ups https://bugs.launchpad.net/bugs/145112 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
