Andi Kleen wrote:
> Hmm, are you sure? Can you double check? With the latest tree?
>
> I could reproduce the problem and my change fixed the problem for me.
>
Hm. Me too. I just booted 2.6.21-rc7-ff-paravirt, and it seems fine.
J
-
To unsubscribe from this list: send the line
Andi Kleen wrote:
Hmm, are you sure? Can you double check? With the latest tree?
I could reproduce the problem and my change fixed the problem for me.
Hm. Me too. I just booted 2.6.21-rc7-ff-paravirt, and it seems fine.
J
-
To unsubscribe from this list: send the line unsubscribe
On Saturday 14 April 2007 23:12:25 Jeremy Fitzhardinge wrote:
> Andi Kleen wrote:
> > Fixed now. The latest sched-clock was leaking preempt counts during
> > cpu frequency changes.
> >
>
> No, that didn't help. I think its cpufreq:
Hmm, are you sure? Can you double check? With the latest
On Saturday 14 April 2007 23:12:25 Jeremy Fitzhardinge wrote:
Andi Kleen wrote:
Fixed now. The latest sched-clock was leaking preempt counts during
cpu frequency changes.
No, that didn't help. I think its cpufreq:
Hmm, are you sure? Can you double check? With the latest tree?
I
Andi Kleen wrote:
> Fixed now. The latest sched-clock was leaking preempt counts during
> cpu frequency changes.
>
No, that didn't help. I think its cpufreq:
Apr 14 13:58:29 localhost kernel: BUG: scheduling while atomic:
swapper/0x0002/1
Apr 14 13:58:29 localhost kernel: 2 locks held
On Saturday 14 April 2007 08:20:50 Jeremy Fitzhardinge wrote:
> I'm seeing this:
>
> Apr 13 21:55:34 localhost kernel: BUG: sleeping function called from invalid
> context at kernel/sched.c:3643
Fixed now. The latest sched-clock was leaking preempt counts during
cpu frequency changes.
-Andi
-
On Saturday 14 April 2007 08:20:50 Jeremy Fitzhardinge wrote:
I'm seeing this:
Apr 13 21:55:34 localhost kernel: BUG: sleeping function called from invalid
context at kernel/sched.c:3643
Fixed now. The latest sched-clock was leaking preempt counts during
cpu frequency changes.
-Andi
-
To
Andi Kleen wrote:
Fixed now. The latest sched-clock was leaking preempt counts during
cpu frequency changes.
No, that didn't help. I think its cpufreq:
Apr 14 13:58:29 localhost kernel: BUG: scheduling while atomic:
swapper/0x0002/1
Apr 14 13:58:29 localhost kernel: 2 locks held by
8 matches
Mail list logo