From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S270136AbTGPMGb (ORCPT ); Wed, 16 Jul 2003 08:06:31 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S270487AbTGPMGb (ORCPT ); Wed, 16 Jul 2003 08:06:31 -0400 Received: from main.gmane.org ([80.91.224.249]:51399 "EHLO main.gmane.org") by vger.kernel.org with ESMTP id S270136AbTGPMGa (ORCPT ); Wed, 16 Jul 2003 08:06:30 -0400 X-Injected-Via-Gmane: http://gmane.org/ To: linux-kernel@vger.kernel.org From: mru@users.sourceforge.net (=?iso-8859-1?q?M=E5ns_Rullg=E5rd?=) Subject: Re: ALSA timer and 2.6.0-test1 panic Date: Wed, 16 Jul 2003 14:16:32 +0200 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@main.gmane.org User-Agent: Gnus/5.1002 (Gnus v5.10.2) XEmacs/21.4 (Rational FORTRAN, linux) Cancel-Lock: sha1:OB6vjb66eqP9rpOOn0nJG8UOtIg= Cc: alsa-devel@lists.sourceforge.net Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org mru@users.sourceforge.net (Måns Rullgård) writes: > I get thousands of these messages when using the ALSA timer in kernel > 2.6.0-test1: > > bad: scheduling while atomic! > Call Trace: > [] schedule+0x3ab/0x3b0 > [] schedule_timeout+0x5f/0xb3 > [] snd_timer_user_poll+0x2a/0x41 [snd_timer] > [] process_timeout+0x0/0x9 > [] do_poll+0xa1/0xc0 > [] sys_poll+0x19c/0x28e > [] __pollwait+0x0/0xc6 > [] syscall_call+0x7/0xb > > bad: scheduling while atomic! > Call Trace: > [] schedule+0x3ab/0x3b0 > [] sys_read+0x61/0x63 > [] work_resched+0x5/0x16 > > bad: scheduling while atomic! > Call Trace: > [] schedule+0x3ab/0x3b0 > [] sys_read+0x61/0x63 > [] work_resched+0x5/0x16 > > Everything works like it should anyhow, until the program stops. At > that time the kernel panics (killing interrupt handler). If I disable the preemptive kernel it works fine. -- Måns Rullgård mru@users.sf.net