Messages in this thread |  | | Date | Sat, 24 Aug 2002 12:01:04 -0600 (MDT) | From | Thunder from the hill <> | Subject | Re: Preempt note in the logs |
| |
Hi,
On 24 Aug 2002, Robert Love wrote: > It is caused by any mismatched locking - it is a good debugging check > regardless of preemption.
Do you think it's useful to temporarily put a lock counter into struct task (TEMPORARILY, Linus, temporarily!) and check that as well? Maybe that will point us something.
Or we should extend that whole crap a bit so we could see exactly what caused the preemption count to rise. I don't know if we can do that, but we can try doing that.
Thunder -- --./../...-/. -.--/---/..-/.-./..././.-../..-. .---/..-/.../- .- --/../-./..-/-/./--..-- ../.----./.-../.-.. --./../...-/. -.--/---/..- .- -/---/--/---/.-./.-./---/.--/.-.-.- --./.-/-.../.-./.././.-../.-.-.-
- 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/
|  |