From: mru@users.sourceforge.net (Måns Rullgård)
To: alsa-devel@lists.sourceforge.net
Cc: linux-kernel@vger.kernel.org
Subject: Re: ALSA timer and 2.6.0-test1 panic
Date: Wed, 16 Jul 2003 14:16:32 +0200 [thread overview]
Message-ID: <yw1x3ch6650f.fsf@users.sourceforge.net> (raw)
In-Reply-To: yw1xlluyln01.fsf@users.sourceforge.net
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:
> [<c0118408>] schedule+0x3ab/0x3b0
> [<c0123190>] schedule_timeout+0x5f/0xb3
> [<d08fffb6>] snd_timer_user_poll+0x2a/0x41 [snd_timer]
> [<c0123128>] process_timeout+0x0/0x9
> [<c0160aa7>] do_poll+0xa1/0xc0
> [<c0160c62>] sys_poll+0x19c/0x28e
> [<c0160035>] __pollwait+0x0/0xc6
> [<c010911b>] syscall_call+0x7/0xb
>
> bad: scheduling while atomic!
> Call Trace:
> [<c0118408>] schedule+0x3ab/0x3b0
> [<c014ed0e>] sys_read+0x61/0x63
> [<c0109142>] work_resched+0x5/0x16
>
> bad: scheduling while atomic!
> Call Trace:
> [<c0118408>] schedule+0x3ab/0x3b0
> [<c014ed0e>] sys_read+0x61/0x63
> [<c0109142>] 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
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
WARNING: multiple messages have this Message-ID (diff)
From: mru@users.sourceforge.net (Måns Rullgård)
To: linux-kernel@vger.kernel.org
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ALSA timer and 2.6.0-test1 panic
Date: Wed, 16 Jul 2003 14:16:32 +0200 [thread overview]
Message-ID: <yw1x3ch6650f.fsf@users.sourceforge.net> (raw)
In-Reply-To: yw1xlluyln01.fsf@users.sourceforge.net
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:
> [<c0118408>] schedule+0x3ab/0x3b0
> [<c0123190>] schedule_timeout+0x5f/0xb3
> [<d08fffb6>] snd_timer_user_poll+0x2a/0x41 [snd_timer]
> [<c0123128>] process_timeout+0x0/0x9
> [<c0160aa7>] do_poll+0xa1/0xc0
> [<c0160c62>] sys_poll+0x19c/0x28e
> [<c0160035>] __pollwait+0x0/0xc6
> [<c010911b>] syscall_call+0x7/0xb
>
> bad: scheduling while atomic!
> Call Trace:
> [<c0118408>] schedule+0x3ab/0x3b0
> [<c014ed0e>] sys_read+0x61/0x63
> [<c0109142>] work_resched+0x5/0x16
>
> bad: scheduling while atomic!
> Call Trace:
> [<c0118408>] schedule+0x3ab/0x3b0
> [<c014ed0e>] sys_read+0x61/0x63
> [<c0109142>] 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
next prev parent reply other threads:[~2003-07-16 12:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-16 11:38 ALSA timer and 2.6.0-test1 panic Måns Rullgård
2003-07-16 11:38 ` Måns Rullgård
2003-07-16 12:16 ` Måns Rullgård [this message]
2003-07-16 12:16 ` Måns Rullgård
2003-07-17 10:17 ` Takashi Iwai
2003-07-17 10:17 ` [Alsa-devel] " Takashi Iwai
2003-07-17 12:06 ` Måns Rullgård
2003-07-17 12:06 ` Måns Rullgård
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yw1x3ch6650f.fsf@users.sourceforge.net \
--to=mru@users.sourceforge.net \
--cc=alsa-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.