I think I may have found the cause: enabling AMD Cool&Quiet (powernowd) when the internal graphics card is used. (Why Shuttle would design an AMD-based motherboard with an IGP that crashes when these two features are actually used? Good question.)
I said above that I never saw this crash in Windows, but that's because I had installed the AMD CPU drivers but not actually turned on C&Q (which on Windows is done through Power Options). Once I did turn it on, I saw the crash happen just as it did under Ubuntu and connected the dots with other reports on Shuttle's web forums. I then turned off powernowd init script and haven't had any crashes since. (Gentoo must have had it disabled by default.) Therefore, I believe this bug can be closed. Once somebody sees this, that is. In six months that it's been open, there hasn't been a single comment by Ubuntu's team, other than changing the importance from 'unconfirmed' to 'medium'. I can appreciate the difficulty of keeping up with the increase in reports that comes with Ubuntu's growing popularity, but you should keep in mind that one of the surest ways for a project to look amateurish and turn off its users is to have slow and unresponsive bug triage. I hope you can take a look at Mozilla's handling of incoming bugs, all of which get an initial response very quickly even if actually fixing them takes much longer. -- System freeze with white screen https://launchpad.net/bugs/46470 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
