Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Sun, 22 Sep 2002 14:25:36 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Sun, 22 Sep 2002 14:25:36 -0400 Received: from svr-ganmtc-appserv-mgmt.ncf.coxexpress.com ([24.136.46.5]:16144 "EHLO svr-ganmtc-appserv-mgmt.ncf.coxexpress.com") by vger.kernel.org with ESMTP id ; Sun, 22 Sep 2002 14:25:36 -0400 Subject: Re: 2.5.38 scheduling oops? at boot From: Robert Love To: scott781@attbi.com Cc: linux-kernel@vger.kernel.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Mailer: Ximian Evolution 1.0.8 Date: 22 Sep 2002 14:30:45 -0400 Message-Id: <1032719445.10108.988.camel@phantasy> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1639 Lines: 41 On Sun, 2002-09-22 at 09:04, Scott M. Hoffman wrote: > I booted into 2.5.38 on a dual amd duron system using profile=2 on > command line, and the system seemed a bit sluggish just to get bash to > complete a filename in /proc. I found the attached oops after these > messages: > Starting migration thread for cpu 1 > bad: Scheduling while atomic! > ... > Trace; c01186ed > Trace; c0118d9c > Trace; c0118b30 > Trace; c0118b30 > Trace; c011a2c5 > Trace; c011a33e > Trace; c011a2f0 > Trace; c0106f0d > Trace; c01186ed > Trace; c0118d9c > Trace; c0118b30 > Trace; c0118b30 > Trace; c011a2c5 > Trace; c012274f > Trace; c0122700 > Trace; c0106f0d This particular occurrence is known; thanks. The startup of the migration_threads calls set_cpus_allowed(), and set_cpus_allowed() sleeps while disabling preemption. It will not hurt anything, but it needs to be fixed. Before that, I need to find out why set_cpus_allowed() dies without the preempt_disable() in there. 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/