It really looks like this bug report is actually a multiple-cause, similar-symptom report, which leads to mixed comments. This makes it impossible for the devs to track all the possible causes, as those have to be pinpointed and fixed one by one. I am too for everybody opening their own bug report. Having multiple bugs mixed in the same report is useless for the developers. It is actually more useful to mark multiple bugs as duplicates of one another; this way, different causes would still be tracked separately.
For instance, my crash-like problem turned out to be an multiple-minutes freeze but my system eventually came back always. I solved it by using 2.6.29 from mainline. So far, I haven't seen any comments of somebody experiencing the exact same-cause symptom.
At KeithR and everybody else:
It really looks like this bug report is actually a multiple-cause, similar-symptom report, which leads to mixed comments. This makes it impossible for the devs to track all the possible causes, as those have to be pinpointed and fixed one by one. I am too for everybody opening their own bug report. Having multiple bugs mixed in the same report is useless for the developers. It is actually more useful to mark multiple bugs as duplicates of one another; this way, different causes would still be tracked separately.
For instance, my crash-like problem turned out to be an multiple-minutes freeze but my system eventually came back always. I solved it by using 2.6.29 from mainline. So far, I haven't seen any comments of somebody experiencing the exact same-cause symptom.