Andrew Morton wrote:
On Tue, 24 Apr 2007 13:00:49 -0700 Jeremy Fitzhardinge [EMAIL PROTECTED]
wrote:
Andrew Morton wrote:
Well, it _is_ mysterious.
Did you try to locate the code which failed? I got lost in macros and
include files, and gave up very very easily. Stop hiding,
Andrew Morton wrote:
It's weird. And I don't think the locking selftest code calls
sched_clock() (or any other time-related thing) at all, does it?
I guess it ends up going through the scheduler, which does use it.
But... shrug
J
___
On Tue, 2007-04-24 at 22:59 +0200, Ingo Molnar wrote:
* Daniel Walker [EMAIL PROTECTED] wrote:
On Tue, 2007-04-24 at 13:24 -0700, Jeremy Fitzhardinge wrote:
And sched_clock's use of local_irq_save/restore appears to be absolutely
correct, so I think it must be triggering a bug in
On Tuesday 24 April 2007 22:52:27 Daniel Walker wrote:
On Tue, 2007-04-24 at 13:24 -0700, Jeremy Fitzhardinge wrote:
And sched_clock's use of local_irq_save/restore appears to be absolutely
correct, so I think it must be triggering a bug in either the self-tests
or lockdep itself.
Why
On Tue, 2007-04-24 at 23:20 +0200, Andi Kleen wrote:
On Tuesday 24 April 2007 22:52:27 Daniel Walker wrote:
On Tue, 2007-04-24 at 13:24 -0700, Jeremy Fitzhardinge wrote:
And sched_clock's use of local_irq_save/restore appears to be absolutely
correct, so I think it must be triggering a
