Re: Linux 2.6.16-rc3

[Andrew Morton]

Andrew Morton <akpm@xxxxxxxx> wrote:
>
> Avuton Olrich <avuton@xxxxxxxxx> wrote:
> >
> > I should have realized that would happen, hopefully here's a better
> >  one. Please let me know anything I can do to help.
> > 
> >  http://68.111.224.150:8080/~sbh/P1010031.JPG
> 
> Thanks.  Yes, it does look like the same bug.

argh.   The fix for this oops is still languishing in David's tree.


--- a/arch/i386/kernel/timers/timer_tsc.c
+++ b/arch/i386/kernel/timers/timer_tsc.c
@@ -272,6 +272,10 @@ time_cpufreq_notifier(struct notifier_bl
 	if (val != CPUFREQ_RESUMECHANGE)
 		write_seqlock_irq(&xtime_lock);
 	if (!ref_freq) {
+		if (!freq->old){
+			ref_freq = freq->new;
+			goto end;
+		}
 		ref_freq = freq->old;
 		loops_per_jiffy_ref = cpu_data[freq->cpu].loops_per_jiffy;
 #ifndef CONFIG_SMP
@@ -297,6 +301,7 @@ time_cpufreq_notifier(struct notifier_bl
 #endif
 	}
 
+end:
 	if (val != CPUFREQ_RESUMECHANGE)
 		write_sequnlock_irq(&xtime_lock);
 

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