For the first laptop on which suspend got broken I was able to pinpoint that the problem happened between 2.6.12-rc5-git5 and 2.6.12-rc5-git6 after several months of testing (the problem occurred only after several days and it was my main work machine). This was by using the git "pre-releases" on kernel.org. After finding that, the response I got was simply "you need to learn git to further bisect otherwise we're not even looking at it" (I had already bisected to within one *day* of patches). At this point I just gave up. I *do* still report bugs for projects that treat reports better (gcc is one that comes to mind), but I'm no longer bothering with kernel bugs unless it *really* annoys me or there's a developer committed to putting some time into finding the problem instead of forever asking me to do more work without even looking at the code.