Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sat, 24 Aug 2002 13:57:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sat, 24 Aug 2002 13:57:10 -0400 Received: from p50887F28.dip.t-dialin.net ([80.136.127.40]:1189 "EHLO hawkeye.luckynet.adm") by vger.kernel.org with ESMTP id ; Sat, 24 Aug 2002 13:57:09 -0400 Date: Sat, 24 Aug 2002 12:01:04 -0600 (MDT) From: Thunder from the hill X-X-Sender: thunder@hawkeye.luckynet.adm To: Robert Love cc: Arador , , Linux Kernel Mailing List , Subject: Re: Preempt note in the logs In-Reply-To: <1030211284.1935.4991.camel@phantasy> Message-ID: X-Location: Potsdam-Babelsberg; Germany MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 953 Lines: 26 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/