User: Password:
|
|
Subscribe / Log in / New account

KS2009: Regressions

KS2009: Regressions

Posted Oct 24, 2009 11:19 UTC (Sat) by nix (subscriber, #2304)
In reply to: KS2009: Regressions by jmspeex
Parent article: KS2009: Regressions

That's when you report the bugs :))) I've kept some machines working for a
decade and more simply by reporting bugs when their old hardware breaks.
The only machine I've ever given up on was a box with an ancient Promise
ISA disk controller, which suddenly broke in 2.4.x versus 2.2.x. Of course
this was before git and bisection: these days I could bisect to find the
faulty commit and report it, but in those days I was pretty stuffed.


(Log in to post comments)

KS2009: Regressions

Posted Oct 24, 2009 18:01 UTC (Sat) by jmspeex (subscriber, #51639) [Link]

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.


Copyright © 2017, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds