Brandon: err, yes. Regardless of the driver/hw, if it's a hard hang in the kernel driver then it really behaves the same way. That's why it's really annoying to see a ton of me-too's in bugs that have nothing to do with their setup (like on bug 993187)...
Grant: if you did the research, you'd notice that those are already included in upstream 3.2.x. pep: 'black screen on resume' is most likely bug 966744 Felix (or anyone else still seeing freezes): then file a new bug, and better yet, try to bisect which upstream kernel (rc-) release fixed it. It's really easy by using the 'mainline kernel ppa'. I don't use Chromium myself, so if it's a way to repro the other freeze, then it should be quite simple to find the _first_ release that works ok. Note that if it requires 3.5 then the commit(s) is(/are) likely to not get backported, since it had some rewrites for IVB that are too risky to be included. And there will be a full 3.5 (or 3.6) backport anyway, fully supported after 12.10 is released. I really hope someone would open a new bug about the other freezer, and just add a pointer here so people can discuss the progress there, not here. now back on vacation mode -> -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/999910 Title: [IVB]12.04 64 bit System freezes (mouse, keyboard) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/999910/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
