Re: first bisection results in -mm3 [was: Re: 2.6.15-mm2: reiser3 oops on suspend and more (bonus oops shot!)]

[john stultz <johnstul@us.ibm.com>]

On Wed, 2006-01-18 at 11:47 +0100, Mattia Dongili wrote:
> On Tue, January 17, 2006 11:49 pm, Mattia Dongili said:
> [...]
> > the stall is still there, tomorrow I'll reapply your debug-patch and
> > report the full dmesg (with the finished_booting-hack enabled).
> 
> Full dmesg attached.
> Stalls happened between in the 16.39-16.55 interval, in 16.70-16.96 and
> 17.89-18.64. They were all much longer than stated in the log timestamp
> (I'd say ~10:1 ratio).	
> 
> Sorry again for my previous false notice about the bug being solved...

Hey Mattia, 
	Sorry I've been so quiet recently, I'm still working on this one.  The
difficult spot is that if the cpufreq notification driver is a module,
then there will always be a window between the point at which we start
using the TSC to the point where we find out that the TSC is changing
frequency. Not sure what to do here just yet.

Although I'm curious: Did the recent changes in 2.6.16-rc1-mm2 had any
effect on this issue?

thanks
-john

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/