![]() | |||||||||||||
Messages in this thread |
On Mon, 27 Mar 2006 20:27:19 EST, Lee Revell said: > On Mon, 2006-03-27 at 18:46 -0500, Greg Lee wrote: > > I have also tried a number of other kernels and the problem exists all > > the way to 2.6.15.6 > > but is fixed in 2.6.16, so I am going to git-bisect 2.6.15.6 to > > 2.6.16, but I thought I > > would get this message out now in case someone has an inkling of what > > the problem is. > > If it's fixed in 2.6.16, what's the problem? It's not as if we can go > back and fix those old kernels... I may be misreading Greg's concern, but I got the feeling that he's worried that 2.6.16 isn't *really* fixed, but that something is just papering over the driver's innate displeasure with HZ==250 (and thus it's likely that in .17 or .18 or whenever, some *other* patch will make it re-manifest). And we've seen *enough* bugs that only manifest in even or odd or divisible-by-7.48 kernels that we know that "it works in 2.6.16" is vastly different than being able to point at a changeset (or even a stream of fixes) and say "fixed by that" or "probably went away when this stream of patches totally reworked the code". [unhandled content-type:application/pgp-signature] | ||||||||||||
| Last update: 2006-03-28 05:40 [W:2.922 / U:0.010 seconds] ©2003-2008 Jasper Spaans | |||||||||||||