Elod is correct. It is marked as Fix Released for Intrepid because he reports that the crash doesn't occur for kernel version > 2.6.25 on his machine. As he is the original reporter, then this means that his bug is fixed in Intrepid. It won't be fixed for Hardy unless we can determine exactly what commit fixed the problem which caused Elod's lock-up.
Other people experiencing lock-ups should open their own individual bug reports containing all the relevant information as per the kernel team bug policy: https://wiki.ubuntu.com/KernelTeamBugPolicies unless they are absolutely sure that their lock-up is caused by the same problem which caused the lock-ups for Elod. You should contain a brief description of your hardware in the bug title (not just kernel 2.6.24 lockup or whatever, otherwise you'll end up with another bug report that is hijacked by lots of other people). Remember, just because you're all experiencing the same symptom doesn't mean that it is the same bug. A lock-up or crash is a fairly generic symptom. Your lock-ups could all have different causes, and without doing detailed debugging, it is not possible to determine what the cause is. Adding "me too's" here just confuses things, makes the bug report difficult to follow and makes it less and less likely that your problem will get fixed. Multiple bug reports specific to a single hardware set-up are much easier to follow than one large bug report with umpteen permutations of hardware configuration. -- Linux kernel 2.6.24-12 lockup https://bugs.launchpad.net/bugs/204996 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
