There are well meaning comments on this bug, try this or that, and this worked for me, but there's an underlying problem here. Ubuntu don't seem to have a mechanism for getting users to gather data on a kernel bug.
The result is we're left on our own. There's plenty of people suffering on here who would be willing to donate their time but don't have the skill and there's no technical solution to help them. At one point, there was talk of using kexec on a panicking kernel to switch to a second kernel and record the state of the first. https://wiki.ubuntu.com/LinuxKernelCrashDumpSpec Perhaps the kernel is panicking some of the time and this would be useful. Or if it's getting stuck somewhere without panicking, how can we help debug that? Is there some kind of trace we can enable? Even at the cost of performance? At the moment we just turn up and say it froze, describe the hardware, and wait. Others turn up and do the same. The light at the end of the tunnel was 8.04 after a six month wait. Well, that's here and the problems remain. I don't mean to gripe, and I'm aware there's a lot of volunteer effort behind Ubuntu for which I'm grateful, but the lack of mechanism for debugging not just this bug, but this *kind* of bug needs raising at a higher level. -- gutsy amd64 freeze crash lockup https://bugs.launchpad.net/bugs/157777 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
