Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 10 Apr 2002 13:00:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 10 Apr 2002 13:00:09 -0400 Received: from zero.tech9.net ([209.61.188.187]:31504 "EHLO zero.tech9.net") by vger.kernel.org with ESMTP id ; Wed, 10 Apr 2002 13:00:08 -0400 Subject: Re: 2.5.8-pre3: kernel BUG at usb.c:849! (preempt_count 1) From: Robert Love To: Johannes Erdfelt Cc: Duncan Sands , Kernel List , linux-usb-devel@lists.sourceforge.net In-Reply-To: <20020410114144.N8314@sventech.com> Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.3 Date: 10 Apr 2002 13:00:07 -0400 Message-Id: <1018458007.6524.2.camel@phantasy> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2002-04-10 at 11:41, Johannes Erdfelt wrote: > > <3>error: rmmod[1787] exited with preempt_count 1 > > I don't like the looks of that. That error means a task exited with a nonzero preempt_count, in this case 1. This means a lock was held after exit (or, a lock was never unlocked - e.g. it was dynamic and just deleted, but the lock counting code can't know that). In this case it may just be because the task oopsed while holding the lock and then exited. This may point to the lock being the BKL since it would be trivial to have it reschedule and then die while holding it. While the main point of that error is to point out code that does rude things with preemption, in this case we probably just have another problem and this is another sign of it. Robert Love - 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/