Comment 687 for bug 88746

(In reply to comment #86)
> (In reply to comment #84)
> > I find the decision to close this bug quick and unfounded.
> The bug report was opened more than a year ago. How can you call that
> "quick"?
I say quick as in quick-thinking.

> Evidently you did not receive the message I sent to you in response to
> comment #67. The gist of it was that this is not a single bug.
I did receive it, but I was just starting out with linux and couldn't really deal with kernel hacking, I needed to get going with my work.
> Most of the bug reports you cited were either non-reproducible or caused by
> hardware problems.
> In others the reporters have stopped responding, making it impossible to find
> out what was wrong.
That's what I call hard to track and elusive. Does that mean there's no bug? No. If there's a bug, even if hard to track, I think there should be an entry for it. All this talk about keeping a log only for reproducible bugs does not make sense to me, and only reflect a dislike for unreproducible bug.

> So far there has been extremely little indication that errors in the software
> are responsible for these resets.
How do you explain other OS had no issue in the same configuration?

> Even if it is true that the software is
> partly to blame, we have no way to fix it unless we can find out exactly
> where
> the errors are. Errors get fixed when they are tracked down, and your rant
> doesn't contribute towards tracking down any of these problems.
Closing this bug doesn't contribute in nailing it down. That's what happened for the last two years: it gets reported and then closed, it reappers somewhere else but the OP quickly disappears because this bug is a showstopper (you can't work with it).

Anyway, there's no need to consider this a rant and get personal about it. I appreciate a lot all the efforts from the so many people in getting GNU/Linux to where it is now. Also, bear in mind that in the past 4 years I really wanted to get away from M$. This bug kept me from making the move. Only recently did I try again, got this bug again, but did not want to get discouraged because of it. So I'm sorry for making so much noise, I'm tired of this bug as much as you are, but I don't want to forget about it.

Is the fix you talked about in 2.6.30? If so then it should be in my arch release kernel. I'll rewire my devices (in order to reproduce the bug) and report back in about a week when I have more time to play.