tags 490694 - moreinfo found 490694 linux-2.6/2.6.25-6 found 490694 linux-2.6/2.6.26-11 tags 490694 + upstream # 2.6.29-rc1, but close enough found 490694 linux-2.6/2.6.28-1 quit
Jeffrey Green wrote: >>> On Feb 16, 2012, at 12:37 PM, Jonathan Nieder wrote: >>>> Jeffrey Green wrote: >>>>> One fact is, it did break, it was graphics card related, and >>>>> modifying the kermel "fixed" it. >>>> >>>> Was your fix applied upstream, or was it a local workaround? [...] > Nope. It was purely local at that point. I was still exploring linux > at that point (when I had the time), Somewhere around Jan of 2000 > was my first connection. Lots of Unix experience but no linux. > Consequently, I wasn't really plugged into all of the various > developer mechanisms that existed. I should have known about them > but either didn't have the time or inclination (or some combo of > both) to work my way through the muck. > > I'm such a pack rat that I could probably track down a vestige of > those kernels although the times when I needed to do mass hard disk > transfers or rebuilds may foil me in that attempt. If you do remember anything about that patch, it could certainly be an interesting clue. Anyway, I'll send any further questions to the upstream report[1]. It will be nice if we can figure this one out. Thanks for the quick feedback. Jonathan [1] https://bugzilla.kernel.org/show_bug.cgi?id=12436 -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120220202124.GG18695@burratino
