Another data point: It crashed with a YouTube clip running and the last audio sample kept repeating over and over, indicating again that the system isn't completely dead as much as userland processes are blocked.
Once again, is there anything I can do to to help find this? It happens on every single kernel after the last Gutsy one, so it must be something in common with all of them. And one of the main things changed is the scheduler, which to me would make it a prime suspect. Anything I can do at all? If there really isn't, then I am ready to throw in the towel by now, and find a way to downgrade this machine to Gutsy again. Or, if downgrading while keeping my data is not an option, try Redhat or Suse instead; they do have their own kernel builds which may be without this issue. As it is, this machine is almost unuseable, since I have to be constantly prepared for another lockup, and since anything putting a load on the machine increases the chance. The Gutsy kernel doesn't lock up, but suspend doesn't work, and it suffers rather horribly from that excess of kernel events (much worse than when I was actually running Gutsy) which mean I soon have to reboot to get rid of it. I'm happy to keep at this as long as I have any kind of expectation that it will help resolve the issue, but if it doesn't help at all I'd rather have a functional system and give up on Hardy for now. -- Hardy kernel causes overheating https://bugs.launchpad.net/bugs/223081 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
